Difference between revisions of "Protect the community"

From HaskellWiki
Jump to navigation Jump to search
(→‎Resources: indet)
Line 5: Line 5:
   
 
* [http://www.red-bean.com/dav/presentations/PoisonousPeople.pdf Protecting projects from poisonous people]
 
* [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] from O'Reilly
 
* [http://meyerweb.com/eric/thoughts/2004/11/11/mailing-list-community-care/ Mailing list community care]
 
* [http://meyerweb.com/eric/thoughts/2004/11/11/mailing-list-community-care/ Mailing list community care]
 
* [http://bikeshed.com/ Avoid bikesheds (related to Wadler's Law of Language Design)]
 
* [http://bikeshed.com/ Avoid bikesheds (related to Wadler's Law of Language Design)]

Revision as of 20:54, 16 April 2008

This page collects resources from the open source world on maintaining and building healthy communities around your open source project.

Resources

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.