[maemo-community] maemo.org infra safety - HiFo action URGENTLY needed.

From: joerg Reisenweber joerg at openmoko.org
Date: Tue Mar 11 16:03:21 UTC 2014
On Tue 11 March 2014 05:02:46 Craig Woodward wrote:
> Here, you react negatively when you are reminded that while you were given
> a sysadmin role, you would not be the person in charge of TMO or
> management of all parts of the systems, but rather as a general manager of
> those who would administer it.  The Board decided (rightly, IMHO) to split
> that duty specifically to prevent a "one man show" in system
> administration.  You make a comment reminiscent of the current ones,
> quoting the e-mail as part of your reply:
> http://lists.maemo.org/pipermail/maemo-community/2012-December/005822.html

This whole section is again an example for what I call made up fairy tales.
let me go through it point by point, though I'd much prefer to answer same way 
I did back when: "I dunno how to comment on that"

*) I don't see me reacting negatively
*) I wasn't given a sysadmin role - my role been and still is maemo admin 
manager (defined as "holding the keys", responsible to decide who's getting 
access to the quite precious assets of privacy data on maemo) & maemo admin 
coordinator (defined as the one guy who gets the flames when party A does 
announced action X that possibly conflicts with activity of party B - like Falk 
planned to do updates and thus downtime, while elections been in progress)
*) I never claimed I'm "the person in charge of TMO or management of all parts 
of the systems" - I had outright rejected that as impossible to accomplish. We 
got sysops and maintainers for that, and my responsibility is to introduce 
them and take care that sysops create accounts for them.
*) "The Board decided (rightly, IMHO) to split" - I don't see any such 
decision made by board, but anyway - as quoted above - it's obvious to 
everybody that a single person can't do that task. The structure of sysadmins 
(responsible for technical aspects of "higher level" aka the complete infra) 
and maintainers (responsible for a [single] subsystem and defined as "users on 
the machines owned by the sysops") got established by me.
*) "...to prevent a "one man show" in system administration."  Here I really 
only can say "fairy tale" since obviously HiFo has no faintest clue how the 
maemo techstaff works. Assuming there even *could* be such a thing like a "one 
man show" clearly disqualifies the one assuming that for any decisions 
regarding maintenance organization. You implying that me was that "one man" is 
considered by me as malicious intent and as an effort to dazzle community.

*) finally your reference to that email seems pretty incoherent to me. Did you 
pick the wrong URL?

()  ascii ribbon campaign - against html e-mail     
/\  www.asciiribbon.org   - against proprietary attachments
(alas the above page got scrapped due to resignation(!!), so here some 
supplementary links:)
http://www.gerstbach.at/2004/ascii/ (German)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.maemo.org/pipermail/maemo-community/attachments/20140311/269a06ef/attachment.pgp>
More information about the maemo-community mailing list