This page details the best practices for MeeGo community members working within the Gitorious code repositories.
Projects are the highest level organization within Gitorious and all MeeGo projects are listed on the http://meego.gitorious.org landing page. Projects in general are organized by the MeeGo architecture diagram. There are some deviations from this, but we are trying to align projects with the diagram as much as possible and have additional community support projects where needed.
If there is a need to add an additional project within http://meego.gitorious.org, submit a bug request: http://bugs.meego.com/enter_bug.cgi?product=meego.gitorious.org first. If it is determined that none of the existing MeeGo projects will serve your repository needs and the MeeGo project needs, then a new project can be added. After the project is created, a request is submitted to the Gitorious administrators who will flag the project to be listed at: http://meego.gitorious.org/.
Follow the steps above and detail why this project should be added.
Most projects are being named in a consistent way to help with search and clarity. New projects should be named with the MeeGo title at the beginning, in both the title and slug. Examples are:
Where projects are largely for organizing, repositories are where all the activity happens. Repositories can be created in any project and each have their own commit rights, merge configurations, and administration.
To add a repository to an existing project, submit a bug request at: http://bugs.meego.com/enter_bug.cgi?product=meego.gitorious.org. Please include the following details in your request:
Each repository should have a person or team designated as the owner or admin. This individual or team has the ability to completely administer their own repository once setup.