diff options
| author | Fredrik Luthander <fredrik.luthander@sonymobile.com> | 2012-01-31 14:42:36 +0100 |
|---|---|---|
| committer | Gustaf Lundh <gustaf.lundh@sonymobile.com> | 2012-03-29 17:36:35 +0200 |
| commit | fd6f4f26f9d7b2ef4af4bfbcb4ec9c564f93c6ab (patch) | |
| tree | 05266c6b76d264e4367edcb09bfb5d4d5d8844dc | |
| parent | f78d65bef4cab60c517e241b25d85a44ea1dde89 (diff) | |
Access control documentation: Developer example role
The developer role has rights to block and approve as well as submit
changes to the project. It's a pretty powerful role as it also allows
pushing by the review step if the developer so wishes.
Change-Id: I5ad6f84cf19f6c9b870a1117f4aba45b248ca05f
Signed-off-by: Fredrik Luthander <fredrik.luthander@sonyericsson.com>
Signed-off-by: Fredrik Luthander <fredrik.luthander@sonymobile.com>
| -rw-r--r-- | Documentation/access-control.txt | 36 |
1 files changed, 36 insertions, 0 deletions
diff --git a/Documentation/access-control.txt b/Documentation/access-control.txt index 70d645d12a..30a6c39dd6 100644 --- a/Documentation/access-control.txt +++ b/Documentation/access-control.txt @@ -805,6 +805,42 @@ Suggested access rights to grant: * <<category_label-Code-Review,`Code review`>> with range '-1' to '+1' +[[examples_developer]] +Developer +~~~~~~~~~ + +This is the typical core developer on a public server. They are able +to read the project, upload changes to a branch. They are allowed to +push merge commits to merge branches together. Also, they are allowed +to forge author identity, thus handling commits belonging to others +than themselves, effectively allowing them to transfer commits +between different branches. + +They are furthermore able to code review and verify commits, and +eventually submit them. If you have an automated CI system that +builds all uploaded patch sets you might want to skip the +verification rights for the developer and let the CI system do that +exclusively. + +Suggested access rights to grant: + +* <<category_read,`Read`>> on 'refs/heads/\*' and 'refs/tags/*' +* <<category_push,`Push`>> to 'refs/for/refs/heads/\*' and 'refs/changes/*' +* <<category_push_merge,`Push merge commit`>> to 'refs/for/refs/heads/\*' and 'refs/changes/*' +* <<category_forge_author,`Forge Author Identity`>> +* <<category_label-Code-Review,`Label: Code review`>> with range '-2' to '+2' +* <<category_label-Verified,`Label: Verify`>> with range '-1' to '+1' +* <<category_submit,`Submit`>> + +If the project is small or the developers are seasoned it might make +sense to give them the freedom to push commits directly to a branch. + +Optional access rights to grant: + +* <<category_push,`Push`>> to 'refs/heads/*' +* <<category_push_merge,`Push merge commit`>> to 'refs/heads/*' + + [[conversion_table]] Conversion table from 2.1.x series to 2.2.x series -------------------------------------------------- |