Difference between revisions of "Protect the community"
Jump to navigation
Jump to search
DonStewart (talk | contribs) |
m (link fix) |
||
| Line 4: | Line 4: | ||
== Resources == |
== Resources == |
||
| − | * [http://www.red-bean.com/dav/presentations/ |
+ | * [http://www.red-bean.com/dav/presentations/PoisonousPeople.pdf Protecting projects from poisonous people] |
* [[/Notes|Notes on this talk]] |
* [[/Notes|Notes on this talk]] |
||
* [http://www.oreillynet.com/conferences/blog/2006/07/oscon_how_open_source_projects.html More notes on this talk] |
* [http://www.oreillynet.com/conferences/blog/2006/07/oscon_how_open_source_projects.html More notes on this talk] |
||
Revision as of 13:35, 27 February 2007
This page collects resources from the open source world on maintaining and building healthy communities around your open source project.
Resources
- Protecting projects from poisonous people
- Notes on this talk
- More notes on this talk
- Mailing list community care
- Avoid bikesheds (related to Wadler's Law of Language Design)
- Reaching consensus in open source
- Reaching consensus
- The community around a product is more important than the product itself
- How to Build a User Community
More notes
- Build a community, not just a mailing list.
- Be very conscious of tone.
- Followup with constructivly with criticisms on blogs (ie "Thanks for you criticism, how can we do this better?").
- Be careful of trolls, and just ignore them. Possibly ban them.
- Spam can't be an afterthought. Don't think oh, we won't get spammed. Google groups does a good job.
- Listen to the community. Everyone has good and bad ideas.
- Don't pay too much attention to vocal minority. But be willing to take big risks when the community asks for them.
- Have to be willing to ask for help and delegating things.