Typo, svn comment
Some external links
|Deletions are marked like this.||Additions are marked like this.|
|Line 1:||Line 1:|
|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.
|Line 49:||Line 51:|
= External Links =
* http://www.crn.com/sections/breakingnews/breakingnews.jhtml?articleId=197003131&printableArticle=true http://producingoss.com/
* http://www.wikipatterns.com/display/wikipatterns/Wikipatterns http://www.ukoln.ac.uk/web-focus/papers/upgrade-2005/html/
* http://www.oss-watch.ac.uk/talks/2004-11-19-bodington/ http://www.oss-watch.ac.uk:81/resources/sfintro.xml
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.
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
[http://involve.jisc.ac.uk/wpmu/oss-watch/2007/05/11/create-a-customised-google-search-engine/ Create a customised Google search engine] Great if there are several sites containing the bulk of the community and these sites a google-accessible. Less good for communities which google doesn't index.
Examples of Targeted Search Engines
[http://www.google.com/coop/cse?cx=007950368875930262986%3Avwrqfjvw_u4&hl=en Open Source in UK Higher Education]
[http://oss.ricshreves.net/ Open Source Project Management & Governance Search Engine]
[http://www.google.com/coop/cse?cx=004162906199039189909%3Aaqiih2cm-fa Learning Technologies]
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.
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