OBS/Community OBS

The Community OBS is:

• for building standalone applications to run on MeeGo
• for building standalone applications to run on the Fremantle and Harmattan distributions
• to collaborate on larger projects that are not in MeeGo core; eg ruby, KDE
• a place to build packages that may make their way into MeeGo Core; a staging ground
• a place to retire packages that are deprecated from MeeGo Core
• to build versions of MeeGo which differ from the official releases; eg MeeGo for generic x86; packages to support alternate graphic drivers

More about the MBS, License restrictions, policy, links to bugzilla etc

Management Team

The Community OBS is currently managed by:

• lbt / David Greaves
• X-fade / Niels Breet
• Jaffa / Andrew Flegg

In other words they do the work to keep it running, fix problems and make policy decisions.

Development Areas

There are several project areas on the community OBS:

• home:
• Apps:
• Project:
• MeeGo:
• Fremantle:

Each project can have subprojects and packages; the packages can be built against various targets and published in repositories.

home: areas

Each user has a home:<username> area and it is up to them how to structure the area underneath. home:<username> areas are created automatically for each user.

Apps: areas

The Apps: project is used to manage user-facing applications that have passed through the MeeGo Community Apps QA process. These packages will be available from the community app-store.

This is a lot like the Maemo Extras area (and will probably integrate with it in the future).

The Apps: area will only be accessed via a promotion and QA process.

Project: areas

Project: areas provide a staging and release area for development work that does not fit into the Apps: section.

This may be because they want an individual repository or there may be a project specific QA and release process.

The process for obtaining a Project: area is to talk to the OBS team (above) and explain why you need one. Typically you should have a list of admins and maintainers and a policy for managing roles, if appropriate explain any relationship with upstream (eg Project:KDE would probably only be approved for a group who had some kind of relationship with the main KDE project). There should be documentation about the purpose of the project and the usual notes on mailing lists, VC systems etc.

There is a list of Community OBS Project Areas

(nb these were originally called 'Team:' areas but 'Project:' seems to be a better name.)

MeeGo: areas

The MeeGo areas are where snapshots of MeeGo releases are available to build against.

Different targets are available with various architectures and subsets of packages.

In general applications should be building against a MeeGo release or a MeeGo:Surrounds release

• MeeGo:1.0 : For historical purposes only.
• MeeGo:1.1 : Latest stable MeeGo release (as of Mar/2011). Available build targets:
  • MeeGo:1.1:Core
  • MeeGo:1.1:Handset
  • MeeGo:1.1:IVI
  • MeeGo:1.1:Netbook
• MeeGo:1.1:Surrounds:1.0 : Not yet available
• MeeGo:current : A weekly import of MeeGo:Trunk. Please note that having this as a target will cause your code/binaries to be rebuilt whenever a new snapshot appears. This may cause breakage.

Fremantle: areas

The Fremantle areas are where snapshots of Fremantle releases are available to build against. This area was approved as a way to support the Maemo community in transitioning to MeeGo.

Harmattan: areas

The Harmattan areas are where snapshots of Harmattan releases will be available to build against. This area was approved as a way to support the Maemo community in transitioning to MeeGo.