52
Community Anti-patterns Dave Neary Neary Consulting [email protected]

Community antipatterns

Embed Size (px)

DESCRIPTION

 

Citation preview

Page 1: Community antipatterns

CommunityAnti-patterns

Dave NearyNeary [email protected]

Page 2: Community antipatterns
Page 3: Community antipatterns
Page 4: Community antipatterns
Page 5: Community antipatterns

“Good artists copy, great artists steal”Pablo Picasso

Page 6: Community antipatterns

Cargo cults

Page 7: Community antipatterns
Page 8: Community antipatterns

Community anti-patterns:Best Practices Run Amok

Page 9: Community antipatterns

Cookie licker

Page 10: Community antipatterns

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”

Page 11: Community antipatterns
Page 12: Community antipatterns

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

Page 13: Community antipatterns

Treatment

● Set deadlines on tasks, and reassign when they run over

● Make failure OK

Page 14: Community antipatterns
Page 15: Community antipatterns

HelpVampire

Page 16: Community antipatterns

Treatment

Good newbie docsEncourage recent newbies to answer newbie questionsTeach newcomers how to search for answers

Page 17: Community antipatterns

See also:RTFM

Page 18: Community antipatterns

Command and Control

Page 19: Community antipatterns

Symptoms

● Joint Copyright Assignment● All committers from one company● No public roadmap, unannounced

features arrive regularly

Page 20: Community antipatterns

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

Page 21: Community antipatterns

Treatment

● Define policies for community access to project resources

● Public roadmap process● Exchange influence for control

Page 22: Community antipatterns

Headless chicken

Page 23: Community antipatterns
Page 24: Community antipatterns

Bikeshed

Page 25: Community antipatterns
Page 26: Community antipatterns

Leadership

Page 27: Community antipatterns
Page 28: Community antipatterns

Mob rule

Page 29: Community antipatterns

Beware Dunbar's Number

Page 30: Community antipatterns

How do your communitymembers self-identify?

Page 31: Community antipatterns

Culture ofDoing

Page 32: Community antipatterns

AvoidSmokeFilledRooms

Page 33: Community antipatterns

TheWaterCooler

Page 34: Community antipatterns

Fear ofcommunity

Page 35: Community antipatterns

Work in a glasshouse

Page 36: Community antipatterns

Open Design!=

Design by Committee

Page 37: Community antipatterns

Black Hole

Page 38: Community antipatterns

“Ironically, since I started working onSyncEvolution full-time beginning of this year, I seem to have *less* time leftcompared to the previous years when Idid it in my spare time"

Patrick Ohly

“I'm too busy to spend time answeringquestions on the mailing list”

OpenWengo developer

Page 39: Community antipatterns

Treatment

● Ensure “doing things in the open” is part of the job description

● Train managers & engineers in community development

● Document who is doing what publicly – and explicitly leave some thing on the roadmap clearly marked “Not us”

Page 40: Community antipatterns

Broken window

Page 41: Community antipatterns

Symptoms

● Off-topic/bikeshed threads on mailing list● Wiki vandalism/decreased article quality● IRC Signal to Noise ratio decreases

Page 42: Community antipatterns

Treatment

● Document Best Practices● Remind offenders early● Spread policing load around

Page 43: Community antipatterns

Broken record

Page 44: Community antipatterns

“I'm the bad guy??? How did thathappen? I did everything they told me to.”

Michael Douglas, Falling Down

Page 45: Community antipatterns

Treatment: Don't be that guy!

(A gentle reminder is usually enough)

Page 46: Community antipatterns

Final thought:Communities are emotional places

Page 47: Community antipatterns
Page 48: Community antipatterns
Page 49: Community antipatterns
Page 50: Community antipatterns
Page 51: Community antipatterns

Community goal:Create a fun, friendly environment

where people feel safe sharing