Preventing Community (from Linux Collab)

541 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
541
On SlideShare
0
From Embeds
0
Number of Embeds
9
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Preventing Community (from Linux Collab)

  1. 1. PreventingCommunitya how-to guide Josh Berkus Community Hit Man Linux Collab 2010
  2. 2. So,you started anopen source project
  3. 3. COMMUNITY
  4. 4. Community Growth RedditCommunity Size User Conference 2.0 LWN Major Announce Adopter Project Bad Release Project Year
  5. 5. The Horror! The Horror!
  6. 6. Thousands of Messages
  7. 7. Hundreds of People
  8. 8. Dozens of Events
  9. 9. Out of Control
  10. 10. Community Size Community Growth Project Year
  11. 11. Carbon Concentration Global CO2 Concentration Year
  12. 12. Community Size Cut Off That Ugly Growth! Project Year
  13. 13. 7 The Habitsof Highly Stagnant Communities
  14. 14. THROW IT OVERTHE WALL
  15. 15. Habit #1DifficultTools
  16. 16. ● Proprietary version control● Idiosyncratic build systems● Antiquated bug trackers● Home-grown CMS with proprietary components● Documentation system with no GUI tools
  17. 17. advantages of difficult tools● huge barrier to entry for new contributors ● most get discouraged and leave● slow down the whole project by making routine tasks difficult● skills are non-portable to other OSS projects● your staff know the tools better than the community
  18. 18. the best thing about difficult tools is ...you probably have them already!
  19. 19. THROW IT OVERTHE WALL
  20. 20. Habit #2Overworked Project Team
  21. 21. enemy #1: your own staff
  22. 22. solution: overwork your team!1. assign your development engineers to managing the project2. increase their engineering workload at the same time3. have no dedicated community liaison, or one who is useless4. add a bunch of ambitious deadlines for the project
  23. 23. 3 possible outcomes● your staff will neglect the community● your staff will hate the community and the community will hate them● staff who care about community will burn out and abandon the project All win!
  24. 24. THROW IT OVERTHE WALL
  25. 25. Habit #3Closed-Door Meetings
  26. 26. Closed-Door MeetingsGood Short-notice online meetingsBetter Telephone meetingsBest Meet in person, in your secure off ce i
  27. 27. THROW IT OVERTHE WALL
  28. 28. Habit #4:Feed TheTrolls
  29. 29. nurture your trollsMaximize the damage they can do! 1. Argue with them at length 2. Denounce them venemously 3. Ban them 4. Argue with them in other projects 5. Allow them back into your project 6. GOTO 1
  30. 30. Habit #5:Lock It Down!
  31. 31. there can be only one!● Only one person should have admin on the web server● Only one person can have control of the DNS● Only one person may touch the mail server● Only one person will administrate the CMS
  32. 32. make it the right person overworked antisocial required to follow elaborate company procedures and never, ever an outsidecommunity member or team!
  33. 33. then, let them go on vacation! what could go wrong?
  34. 34. THROW IT OVERTHE WALL
  35. 35. Habit #6Legalese, Legalese, Legalese
  36. 36. you cant have too much legalese! The longer and more complex the better! Contributor agreements Website content licensing Non-disclosure agreements Trademark licensing terms Open source release review process● Bonus: change the documents every couple of months, without any official notice.
  37. 37. THROW IT OVERTHE WALL
  38. 38. Habit #7
  39. 39. silence is golden
  40. 40. The 7 Habits1. Difficult Tools2. Overworked Project Team3. Closed-Door Meetings4. Feed The Trolls5. Lock it Down!6. Legalese, Legalese, Legalese7. Silence
  41. 41. The 7 Other Habits1. easy, common tools2. allocate time for project3. open decision-making4. manage & expel trolls5. share control6. minimize legalese7. communicate
  42. 42. THROW IT OVERTHE WALL
  43. 43. contact● Josh Berkus ● josh@pgexperts.com ● www.pgexperts.com ● it.toolbox.com/blogs/database-soup● events ● open source bridge Portland june 1 ● community leadership summit Portland july 17 ● OSCON Portland july 19 Thanks to Ted Tso, Joe Brockmeier and Greg KH for helping me with the material for this presentation. This presentation copyright 2010 Josh Berkus, licensed for distribution under the Creative Commons Attribution License, except for photos, most of which were stolen from other peoples websites via images.google.com. Thanks, Google!

×