You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by Karthik Kambatla <ka...@cloudera.com> on 2014/05/12 21:03:26 UTC
#Contributors on JIRA
Hi devs
Looks like we ran over the max contributors allowed for a project, again. I
don't remember what we did last time and can't find it in my email either.
Can we bump up the number of contributors allowed? Otherwise, we might have
to remove some of the currently inactive contributors from the list?
Thanks
Karthik
Re: #Contributors on JIRA
Posted by Pete of Pete <pe...@gmail.com>.
Cheers Aaron!
All the best,
;-pete
On 16 May 2014 19:47, "Aaron T. Myers" <at...@cloudera.com> wrote:
> Hey Pete,
>
> The "contributor list" we're referring to is just the collection of folks
> in JIRA that JIRAs can be assigned to. It doesn't impact anyone's ability
> to follow JIRAs, just have new JIRAs assigned to them. It also doesn't do
> anything to JIRAs that are already assigned.
>
> --
> Aaron T. Myers
> Software Engineer, Cloudera
>
>
> On Thu, May 15, 2014 at 6:39 AM, Pete of Pete <peterbortoli@gmail.com
> >wrote:
>
> > On behalf of those of us who keep an eye on posts for commercial reasons
> > (but do not contribute) Is there the option of setting up a list that
> > accesses the dev comms, but doesn't impact the contributor list?
> >
> > P
> >
> >
> > On Wed, May 14, 2014 at 4:31 AM, Suresh Srinivas <suresh@hortonworks.com
> > >wrote:
> >
> > > Last time we cleaned up names of people who had not contributed in a
> long
> > > time. That could be an option.
> > >
> > >
> > > On Mon, May 12, 2014 at 12:03 PM, Karthik Kambatla <kasha@cloudera.com
> > > >wrote:
> > >
> > > > Hi devs
> > > >
> > > > Looks like we ran over the max contributors allowed for a project,
> > > again. I
> > > > don't remember what we did last time and can't find it in my email
> > > either.
> > > >
> > > > Can we bump up the number of contributors allowed? Otherwise, we
> might
> > > have
> > > > to remove some of the currently inactive contributors from the list?
> > > >
> > > > Thanks
> > > > Karthik
> > > >
> > >
> > >
> > >
> > > --
> > > http://hortonworks.com/download/
> > >
> > > --
> > > CONFIDENTIALITY NOTICE
> > > NOTICE: This message is intended for the use of the individual or
> entity
> > to
> > > which it is addressed and may contain information that is confidential,
> > > privileged and exempt from disclosure under applicable law. If the
> reader
> > > of this message is not the intended recipient, you are hereby notified
> > that
> > > any printing, copying, dissemination, distribution, disclosure or
> > > forwarding of this communication is strictly prohibited. If you have
> > > received this communication in error, please contact the sender
> > immediately
> > > and delete it from your system. Thank You.
> > >
> >
>
Re: #Contributors on JIRA
Posted by "Aaron T. Myers" <at...@cloudera.com>.
Hey Pete,
The "contributor list" we're referring to is just the collection of folks
in JIRA that JIRAs can be assigned to. It doesn't impact anyone's ability
to follow JIRAs, just have new JIRAs assigned to them. It also doesn't do
anything to JIRAs that are already assigned.
--
Aaron T. Myers
Software Engineer, Cloudera
On Thu, May 15, 2014 at 6:39 AM, Pete of Pete <pe...@gmail.com>wrote:
> On behalf of those of us who keep an eye on posts for commercial reasons
> (but do not contribute) Is there the option of setting up a list that
> accesses the dev comms, but doesn't impact the contributor list?
>
> P
>
>
> On Wed, May 14, 2014 at 4:31 AM, Suresh Srinivas <suresh@hortonworks.com
> >wrote:
>
> > Last time we cleaned up names of people who had not contributed in a long
> > time. That could be an option.
> >
> >
> > On Mon, May 12, 2014 at 12:03 PM, Karthik Kambatla <kasha@cloudera.com
> > >wrote:
> >
> > > Hi devs
> > >
> > > Looks like we ran over the max contributors allowed for a project,
> > again. I
> > > don't remember what we did last time and can't find it in my email
> > either.
> > >
> > > Can we bump up the number of contributors allowed? Otherwise, we might
> > have
> > > to remove some of the currently inactive contributors from the list?
> > >
> > > Thanks
> > > Karthik
> > >
> >
> >
> >
> > --
> > http://hortonworks.com/download/
> >
> > --
> > CONFIDENTIALITY NOTICE
> > NOTICE: This message is intended for the use of the individual or entity
> to
> > which it is addressed and may contain information that is confidential,
> > privileged and exempt from disclosure under applicable law. If the reader
> > of this message is not the intended recipient, you are hereby notified
> that
> > any printing, copying, dissemination, distribution, disclosure or
> > forwarding of this communication is strictly prohibited. If you have
> > received this communication in error, please contact the sender
> immediately
> > and delete it from your system. Thank You.
> >
>
Re: #Contributors on JIRA
Posted by Ravi Prakash <ra...@ymail.com>.
You mean {common,mapreduce,yarn,hdfs}-{dev,commits,issues}@hadoop.apache.org lists mentioned on https://hadoop.apache.org/mailing_lists.html ?
On Friday, May 16, 2014 4:44 PM, Pete of Pete <pe...@gmail.com> wrote:
On behalf of those of us who keep an eye on posts for commercial reasons
(but do not contribute) Is there the option of setting up a list that
accesses the dev comms, but doesn't impact the contributor list?
P
On Wed, May 14, 2014 at 4:31 AM, Suresh Srinivas <su...@hortonworks.com>wrote:
> Last time we cleaned up names of people who had not contributed in a long
> time. That could be an option.
>
>
> On Mon, May 12, 2014 at 12:03 PM, Karthik Kambatla <kasha@cloudera.com
> >wrote:
>
> > Hi devs
> >
> > Looks like we ran over the max contributors allowed for a project,
> again. I
> > don't remember what we did last time and can't find it in my email
> either.
> >
> > Can we bump up the number of contributors allowed? Otherwise, we might
> have
> > to remove some of the currently inactive contributors from the list?
> >
> > Thanks
> > Karthik
> >
>
>
>
> --
> http://hortonworks.com/download/
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
Re: #Contributors on JIRA
Posted by Pete of Pete <pe...@gmail.com>.
On behalf of those of us who keep an eye on posts for commercial reasons
(but do not contribute) Is there the option of setting up a list that
accesses the dev comms, but doesn't impact the contributor list?
P
On Wed, May 14, 2014 at 4:31 AM, Suresh Srinivas <su...@hortonworks.com>wrote:
> Last time we cleaned up names of people who had not contributed in a long
> time. That could be an option.
>
>
> On Mon, May 12, 2014 at 12:03 PM, Karthik Kambatla <kasha@cloudera.com
> >wrote:
>
> > Hi devs
> >
> > Looks like we ran over the max contributors allowed for a project,
> again. I
> > don't remember what we did last time and can't find it in my email
> either.
> >
> > Can we bump up the number of contributors allowed? Otherwise, we might
> have
> > to remove some of the currently inactive contributors from the list?
> >
> > Thanks
> > Karthik
> >
>
>
>
> --
> http://hortonworks.com/download/
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
Re: #Contributors on JIRA
Posted by Kihwal Lee <ki...@yahoo-inc.com>.
I removed a bunch who have been inactive for years a couple of months ago
from hdfs. Having a limit forces us to remove stale entries, so it is not
entirely bad. If the actual number of contributors reach the limit and
the limit can't be changed easily, we might be able to create another jira
group and give it a necessary permission.
Kihwal
On 5/13/14, 10:31 PM, "Suresh Srinivas" <su...@hortonworks.com> wrote:
>Last time we cleaned up names of people who had not contributed in a long
>time. That could be an option.
>
>
>On Mon, May 12, 2014 at 12:03 PM, Karthik Kambatla
><ka...@cloudera.com>wrote:
>
>> Hi devs
>>
>> Looks like we ran over the max contributors allowed for a project,
>>again. I
>> don't remember what we did last time and can't find it in my email
>>either.
>>
>> Can we bump up the number of contributors allowed? Otherwise, we might
>>have
>> to remove some of the currently inactive contributors from the list?
>>
>> Thanks
>> Karthik
>>
>
>
>
>--
>http://hortonworks.com/download/
>
>--
>CONFIDENTIALITY NOTICE
>NOTICE: This message is intended for the use of the individual or entity
>to
>which it is addressed and may contain information that is confidential,
>privileged and exempt from disclosure under applicable law. If the reader
>of this message is not the intended recipient, you are hereby notified
>that
>any printing, copying, dissemination, distribution, disclosure or
>forwarding of this communication is strictly prohibited. If you have
>received this communication in error, please contact the sender
>immediately
>and delete it from your system. Thank You.
Re: #Contributors on JIRA
Posted by Steve Loughran <st...@hortonworks.com>.
think it's unrelated ... hadoop-* hasn't moved to the role-based model yet
AFAIK
On 6 June 2014 00:03, Henry Saputra <he...@gmail.com> wrote:
> Hi Steve,
>
> Just notice this email. So do you know if the unable to assign issues
> for contributors a side effect result or intended behavior?
>
> - Henry
>
> On Fri, May 16, 2014 at 2:48 AM, Steve Loughran <st...@hortonworks.com>
> wrote:
> > ASF JIRA has been moving to role-based over group-based security -you may
> > be able to give more people a role than a group allows. But, as of last
> > week and a spark-initiated change, by default contributors can't assign
> > issues.
> >
> > someone could talk to infra@apache and see if a move would help
> >
> >
> > On 14 May 2014 04:31, Suresh Srinivas <su...@hortonworks.com> wrote:
> >
> >> Last time we cleaned up names of people who had not contributed in a
> long
> >> time. That could be an option.
> >>
> >>
> >> On Mon, May 12, 2014 at 12:03 PM, Karthik Kambatla <kasha@cloudera.com
> >> >wrote:
> >>
> >> > Hi devs
> >> >
> >> > Looks like we ran over the max contributors allowed for a project,
> >> again. I
> >> > don't remember what we did last time and can't find it in my email
> >> either.
> >> >
> >> > Can we bump up the number of contributors allowed? Otherwise, we might
> >> have
> >> > to remove some of the currently inactive contributors from the list?
> >> >
> >> > Thanks
> >> > Karthik
> >> >
> >>
> >>
> >>
> >> --
> >> http://hortonworks.com/download/
> >>
> >> --
> >> CONFIDENTIALITY NOTICE
> >> NOTICE: This message is intended for the use of the individual or
> entity to
> >> which it is addressed and may contain information that is confidential,
> >> privileged and exempt from disclosure under applicable law. If the
> reader
> >> of this message is not the intended recipient, you are hereby notified
> that
> >> any printing, copying, dissemination, distribution, disclosure or
> >> forwarding of this communication is strictly prohibited. If you have
> >> received this communication in error, please contact the sender
> immediately
> >> and delete it from your system. Thank You.
> >>
> >
> > --
> > CONFIDENTIALITY NOTICE
> > NOTICE: This message is intended for the use of the individual or entity
> to
> > which it is addressed and may contain information that is confidential,
> > privileged and exempt from disclosure under applicable law. If the reader
> > of this message is not the intended recipient, you are hereby notified
> that
> > any printing, copying, dissemination, distribution, disclosure or
> > forwarding of this communication is strictly prohibited. If you have
> > received this communication in error, please contact the sender
> immediately
> > and delete it from your system. Thank You.
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: #Contributors on JIRA
Posted by Henry Saputra <he...@gmail.com>.
Hi Steve,
Just notice this email. So do you know if the unable to assign issues
for contributors a side effect result or intended behavior?
- Henry
On Fri, May 16, 2014 at 2:48 AM, Steve Loughran <st...@hortonworks.com> wrote:
> ASF JIRA has been moving to role-based over group-based security -you may
> be able to give more people a role than a group allows. But, as of last
> week and a spark-initiated change, by default contributors can't assign
> issues.
>
> someone could talk to infra@apache and see if a move would help
>
>
> On 14 May 2014 04:31, Suresh Srinivas <su...@hortonworks.com> wrote:
>
>> Last time we cleaned up names of people who had not contributed in a long
>> time. That could be an option.
>>
>>
>> On Mon, May 12, 2014 at 12:03 PM, Karthik Kambatla <kasha@cloudera.com
>> >wrote:
>>
>> > Hi devs
>> >
>> > Looks like we ran over the max contributors allowed for a project,
>> again. I
>> > don't remember what we did last time and can't find it in my email
>> either.
>> >
>> > Can we bump up the number of contributors allowed? Otherwise, we might
>> have
>> > to remove some of the currently inactive contributors from the list?
>> >
>> > Thanks
>> > Karthik
>> >
>>
>>
>>
>> --
>> http://hortonworks.com/download/
>>
>> --
>> CONFIDENTIALITY NOTICE
>> NOTICE: This message is intended for the use of the individual or entity to
>> which it is addressed and may contain information that is confidential,
>> privileged and exempt from disclosure under applicable law. If the reader
>> of this message is not the intended recipient, you are hereby notified that
>> any printing, copying, dissemination, distribution, disclosure or
>> forwarding of this communication is strictly prohibited. If you have
>> received this communication in error, please contact the sender immediately
>> and delete it from your system. Thank You.
>>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
Re: #Contributors on JIRA
Posted by Steve Loughran <st...@hortonworks.com>.
ASF JIRA has been moving to role-based over group-based security -you may
be able to give more people a role than a group allows. But, as of last
week and a spark-initiated change, by default contributors can't assign
issues.
someone could talk to infra@apache and see if a move would help
On 14 May 2014 04:31, Suresh Srinivas <su...@hortonworks.com> wrote:
> Last time we cleaned up names of people who had not contributed in a long
> time. That could be an option.
>
>
> On Mon, May 12, 2014 at 12:03 PM, Karthik Kambatla <kasha@cloudera.com
> >wrote:
>
> > Hi devs
> >
> > Looks like we ran over the max contributors allowed for a project,
> again. I
> > don't remember what we did last time and can't find it in my email
> either.
> >
> > Can we bump up the number of contributors allowed? Otherwise, we might
> have
> > to remove some of the currently inactive contributors from the list?
> >
> > Thanks
> > Karthik
> >
>
>
>
> --
> http://hortonworks.com/download/
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: #Contributors on JIRA
Posted by Suresh Srinivas <su...@hortonworks.com>.
Last time we cleaned up names of people who had not contributed in a long
time. That could be an option.
On Mon, May 12, 2014 at 12:03 PM, Karthik Kambatla <ka...@cloudera.com>wrote:
> Hi devs
>
> Looks like we ran over the max contributors allowed for a project, again. I
> don't remember what we did last time and can't find it in my email either.
>
> Can we bump up the number of contributors allowed? Otherwise, we might have
> to remove some of the currently inactive contributors from the list?
>
> Thanks
> Karthik
>
--
http://hortonworks.com/download/
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.