Partly inspired by Debby Peters' post on Eliminating Loneliness as well as her related 10 Rules for Connecting, here are my set of 10 key points for encouraging participation/connection within open source software communities.
- Software first - a useful, good open source software foundation is a must.
- Recognition is a currency - Acknowledging contributions serves as a rate of exchange for participation.
- Culture is key - community culture should reflect the needs and nature of its primary focus: open source software development.
- Opportunities to succeed - What can be done, how often, before which date all have relevance within the scope of outstanding tasks/duties.
- Incentives still count - can be packaged in a number of shapes and sizes but these remain a must.
- Stickiness rules - if apps can be sticky so can communities...perhaps the best ones are those that make it less confusing to step in and 'get your hands dirty.'
- The art of the give back - Community as an open ended channel through which to perfect this art is a powerful idea.
- Understanding individual motivation - Not everyone can/wants to be a source code committer, understanding what makes other groups consider getting involved is paramount.
- Altruism need not apply - The generalization of the open source software developer as primarily a sort of self-sacrificing idealist is passé. Even if open source boasts several altruistic concepts at its core.
- A marathon pace - building successful communities takes time, seeing how they aren't so easily bought or faked or imitated.
Bravo! Your ten rules are universal. They are so right and not just for the open source community but for all. Thanks for the thought that went into this!
Posted by: Debby Peters | June 20, 2007 at 04:15 AM
Debbie,
Thanks for taking the time to respond...and you're right there's so much that applies across the board, after all group dynamics are group dynamics no matter what.
Alex
Posted by: Alex Fletcher | June 22, 2007 at 08:27 AM