[sldev] [META] *IMPORTANT* New PJIRA Perms

[Iridium Linden]

Lindens will NOT assign JIRA tasks to Open Source contributors without 
explicit consent. We expect the same courtesy. In that vein, I'm 
assuming that Open Source contributors will not assign tasks to other 
Open Source contributors without consent. The purpose of this move on 
our part is to allow Open Source contributors to make their work more 
transparent in JIRA. If you are working on a patch, it makes sense that 
you should be able to indicate progress. Assigning an issue to yourself 
will inform Lindens and your peers of that work in progress or your 
forthcoming contribution.

So:
1) Lindens will not assign tasks to OS contributors without consent.
2) OS contributors should not assign tasks to other OS contributors 
without consent.
3) OS contributors must not assign tasks to Lindens without consent.
These permissions are intended to give OS contributors the power to 
assign tasks to themselves as an effort to indicate work in progress or 
forthcoming commitment to a patch.

Iridium

Dale Glass wrote:
> On Thu, Sep 06, 2007 at 08:04:44PM +0900, Alissa Sabre wrote:
>   
>> Just to making sure.
>>
>>     
>>> a) These permissions were introduced so that Open Source Contributors 
>>> could assign JIRA tasks to *themselves* in order to show that work is in 
>>> progress.
>>> b) These permissions also allow you to assign tasks to Lindens.
>>> c) *If you assign a JIRA task to a Linden without the explicit consent 
>>> of that Linden, you will immediately be ejected from the group and your 
>>> permissions thusly lost.
>>>       
>> That means:
>>
>> - An Open Souece Contributor may assign a taks to another Open Source
>>   Contributor.
>> - A Linden may assign a task to another Linden.
>> - A Linden may assign a taks to an Open Source Contributor.
>> - An Open Source Contributor *must*not* assign a task to a Linden.
>>
>> Am I correct?
>>     
>
> My reading is:
>
> The rules are:
>
> * A contributor may assign bugs to themselves
> * A contributor MAY NOT assign bugs to a Linden without their consent
>
> Speculation:
>
> Rules for Lindens are unclear, but that's an internal matter between
> them an LL. My guess is that Lindens can assign bugs to each other and
> consent will be there pretty much all the time, although we won't see
> them discuss it on the list.
>
> Whether Lindens can assign bugs to residents is undefined as well. My
> guess is that it may be allowed, but they probably won't do it, unless
> at some point a contributor for example declares themselves and is
> accepted as the maintainer of a part of the code (eg, if my avatar
> scanner gets merged and I say I'm willing to do it, maybe they'll
> start assigning its bugs to me)
>
> It's not specified whether assigning a bug to another contributor is
> allowed. My guess is that it also requires consent and there may be 
> consequences if you do it without permission and the one you assigned
> it to complains.
>
>
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/sldev/attachments/20070906/52794948/attachment.htm