Let's set Assignee for Fixed JIRAs

[Sean Owen <so...@cloudera.com>]

Following my comment earlier that "I think we set Assignee for Fixed
JIRAs consistently", I found there are actually 880 counter examples.
Lots of them are old, and I'll try to fix as many that are recent (for
the 1.4.0 release credits) as I can stand to click through.

Let's set Assignee after resolving consistently though. In various
ways I've heard that people do really like the bit of credit, and I
don't think anybody disputed setting Assignee *after* it was resolved
as a way of giving credit.

People who know they're missing a credit are welcome to ping me
directly to get it fixed.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@spark.apache.org
For additional commands, e-mail: dev-help@spark.apache.org

Re: Let's set Assignee for Fixed JIRAs

[Sean Owen <so...@cloudera.com>]

Permission to change project roles is restricted to admins / PMC,
naturally. I don't know if it's documented beyond this that Gavin
helpfully pasted:
https://cwiki.apache.org/confluence/display/SPARK/Jira+Permissions+Scheme

Another option is to make the list of people who you can assign to
include "Anyone". You'd get all of Apache in the list, so I assume
that's why it isn't the default, but might be the easier thing at this
point in Spark. I had to add 6 new people just now while assigning ~40
JIRAs.

On Thu, Apr 23, 2015 at 9:08 PM, Luciano Resende <lu...@gmail.com> wrote:
>
> On Thu, Apr 23, 2015 at 5:47 PM, Hari Shreedharan
> <hs...@cloudera.com> wrote:
>>
>> You’d need to add them as a contributor in the JIRA admin page. Once you
>> do that, you should be able to assign the jira to that person
>>
>>
>
> Is this documented, and does every PMC (or committer) have access to do that
> ?
>
>>
>>
>>
>> Thanks, Hari
>>
>> On Thu, Apr 23, 2015 at 5:33 PM, Shivaram Venkataraman
>> <sh...@eecs.berkeley.edu> wrote:
>>
>> > A related question that has affected me in the past: If we get a PR from
>> > a
>> > new developer I sometimes find that I am not able to assign an issue to
>> > them after merging the PR. Is there a process we need follow to get new
>> > contributors on to a particular group in JIRA ? Or does it somehow
>> > happen
>> > automatically ?
>> > Thanks
>> > Shivaram
>> > On Thu, Apr 23, 2015 at 5:26 PM, Sean Owen <so...@cloudera.com> wrote:
>> >> Following my comment earlier that "I think we set Assignee for Fixed
>> >> JIRAs consistently", I found there are actually 880 counter examples.
>> >> Lots of them are old, and I'll try to fix as many that are recent (for
>> >> the 1.4.0 release credits) as I can stand to click through.
>> >>
>> >> Let's set Assignee after resolving consistently though. In various
>> >> ways I've heard that people do really like the bit of credit, and I
>> >> don't think anybody disputed setting Assignee *after* it was resolved
>> >> as a way of giving credit.
>> >>
>> >> People who know they're missing a credit are welcome to ping me
>> >> directly to get it fixed.
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@spark.apache.org
>> >> For additional commands, e-mail: dev-help@spark.apache.org
>> >>
>> >>
>
>
>
>
> --
> Luciano Resende
> http://people.apache.org/~lresende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@spark.apache.org
For additional commands, e-mail: dev-help@spark.apache.org

Re: Let's set Assignee for Fixed JIRAs

[Luciano Resende <lu...@gmail.com>]

On Thu, Apr 23, 2015 at 5:47 PM, Hari Shreedharan <hshreedharan@cloudera.com
> wrote:

> You’d need to add them as a contributor in the JIRA admin page. Once you
> do that, you should be able to assign the jira to that person
>
>
>
Is this documented, and does every PMC (or committer) have access to do
that ?


