“Most developers are itching to be a part of their favorite projects. You do not scale, but by giving developers tools and getting out of their way, your project can. So please remember that when issues are reported on your open source project, you should not fix them. I hope this serves you well and would love to hear about your experiences and help any way I can.”
By Wesley Beary in “Less is More published Nov 27, 2011. Hat tip Jake Dahn.
A leader will always lead by being prepared to do the work themselves, but I’m really feeling what @geemus wrote.
It is in the ethos of the WordPress community, and the company, my former employer, Matt Mullenweg formed to support it. Here is my favorite part of the Automattic Creed:
“I will never pass up an opportunity to help out a colleague, and I’ll remember the days before I knew everything.”
I’m excited by the help I’m receiving from my new colleagues at Piston Cloud and the OpenStack community.
Pistoneers are kindred spirits of Automatticians. Before joining the Piston Cloud team I noted automation being a regular theme on “Our Team“.
That’s true to a certain extent but I’m more cynical about it. The founder or main members of a project will still do 99% of the hard work. That has been my experience with my projects unfortunately. Even my calls for Supercache testers on my blog only garnered a few RTs on Twitter and one or two comments. Then people will bitch and complain about broken features (that work fine on my sites) because they weren’t widely tested ..
/rant
PS.Good luck in the new job. You just happened to catch me at a bad moment.