Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Community antipatterns

569 views

Published on

Sometimes good intentions can lead to unintentional results. This was a presentation to the OPNFV Community on identifying and mitigating some community anti-patterns.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Community antipatterns

  1. 1. Community Anti-patterns Dave Neary SDN/NFV Community Strategy Red Hat dneary@redhat.com @nearyd
  2. 2. “Good artists copy, great artists steal” Pablo Picasso
  3. 3. Cargo cults
  4. 4. Community anti-patterns: Best Practices Run Amok
  5. 5. Cookie licker
  6. 6. Symptoms ● Community member volunteers for tasks ● Progress reports are infrequent & vague ● “I'm working on a draft” ● “It's nearly ready to go” ● When it's suggested someone takes over, the task owner resists ● “I'll make time next week” ● “I've almost finished”
  7. 7. Causes ● Desire to have things done well ● Best community members always over-commit ● Truly believes they can make time ● Once committed, handing off task is admitting failure
  8. 8. Treatment ● Set deadlines on tasks, and reassign when they run over ● Make failure OK
  9. 9. Headless chicken
  10. 10. Bikeshed
  11. 11. Mob rule
  12. 12. Alpha Male
  13. 13. Command and Control
  14. 14. Symptoms ● Joint Copyright Assignment ● All committers from one company ● No public roadmap, unannounced features arrive regularly
  15. 15. Justification ● Have a company to run ● We need to own the code for our business model ● The company paid for it, we should be special ● Community contributions are small anyway
  16. 16. Treatment ● Define policies for community access to project resources ● Public roadmap process ● Exchange influence for control
  17. 17. Smoke Filled Rooms
  18. 18. The Water Cooler
  19. 19. “Shy Developers Syndrome”
  20. 20. Fear of community
  21. 21. Avoid the Big Reveal Surprise is the opposite of engagement John Lilly, Mozilla
  22. 22. Work in a glasshouse
  23. 23. Culture of Doing
  24. 24. Open Design != Design by Committee
  25. 25. Broken window
  26. 26. Symptoms ● Off-topic/bikeshed threads on mailing list ● Wiki vandalism/decreased article quality ● IRC Signal to Noise ratio decreases
  27. 27. Treatment ● Document Best Practices ● Remind offenders early ● Spread policing load around
  28. 28. Final thought: Communities are emotional places
  29. 29. Community goal: Create a fun, friendly environment where people feel safe sharing
  30. 30. Thank you! Dave Neary / @nearyd dneary@redhat.com

×