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

[Rob Lanphier]

Dale's got this roughly right.  I doubt we're going to be as draconian
as Iridium is letting on, but the point is: please don't abuse the new
tool we're putting in your hands.  And, if Iridium does deem it
necessary to pull out the can of whip-ass, consider yourself warned.

Could someone volunteer to capture this somewhere on the wiki?  I'm
happy to review for accuracy.

Rob

On 9/6/07 4:35 AM, 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.
>
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Click here to unsubscribe or manage your list subscription:
> /index.html
>   


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 249 bytes
Desc: OpenPGP digital signature
Url : http://lists.secondlife.com/pipermail/sldev/attachments/20070906/f6f2a94b/signature.pgp