(→Teams) |
(→Teams) |
||
| Line 39: | Line 39: | ||
Groups of developers can form a team to help manage collaborator rights within repositories. As with a repository, a team has individuals who are designated as "admins" and control who is a member of their team. It is up to the team admins to control their own membership to the team, which will translate into repository rights. Be sure to understand fully the repositories your team has access rights to, so you are not adding members to a team who shouldn't have access to a particular repository. | Groups of developers can form a team to help manage collaborator rights within repositories. As with a repository, a team has individuals who are designated as "admins" and control who is a member of their team. It is up to the team admins to control their own membership to the team, which will translate into repository rights. Be sure to understand fully the repositories your team has access rights to, so you are not adding members to a team who shouldn't have access to a particular repository. | ||
| - | + | '''Creating Teams''' | |
Anyone can create a team and add members to it. No special permissions are required. | Anyone can create a team and add members to it. No special permissions are required. | ||
| - | + | '''Requesting to be added to a team''' | |
As with repositories, contact the individuals in a team who are designated "admins" to be added to a particular team. It is up to the team admins to then determine if you should be added. | As with repositories, contact the individuals in a team who are designated "admins" to be added to a particular team. It is up to the team admins to then determine if you should be added. | ||
| - | + | '''Teams listed at http://meego.gitorious.org''' | |
Teams working on particular meego repositories will show up on the http://meego.gitorious.org landing page under the "Teams involved in MeeGo projects". This list is automatically created based on team activity in the meego repositories. | Teams working on particular meego repositories will show up on the http://meego.gitorious.org landing page under the "Teams involved in MeeGo projects". This list is automatically created based on team activity in the meego repositories. | ||
== Merge Requests == | == Merge Requests == | ||
This page details the best practices for MeeGo community members working within the Gitorious code repositories.
Contents |
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:
Example: http://bugs.meego.com/show_bug.cgi?id=6239
When each repository is created it should have a person or team designated as the owner or admin. This individual or team has the ability to administer their own repository, including adding collaborators. Individuals or teams can be added to the repository from the committership page and be given Read, Commit, or Admin rights. Example: http://meego.gitorious.org/meego-handset-ux/meego-handset-dialer/committerships
It is up to the admin to determine their collaborators list and maintain it.
To get added to the collaborators list in a particular repository, contact the individual who has admin rights in that repository. Gitorious allows you to send messages directly within it's interface to any other user by visiting their page and selecting the "Send Message" button.
Groups of developers can form a team to help manage collaborator rights within repositories. As with a repository, a team has individuals who are designated as "admins" and control who is a member of their team. It is up to the team admins to control their own membership to the team, which will translate into repository rights. Be sure to understand fully the repositories your team has access rights to, so you are not adding members to a team who shouldn't have access to a particular repository.
Creating Teams Anyone can create a team and add members to it. No special permissions are required.
Requesting to be added to a team As with repositories, contact the individuals in a team who are designated "admins" to be added to a particular team. It is up to the team admins to then determine if you should be added.
Teams listed at http://meego.gitorious.org Teams working on particular meego repositories will show up on the http://meego.gitorious.org landing page under the "Teams involved in MeeGo projects". This list is automatically created based on team activity in the meego repositories.