Personal tools

Protect the community

From HaskellWiki

(Difference between revisions)
Jump to: navigation, search
(more notes)
(Resources: indet)
 
(6 intermediate revisions by 2 users not shown)
Line 4: Line 4:
 
== Resources ==
 
== Resources ==
   
* [http://www.red-bean.com/dav/presentations/Poisonous-people.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)]
 
* [http://bobstopper.livejournal.com/22939.html Reaching consensus in open source]
 
* [http://bobstopper.livejournal.com/22939.html Reaching consensus in open source]
 
* [http://www.consensus.net/ocaccontents.html Reaching consensus]
 
* [http://www.consensus.net/ocaccontents.html Reaching consensus]
  +
* [http://www.codinghorror.com/blog/archives/000706.html The community around a product is more important than the product itself]
  +
* [http://headrush.typepad.com/creating_passionate_users/2006/12/how_to_build_a_.html How to Build a User Community]
  +
* [http://praxagora.com/andyo/professional/mailing_list_follow_up/ How to Help Mailing Lists Help Readers]
  +
* [http://www.shirky.com/writings/group_enemy.html A Group Is Its Own Worst Enemy]
  +
  +
== 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.
  +
  +
   
 
[[Category:Community]]
 
[[Category:Community]]

Latest 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.

[edit] 1 Resources

[edit] 2 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.