On Tue, Jul 31, 2012 at 10:17:36PM -0500, Michael Ludvig wrote:
> On 01/08/12 06:30, Matt Domsch wrote:
> Hi Matt and everyone who sent me pull requests over the past year or so.
> I'm really sorry for not following up and for ... basically
> ... ignoring your efforts. I know this is not the right way the
> project is meant to be led.
> As it's often the case in the open source world these projects are
> only a hobby for their founders and so was s3cmd my hobby for over 5
> years. Not generating any real income but it was fun and a great
> learning experience. However after such a long time of working on
> s3cmd, bringing it to the masses, making it one of the best products
> in its class (ok, enough bragging :) and seeing the community of
> users and contributors grow I'm afraid I have now became the
> bottleneck slowing the project down instead of being the leader
> pushing it forward. And unfortunately it's not about to improve
> anytime soon - I now have other commitments, family, less free time
> overall and can't spend as much time on s3cmd as the project
Michael: first, let me thank you for your note here. It takes a lot
of courage to start an open source project, and your commitment to
s3tools over the years has helped many many people, myself included.
It takes even more courage to recognize when it's time to pass the
torch to someone else.
> Is there anyone on the list who is keen to step in and assume the
> s3cmd leadership role? Raise your hands! One, two, three leaders /
> maintainers, not a problem :)
> Guys? Girls? Cats? Dogs? Parrots? Matt? Anyone?
While I appreciate thought, I must decline with hopes that a more
long-standing or active contributor can take on the responsiblity.
For my own part, time I've spent on s3tools recently has been out of
necessity in my role as Fedora Mirror Wrangler to create AWS-local
mirrors in each region for the benefit of EC2 users running Fedora or
a distro in the RHEL family. I have my own MirrorManager project
which I've neglected, optimistically thinking "oh, I can just fix this
in s3tools, it won't take much time...". My efforts to merge in the
outstanding patch queue have been quite selfish, hoping to spur you
(or the next maintainer) to merge my patches too, so as Fedora/EPEL
package maintainer for s3tools I don't have to carry my patches there
separately without the blessing of the upstream project, as I do in
the Fedora Infrastructure private repo now.
That said, I hope my merge tree proves to be more than "merge w/o
review and thought", that the next maintainer can benefit from.
Dell | Office of the CTO