Great, thanks everyone! I have filed INFRA-10652 to request both the permission scheme and the Release Note field.
https://issues.apache.org/jira/browse/INFRA-10652 --Chris Nauroth On 10/22/15, 5:35 PM, "Kengo Seki" <[email protected]> wrote: >I also agree to the Yetus specific scheme. Thanks a lot, Chris! > >2015-10-22 1:58 GMT+09:00 Sean Busbey <[email protected]>: > >> Sorry I missed the request the first time around. >> >> That all sounds reasonable to me. If there's an "assign to self" >> permission rather than blanket assign to whomever I'd prefer that, but >> not strongly. >> >> AFAICT, I don't have any ability to change or create permission >> schemes. I agree that we should request one for Yetus rather than use >> Hadoop's. >> >> On Wed, Oct 21, 2015 at 11:53 AM, Chris Nauroth >> <[email protected]> wrote: >> > Gentle nudge on this thread... Could I please get some feedback? >> > >> > Is there agreement or disagreement with the changes I'm proposing for >>the >> > Yetus JIRA permissions? >> > >> > Assuming there is agreement, Sean, does being listed as the project >>lead >> > in JIRA give you the super-powers to do this, or shall I proceed with >> > filing an INFRA JIRA? >> > >> > Thanks! >> > >> > --Chris Nauroth >> > >> > >> > >> > >> > On 10/17/15, 2:39 PM, "Chris Nauroth" <[email protected]> >>wrote: >> > >> >>Thanks for the further details, Kengo. >> >> >> >>For 1, I think this means that we want to give Contributors the >> Transition >> >>Issues permission. >> >> >> >>For 2, I think this means that we want to give Contributors the Assign >> >>Issues permission. >> >> >> >>Right now, Yetus is using the default JIRA permission scheme. One >>way to >> >>solve this would be to change Yetus to use the "Hadoop Permissions" >> >>scheme, which already does the above. Another way to solve it would >>be >> to >> >>branch off and create our own permissions scheme just for Yetus. >> >> >> >>Sean, do you have the ability to switch permissions schemes due to any >> >>super-powers you get from having the project Lead role in JIRA? If >>not, >> >>then I'll file the INFRA JIRA. I'd suggest that we go ahead and >>request >> >>our own Yetus permission scheme instead of using Hadoop's. >> >> >> >>I can include the request for the release note field at the same time. >> >> >> >>--Chris Nauroth >> >> >> >> >> >> >> >> >> >>On 10/17/15, 12:42 AM, "Kengo Seki" <[email protected]> wrote: >> >> >> >>>Thanks for picking up my comment and investigation. >> >>>There are two problems, and both of them are not resolved at the >>time of >> >>>writing. >> >>> >> >>>1. On the issues which I didn't file, "Submit Patch" and "Resolve >>Issue" >> >>>buttons are not shown. >> >>>2. On any issues, I can't assign myself to them. >> >>> >> >>> >> >>>2015-10-17 4:56 GMT+09:00 Chris Nauroth <[email protected]>: >> >>> >> >>>> I was about to file an INFRA JIRA, but I took a closer look, and >>I'm >> >>>>not >> >>>> sure we really have a problem. >> >>>> >> >>>> jira-users is in the Contributors role. >> >>>> >> >>>> >> >>>> >> https://issues.apache.org/jira/plugins/servlet/project-config/YETUS/role >> >>>>s >> >>>> >> >>>> >> >>>> Members of the Contributors role may be assigned issues. >> >>>> >> >>>> >> >>>> >> https://issues.apache.org/jira/plugins/servlet/project-config/YETUS/perm >> >>>>i >> >>>>ss >> >>>> ions >> >>>> >> >>>> >> >>>> However, note that Contributors does not have the "Assign Issues" >> >>>> permission, so they can't assign issues to anyone. Maybe that is >>the >> >>>> problem Kengo reported? >> >>>> >> >>>> I did some basic testing and verified that multiple people who are >>not >> >>>> Yetus committers can be the assignee on a YETUS issue. >> >>>> >> >>>> Do we think this is OK now, or did I misunderstand the problem? >> >>>> >> >>>> We'd still need to request the release note field. >> >>>> >> >>>> --Chris Nauroth >> >>>> >> >>>> >> >>>> >> >>>> >> >>>> On 10/15/15, 9:56 AM, "Allen Wittenauer" <[email protected]> wrote: >> >>>> >> >>>> > >> >>>> >On Oct 15, 2015, at 9:29 AM, Chris Nauroth >><[email protected] >> > >> >>>> >wrote: >> >>>> >> >> >>>> >> If it's not working for us, then shall we file an INFRA JIRA? >> >>>> > >> >>>> > >> >>>> >While we¹re talking to infra about JIRA, I¹d really like to have >>the >> >>>> >release note field tooŠ esp since releasedocmaker supports it. :) >> >>>> > >> >>>> > >> >>>> > >> >>>> >> >>>> >> >> >> > >>
