The role of MeeGo working groups are explained at http://meego.com/about/governance
This is a request to the Technical Steering Group to approve the creation of a Repository working group. There is no procedure defined but we can can improvise with some common sense.
To set the context: like most linux distros, Meego will inevitably consist of "Meego supported packages" and "Community supported packages" this proposal is about the latter.
The (so far un-official) Repository Working Group (RWG) held its first meeting on Sunday, 21. March 2010.
Nb It has been suggested that the name is not quite right - maybe "Community Repository WG"... but since Meego aims to be a community project then phrases like Non-Core or Unsupported or "Surrounding Repository WG". At this point lets focus on the objective, not the name.
The Repository Working Group (RWG) would define and oversee implementation of the strategy for publishing community created software with the MeeGo project.
The goal of the RWG would be to unite the various community contributions interested in applications & libraries, packaging, policy, QA processes, building, etc.
We realise this is a wide scope but feel it should have coherent representation in the community.
We propose 3 sub-groups to cover:
The nature of this area means it would likely form a gateway to the inclusion of packages in Meego Core and a community maintainable location for packages removed from the Core.
The proposed repositories would cover distinct areas:
This area would provide a home for more discrete applications with individual release cycles. This brings something equivalent to the maemo.org Extras repository to MeeGo.
Meego plans to be a 1st class distro and should not prevent packages from being made available. Cf MeeGo:Universe and MOTU. Surrounds therefore provides a more coherent set of inter-related or depended-upon libraries and applications. The entire collection would follow the same release cycle (which may be the same as MeeGo core). The surrounds area would probably support historical releases of Meego for situations where vendors didn't provide updates for devices.
It may make sense for the Surrounds area to establish relationships (close, arms-length, formal or informal) to maintainers in other community distros to share the burden of maintaining some packages.
Policy would cover:
This WG area would also provide a support function for other teams and workgroups.
MeeGo members interested in taking an active role in this working group. Please detail your interests and what you can contribute to the group:
The initial representatives are: lbt (David Greaves) and th0br0 (Andreas Osowski)
Volunteer to work in a particular area, participate constructively in conversations and help develop code, docs, processes or community spirit... Add your name to the list above and dive in - this is a community project. As usual, respect the status quo until you understand why it exists - but then feel free to offer constructive criticism.
Feel free to ask for help on irc, the mailing lists or the forums.