I hate to say “on my project”, but I will.

My understanding, from my experience on my project (Apache Metron) is that
PMC members have jira rights within their project such that they can change
the rights or add rights to jira accounts.
I have these rights myself.

We give contributor rights to community members when they ask, if they have
been working on issues in the apache jira, such that they can assign,
track, and close based on their work.  Having
unassigned jiras that get worked and closed isn’t a good way to handle

I am sorry if I am misunderstanding something, but I didn’t imagine this to
be different across projects.

On February 19, 2018 at 09:34:28, Otto Fowler (ottobackwa...@gmail.com)

As I stated in my original mail.  I would like to assign the Jiras for the
issues I create and will be submitting Pull Requests for or for the issues
that I didn’t create but will
be creating Pull Requests for to myself.

I am not requesting or mentioning commit rights.  I just want to have
everything in my dashboard.

But since commit rights keeps coming up.  Is there a link to commit
procedures and requirements for VFS and or LANG or a guide for committers
I don’t imagine ‘just committing’ to either LANG or VFS.  I would feel more
comfortable with the standard submit until we trust you model.  Also, my
doesn’t use SVN, we use Apache Git, and we have guides and scripts that we
have committers use, I don’t think I’d just start committing to SVN willy
nilly to start with.



On February 18, 2018 at 21:48:47, Matt Sicker (boa...@gmail.com) wrote:

On 17 February 2018 at 12:09, Otto Fowler <ottobackwa...@gmail.com> wrote:

> I am familiar with the differences between a contributor or a committer
> both in the foundation and jira.
> I would like _contributor_ rights, not commit rights.

In what context? You already have commit rights if you're a committer on
any other project at Apache. Alternatively, you can submit PRs on GitHub if
you prefer that interface.

Matt Sicker <boa...@gmail.com>

Reply via email to