Should open-source companies fire their community members?
In response to a middling post of mine on whether open-source companies offer better support than proprietary companies, Russ Danner shot back a list of questions that really set me to thinking. One, in particular, pushed my thinking on open source:
Sometimes you need to fire customers, is it ever appropriate to fire a community member?
"Firing a customer" refers to getting rid of customers who cost a company too much money to service/support. All industries do this to greater or lesser degrees (if you have cancer, try getting a new health insurance provider in the U.S.), but I've never seen the question related to open-source communities.
Community is the lifeblood of an open-source project, after all. Don't needy, loudmouth community members contribute, too?
I don't know. I can see two sides of this. On one hand, you may have a person that is disruptive to 95 percent of the other community members. Or that person may simply be a massive time sink for the leading developers on a project. (With some people, you can never answer their questions to the level they'd like, and so you get sucked into a black hole of endless questions.)
On the other hand, what would those other 95 percent think if they saw a community member--even an obnoxious one--dumped from the forums? That doesn't sound like the sort of community I'd want to join, where your voice is only valid if you happen to be singing in tune with everyone else.
I suspect that the answer is to let the community--and not the company or project lead--sort it out. If you lay out the ground rules for participation in a community, you can effectively push overly needy community members back to the community for answers to their questions. If the community opts to silence the needy member ("Go check the FAQ! We've answered that a million times already"), then so be it.
What do you think? I imagine this is a fairly common occurrence. How have you/your companies dealt with this kind of issue in the past?
Matt Asay brings a decade of in-the-trenches open-source business and legal experience to The Open Road, with an emphasis on emerging open-source business strategies and opportunities. Matt is chief operating officer at Canonical, the company behind the Ubuntu Linux operating system. Prior to Canonical, Matt was general manager of the Americas division and vice president of business development at Alfresco, an open-source applications company. He is a member of the CNET Blog Network and is not an employee of CNET. Disclosure. You can follow Matt on Twitter @mjasay. 
- Better than firing is avoiding hiring
- by dneary September 4, 2007 7:13 AM PDT
- A community grows according to shared values - if a community is friendly and welcoming, its newer members are likely to be friendly and welcoming. If a community is a little rough around the edges, then new arrivals are going to be the people who can ride out those rough edges - and are likely to have a few of their own.<br /><br />The best way to establish a good community, then, is to identify good core values, and encourage them. A code of conduct, or benevolent dictators who pinch poor behaviour in the bud, are likely to help avoid the need of firing anyone.<br /><br />If someone comes along acting in a way which is unacceptable for the existing community, they will hear about it, and are likely to feel misunderstood, unpopular, picked on - but they're not going to stick around. In the same way, if you allow bad behaviour to go uncensured, newcomers are likely to feel that the community is rude, unwelcoming, beligerent - and they will go elsewhere.
- Like this Reply to this comment
-
(3 Comments)