Lessons From Flourish 2010

My wife and I volunteer for FlourishConf, UIC’s annual conference on open source software and innovation. The fourth annual session wrapped up earlier this month.
Among the highlights for me were Robert Landley’s opener “The Prototype and the Fan Club”, Ross Boucher’s discussion of 280 North the Cappuccino developer environment, and Randi Harper’s lightning-rod “Women in Open Source” talk. (I also was amazed by Ryan Schultz’s overview of Studio Wikitecture, the community aspects of which I’ll discuss in a later post.)
Sometimes (not too often, but enough to notice) I observe folks in the PR-and-marketing-two-dot-oh space throwing around the term “open source” a bit carelessly, I suspect because they! think! it! just! makes! them! sound! sooo! hip! In any event, it’s a good bet that many in that same group have never really engaged with that community.
Truth is PR (and, specifically, PR practitioners who have a focus on community engagement) can learn plenty from the “Free, Libre, and Open-Source Software” (FLOSS) community.
Some aspects that come immediately to mind:
Believe it or not, there are some online communities — yes, even in the software and tech space — that don’t care as much about the latest Web 2.0 doodad as you do.
I keep wondering how many in our industry have ever been on IRC or could articulate its continued value. Participation in IRC and LISTSERVs (hardly things that trade orgs will sell a webconference about) is essential in terms of evangelism, technical contribution, and obtaining support in the FLOSS community.
The presence of an online argument doesn’t mean that PR has failed.
In fact, arguments among the FLOSS community (short of flamewars) contribute to better shared understanding and, ultimately, better software. To gain value from those discussions, it’s important to have a fairly thick skin. On the other hand, the very strong service-oriented mentality of many PR folks makes it more likely that any disagreement, no matter how polite, might be deemed a failure of PR. The point is that maintaining intellectual honesty about argument as a vehicle for improvement is vital. And while one cannot control a conversation, a good communicator should be able to ethically make a case and influence an outcome.
Starting small is not only okay, but encouraged.
When asked by programmers how they can best start getting involved in a FLOSS project, FLOSS veterans consistently say that proving yourself by submitting smaller contributions in the very beginning is absolutely the best way to go. Many companies considering any communications exercise, within the social media space or elsewhere, too often believe in the “go big or go home” axiom. We’re well past the era of giving a company brownie points just for showing up or making a splash. A sustainable and mutually beneficial community presence is earned bit by bit over time, not bought.
Call it the Zuckerberg Corollary:
“Communities already exist. Instead, think about how you can help that community do what it wants to do.” Many FLOSS projects start when someone tries to scratch his or her own technical itch. If others have the same itch (or, at the very least, find someone’s itch interesting) they may choose to contribute in a variety of ways, from delivering software patches to volunteering to quality-test. The lesson: Done right, companies have the opportunity to be heroes to communities they most want to influence. Caution, however: If you’re going to go in thinking you’re going to make the conversation about you, you better be prepared to give the community an opportunity to contribute to — and meaningfully see their contributions within — your product or service.
More thoughts coming as I continue to explore open source.

















