[Meego-community] Community working group - status update
dneary at maemo.org
Mon Mar 15 08:52:18 CDT 2010
Jeremiah Foster wrote:
>> The TSG appointment makes sense at the creation of working groups. After
>> that I would expect that the group leadership would be defined by the
>> own group dynamics. "Some kind of election" can include e.g. candidates
>> and votes among the own working group members in an extraordinary
>> meeting. Anyway, we will have time to discuss this.
> It still is not clear the overall governance model. In debian, a
> technical committee can advise revocation of ssh keys which prevent a
> developer from uploading to debian's servers. What is going to be the
> analog in MeeGo? Who has final say about what sits on the servers for
Mike knows better than me what servers we're going to be using & what
their configuration would be, and where the hardware is physically
located (are they in OSU's Open Source Labs?) but I imagine that we
would aim for a clean separation of anything that might require an NDA
and MeeGo servers - which would, in theory, allow a reputation culture
to developer where MeeGo "volunteers" (a word I don't really like in
this context, but anyway...) to become application admins, or even
become root on MeeGo servers.
> I hope we have Niels and others helping us at MeeGo. But we cannot have
> the web infrastructure in the hands of just paid staff (speaking as a
> member of the paid staff.)
Nor can we indiscriminately add sysadmins to project servers just to
avoid this situation.
>> I have been in free software projects made 100% out of volunteers and
>> there was also problems finding volunteers for the web infrastructure.
>> Low entry barriers (as opposed to 'from zero to root') and well known
>> tools do help.
> There were problems on Nokia's side too. Nokia often employed their own
> technology, like NetApp and Akamai, that went against the wishes of the
> community. I think it is a little disingenuous to blame the community
> for lack of contribution when Nokia would not accept community
> contribution, specifically in the areas of community mirrors.
Many communities struggle to renovate sysadmin teams, because a sysadmin
by nature must be risk averse, and adding new members to the team can be
a time-consuming experience which isn't necessarily pleasant for the
incumbent sysadmin or for the newcomer. It's vital that people be able
to prove themselves worthy of the trust of existing sysadmins, and
that's a very hard thing to prove if you haven't worked with them. So
once again (as with commit rights, or any of the non-technical roles
we'll have) establishing a trust hierarchy & a way for people to prove
themselves at things is vital.
The recent Maemo server move is an excellent example - by having various
services running independently on different VMs, the Maemo sysadmins
have created a way to give community members fine-grained control of the
administration of individual applications, without giving access to
everything. Once you've proved yourself a competent sysadmin for one
application, it's a hop & a skip to gain access to administer others.
It's still establishing itself for Maemo, but the strategy should
definitely carry over to MeeGo if possible.
Email: dneary at maemo.org
Jabber: bolsh at jabber.org
More information about the Meego-community