Latest revision as of 13:11, 3 April 2013

Mer source is in kept in git

[edit] Services

• gitweb view here: http://gitweb.merproject.org/gitweb
• anonymous git clones can be done from http://review.merproject.org/p/<area>/<package>.git
• gerrit at https://review.merproject.org/

We will be moving to gitlab 'soon'.

[edit] Project areas

There are a number of project areas.

[edit] mer-core

The source for the actual packages in a Mer base system live here.

[edit] mer-crosshelpers

Packages somewhat related to cross compile (ie, don't exist in the x86 port) go in here

When Mer moves to Scratchbox2, the approach to cross-compilation that requires these packages will be deprecated.

[edit] mer-tools

Mer's [Platform SDK] and [QA] projects use the tools managed in this area.

[edit] mer

This area contains:

[edit] boss-workflow

The code used by the Mer project automation systems. This includes the code for the QA checks run when changes are submitted to Core.

[edit] project-core

This area essentially describes the core. It contains configuration for the OBS and other build tools used to build Mer. This includes:

• OBS prjconfig
• A snapshot of the packages in the core.
• Repository pattern / group definitions used in kickstarts (see Kickstart groups) are in /patterns/
• scripts used when releasing or exchanging Mer

[edit] release-tools

The Mer Delivery System lives here.

[edit] MINT

Currently kept at https://github.com/Merproject/

[edit] Contribution

Contributions to any part of Mer source is welcome.

[edit] Upstream

Mer does not currently track upstream sources but there is a bug about that: https://bugs.merproject.org/show_bug.cgi?id=97

[edit] Management

Mer uses gerrit to manage the git repositories.