On Mon, 2011-01-03 at 19:34 +0000, ext Andrew Flegg wrote: > On Mon, Jan 3, 2011 at 12:55, <[email protected]> wrote: > > > > Andrew wrote: > >> I've been thinking about this as well. I think it's time to revise the > >> Community Repository Working Group idea again. > > > > Sure, just call it "team" instead of "working group" and put its work in > > the framework of the Community Office. > > Are you *sure* the CO is the right place?
What I'm sure is that it is better than no place. After months of intermittent discussions we have got no better conclusions. In the meantime the work related to community OBS-packages-apps is happening out of the MeeGo project channels and is difficult to trace, follow and get involved. As a matter of fact "Proposal for Community Application Support" (aka Apps, Surrounds, Packages, community OBS...) has been listed at http://wiki.meego.com/Community_Office#Tasks for ages. The team is elsewhere, though. > I view the Community Office > as the hub for community collaboration, websites, events, etc. Whereas > this is a lot more technical; impacts MeeGo's own repository process > and requires enough visibility within the project to discuss issues on > equal terms with the Compliance team (for example). We are talking about a set of tools and processes organized by the community independently from the Program Office and the Working Groups. The frontend is a web based catalog with high end user appeal under apps.meego.com. And yes, the links to Infrastructure, Compliance and SDK teams are many. Sounds like many of the things we organize in the Community Office. > > However, you're right - "working group" is the wrong term: it suggests > a project team to tackle a specific problem, whereas this is an > ongoing group who, certainly, have some immediate issues to face, but > should be in charge of the repos permanently. Fits in the CO. > > I believe this had been discussed and even agreed by Tero / David Niels? > > Publicly? If so, can you share a URL? Honestly, I don't recall where. Could be an email in this list, a fragment of #meego IRC chat, a bug report, a chat in the corridors of the MeeGo Conference... No big secret but casual discussion. > I remember having the feeling > that when it was first taken to the TSG the reaction was (perhaps, if > I'm being harsh, the now typical), "can you explain more and we'll > come back to it" and so I'm probably getting muddled between > proposals; acceptances etc. No, I'm talking about a soft agreement with David and/or Tero in the past months. As you can see my memory is not able to provide further details. Anyway, let's just discuss and decide something. We have started this discussion so many times and it would be nice to finish it. PS: Still waiting for the basic documentation and status updates traceable from http://wiki.meego.com/Marketing/Meego.com_1.2_update -- Quim _______________________________________________ MeeGo-community mailing list [email protected] http://lists.meego.com/listinfo/meego-community
