Yeah, I've just realized a problem, that the permission for Developer are not the same as Contributor. It includes the ability to Assign, but doesn't seem to include other more basic permission.
I cleared room in Contributor the meantime (no point in having Committers there; Committer permission is a superset), and I think we can actually fix this long-term by just removing barely-active people from Contributor since it won't matter (they only need to be in the group to be Assigned usually). I've also pinged the ticket to get more control over JIRA permissions so we can rectify more of this. On Tue, Jul 7, 2015 at 9:39 PM, Reynold Xin <r...@databricks.com> wrote: > I've been adding people to the developer role to get around the jira limit. > > > On Tue, Jul 7, 2015 at 3:05 AM, Sean Owen <so...@cloudera.com> wrote: >> >> PS the resolution on this is just that we've hit a JIRA limit, since >> the Contributor role is so big now. >> >> We have a currently-unused Developer role that barely has different >> permissions. I propose to move people that I recognize as regular >> Contributors into the Developer group to make room. Practically >> speaking, there's no difference. Just a heads up in case you see >> changes here. >> >> But for reference, new contributors should go to Contributors by default. >> >> On Sun, Jun 28, 2015 at 11:27 AM, Sean Owen <so...@cloudera.com> wrote: >> > In case you've tried and failed to add a person to a role in JIRA... >> > https://issues.apache.org/jira/browse/INFRA-9891 >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org >> For additional commands, e-mail: dev-h...@spark.apache.org >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org For additional commands, e-mail: dev-h...@spark.apache.org
