The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)
Source
Mer source is in kept in git
Contents |
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'.
Project areas
There are a number of project areas.
mer-core
The source for the actual packages in a Mer base system live here.
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.
mer-tools
Mer's [Platform SDK] and [QA] projects use the tools managed in this area.
mer
This area contains:
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.
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
release-tools
The Mer Delivery System lives here.
MINT
Currently kept at https://github.com/Merproject/
Contribution
Contributions to any part of Mer source is welcome.
Upstream
Mer does not currently track upstream sources but there is a bug about that: https://bugs.merproject.org/show_bug.cgi?id=97
Management
Mer uses gerrit to manage the git repositories.