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 <peterbort...@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 <sur...@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. > > >
