On Mar 28, 2010, at 11:34 AM, Andrew Flegg wrote: > On Sun, 28 Mar 2010, 08:37:43 BST, [email protected] wrote: >> >> It sounds like a good description of the goals of the "Extras / Downloads >> team" >> (final name to be defined) proposed at >> http://wiki.meego.com/Community_working_group#Web_infrastructure > > Indeed. > >> Is there any reason why this team couldn't be part of the Community WG? It's >> all >> about community software. > > AIUI, the Repository WG would also define how MeeGo's core repositories > interacts with the community repos. As we've seen over the years in Maemo, in > particular recently with PR1.2 and Qt 4.6, there's a requirement for very > close collaboration between the core and community repos. My gut says that > the "repositoriness" is a more defining factor than the "communitiness"; > although there's obviously an overlap.
It is very difficult for a developer to co-ordinate with a release process when that release process is secret. Having insight into that process by being a member of the team that runs that release process solves a lot of problems. Having community release engineers is crucial - otherwise you are keeping the community at arm's length. I think this is what the repository working group would do: help with release engineering. Then they can interact with the TSG and the community to align those interests. The concrete proposal is to make sure community members have access to the repos and their voice is heard when the time comes for code freeze, etc. Instead of the current process which is, "Oh yeah. New release today. Sorry if it broke your software." You can do that to individual developers, but as the community grows, and other corporations plan their product releases around MeeGo, you will find some pretty angry managers showing up in your back channels with complaints about broken software. Jeremiah _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
