Contents 1 MeeGo Extras 1.1 Process 1.2 Repositories 1.3 Promotion 1.3.1 Extras-testing 1.3.1.1 Automated tests 1.3.2 Extras 1.3.2.1 Automated tests 1.3.2.2 Community tests 1.4 Packaging

MeeGo Extras

[WIP]

MeeGo Extras is the repository where software created by the MeeGo community can be found. Developers can build their applications on the MeeGo Community OBS, a sofisticated build system. These applications can be published into the end-user facing Extras repository after certain conditions have been met.

Process

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 Extras 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 Extras-testing. The promotion request triggers some automated tests on the package (TBD). The Extras-testing repository is intended for stability testing and community QA. If the package meets all promotion criteria, it will be moved to the Extras repository. This makes it available for every end user with a MeeGo device, provided they have enabled the repository in their garage client.

Repositories

There will be multiple repositories for a certain MeeGo release. Let's use MeeGo 1.1 as an example:

• MeeGo:1.1:Extras This targets MeeGo 1.1 Core. This means that applications in this repository can only have dependencies on MeeGo 1.1 Core and the repository itself.
• MeeGo:1.1:Extras:Handset This targets MeeGo 1.1 Core and MeeGo 1.1 Handset UX.
• MeeGo:1.1:Extras:IVI This targets MeeGo 1.1 Core and MeeGo 1.1 IVI UX.
• MeeGo:1.1:Extras:Netbook This targets MeeGo 1.1 Core and MeeGo 1.1 Netbook UX.

• 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:Handset This repository targets Handset UX
• MeeGo:1.1:Surrounds:IVI This repository targets IVI UX
• MeeGo:1.1:Surrounds:Netbook This repository targets Netbook UX

Promotion

Following rules are proposed to be a starting point of QA and sanity checking. They are up for discussion and not final. These checks will be carried out before the package reaches the target repository.

Extras-testing

Automated tests

• Does package name already exist in repository
  • If yes: Check if owner
• Are all dependencies available in the repository or it's parents.
• Does it build against Extras-testing
• Does the package have a description

Extras

Automated tests

Extras-testing tests plus:

• Does it build against Extras
• Is it an application
  • If yes: Is there at least one screenshot in the OBS package files
• Does the package have 5 positive votes from community testers
• 10 day quarantine period.

Community tests

• Proper description
• Does it have an icon
• Does it install/uninstall correctly
• Does it run

Packaging

Any package in the Extras repositories must follow the Packaging/Guidelines. A package will be checked against these guidelines before promotion to Extras-testing.