Managing an Open Source project - LugRadio

By John Locke on June 5, 2008

LugRadio has a very interesting discussion in their current podcast about the role of a community manager, in creating a vibrant community around an open source project. They came to the conclusion that each project needs a leader that people trust to take the project in the right direction, someone to be a diplomat to resolve issues among people in the community and keep everyone rowing in the same direction, and a strong technical lead to solve the hard problems.

This sounds quite similar to the challenges a small business faces. "The E-Myth Revisited," by Michael Gerber, is essential reading for anyone wanting to start a small business, and some of the same ideas apply to building a successful open source project.

Basically, Gerber says you need to have 3 personalities in your business:

  • The entrepreneur, the person with the vision to drive the business/project forward, always a step ahead working on what's next
  • The manager, somebody to make sure all the work gets done on schedule, delivered on time, and that everybody is working in the same direction with the same priorities
  • The technician, who actually does the work

And small businesses, like open source projects, are almost always started by technicians, people who just know they can do a better job than anybody else, so they set out to do it themselves. The reason why so many businesses fail is because the founders spend all their time building something without setting enough overall direction or managing their cash flow. Sound familiar?

The key to creating both a successful business and an open source project is balancing out these 3 personalities and making sure all are represented to an appropriate degree.

Add new comment

The content of this field is kept private and will not be shown publicly.

Filtered HTML

  • Web page addresses and email addresses turn into links automatically.
  • Allowed HTML tags: <a href hreflang> <em> <strong> <blockquote cite> <cite> <code> <ul type> <ol start type> <li> <dl> <dt> <dd> <h1> <h2 id> <h3 id> <h4 id> <h5 id> <p> <br> <img src alt height width>
  • Lines and paragraphs break automatically.

Drupal Canvas — Block HTML (locked)

  • Allowed HTML tags: <strong> <em> <u> <a href> <p> <br> <ul> <ol> <li>

Drupal Canvas — Inline HTML (locked)

  • Allowed HTML tags: <strong> <em> <u> <a href>

More Like This

Clockworks, gears
🕑Nov 12, 2021 🖋John Locke 💬0

Picking a technology for internal use

The only kinds of proprietary software Freelock actually pays for are development and testing tools – tools we use to actually create our work products, or provide us with access to tools we otherwise can’t support (e.g. testing across a bunch of browsers we don’t have).
Choosing a path
🕑Mar 28, 2021 🖋John Locke 💬0

Picking a technology for a client project

Aside from the technologies we choose to develop expertise in and market prominently, we can support a range of related technologies without much trouble. Given our experience and expertise, this means we’re comfortable in just about anything in PHP. If a client comes to us with an existing platform and want our support with it, we’re happy to provide it.