(→Apps: Link to proposed criteria) |
Dawnfoster (Talk | contribs) (Complete revamp of page) |
||
| Line 1: | Line 1: | ||
| - | + | MeeGo Community Apps is the repository where open source software created by the MeeGo community can be found. Developers can build their applications on the MeeGo Community OBS, a sophisticated build system. These applications can be published into the end-user facing Apps repository after certain conditions have been met. This project falls under the responsibility of the [[Community Office]]. | |
| - | + | ||
| - | = | + | = Community Apps Team = |
| - | + | * Lead Developer: Niels Breet | |
| + | * Client Application: Martin Grimme | ||
| + | * Web Site: Ferenc Szekely | ||
| + | * OCS Interface: Henri Bergius | ||
| + | * Build Service: David Greaves | ||
| - | == | + | = Plans and Schedule = |
| + | |||
| + | '''Henri & Neils to add''' | ||
| + | |||
| + | = Accessing Apps = | ||
| + | |||
| + | * [http://apps-beta.meego.com Apps Beta Web Interface] | ||
| + | * [gitorious.org/meego-community-extras-client Client code in Gitorious] | ||
| + | |||
| + | = Process = | ||
A developer will need to [[Build_Infrastructure/Community_Builder#Getting_Access|request access]] to the Community OBS. Once the account has been activated, the developer can create a 'home' project. Inside this project one can build packages against any project(repository) in the OBS. This allows the developer to build an application against the Apps repository and make sure there are no dependency issues or other problems. | A developer will need to [[Build_Infrastructure/Community_Builder#Getting_Access|request access]] to the Community OBS. Once the account has been activated, the developer can create a 'home' project. Inside this project one can build packages against any project(repository) in the OBS. This allows the developer to build an application against the Apps repository and make sure there are no dependency issues or other problems. | ||
| - | Once a developer determines that the application is ready for end-users, the package can be promoted to Apps-testing. The promotion request triggers some automated tests on the package (TBD). The Apps-testing repository is intended for stability testing and community QA. If the package meets all promotion criteria, it will be moved to the Apps repository. This makes it available for every end user with a MeeGo device, provided they have enabled the repository in their garage client. | + | Once a developer determines that the application is ready for end-users, the package can be promoted to Apps-testing. The promotion request triggers some automated tests on the package (TBD). The Apps-testing repository is intended for [[MeeGo Apps/QA|stability testing and community QA]]. If the package meets all promotion criteria, it will be moved to the Apps repository. This makes it available for every end user with a MeeGo device, provided they have enabled the repository in their garage client. |
| + | |||
| + | == Supporting Process References == | ||
| + | * [[Build_Infrastructure/Community_Builder#Getting_Access|Getting access to the Community OBS]] | ||
| + | * [[Packaging/Guidelines|Packaging Guidelines]] | ||
| + | * [[MeeGo Apps/QA|QA Process]] | ||
| - | = | + | = OLD CONTENT = |
| + | == Repositories - MOVE TO SUBPAGE == | ||
There will be multiple repositories for a certain MeeGo release. Let's use MeeGo 1.1 as an example: | There will be multiple repositories for a certain MeeGo release. Let's use MeeGo 1.1 as an example: | ||
| Line 32: | Line 50: | ||
*'''MeeGo:1.1:Surrounds''' This repository hosts libraries which are not included in MeeGo, but are a dependency for common Linux applications. | *'''MeeGo:1.1:Surrounds''' This repository hosts libraries which are not included in MeeGo, but are a dependency for common Linux applications. | ||
| - | |||
| - | + | === Apps-testing MOVE TO QA PAGE === | |
| - | + | ||
| - | === Apps-testing === | + | |
==== Automated tests ==== | ==== Automated tests ==== | ||
* Does package name already exist in repository | * Does package name already exist in repository | ||
| Line 43: | Line 58: | ||
* Does it build against Apps-testing | * Does it build against Apps-testing | ||
* Does the package have a description | * Does the package have a description | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
MeeGo Community Apps is the repository where open source software created by the MeeGo community can be found. Developers can build their applications on the MeeGo Community OBS, a sophisticated build system. These applications can be published into the end-user facing Apps repository after certain conditions have been met. This project falls under the responsibility of the Community Office.
Contents |
Henri & Neils to add
A developer will need to request access to the Community OBS. Once the account has been activated, the developer can create a 'home' project. Inside this project one can build packages against any project(repository) in the OBS. This allows the developer to build an application against the Apps repository and make sure there are no dependency issues or other problems.
Once a developer determines that the application is ready for end-users, the package can be promoted to Apps-testing. The promotion request triggers some automated tests on the package (TBD). The Apps-testing repository is intended for stability testing and community QA. If the package meets all promotion criteria, it will be moved to the Apps repository. This makes it available for every end user with a MeeGo device, provided they have enabled the repository in their garage client.
There will be multiple repositories for a certain MeeGo release. Let's use MeeGo 1.1 as an example:
Additionally there is Apps+
As a separate project there will be: