“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“.

“During a break on the Thursday I took the chance to ask Nancy White a question – “What is a ‘healthy’ community?” In looking at these various orientations it struck me that there must be recognizable ‘patterns,’ say, of a “successful open source community,” that could help us recognize others when we see them. This is exactly right and exactly wrong; as Nancy helped me understand, exactly wrong because it locates the notion of health in some abstract standard outside the community, when the notion of health being put out here is about internal coherence and accord – is the community becoming (or at least striving to be) what it wants to be“.
By Scott Leslie, Northern Voice ‘10: …, May 11th, 2010

Emphasis mine.

2. You should write your own biography, not delegate it to invisible masses on Wikipedia.

3. You should write other people’s biographies, from your point of view. Or at least tell true stories about them, which can be assembled by others into alternate views.

4. Sign your name to all your writing. Use your real name, the one on your driver’s license, tax returns, passport, draft card.

5. If you care about a subject, write a definitive piece on it that reflects your point of view,. Don’t settle for a compromise, group-think sanitized version in the form of a Wikipedia page.

Dave Winer, “Corporate media is the problem“, Jan 17th, 2010

If you want better communication, clarify the following:

• Who is the single person who has decision making authority for decision X
• Who should have input into that decision
• Who should be informed when the decision has been made

This sets everyone’s expectations for who needs to know what.  It reduces endless forwarding of fyi material on the hopes someone might need it.

Scott Berkun, “How to stop overcommunication“, Jan 21, 2010

The best of 252,029 bloggers, 223,676 new posts, 327,799 comments, & 54,240,782 words today on WordPress.com.

Those numbers get me far more excited than page views and other “monetization” stats, because these right now front page stats reminds me blogging works.

These stats are about people expressing themselves (writing words) and connecting with other people (commenting).

These are the numbers I look to when I need inspiration.

“Yourself, plus two others. With only two, each person needs to be aware of all the details in case the other person needs to take a break / gets run over by a bus / whatever. With three, the load is spread a bit more easily.”

Boris Mann, thoughts on Passion and Frustration, October 5th, 2009

"Three lemurs eating" by Tambako the Jaguar. CC by-nd. Flickr Hosted.

From starting a company with Boris and Co’s Bootup Labs to being the area experts for your company, you want three of you.

3 is a magic number.

I’ve always just gone with having one backup, but reflecting on it now, I should have two backups in each area.

At first it seems like an incredible amount of redundancy, but someone’s own focuses and work doesn’t go away when they have to fill in for you. You need two backups, two people who can step in to carry your load — each carrying some of your load.

This extends beyond backing you up. This creates a mesh of collaboration,. Having different collaborators (back ups) in different areas leaves no weak links.

Disagreeing about something with your backup? With three there is always a moderator / negotiator / tie breaker.