Four ways to undermine a community | Opensource.com

Four ways to undermine a community

Image by : 

opensource.com

At opensource.com, we often talk about ways to build and nourish communities. But sometimes what you do right is less important than what you’re doing wrong. We dug through our archives looking for cautionary tales that show how communities break down—or never begin to flourish in the first place.

How to wreck just about any community

1. Set up lots of policies, red tape, and bureaucracy

Nothing kills innovation quite like a mountain of paperwork. This story comes from Mel Chua:

Three unspoken blockers that prevent professors from teaching open source community participation
One of the hardest things about trying to bridge two worlds--for instance, open source communities and academic institutions--is all the stuff you don't hear on a daily basis when you're working remotely. Sometimes it takes several rounds of garlic bread and pasta for people to begin articulating what's blocking them from teaching their students how to participate in FOSS communities.
» Read more

2. Focus on tools and technology, rather than people

From Chris Grams we get an excellent piece of advice:

Avoid the tool trap when building communities
Over the last few years, I've had the opportunity to work with many different organizations attempting to build successful communities inside and outside the open source world. Many of them quickly fall into something I call the tool trap.

Meaning, they immediately jump into a conversation about what tool or technology they will use to support the community:

"Where are we going to put the wiki?"

"Should we build the website using Drupal?"
» Read more

3. Don’t bother recognizing the work of individuals

Wikipedia provides the example for this common source of community breakdown:

Love, hate, and the Wikipedia contributor culture problem
Last fall, a group of researchers at the Palo Alto Research Center (PARC) released a study showing an abrupt leveling off in the number of editors and edits to Wikipedia, starting in about 2007.
» Read more

4. Think of contributions, no matter how valuable or innovative, as coming from the nebulous “crowd”

Jaron Lanier's distaste for crowdsourcing provokes a debate between opensource.com writers:

Jaron Lanier: open textbooks "appalling and preposterous"
Jaron Lanier is certainly getting his share of press lately.  His latest guest starring role: a rant in Monday's very special episode of L. Gordon Crozier's technology column for the Wall Street Journal.  Seems like Lanier is becoming a go-to guy when one is in need of a sound bite denouncing "free culture" in all of its radical and dangerous forms.
» Read more


Is Jaron Lanier just a hater, or should we be paying attention?

Last week, my friend Greg DeKoenigsberg posted an article about Jaron Lanier's negative comments regarding open textbooks. At almost very same time, I happened to stumble upon an article Jaron wrote back in 2006 criticizing Wikipedia.

The common theme is Jaron taking issue with what he calls "online collectivism," "the hive mind," and even "digital Maoism" (ouch!).
» Read more

So, what did we miss?

We know that many of you are community-building experts, and some have revived a floundering community. We’d love to hear your stories. Together we can create a collection of "worst practices" that will help communities identify and address the problems plaguing them.

 

About the author

Rebecca Fernandez - Rebecca Fernandez is a Principal Employment Branding + Communications Specialist at Red Hat, a contributor to The Open Organization book, and the maintainer of the Open Decision Framework. She is interested in open source and the intersection of the open source way with business management models.