Task:Community Council

A process for electing a small "Community Council" should be created and elections held.

qgil is responsible for managing the maemo community on behalf of Nokia. But who is the community? Getting consensus of hundreds of disparate people through mailing lists and wiki-edits means the person who shouts loudest wins.

Therefore - inspired by Debian's Project Leader concept - during the next 100Days, a process for electing a small "Community Council" should be created and elections held.

Mmm... It is probably benefitial for the maemo community and for the dialog with Nokia to have some structure. We are doing effective steps towards this: some people get admin rights, some people might become QA evaluators in the extras repositories, some people receive are more visible and push for certain things in a structured way... However, also with my community shirt I think that 10 days of brainstorm is not enough to define a proposal, and probably 100 days are not enough to implement it either. So, what about 100 Days for the community to discuss and agree on the way to be formally structured?--qgil 08:54, 4 June 2008 (UTC)
Possibly true - however I'd want to avoid us getting into too long talking about a process which can be enhanced/refined at a later date, and get some of the structure in-place sooner. Perfectly happy to go with the consensus on this (since it's necessary for it to work ;-)) --jaffa 10:39, 4 June 2008 (UTC)
Alright, you have the (obvious) pre-agreement on my side. Please discuss and once there is an agreed idea create page accordingly and move this content there. Thanks! --qgil 20:41, 4 June 2008 (UTC)
It's a good idea but I think it too early to do this. I suggest to do this after the 100 days when all maemo is well defined and everyone's on the same page with what maemo is and what's its direction. --Reggie 14:07, 5 June 2008 (UTC)
Perhaps. But there's always something round the corner: it's like buying a computer (or gadget ;-)): if you wait, there's always something better. --jaffa 16:18, 5 June 2008 (UTC)
Having a focusing agent like the council is more important now than in 100 days after everything has settled and there's nothing to do anymore. —GeneralAntilles 20:44, 5 June 2008 (UTC)
My point here is, Nokia hasn't officially announced anything yet with regards to all the plans suggested. I heard Ari and the maemo.org team are officially announcing something at the Maemo Summit 2008. If the decision is 100% (or a good percentage) community run, then it's all good. There are lots to do after the 100 Days - mainly implement, prioritize, and streamline the plans, and keep things organized, as what is defined in the 'Roles of the council' below. --Reggie 13:41, 6 June 2008 (UTC)
Nokia aren't supposed to be announcing anything official with regards to all the plans suggested: this is a community action plan, and has very little to do with Nokia (albeit lots to do with qgil's role of community manager). Unless Nokia are going to fundamentally change the purpose of maemo (and maemo.org), there will still be times when they ask for the "community"'s input. And for that we need a way of the community speaking with one voice. --jaffa 13:51, 6 June 2008 (UTC)
Agree on the community voice. I would still like to hear qgil's thoughts on this though, mainly on how much say/control Nokia will have, and/or if the community can override Nokia. Maybe Nokia will just be in the sidelines and watch maemo.org takes its course. --Reggie 14:04, 6 June 2008 (UTC)
Nokia likes the idea of maemo.org being really a community driven site, moving the official content and software releases to Forum Nokia or somewhere else under the nokia.com domain and control. Having a growing and engaged community willing to assume more responsibilities and power is part of the common success. In this sense the community council is helpful if it's representative and backed by the community. Note the difference between maemo.org activities and the planning, development and release of the official maemo software. There Nokia keeps the same control as now. The structured community might have more influence, power to lobby and to organize alternative maemo variants at their will, though. Personally I have no problems about starting this task now. My only personal concern as community member is to go so fast that the community doesn't follow and then we have a not-really representative council, unable to canalize the hundred voices and becoming at the end one source of feedback more to deal with. This risk is probably the same now and in 100 days, though. If you take a 'release soon & often' approach open to iterations until consolidating the model, then starting soon shouldn't be a problem per se.--qgil 19:44, 6 June 2008 (UTC)

Roles of the council

  • Monthly IRC meeting with qgil. Open to all, but moderated so only the council members and Quim can talk.
  • Distill maemo community issues, from maemo-* mailing lists, ITT, etc. and raise with Nokia.
  • Understand, and help explain, Nokia's decisions and processes to the rest of the community.
  • Advocate maemo, and involvement in its community, to end-users.
  • Help manage community involvement, for example Maemowiki Action Group, 100Days and 2010 Agenda.

For example, if it already existed, the Council would take responsibility for defining the outcome of the brainstorm, i.e. the format and structure of the individual streams' plans.


The full process would be defined during the first 30 days, however here's an outline:

  • Council positions open to anyone with karma above a certain threshold - say, 100.
  • Community votes open to anyone with karma above another threshold - say, 50.
  • One member, one vote.
  • 5 nominees with highest number of votes elected.
  • The chairperson will be the nominee with the highest number of votes.
  • Elections held every 6 months.
  • Nominations accepted 2 weeks before election.
  • Votes tallied after 1 week of elections.