I'm sorry Ryan I thought I was being polite and constructive so I'm not sure
where the "since long before you came aboard the project" is coming from?
I also realise I've only been around MeeGo almost every single day since the day
it launched - I'll try harder to be more passionate, more visible and part of it
for longer next time around :D
So, back to the question: We, as members of the 'official' MeeGo IT team, are
offering to help support some MeeGo infrastructure which is clearly not being
maintained to anything like a professional standard.
I did copy the only known member of the TSG in on the email as well as Anas and
Brian.
I'm sure many others in both the hacker community and the commercial community
feel that there's a very high risk associated with relying on an apparently
absent RE team and on a service which is now at <80% availability.
At least the MeeGo IT team are present and replying to email and irc - both in
US and EU timezones.
David
PS I do get the impression that people think we're on some kind of power-trip
and want to "take over" the main OBS. Well, trust me, looking after an OBS as
well as the rest of the MeeGo.com infrastructure is a HUGE chore, *not* fun. It
eats massively into our personal time and can be immensley frustrating. We do
however take our responsibility seriously and as professionals and community
members we hate to stand by and let people suffer when we could easily help out.
On 12/10/11 15:32, Ware, Ryan R wrote:
David,
The MeeGo OBS is the purview of the Release Engineering team. It has been that
way since long before you came aboard the project. If you have concerns about
that, please bring it up with the TSG.
Ryan
-----Original Message-----
From: David Greaves [mailto:da...@dgreaves.com]
Sent: Wednesday, October 12, 2011 2:40 AM
To: meego-dev@meego.com; Ware, Ryan R;
brian.war...@linuxfoundation.org; Sousou, Imad; Anas Nashif; meego-
i...@meego.com
Subject: The future for the MeeGo OBS
The MeeGo OBS at build.meego.com is down... again.
The MeeGo IT team renew their offer to provide additional service level
support for the main OBS.
This would allows the community to have some confidence in the continuity
and availability of these important services and provides the commercial
organisations still working on MeeGo with the same confidence.
This means that everyone who wants to work on any aspect of MeeGo Trunk
is essentially blocked.
This is not a recent issue:
https://bugs.meego.com/show_bug.cgi?id=22134
A few weeks ago the MeeGo IT team (ie the guys who run DNS,
www.meego.com, the mailing lists, the forum, the community OBS etc)
asked for permission to access the main OBS to provide support. This was
refused. An explanation was due to be given but some urgent issues
apparently prevented that. Since this was mere weeks before the shift to
Tizen it is possible that that was related. In any case it is time to revisit
this
request.
Ryan - I think you got landed with being point-man last time so I'm cc'ing you
directly :) Since MeeGo is a Linux Foundation project I'm cc'ing you too Brian.
Anas - I guess the OBS used to be your responsibility but I have no idea if it
still is.
Imad - just so you know.
To illustrate the problem this graph shows availability of the main OBS:
http://isobsdown.bfst.de/trends.api-obs_api.1314144000_1317921806_2011-
10-06T17.23.26.png
This shows corresponding availability of the community OBS:
http://isobsdown.bfst.de/trends.cobs_api-
obs_api.1314144000_1317921806_2011-10-06T17.23.26.png
David
Niels
(Stefano is on vacation)
--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
_______________________________________________
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines
