m (→How to contribute) |
|||
| Line 5: | Line 5: | ||
=== Announcement === | === Announcement === | ||
| - | + | The (so far un-official) Repository Working Group (RWG) held its [http://meego.mkdir.name/logs/meego-meeting/2010/meego-meeting.2010-03-21-20.02.html first meeting on Sunday, 21. March 2010]. | |
| - | + | ||
=== How to contribute === | === How to contribute === | ||
| Line 13: | Line 13: | ||
=== Mission === | === Mission === | ||
| - | The | + | 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: | ||
| + | * Repository: take responsibility for maintaining the applications repository, the community supported packages repository (cf Ubuntu Universe) and associated QA and policies for MeeGo, | ||
| + | * Build: support administrative implementation with the Build System team in coordination with these goals, | ||
| + | * Document: take responsibility for the MeeGo community packaging documentation | ||
| + | |||
| + | 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. | ||
=== Areas === | === Areas === | ||
| - | The | + | The proposed repositories would cover distinct areas: |
| - | * ''' | + | * '''Applications repository''' |
| - | * ''' | + | 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 Surrounds repository''' | ||
| + | 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: | ||
| + | * '''Community Package QA''': Quality Assurance on packages. | ||
* '''Packaging policy''': Define a clear packaging policy for MeeGo, and keeping the packaging system open to the community | * '''Packaging policy''': Define a clear packaging policy for MeeGo, and keeping the packaging system open to the community | ||
* '''Package maintaining''': Provide an interface for maintainers of a package to maintain their package. | * '''Package maintaining''': Provide an interface for maintainers of a package to maintain their package. | ||
* '''Documentation''': Document package contribution, creation and maintenance. | * '''Documentation''': Document package contribution, creation and maintenance. | ||
| + | * '''Managing dependencies''': Make sure dependencies for user applications are maintained by maintainers. The 'Surrounds' area will prevent developers from having to maintain their whole dependency chain. | ||
| - | + | This WG area would also provide a support function for other teams and workgroups. | |
| - | + | ||
=== Contributors === | === Contributors === | ||
| Line 42: | Line 63: | ||
* [http://meego.com/users/clay Clay Carey/Clay] - Moblin community member. Interested in helping with packaging | * [http://meego.com/users/clay Clay Carey/Clay] - Moblin community member. Interested in helping with packaging | ||
* [http://meego.com/users/clintcan Clint Christopher Cañada/clintcan] - Uses Moblin extensively on his netbook. Helped a little bit in introducing [http://apt4rpm.sourceforge.net apt4rpm] to [http://www.alinux.tv aLinux] a few years ago through [http://pnutproject.org pnutproject]. Also set up a small repo of Moblin and CentOS packages at [http://ostalks.com ostalks.com]. Interested in helping out with packaging. | * [http://meego.com/users/clintcan Clint Christopher Cañada/clintcan] - Uses Moblin extensively on his netbook. Helped a little bit in introducing [http://apt4rpm.sourceforge.net apt4rpm] to [http://www.alinux.tv aLinux] a few years ago through [http://pnutproject.org pnutproject]. Also set up a small repo of Moblin and CentOS packages at [http://ostalks.com ostalks.com]. Interested in helping out with packaging. | ||
| + | |||
| + | |||
| + | The initial representatives are: lbt (David Greaves) and th0br0 (Andreas Osowski) | ||
[[Category:Community]] | [[Category:Community]] | ||
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.
Contents |
The (so far un-official) Repository Working Group (RWG) held its first meeting on Sunday, 21. March 2010.
Please expand.
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)