>
>
> Thanks, Hari
>
> On Thu, Apr 23, 2015 at 5:33 PM, Shivaram Venkataraman
> <sh...@eecs.berkeley.edu> wrote:
>
> > A related question that has affected me in the past: If we get a PR from
> a
> > new developer I sometimes find that I am not able to assign an issue to
> > them after merging the PR. Is there a process we need follow to get new
> > contributors on to a particular group in JIRA ? Or does it somehow happen
> > automatically ?
> > Thanks
> > Shivaram
> > On Thu, Apr 23, 2015 at 5:26 PM, Sean Owen <so...@cloudera.com> wrote:
> >> Following my comment earlier that "I think we set Assignee for Fixed
> >> JIRAs consistently", I found there are actually 880 counter examples.
> >> Lots of them are old, and I'll try to fix as many that are recent (for
> >> the 1.4.0 release credits) as I can stand to click through.
> >>
> >> Let's set Assignee after resolving consistently though. In various
> >> ways I've heard that people do really like the bit of credit, and I
> >> don't think anybody disputed setting Assignee *after* it was resolved
> >> as a way of giving credit.
> >>
> >> People who know they're missing a credit are welcome to ping me
> >> directly to get it fixed.
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@spark.apache.org
> >> For additional commands, e-mail: dev-help@spark.apache.org
> >>
> >>
>



-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Let's set Assignee for Fixed JIRAs

[Hari Shreedharan <hs...@cloudera.com>]

You’d need to add them as a contributor in the JIRA admin page. Once you do that, you should be able to assign the jira to that person




Thanks, Hari

On Thu, Apr 23, 2015 at 5:33 PM, Shivaram Venkataraman
<sh...@eecs.berkeley.edu> wrote:

> A related question that has affected me in the past: If we get a PR from a
> new developer I sometimes find that I am not able to assign an issue to
> them after merging the PR. Is there a process we need follow to get new
> contributors on to a particular group in JIRA ? Or does it somehow happen
> automatically ?
> Thanks
> Shivaram
> On Thu, Apr 23, 2015 at 5:26 PM, Sean Owen <so...@cloudera.com> wrote:
>> Following my comment earlier that "I think we set Assignee for Fixed
>> JIRAs consistently", I found there are actually 880 counter examples.
>> Lots of them are old, and I'll try to fix as many that are recent (for
>> the 1.4.0 release credits) as I can stand to click through.
>>
>> Let's set Assignee after resolving consistently though. In various
>> ways I've heard that people do really like the bit of credit, and I
>> don't think anybody disputed setting Assignee *after* it was resolved
>> as a way of giving credit.
>>
>> People who know they're missing a credit are welcome to ping me
>> directly to get it fixed.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@spark.apache.org
>> For additional commands, e-mail: dev-help@spark.apache.org
>>
>>

Re: Let's set Assignee for Fixed JIRAs

[Shivaram Venkataraman <sh...@eecs.berkeley.edu>]

A related question that has affected me in the past: If we get a PR from a
new developer I sometimes find that I am not able to assign an issue to
them after merging the PR. Is there a process we need follow to get new
contributors on to a particular group in JIRA ? Or does it somehow happen
automatically ?

Thanks
Shivaram

On Thu, Apr 23, 2015 at 5:26 PM, Sean Owen <so...@cloudera.com> wrote:

> Following my comment earlier that "I think we set Assignee for Fixed
> JIRAs consistently", I found there are actually 880 counter examples.
> Lots of them are old, and I'll try to fix as many that are recent (for
> the 1.4.0 release credits) as I can stand to click through.
>
> Let's set Assignee after resolving consistently though. In various
> ways I've heard that people do really like the bit of credit, and I
> don't think anybody disputed setting Assignee *after* it was resolved
> as a way of giving credit.
>
> People who know they're missing a credit are welcome to ping me
> directly to get it fixed.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@spark.apache.org
> For additional commands, e-mail: dev-help@spark.apache.org
>
>

Re: Let's set Assignee for Fixed JIRAs

[Luciano Resende <lu...@gmail.com>]

On Thu, Apr 23, 2015 at 5:26 PM, Sean Owen <so...@cloudera.com> wrote:

> Following my comment earlier that "I think we set Assignee for Fixed
> JIRAs consistently", I found there are actually 880 counter examples.
> Lots of them are old, and I'll try to fix as many that are recent (for
> the 1.4.0 release credits) as I can stand to click through.
>
> Let's set Assignee after resolving consistently though. In various
> ways I've heard that people do really like the bit of credit, and I
> don't think anybody disputed setting Assignee *after* it was resolved
> as a way of giving credit.
>
> People who know they're missing a credit are welcome to ping me
> directly to get it fixed.
>
>
>
+1, this will help with giving people the "bit of credit", but I guess it
also helps on recognizing the community contributors towards becoming
committers much easier.



-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/