cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Jirsa <jji...@gmail.com>
Subject Re: jira ticket assignment
Date Wed, 15 Mar 2017 00:17:54 GMT
Based on Jason's the INFRA jira (
https://issues.apache.org/jira/browse/INFRA-11950 ) , it looks like we can
remove the blocker if desired - does anyone have any argument for keeping
it? Or should we just jump to a vote?


On Tue, Mar 14, 2017 at 4:59 PM, Jonathan Ellis <jbellis@gmail.com> wrote:

> Sankalp had a thread about this last month.  He was going to look into our
> options.
>
> On Tue, Mar 14, 2017 at 6:45 PM, Jason Brown <jasedbrown@gmail.com> wrote:
>
> > Hey all,
> >
> > Currently, when a new contributor wants to have a ticket assigned to
> > themselves, they cannot due to JIRA permissions. The contributor (or
> > someone on behalf of the contributor) usually needs to contact the
> > dev-channel and ask for the magical permissions to be granted, and
> there's
> > only a handful of folks who can grant that.
> >
> > Is anyone aware of why this restriction is in place, or feel strongly it
> > should exist? I'd like to change the JIRA defaults and let anyone assign
> > themselves to a ticket (see
> > https://issues.apache.org/jira/browse/INFRA-11950 for an example of
> > another
> > Apache project that has done this already).
> >
> > Thoughts?
> >
> > If no strong objections I'll set up a PMC vote within a day or two.
> >
> > Thanks,
> >
> > -Jason
> >
>
>
>
> --
> Jonathan Ellis
> co-founder, http://www.datastax.com
> @spyced
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message