Developing the MeeGo community

A great deal of useful conversation during Linux Foundation Collaboration Summit 2010 (LFCS2010) earlier this year revolved around what a MeeGo community should look like.  There are of course numerous aspects to this but for now I want to focus on three only: what sort of constituency would best benefit MeeGo, how could the website structure reflect, support and encourage that constituency, and what might this mean for

It might be helpful for the reader to browse through threads under Community Matters at the MeeGo discussion forum, as I will be referring to points raised there.  However, that won’t be necessary for a high-level perspective.  Regardless, a community is actually taking shape so I think it’s time to discuss a few subjects. 

For members only

There’s been some debate amongst and MeeGo community members over what actually constitutes a community in general, and more specifically, how a community arising around Maemo/MeeGo endeavors should look.  Opinions range from “every one creating an account is automatically a member” to “only those actively contributing quantifiable work are members”.

I lean toward the latter (with the caveat that not all useful contributions are easily quantifiable).  As an analogy, we can compare a physical neighborhood comprised of home buyers and renters.  Buyers tend to take a high interest in improving the home’s value; renters tend to only reside in any given one a short while and it typically makes no sense for them to invest in that.  (note: this is neither an endorsement nor indictment of either).

Planning and zoning

Quim Gil conducted a very good interactive presentation at LFCS2010 that described the roles, functions and general structure of the emerging MeeGo community.  I tacked onto that recently by drawing up my own interpretation, and then refining that based on community input.  The latest rendition is below:

MeeGo Community Model proposal, version 2

This was met with a mixed reception and the conversation around it quickly died.  The main hangup was over member groups, a feature of the vbulletin forum software.  Some see value in letting community members strive for and adopt titles that suit their interests.  Others see that as unnecessary or even divisive.  The MeeGo Greeters program has found acceptance and I will push for a forum group supporting that activity at the very least (UPDATE: group created).

MeeGo Greeters

At we tried a little experiment to see if adding resource links to forum posters’ signatures could help newcomers.  We didn’t quantify the effectiveness of the effort, but participation was enthusiastic and feedback highly positive.

We just recently introducd the idea into MeeGo, where it has also been quickly welcomed.  The MeeGo community is much younger than was when we created the concept, but I think that works in our favor now.  MeeGo Greeters will be seen as a natural part of the social structure and we can easily, organically grow the effort as the community grows.

Potential hazards

A highly popular presentation at LFCS2010 was the keynote by Josh Berkus: How to Prevent Community: Making Sure Your Pond Stays Small.  Josh outlined with gently sarcastic humor the sort of mistakes that poison and even kill communities, especially those built around open source endeavors.

The 2600Hz blog riffs on Josh’s theme with an article specific to MeeGo.  I’ll leave it to the reader to judge the validity of the analysis there.

A place for

The question of course remains, what is the future of  Unfortunately that’s answered by a great big “it depends”.  It’s too early to close any doors completely, but at the same time, MeeGo has been named as the future so it would only be natural for Maemo to experience a slow fade.

At the same time, though, work continues on a community distribution of Maemo 4 (Diablo) which will ensure that at least the lives of N800s and N810s can be extended.  Harmattan could do the same for N900s (although at this point I question its actual usefullness).  But ultimately, those devices will wear out and their replacements will be designed around MeeGo.  At some point, and it’s difficult to determine when, the Maemo community will shrink to a size too small for Nokia to justify supporting with infrastructure and personnel.  At that time the remaining community will have to find some way to sustain itself or, like so many predecessors, accept a slow fade into the sunset.

Going forward

I’ll conclude on an optimistic note.  There’s been a great deal of buzz around MeeGo’s first international conference to be held November 15 through 17 this year.  The big event will of course be measured against previous examples, especially the energetic Maemo Summit 2009 held in Amsterdam, but it will certainly have its unique aspects that can’t be compared.  The tone will be set by the key sponsors and develop around the accepted talks and myriad attendees.  I’m confident that both Nokia and Intel are going to kick this off in a big way, and can’t wait to see how that manifests.

LFCS2010 introduced the MeeGo community.   The outcome of MeeGo Conference 2010 (MC2010), along with member contributions of course, will go a long way toward shaping it.

5 responses to “Developing the MeeGo community

  1. There is no community to speak of.

    As far as I’ve seen, unless you’re internal at Nokia/Intel, you are not a member, nor are they interested in having a community. Doesn’t matter that there’s a forum called Community Matters. Having installed someone as community manager that is decidedly anti-community is a very interesting development, by the way. Especially someone who had no experience with Maemo.

    There’s no place for us, therefore I’m not there.

    • Despite the positive tone of this article, zerojay, I do understand your concerns. I’m doing my personal best to help support development of an actual community. My hope is that push from community members can force change for the good.

  2. There! I commented. I think everyone’s just waiting to see motion and momentum from MeeGo. All we see is YouTube videos, Nokia refusing to talk about it when asked, saying they’re focused on Symbian, and Maemo still Maemo. When MeeGo matters, we should see more action. Right now, no one cares or feels much can be done about it but the internals folks, by design or default.

    We need more public talk about MeeGo, and not so much internal dev speak.

    • An open source project depends on a community… and that community needs to push those involved in governance for full openness. Granted the opening of MeeGo has been slower than many would like, but it IS happening.

      Anyway it looks to me like your sights may be too narrow. Sure, Nokia has decided to be quiet about MeeGo DEVICES, but employees are all over the place talking about the operating system. Check out the forum and mailing lists for starters! Nokia has also been highly supportive of the local MeeGo network groups, sponsoring meetup accounts and attending meetings.

      Feel free to join the forum and mailing lists, and make your voice heard!

  3. Texrat, I’m just being a smart alec. You know how rabid I am about MeeGo, and not just Nokia, but as a uberplatform. I’m signed up to attend the post MeeGo Conf. Meetup in Irving, and am pretty much reading all things MeeGo until I lose conciousness.

    Its obvious Nokia’s real intent is to slowly get MeeGo efficient enough to run on low end hardware, and phase out Symbian altogether over the next few years. I’m waiting to see it happen asap, but will enjoy the ups and downs of a good story along the way. Now is a great time for mobile. Competition, disruption, reorganization, and standards adoption at its best.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s