10. 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”
11.
12. 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
13. Treatment
● Set deadlines on tasks, and reassign when they
run over
● Make failure OK
19. Symptoms
● Joint Copyright Assignment
● All committers from one company
● No public roadmap, unannounced
features arrive regularly
20. 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
21. Treatment
● Define policies for community access to project
resources
● Public roadmap process
● Exchange influence for control
38. “Ironically, since I started working on
SyncEvolution full-time beginning of this
year, I seem to have *less* time left
compared to the previous years when I
did it in my spare time"
Patrick Ohly
“I'm too busy to spend time answering
questions on the mailing list”
OpenWengo developer
39. 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”
