[JEG] Fwd: Re: [Development] Changes to the Jira roles and workflow

[marius.storm-olsen at nokia.com]

Hi Jira Expert Group,

A whole month has now passed since the last comment was made on this 
thread, and I think therefore it is time to take action on the items 
mentioned in that thread.

AFAIK there has not been elected a JEG lead, so I was hoping that 
someone would step up to that task, and sum up a conclusion on the 
initial proposal + corrections/amendments from the discussions on 
development at qt-project.org.

Then the next step would be to hand over the final implementation 
document to a Nokia representative which would facilitate the 
implementation.

So please, can someone on this list take the lead on this?

-- 
.marius


-------- Original Message --------
Subject: 	Re: [Development] Changes to the Jira roles and workflow
Date: 	Mon, 13 Feb 2012 19:55:37 +0000
From: 	ext marius.storm-olsen at nokia.com <marius.storm-olsen at nokia.com>
To: 	<development at qt-project.org>



On 02/13/2012 01:27 PM, ext shane.kearns at accenture.com wrote:
> Maybe you're looking at a"triage"  role, if the role is prioritizing and assigning of tasks among a team that is mostly funded by one company.
>
> Another role we need in JIRA is"contributor".
> This is somebody who is not a reviewer, but can still be assigned tasks&  transition their assigned tasks through the normal workflow.
> Ideally, anyone who has had a patch accepted should be given this level of access if they want it.*
> For example, to work on bugs related to code they previously submitted.
> Also, this covers most Nokia (or other organization) engineers who are not approvers.

The "contributor" role in Jira was part of the original recommendation:

*Map old roles over to OG roles*

The current suggestion is:

Reports -> User
Developer -> Contributor
Assignee -> Contributor
QA -> Approvers
RM -> Maintainers*<- note, discussion over this
*

Note the "Developer" + "Assignee" -> "Contributor" transition in the
roles, meaning that the "Contributor" role can be assigned tasks.

-- 
.marius

> I'm hoping abuse of JIRA privileges is rare, but it should also be easy to revoke them if needed.
>
> *Some people will contribute a patch for a bug they found in their project that uses Qt, and we don't want to discourage this by giving unwanted responsibility.


-- 
.marius

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Attached Message Part
Url: http://lists.qt-project.org/pipermail/jeg/attachments/20120313/55d31716/attachment.pl