There is no doc.

1. Login to ASF JIRA
2. Go to the project page (e.g. https://issues.apache.org/jira/browse/HADOOP )
3. Hit "Administration" tab
4. Hit "Roles" tab in left side
5. Add administrators/committers/contributors

I'll document this in https://wiki.apache.org/hadoop/HowToCommit

Regards,
Akira

On 6/20/16 16:08, Zheng, Kai wrote:
Thanks Akira for the nice info. So where is the link to do it or any how to 
doc? Sorry I browsed the existing wiki doc but didn't find how to add 
contributors.

Regards,
Kai

-----Original Message-----
From: Akira AJISAKA [mailto:ajisa...@oss.nttdata.co.jp]
Sent: Monday, June 20, 2016 12:22 PM
To: Zheng, Kai <kai.zh...@intel.com>; common-dev@hadoop.apache.org
Subject: Re: Different JIRA permissions for HADOOP and HDFS

Yes, the role allows committers to add/remove all the roles.

Now about 400 accounts have contributors roles in Hadoop common, and about 1000 
contributors in history.

Regards,
Akira

On 6/19/16 19:43, Zheng, Kai wrote:
Thanks Akira for the work.

What the committer role can do in addition to the committing codes? Can the 
role allow to add/remove a contributor? As I said in my last email, I want to 
have some contributor(s) back and may add more in some time later.

Not sure if we need to clean up long time no active contributors. It may be 
nice to know how many contributors the project has in its history. If the list 
is too long, maybe we can put them in another list, like OLD_CONTRIBUTORS.

Regards,
Kai

-----Original Message-----
From: Akira AJISAKA [mailto:ajisa...@oss.nttdata.co.jp]
Sent: Saturday, June 18, 2016 12:56 PM
To: Zheng, Kai <kai.zh...@intel.com>; common-dev@hadoop.apache.org
Subject: Re: Different JIRA permissions for HADOOP and HDFS

I'm doing the following steps to reduce the number of contributors:

1. Find committers who have only contributor role 2. Add them into
committer role 3. Remove them from contributor role

However, this is a temporary solution.
Probably we need to do one of the followings in the near future.

* Create contributor2 role to increase the limit
* Remove contributors who have not been active for a long time

Regards,
Akira

On 6/18/16 10:24, Zheng, Kai wrote:
Hi Akira,

Some contributors (not committer) I know were found lost and we can't assign 
tasks to. Any way I can add them or have to trouble others for that each time 
when there is a new one? Thanks!

Regards,
Kai

-----Original Message-----
From: Akira AJISAKA [mailto:ajisa...@oss.nttdata.co.jp]
Sent: Monday, June 06, 2016 12:47 AM
To: common-dev@hadoop.apache.org
Subject: Re: Different JIRA permissions for HADOOP and HDFS

Now I can't add any more contributors in HADOOP Common, so I'll remove the 
contributors who have committers role to make the group smaller.
Please tell me if you have lost your roles by mistake.

Regards,
Akira

On 5/18/16 13:48, Akira AJISAKA wrote:
In HADOOP/HDFS/MAPREDUCE/YARN, I removed the administrators from
contributor group. After that, added Varun into contributor roles.
# Ray is already added into contributor roles.

Hi contributors/committers, please tell me if you have lost your
roles by mistake.

just remove a big chunk of the committers from all the lists
In Apache Hadoop Project bylaws, "A Committer is considered emeritus
by their own declaration or by not contributing in any form to the
project for over six months." Therefore we can remove them from the
list, but I'm thinking this is the last option.

Regards,
Akira

On 5/18/16 09:07, Allen Wittenauer wrote:

We should probably just remove a big chunk of the committers from
all the lists.  Most of them have disappeared from Hadoop anyway.
(The 55% growth in JIRA issues in patch available state in the past
year alone a pretty good testament to that fact.)

On May 17, 2016, at 4:40 PM, Akira Ajisaka <aajis...@apache.org> wrote:

Is there some way for us to add a "Contributors2" group with the
same permissions as a workaround?  Or we could try to clean out
contributors who are no longer active, but that might be hard to figure out.

Contributors2 seems fine. AFAIK, committers sometimes cleaned out
contributors who are no longer active.
http://search-hadoop.com/m/uOzYt77s6mnzcRu1/v=threaded

Another option: Can we remove committers from contributor group to
reduce the number of contributors? I've already removed myself
from contributor group and it works well.

Regards,
Akira

On 5/18/16 03:16, Robert Kanter wrote:
We've also had a related long-standing issue (or at least I have)
where I can't add any more contributors to HADOOP or HDFS because
JIRA times out on looking up their username.  I'm guessing we
have too many contributors for those projects.  I bet YARN and MAPREDUCE are 
close.
Is there some way for us to add a "Contributors2" group with the
same permissions as a workaround?  Or we could try to clean out
contributors who are no longer active, but that might be hard to figure out.

- Robert

On Tue, May 17, 2016 at 11:12 AM, Ray Chiang
<rchi...@cloudera.com <mailto:rchi...@cloudera.com>> wrote:

   Similar issue for me.  I can't modify HDFS and HADOOP JIRAs now.

   -Ray


   On Tue, May 17, 2016 at 9:54 AM, Varun Saxena
   <vsaxena.va...@gmail.com <mailto:vsaxena.va...@gmail.com>>
   wrote:

   > Hi,
   >
   > I do not have permissions for any project other than YARN as well.
   Unable
   > to assign a JIRA in MAPREDUCE for instance.
   > Can somebody give me permission ?
   >
   > Regards,
   > Varun Saxena.
   >
   >
   > On Tue, May 17, 2016 at 11:03 AM, Vinayakumar B <
   > vinayakumarb.apa...@gmail.com
   <mailto:vinayakumarb.apa...@gmail.com>> wrote:
   >
   > > Thanks Akira.
   > > On 17 May 2016 10:59, "Akira Ajisaka" <aajis...@apache.org
   <mailto:aajis...@apache.org>> wrote:
   > >
   > > > Hi Vinay,
   > > >
   > > > Added you into committer roles for HADOOP/MAPREDUCE/YARN.
   > > >
   > > > Regards,
   > > > Akira
   > > >
   > > > On 5/17/16 13:45, Vinayakumar B wrote:
   > > >
   > > >> Hi Junping,
   > > >>
   > > >> It looks like, I too dont have permissions in projects except
   HDFS.
   > > >>
   > > >> Please grant me also to the group.
   > > >>
   > > >> Thanks in advance,
   > > >> -Vinay
   > > >> On 17 May 2016 6:10 a.m., "Sangjin Lee" <sj...@apache.org
   <mailto:sj...@apache.org>> wrote:
   > > >>
   > > >> Thanks Junping! It seems to work now.
   > > >>
   > > >> On Mon, May 16, 2016 at 5:22 PM, Junping Du
   <j...@hortonworks.com <mailto:j...@hortonworks.com>>
   > > wrote:
   > > >>
   > > >> Someone fix the permission issue so that Administrator,
   committer and
   > > >>> reporter can edit the issue now.
   > > >>>
   > > >>> Sangjin, it sounds like you were not in JIRA's committer
   list before
   > > and
   > > >>> I
   > > >>> just add you into committer roles for 4 projects. Hope it
   works for
   > > >>> you now.​
   > > >>>
   > > >>>
   > > >>> Thanks,
   > > >>>
   > > >>>
   > > >>> Junping
   > > >>> ------------------------------
   > > >>> *From:* sjl...@gmail.com <mailto:sjl...@gmail.com>
   <sjl...@gmail.com <mailto:sjl...@gmail.com>> on behalf of Sangjin
   > Lee <
   > > >>> sj...@apache.org <mailto:sj...@apache.org>>
   > > >>> *Sent:* Monday, May 16, 2016 11:43 PM
   > > >>> *To:* Zhihai Xu
   > > >>> *Cc:* Junping Du; Arun Suresh; Zheng, Kai; Andrew Wang;
   > > >>> common-dev@hadoop.apache.org
   <mailto:common-dev@hadoop.apache.org>; yarn-...@hadoop.apache.org
   <mailto:yarn-...@hadoop.apache.org>
   > > >>>
   > > >>> *Subject:* Re: Different JIRA permissions for HADOOP
and HDFS
   > > >>>
   > > >>> I also find myself unable to edit most of the JIRA fields,
   and that
   > is
   > > >>> across projects (HADOOP, YARN, MAPREDUCE, and HDFS).
   Commenting and
   > the
   > > >>> workflow buttons seem to work, however.
   > > >>>
   > > >>> On Mon, May 16, 2016 at 8:14 AM, Zhihai Xu <zhi...@uber.com
   <mailto:zhi...@uber.com>> wrote:
   > > >>>
   > > >>> Great, Thanks Junping! Yes, the JIRA assignment works for me
   now.
   > > >>>>
   > > >>>> zhihai
   > > >>>>
   > > >>>> On Mon, May 16, 2016 at 5:29 AM, Junping Du
   <j...@hortonworks.com <mailto:j...@hortonworks.com>>
   > > >>>> wrote:
   > > >>>>
   > > >>>> Zhihai, I just set you with committer permissions on
   MAPREDUCE JIRA.
   > > >>>>>
   > > >>>> Would
   > > >>>>
   > > >>>>> you try if the JIRA assignment works now? I cannot help on
   Hive
   > > >>>>>
   > > >>>> project. It
   > > >>>>
   > > >>>>> is better to ask hive project community for help.
   > > >>>>> For Arun's problem. from my check, the Edit permission on
   JIRA only
   > > >>>>> authorized to Administrator only. I don't know if this
   setting is
   > by
   > > >>>>> intention but it was not like this previously.
   > > >>>>> Can someone who make the change to clarify why we need
   this change
   > or
   > > >>>>> revert to whatever it used to be?
   > > >>>>>
   > > >>>>> Thanks,
   > > >>>>>
   > > >>>>> Junping
   > > >>>>> ________________________________________
   > > >>>>> From: Arun Suresh <asur...@apache.org
   <mailto:asur...@apache.org>>
   > > >>>>> Sent: Monday, May 16, 2016 9:42 AM
   > > >>>>> To: Zhihai Xu
   > > >>>>> Cc: Zheng, Kai; Andrew Wang; common-dev@hadoop.apache.org
   <mailto:common-dev@hadoop.apache.org>;
   > > >>>>> yarn-...@hadoop.apache.org
<mailto:yarn-...@hadoop.apache.org>
   > > >>>>> Subject: Re: Different JIRA permissions for HADOOP
and HDFS
   > > >>>>>
   > > >>>>> Not sure if this is related.. but It also looks like I am
   now no
   > > longer
   > > >>>>> allowed to modify description and headline of JIRAs
anymore..
   > > >>>>> Would appreciate greatly if someone can help revert this !
   > > >>>>>
   > > >>>>> Cheers
   > > >>>>> -Arun
   > > >>>>>
   > > >>>>> On Mon, May 16, 2016 at 1:21 AM, Zhihai Xu
   <zhi...@uber.com <mailto:zhi...@uber.com>>
   > wrote:
   > > >>>>>
   > > >>>>> Currently I also have permission issue to access the JIRA.
   I can't
   > > >>>>>>
   > > >>>>> assign
   > > >>>>
   > > >>>>> the JIRA(I created) to myself. For example,
   > > >>>>>> https://issues.apache.org/jira/browse/MAPREDUCE-6696 and
   > > >>>>>> https://issues.apache.org/jira/browse/HIVE-13760. I can't
   find
   > the
   > > >>>>>>
   > > >>>>> button
   > > >>>>>
   > > >>>>>> to assign the JIRA to myself.
   > > >>>>>> I don't have this issue two three weeks ago. Did anything
   change
   > > >>>>>>
   > > >>>>> recently?
   > > >>>>>
   > > >>>>>> Can anyone help me solve this issue?
   > > >>>>>>
   > > >>>>>> thanks
   > > >>>>>> zhihai
   > > >>>>>>
   > > >>>>>>
   > > >>>>>>
   > > >>>>>>
   > > >>>>>> On Mon, May 16, 2016 at 12:22 AM, Zheng, Kai
   <kai.zh...@intel.com <mailto:kai.zh...@intel.com>
   > >
   > > >>>>>>
   > > >>>>> wrote:
   > > >>>>>
   > > >>>>>>
   > > >>>>>> It works for me now, thanks Andrew!
   > > >>>>>>>
   > > >>>>>>> Regards,
   > > >>>>>>> Kai
   > > >>>>>>>
   > > >>>>>>> -----Original Message-----
   > > >>>>>>> From: Andrew Wang [mailto:andrew.w...@cloudera.com
   <mailto:andrew.w...@cloudera.com>]
   > > >>>>>>> Sent: Monday, May 16, 2016 12:14 AM
   > > >>>>>>> To: Zheng, Kai <kai.zh...@intel.com
   <mailto:kai.zh...@intel.com>>
   > > >>>>>>> Cc: common-dev@hadoop.apache.org
   <mailto:common-dev@hadoop.apache.org>
   > > >>>>>>> Subject: Re: Different JIRA permissions for HADOOP
and HDFS
   > > >>>>>>>
   > > >>>>>>> I just gave you committer permissions on JIRA, try now?
   > > >>>>>>>
   > > >>>>>>> On Mon, May 16, 2016 at 12:03 AM, Zheng, Kai <
   > kai.zh...@intel.com <mailto:kai.zh...@intel.com>>
   > > >>>>>>>
   > > >>>>>> wrote:
   > > >>>>>>
   > > >>>>>>>
   > > >>>>>>> I just ran into the bad situation that I committed
   HDFS-8449 but
   > > >>>>>>>>
   > > >>>>>>> can't
   > > >>>>>
   > > >>>>>> resolve the issue due to lacking the required permission
   to me.
   > > >>>>>>>>
   > > >>>>>>> Am
   > > >>
   > > >>> not
   > > >>>>>
   > > >>>>>> sure if it's caused by my setup or environment change
   (temporally
   > > >>>>>>>> working in a new time zone). Would anyone help resolve
   the issue
   > > >>>>>>>>
   > > >>>>>>> for
   > > >>>>
   > > >>>>> me to avoid bad state? Thanks!
   > > >>>>>>>>
   > > >>>>>>>> -----Original Message-----
   > > >>>>>>>> From: Zheng, Kai [mailto:kai.zh...@intel.com
   <mailto:kai.zh...@intel.com>]
   > > >>>>>>>> Sent: Sunday, May 15, 2016 3:20 PM
   > > >>>>>>>> To: Allen Wittenauer
<allenwittena...@yahoo.com.INVALID>
   > > >>>>>>>> Cc: common-dev@hadoop.apache.org
   <mailto:common-dev@hadoop.apache.org>
   > > >>>>>>>> Subject: RE: Different JIRA permissions for
HADOOP and HDFS
   > > >>>>>>>>
   > > >>>>>>>> Thanks Allen for illustrating this in details. I
   understand. The
   > > >>>>>>>>
   > > >>>>>>> left
   > > >>>>
   > > >>>>> question is, is it intended only JIRA owner (not sure
   about admin
   > > >>>>>>>> users) can do the operations like updating a patch?
   > > >>>>>>>>
   > > >>>>>>>> Regards,
   > > >>>>>>>> Kai
   > > >>>>>>>>
   > > >>>>>>>> -----Original Message-----
   > > >>>>>>>> From: Allen Wittenauer [mailto:
   > allenwittena...@yahoo.com.INVALID]
   > > >>>>>>>> Sent: Saturday, May 14, 2016 9:38 AM
   > > >>>>>>>> To: Zheng, Kai <kai.zh...@intel.com
   <mailto:kai.zh...@intel.com>>
   > > >>>>>>>> Cc: common-dev@hadoop.apache.org
   <mailto:common-dev@hadoop.apache.org>
   > > >>>>>>>> Subject: Re: Different JIRA permissions for
HADOOP and HDFS
   > > >>>>>>>>
   > > >>>>>>>>
   > > >>>>>>>> On May 14, 2016, at 7:07 AM, Zheng, Kai
   <kai.zh...@intel.com <mailto:kai.zh...@intel.com>>
   > > >>>>>>>>>
   > > >>>>>>>> wrote:
   > > >>>>>
   > > >>>>>>
   > > >>>>>>>>> Hi,
   > > >>>>>>>>>
   > > >>>>>>>>> Noticed this difference but not sure if it’s intended.
   YARN is
   > > >>>>>>>>> similar
   > > >>>>>>>>>
   > > >>>>>>>> with HDFS. It’s not convenient. Any clarifying?
   > > >>>>>>>>
   > > >>>>>>>>
   > > >>>>>>>>         Under JIRA, different projects (e.g.,
HADOOP, YARN,
   > > >>>>>>>>
   > > >>>>>>> MAPREDUCE,
   > > >>>>>
   > > >>>>>> HDFS, YETUS, HBASE, ACCUMULO, etc) may have different
   settings.
   > > >>>>>>>>
   > > >>>>>>> At
   > > >>>>
   > > >>>>> one point in time, all of the Hadoop subprojects were
   under one
   > > >>>>>>>>
   > > >>>>>>> JIRA
   > > >>>>
   > > >>>>> project (HADOOP). But then a bunch of folks decided they
   didn’t
   > > >>>>>>>>
   > > >>>>>>> want
   > > >>>>
   > > >>>>> to see the other sub projects issues so they split them
   up…. and
   > > >>>>>>>>
   > > >>>>>>> thus
   > > >>>>
   > > >>>>> setting the stage for duplicate code and operational
   divergence
   > > >>>>>>>>
   > > >>>>>>> in
   > > >>
   > > >>> the
   > > >>>>>
   > > >>>>>> source.
   > > >>>>>>>
   > > >>>>>>>>
   > > >>>>>>>>         Since people don’t realize or care that they
are
   > > >>>>>>>>
   > > >>>>>>> separate,
   > > >>
   > > >>> people will file INFRA tickets or whatever to change “their
   > > >>>>>>>>
   > > >>>>>>> project”
   > > >>>>
   > > >>>>> and not the rest. This leads to the JIRA projects also
   diverging…
   > > >>>>>>>> which ultimately drives those of us who actually look
   at the
   > > >>>>>>>>
   > > >>>>>>> project
   > > >>>>
   > > >>>>> as
   > > >>>>>
   > > >>>>>> a whole bonkers.
   > > >>>>>>>
   > > >>>>>>>>
   > > >>>>>>>>
   > > >>>>
   >
---------------------------------------------------------------------
   > > >>>>
   > > >>>>> To unsubscribe, e-mail:
   common-dev-unsubscr...@hadoop.apache.org
   <mailto:common-dev-unsubscr...@hadoop.apache.org>
   > > >>>>>>>> For additional commands, e-mail:
   > > >>>>>>>>
   > > >>>>>>> common-dev-h...@hadoop.apache.org
   <mailto:common-dev-h...@hadoop.apache.org>
   > > >>>>
   > > >>>>>
   > > >>>>>>>>
   > > >>>>>>>>
   > > >>>>>>>>
   > > >>>>
   >
---------------------------------------------------------------------
   > > >>>>
   > > >>>>> To unsubscribe, e-mail:
   common-dev-unsubscr...@hadoop.apache.org
   <mailto:common-dev-unsubscr...@hadoop.apache.org>
   > > >>>>>>>> For additional commands, e-mail:
   > > >>>>>>>>
   > > >>>>>>> common-dev-h...@hadoop.apache.org
   <mailto:common-dev-h...@hadoop.apache.org>
   > > >>>>
   > > >>>>>
   > > >>>>>>>>
   > > >>>>>>>
   > > >>>>>>>
   > >

---------------------------------------------------------------------
   > > >>>>
   > > >>>>> To unsubscribe, e-mail:
   common-dev-unsubscr...@hadoop.apache.org
   <mailto:common-dev-unsubscr...@hadoop.apache.org>
   > > >>>>>>> For additional commands, e-mail:
   > common-dev-h...@hadoop.apache.org
   <mailto:common-dev-h...@hadoop.apache.org>
   > > >>>>>>>
   > > >>>>>>>
   > > >>>>>>
   > > >>>>>
   > > >>>>
   > > >>>
   > > >>>
   > > >>
   > > >
   > >
   >




------------------------------------------------------------------
-
-
- To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org



-------------------------------------------------------------------
-
- To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org



--------------------------------------------------------------------
- To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org





---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Reply via email to