Differences between revisions 8 and 9
Revision 8 as of 2007-05-18 15:34:45
Size: 3552
Editor: RossGardler
Comment: Some external links
Revision 9 as of 2007-05-18 15:42:16
Size: 4866
Editor: RossGardler
Comment: Add content to user community
Deletions are marked like this. Additions are marked like this.
Line 29: Line 29:

Your user community is the one you need to nurture the most. Users are the lifeblood of any project, without them there is no project. However, they provide more than a reason for being, they also provide valuable feedback about whether the project is doing the right thing. You should give your users the opportunity to tell you what the requirements of the project are, which are the most important features to implement, which bugs are the most important and what strategy the project should adopt.

Users are also the best people to support other users. People who work on the code are often too involved to be able to give clear and concise answers about how to do something. However, those who are actually using the code on a day to day basis understand the frustrations of being a new user and have found the simplest way of doing things.

Finally, your users are important because they are your future developers. Their contributions may be in the form of documentation, or they may be in the form of bug features or even new features. If they do not have the skills themselves to implement what they need they may have the financial resources and sufficient desire to seek out a contractor to do the work as a paid employee.

Rule number one of community development is "look after your users".

Having an Open Source license is not enough to bring users and developers to your project. You need an active and supportive community too. This document looks at what makes a successful open source community.

Attracting Community

Supporting Common Interests

Communities have common interests, one way of ensuring that new members become aware of your community, and to ensure existing members keep coming back, is to provide services supporting those common interests. This section describes how you can leverage other sites services to increase the offering to your own community.

Targeted Search Engines

Examples of Targeted Search Engines

Calendars

Your community will undoubtedly be interested in events relating to their interests. Why not maintain a calendar containing these events?

Keeping the Community Informed

There are two types of community member, the user community and the contributor community. Each requires different information, so each requires a different communication channel.

User Community

Your user community is the one you need to nurture the most. Users are the lifeblood of any project, without them there is no project. However, they provide more than a reason for being, they also provide valuable feedback about whether the project is doing the right thing. You should give your users the opportunity to tell you what the requirements of the project are, which are the most important features to implement, which bugs are the most important and what strategy the project should adopt.

Users are also the best people to support other users. People who work on the code are often too involved to be able to give clear and concise answers about how to do something. However, those who are actually using the code on a day to day basis understand the frustrations of being a new user and have found the simplest way of doing things.

Finally, your users are important because they are your future developers. Their contributions may be in the form of documentation, or they may be in the form of bug features or even new features. If they do not have the skills themselves to implement what they need they may have the financial resources and sufficient desire to seek out a contractor to do the work as a paid employee.

Rule number one of community development is "look after your users".

Contributing Community

Version Control Commit Mails

Most version control systems will send an email to a mail list whenever a change is committed. This can create a considerable amount of mail, however, it is a very useful mechanism for keeping your contributors informed. Once you get used to reading them they don't take a great deal of time to process. Also a good way to encourage committers use good commit comments, because people actually see the comments immediately.

My approach is outlined below:

- I use Thunderbird so the [https://addons.mozilla.org/en-US/thunderbird/addon/4268 Colored Diffs] add-on is really useful. It makes reading the emails much easier.

- have filters that separate the commit mails into sensible groups (the subject is always the same form, so I filter on the module name, in this case "trunk/communityWorkshop"

- review subject line first - it may be a file you don't care about

- Review the log message - this should be enough to understand the intent

- if appropriate review the actual change (check for spelling errors, get full details of the change etc.)

- if comment is necessary just hit reply, it will go to the team discussion list

- if no comment is necessary archive the mail

External Links

OSSWatchWiki: CommunityDevelopment (last edited 2013-04-15 13:56:22 by localhost)

Creative Commons License
The content of this wiki is licensed under the Creative Commons Attribution-ShareAlike 2.0 England & Wales Licence.

OSS Watch is funded by the Joint Information Systems Committee (JISC) and is situated within the Research Technologies Service (RTS) of the University of Oxford.