(→Apps: Link to proposed criteria) |
(→Accessing Apps) |
||
| (20 intermediate revisions not shown) | |||
| 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]]. The LF have refused to allow 'apps' in the meego.com namespace; the [[/Problem Statement|problem statement]] tries to explain more. | |
| - | + | ||
| - | = | + | = Accessing Apps = |
| - | + | * [http://apps.formeego.org Apps for MeeGo web interface] | |
| + | * [http://apps.formeego.org/ocs/providers.xml Open Collaboration Services (OCS) API provider file for Apps] | ||
| + | * [http://gitorious.org/meego-community-extras-client Client code in Gitorious] | ||
| + | * [http://github.com/nemein Server code on GitHub] | ||
| + | * [[MeeGo_Apps/Packaging]] Packaging guidelines. | ||
| - | + | = 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 | + | 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. 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]] | ||
| + | * [[MeeGo_Apps/repositories|Repository layout description]] | ||
| - | + | = Community Apps Team = | |
| - | * | + | * Client Application: Martin Grimme |
| - | * | + | * Web Site: Niels Breet, Henri Bergius, Ferenc Szekely |
| - | * | + | * OCS Interface: Niels Breet, Henri Bergius, Ferenc Szekely |
| - | * | + | * Build Service: Niels Breet, David Greaves |
| + | * Graphics, design: Istvan Jozsa | ||
| - | + | == Community Apps Volunteer Team == | |
| - | * | + | * Graphics: Tim Samoff |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | == Team Communication Channels == | |
| + | * Use the [http://lists.meego.com/listinfo/meego-community MeeGo-Community Mailing List] for questions and discussion. | ||
| + | * File bugs in the [https://bugs.meego.com/enter_bug.cgi?product=Community%20Apps Community Apps Component] | ||
| + | * Ask questions in the #meego IRC Channel | ||
| - | + | = Plans and Schedule = | |
| - | + | Working on: | |
| - | + | W26: | |
| + | * Automatic import/delete packages in MeeGo Apps by BOSS participant signaling (niels) | ||
| + | * OCS interface additions: commenting and voting (ferenc/henri) | ||
| + | * List apps in testing queue (ferenc) | ||
| + | * QA result signaling to BOSS (niels/david) | ||
| + | * Configure Apps build targets in OBS, cleanup old build targets (niels) | ||
| + | * Document Apps submit process (niels) | ||
| - | + | Open issues (help appreciated): | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | Documentation: | |
| - | + | * Document QA process | |
| - | + | Design: | |
| - | * | + | * Front page design (Mike?/Tim) |
| - | * | + | * Icons for App categories |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
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. The LF have refused to allow 'apps' in the meego.com namespace; the problem statement tries to explain more.
Contents |
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. 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.
Working on:
W26:
Open issues (help appreciated):
Documentation:
Design: