{"id":1304,"date":"2009-02-05T03:47:46","date_gmt":"2009-02-05T08:47:46","guid":{"rendered":"http:\/\/www.bytebot.net\/blog\/?p=1304"},"modified":"2009-02-05T03:47:46","modified_gmt":"2009-02-05T08:47:46","slug":"lessons-from-mozilla-that-apply-to-other-communities","status":"publish","type":"post","link":"http:\/\/www.bytebot.net\/blog\/archives\/2009\/02\/05\/lessons-from-mozilla-that-apply-to-other-communities","title":{"rendered":"Lessons from Mozilla, that apply to other communities"},"content":{"rendered":"

John Lilly, CEO of Mozilla, shares some insights and thoughts<\/a> on Mozilla, and its a most interesting presentation to go through. The insights are (drizzled with some of my comments):<\/p>\n

    \n
  1. Superior Products Matter<\/strong> – Without excellent experience and utility, the rest is meaningless. This is true, even with MySQL – our aims and values have always been performance, reliability and ease of use.<\/li>\n
  2. Push (most) decision-making to the edges<\/strong> – I understand that as make sure your community has a significant voice (kind of like Wikipedia’s anyone edits policy, but there’s patrolling). He also suggests that on a regular basis, you need to have surprising innovation – things that blow people’s minds. In Mozilla’s case, there are a set of core values that everyone agrees too; decision making is with the module owners (very much like how the Linux kernel, tends to run), after all, groups have different ways of working. Mozilla has decision makers, that are even outside the “official” organisation – i.e. community has a voice. And communication, is key.<\/li>\n
  3. Communication will happen in every possible way (so make sure it’s reusable)<\/strong> – this means via Wikis, blogs, the bug tracker, IRC, forums\/newsgroups, mailing lists, audio, video, Skype chat, real-life get-togethers, and probably more. Writing notes, and sharing them, might be useful – I’ve found that the Mozilla Weekly Progress Reports on Planet Mozilla (and especially from Zak Greant<\/a>) to be really useful. I’m thinking of something similar, in the MySQL (and other Sun open source communities) scope. A lot of decisions tend to be taken up on IRC, and people go on hacking on stuff, without writing documentation (worklogs\/blueprints), or consulting with the mailing lists – I guess we all have communication improvements in us.<\/li>\n
  4. Make it easy<\/font> for your community to do the important things<\/strong> – Here the highlights are SpreadFirefox, Mozilla QA, localisation and more. A focus “to help others do more” should be the mantra of every community! I see it as very easy to translate Drizzle now, that its on Launchpad, but its not the same with MySQL. Translation, documentation, non-code related tasks tend to increase community contributions – though, what do you do when you already have an excellent manual?<\/li>\n
  5. Surprise is overrated<\/strong> – John suggests that surprise is the opposite of engagement, which is true – no one likes surprises, and everyone wants to feel they’re important and had a role to play when something has happened. The “inner circle” needs more participation. I remember back in the days of Red Hat Linux to Fedora… there was something called the “Fedora Merge” group, and this allowed externals to provide significant decisions towards the direction of the Fedora Project. This was eventually eclipsed by fedora-maintainers, and the various boards like FESCO, and so on. As a participant in the Merge group, I felt like I had a voice, and was part of the “cabal” (there is no cabal), or the inner circle, so to speak – decisions I made, mattered. The inner circle grew, so that everyone (a maintainer, i.e. a person who “deserved” a voice) could feel included. Similar things happened for documentation, marketing, and so on, with various members and boards.<\/li>\n
  6. Communities are not markets: members are citizens<\/strong> – John stats that citizens are more than consumers, bystanders and stake-holders – we are all citizens in the community (whether you’re a paid staff member, or an external). The best citizens even challenge the status quo, propose improvements and make the conversation richer – I think we have this, via Planet MySQL. The question though is, are we as Sun, listening to the citizens?<\/li>\n
  7. The key is the art of figuring out whether & how to apply each of these ideas<\/strong> – John suggests experimenting, trying new things, and then measuring the reaction.<\/li>\n<\/ol>\n

    Of course, back to point #6, engaged citizens are noisy<\/strong> is highly true. But the old adage of people complaining because they care, is probably a good thing to remember. Expect noise, demands, threats, contradictions, and more. You can’t please everyone in a healthy community, but they will help you make decisions.<\/p>\n

    A most interesting presentation, and there’s a lot to learn from Mozilla, for other communities to apply.<\/p>\n

    Share this:<\/h3>