hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Loughran <ste...@hortonworks.com>
Subject Re: #Contributors on JIRA
Date Fri, 06 Jun 2014 07:12:28 GMT
think it's unrelated ... hadoop-* hasn't moved to the role-based model yet
AFAIK


On 6 June 2014 00:03, Henry Saputra <henry.saputra@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 <stevel@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 <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.
> >>
> >
> > --
> > 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.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message