10 Ways to Destroy Your Community

  • Published on
    18-Dec-2014

  • View
    728

  • Download
    0

Embed Size (px)

DESCRIPTION

 

Transcript

  • 1. 10 Ways to Destroy Your Community AHowToGuide JoshBerkus,CommunityGuy
  • 2. Part I: The Evil of Communities
  • 3. They mess up your marketing plans bydoingtheirownmarketingandPR
  • 4. They mess up your product plans withunexpectedinnovation
  • 5. Theyre never satisfied by any amount of quality andkeepwantingtoimprovethesoftware
  • 6. They re-define your partner and customer relationships andconfuseyoursalespeople
  • 7. They require you to communicate constantly andwhohastimeforthat?
  • 8. If Only There Were Some Way to Rid Yourself of the Community Menace ...
  • 9. TheBerkus Patented TenStepMethod To Destroy Your Community
  • 10. 1. Difficult Tools weirdbuildsystems proprietaryversioncontrolsystems limitedlicenseissuetrackers singleplatformconferencingsoftware unusual&flakyCMS
  • 11. 2. Poisonous people Maximizethedamagetheycando! 1.Arguewiththematlength
  • 12. 2. Poisonous people Maximizethedamagetheycando! 1.Arguewiththematlength 2.Denouncethemvenemously
  • 13. 2. Poisonous people Maximizethedamagetheycando! 1.Arguewiththematlength 2.Denouncethemvenemously 3.Banthem
  • 14. 2. Poisonous people Maximizethedamagetheycando! 1.Arguewiththematlength 2.Denouncethemvenemously 3.Banthem 4.Arguewiththeminotherprojects/sites
  • 15. 2. Poisonous people Maximizethedamagetheycando! 1.Arguewiththematlength 2.Denouncethemvenemously 3.Banthem 4.Arguewiththeminotherprojects/sites 5.Allowthembackintoyourproject
  • 16. 2. Poisonous people Maximizethedamagetheycando! 1.Arguewiththematlength 2.Denouncethemvenemously 3.Banthem 4.Arguewiththeminotherprojects 5.Allowthembackintoyourproject 6.GOTO1
  • 17. 3. No documentation DONT documentthecode documentthebuildmethods documentthesubmissionprocess documentthereleaseprocess documenthowtoinstallit
  • 18. 3. No documentation DONT documentthecode documentthebuildmethods documentthesubmissionprocess documentthereleaseprocess documenthowtoinstallit butalwaystellpeopleRTFM!
  • 19. 4. Closed-Door Meetings Good Shortnoticeonlinemeetings
  • 20. 4. Closed-Door Meetings Good Shortnoticeonlinemeetings Better Telephonemeetings
  • 21. 4. Closed-Door Meetings Good Shortnoticeonlinemeetings Better Telephonemeetings Best Meetinperson,inyoursecureoffice
  • 22. 5. Legalese, legalese, legalese Thelongerandmorecomplexthebetter! Contributoragreements Websitecontentlicensing Nondisclosureagreements Trademarklicensingterms Bonus:changethedocumentseverycoupleof months,withoutanyofficialnotice.
  • 23. 6. Bad liaison Someonereclusive
  • 24. 6. Bad liaison Someonereclusive or Someonewithnotime
  • 25. 6. Bad liaison Someonereclusive or Someonewithnotime or Someonewithnoauthority
  • 26. 6. Bad liaison Someonereclusive or Someonewithnotime or Someonewithnoauthority or Someoneunfamiliarwiththetechnology
  • 27. 6. Bad liaison Someonereclusive or Someonewithnotime or Someonewithnoauthority or Someoneunfamiliarwiththetechnology or Noliaisonatall!
  • 28. 7. Governance obfuscation
  • 29. 7. Governance obfuscation ThreePrinciples: (1) Decisionmakingandelectionsshouldbe extremelycomplexandlengthy; (2) Makeitunclearwhatpowerscommunity officials&committeesactuallyhave; (3) Makegovernancerulesnearlyimpossibleto change.
  • 30. 8. Screw around with licenses LicenseIdentity
  • 31. 9. No outside committers I. Nomatterhowmuchcodeoutsiderswrite, onlyemployeesgettobecommitters.
  • 32. 9. No outside committers I. Nomatterhowmuchcodeoutsiderswrite, onlyemployeesgettobecommitters. II. Iftheyaskwhytheyrenotpromoted,be evasive!
  • 33. 9. No outside committers I. Nomatterhowmuchcodeoutsiderswrite, onlyemployeesgettobecommitters. II. Iftheyaskwhytheyrenotpromoted,be evasive! III.Makesuretherearenowrittenrulesonwho getstobeacommitter,orthatthethecriteria areimpossibletofulfill.
  • 34. 9. No outside committers I. Nomatterhowmuchcodeoutsiderswrite, onlyemployeesgettobecommitters. II. Iftheyaskwhytheyrenotpromoted,be evasive! III.Makesuretherearenowrittenrulesonwho getstobeacommitter,orthatthethecriteria areimpossibletofulfill. IV.Bonus:promoteanemployeewhodoesnt codetocommitter!
  • 35.
  • 36. 10. Be silent
  • 37. The Ten Ways 1.Difficult tools 2. Encourage poisonous people 3. Dont document anything 4. Closed-door meetings 5. Lots of legalese 6. Bad liason 7. Governance obfuscation 8. Screw around with licenses 9. Stop outside committers 10. Be silent
  • 38. The Ten Ways 1.Familiar Tools 2. Discourage poisonous people 3. Document everything 4. Accessible online meetings 5. Minimize legalese 6. Expert liason 7. Governance simplification 8. Treat licenses with respect 9. Promote outside committers 10. Communicate
  • 39. More Advice JoshBerkus:josh.berkus@pgexperts.com Presentation: www.pgexperts.com/documents.html Blog:it.toolbox.com/blogs/databasesoupCopyright2010JoshBerkus,distributableunderthecreativecommonsattributionlicense