(Difference between revisions)
|
|
| Line 21: |
Line 21: |
| | [http://mer-l-in.blogspot.com/2011/01/meego-community-development-apps.html This blog post] attempts to summarise the position as at Jan 2011. The content is intended to be used as a basis for discussion and is being wikified. | | [http://mer-l-in.blogspot.com/2011/01/meego-community-development-apps.html This blog post] attempts to summarise the position as at Jan 2011. The content is intended to be used as a basis for discussion and is being wikified. |
| | | | |
| - | * [[Community Office/Task Forces/MeeGo Surrounds and Extras/Apps|Apps]] covers the area around the MeeGo Apps store | + | * [[Community Office/Task Forces/MeeGo Surrounds and Apps/Apps|Apps]] covers the area around the MeeGo Apps store |
| - | * [[Community Office/Task Forces/MeeGo Surrounds and Extras/OBS|OBS]] is about the OBS and policies and technology there | + | * [[Community Office/Task Forces/MeeGo Surrounds and Apps/OBS|OBS]] is about the OBS and policies and technology there |
| - | * [[Community Office/Task Forces/MeeGo Surrounds and Extras/Surrounds|Surrounds]] discusses the idea of how typical opensource code sharing can be managed in a distro-like manner around MeeGo. | + | * [[Community Office/Task Forces/MeeGo Surrounds and Apps/Surrounds|Surrounds]] discusses the idea of how typical opensource code sharing can be managed in a distro-like manner around MeeGo. |
Revision as of 17:36, 13 February 2011
MISSION
- To ensure a vibrant and quality area for community open source software.
- To have at least one repository which contains software of such quality that vendors (such as Nokia[2]) who would be willing to ship it enabled on devices out-of-the-box.
- To work towards having applications within the community repositories be able to be classed as "MeeGo Compliant".
SCOPE
- Management of the community OBS, the repositories it hosts, and the packages contained within it.
- Policies and procedures (including QA) governing the repositories.
- Align policies where possible, to ease the path for packages from the community repositories to the MeeGo trunk as well as application stores such as Ovi or AppUp.
- Work with the compliance folks on an approach acceptable to all on third-party software compliance[3]
TEAM
- Niels Breet (X-Fade)
- David Greaves (lbt)
- TBC (a MeeGo architect)
- TBC (a developer, like Graham Cobb/Shane Bryan/so many others)
- TBC (someone to help with the work ;-))
Initial Steps
This blog post attempts to summarise the position as at Jan 2011. The content is intended to be used as a basis for discussion and is being wikified.
- Apps covers the area around the MeeGo Apps store
- OBS is about the OBS and policies and technology there
- Surrounds discusses the idea of how typical opensource code sharing can be managed in a distro-like manner around MeeGo.