Makes sense, +1 Carsten
Am 06.05.15 um 15:31 schrieb Robert Munteanu: > Hi, > > I took a look at the Jira roles that we have set up for the SLING > project.The situation looks roughly like this: > > - Administrators: most members of the PMC ( missing 6 ), some committers ( 4 ) > - Committers: a few members of the PMC, some committers ( missing 4 ) > + the sling-developers group > > Given that we mostly use the extra Administrators group to allow > administration of the project in relation to release management, I > would suggest the following setup. > > a) Remove all user entries from the Administrators and Committers group. > b) Add the sling-developers group as Administrators. > > The advantage is that we have a setup which allows committers to > handle as much of release management work by default. This of course > assumes that: > > 1. We feel comfortable with allowing all committers administrator > permission for the project > 2. The sling-developers group actually contains all sling committers > > For the record, these are the extra permissions that the > Administrators group has: > > - Administer project: Ability to administer a project in JIRA. > - Move Issues: Ability to move issues between projects or between > workflows of the same project (if applicable). Note the user can only > move issues to a project he or she has the create permission for. > - Modify Reporter: Ability to modify the reporter when creating or > editing an issue. > - Delete Issues: Ability to delete issues. > - Edit All Comments: Ability to edit all comments made on issues. > - Delete All Comments: Ability to delete all comments made on issues. > - Delete All Attachments: Users with this permission may delete all > attachments. > > Thoughts? > > Cheers, > > Robert > -- Carsten Ziegeler Adobe Research Switzerland [email protected]
