It turns out there's a limit on the number of people you can list as "contributors" for any given JIRA project. I bumped into this a couple months back when I tried adding someone to the list and found this:
https://issues.apache.org/jira/browse/INFRA-7293 On Mon, May 4, 2015 at 10:02 PM, Lefty Leverenz <leftylever...@gmail.com> wrote: > Sure, go for it. > > > -- Lefty > > On Mon, May 4, 2015 at 5:33 PM, Thejas Nair <thejas.n...@gmail.com> wrote: > > > As Lefty noted, we don't require anyone being made a jira contributor > > or uploading a patch to have ICLA on file. Apache does not require > > that, though that is encouraged. > > So allowing any user to be a contributor without asking for permission > > does not change things with respect to ICLA. > > > > Looks like people are on board with this. I will change the settings > > in another day as long as there are no objections. > > > > > > > > > > On Sat, May 2, 2015 at 11:44 PM, Lefty Leverenz <leftylever...@gmail.com > > > > wrote: > > > Hive only requires committers to sign ICLAs. That doesn't seem to > > provide > > > any legal protection when non-committers contribute patches. > > > > > > In days gone by, JIRA made us assign rights to Apache when we attached > a > > > patch to an issue. That's still in the instructions for Contributing > > Your > > > Work > > > < > > > https://cwiki.apache.org/confluence/display/Hive/HowToContribute#HowToContribute-ContributingYourWork > > >: > > > "Please note that the attachment should be granted license to ASF for > > > inclusion in ASF work" although the JIRA GUI doesn't have that option > > > anymore. > > > > > > See Apache's page on licenses <http://www.apache.org/licenses/#clas>: > > "The > > > ASF desires that all contributors of ideas, code, or documentation to > the > > > Apache projects complete, sign, and submit (via postal mail, fax or > > email) > > > an Individual Contributor License Agreement" *(highlighting added)*. > > > > > > So documentation in the wiki should also be covered by ICLAs. Carried > to > > > extremes, anyone who participates on a mailing list, comments on a JIRA > > > issue, or reviews a patch should sign an ICLA. > > > > > > > > > -- Lefty > > > > > > On Sun, May 3, 2015 at 12:30 AM, Sushanth Sowmyan <khorg...@gmail.com> > > > wrote: > > > > > >> I seem to remember something on the lines of that the traditional > reason > > >> was so that a project could be sure that the contributor had an ICLA > on > > >> file with apache so as to not expose the project to legal risk of code > > that > > >> was contributed that the contributor did not have any rights to. We > > should > > >> probably check with folks from other projects who've had experience > > dealing > > >> with stuff like this? > > >> > > >> Maybe Owen? > > >> On May 2, 2015 17:08, "Thejas Nair" <thejas.n...@gmail.com> wrote: > > >> > > >> > Sending again, didn't make to the list for some reason. > > >> > > > >> > > > >> > ---------- Forwarded message ---------- > > >> > From: Thejas Nair <thejas.n...@gmail.com> > > >> > Date: Fri, May 1, 2015 at 1:53 PM > > >> > Subject: [DISCUSS] Allow any jira user to assign HIVE bugs to them > > self > > >> > To: dev <dev@hive.apache.org> > > >> > > > >> > > > >> > I am not sure why a user needs to ask to be added as a contributor > in > > >> > HIVE jira to be able to assign jiras to themselves. I don't see it > > >> > adding any value. Also the jira ADMIN UI for adding this is usually > > >> > flaky. > > >> > > > >> > I think we should let any jira users assign the bugs to them self. > > >> > Looks like adding jira-users group to contributions would do it. > > >> > > > >> > Thoughts ? > > >> > > > >> > Thanks, > > >> > Thejas > > >> > > > >> > > >
