...@cloudera.com
To: dev dev@hbase.apache.org; lars hofhansl la...@apache.org
Sent: Sunday, March 15, 2015 9:46 PM
Subject: Re: Jira role cleanup
I can make it so that issues can be assigned to non-contributors. Even if
we don't do that, I believe jira permissions are all about constraining
current
willing to host one at Salesforce.
-- Lars
From: Sean Busbey bus...@cloudera.com
To: dev dev@hbase.apache.org; lars hofhansl la...@apache.org
Sent: Sunday, March 15, 2015 9:46 PM
Subject: Re: Jira role cleanup
I can make it so that issues can be assigned to non-contributors. Even if
we
Okay, it sounds like there's decent consensus. How much of this cleanup can
I take care of before the PMC meets?
Everyone fine if I do the earlier pruning we talked about and look into the
anyone is assignable bit?
On Mon, Mar 16, 2015 at 12:38 PM, Andrew Purtell apurt...@apache.org
wrote:
.
-- Lars
From: Sean Busbey bus...@cloudera.com
To: dev dev@hbase.apache.org; lars hofhansl la...@apache.org
Sent: Sunday, March 15, 2015 9:46 PM
Subject: Re: Jira role cleanup
I can make it so that issues can be assigned to non-contributors. Even if
we don't do that, I believe
at Salesforce.
-- Lars
From: Sean Busbey bus...@cloudera.com
To: dev dev@hbase.apache.org; lars hofhansl la...@apache.org
Sent: Sunday, March 15, 2015 9:46 PM
Subject: Re: Jira role cleanup
I can make it so that issues can be assigned to non-contributors. Even if
we don't do that, I
On Mon, Mar 16, 2015 at 1:28 PM, Andrew Purtell apurt...@apache.org wrote:
On Mon, Mar 16, 2015 at 11:02 AM, Nick Dimiduk ndimi...@gmail.com wrote:
bq. Our commit log conventions aren't universally followed, due to human
error
Going forward, I think we can alleviate this issue with a
:46 PM
Subject: Re: Jira role cleanup
I can make it so that issues can be assigned to non-contributors. Even
if
we don't do that, I believe jira permissions are all about constraining
current actions, and are not enforced on existing ticketes.
However, the contributor role
To: dev dev@hbase.apache.org
Sent: Friday, March 13, 2015 9:09 AM
Subject: Re: Jira role cleanup
On Fri, Mar 13, 2015 at 11:01 AM, Andrew Purtell apurt...@apache.org
wrote:
+1
I think it would be fine to trim the contributor list too. We can always
add people back on demand in order to (re
: Jira role cleanup
On Fri, Mar 13, 2015 at 11:01 AM, Andrew Purtell apurt...@apache.org
wrote:
+1
I think it would be fine to trim the contributor list too. We can always
add people back on demand in order to (re)assign issues.
I wasn't sure how we generate the list of contributors
13, 2015 9:31 AM
Subject: Re: Jira role cleanup
How about I make a saved jira query for people who have had jira's assigned
to them, add a link to that query for our here are the contributors
section, and then trim off from the role anyone who hasn't been assigned an
issue
FYI, some time next week I'm going to try to simplify our jira role list.
When I go to add new contributors it takes forever, I'm guessing because of
the list size.
I think I can trim it down some by making sure folks who are committers are
in the committer list and not the contributor list.
On Fri, Mar 13, 2015 at 11:01 AM, Andrew Purtell apurt...@apache.org
wrote:
+1
I think it would be fine to trim the contributor list too. We can always
add people back on demand in order to (re)assign issues.
I wasn't sure how we generate the list of contributors. But then I noticed
that we
+1
I think it would be fine to trim the contributor list too. We can always
add people back on demand in order to (re)assign issues.
On Fri, Mar 13, 2015 at 8:32 AM, Sean Busbey bus...@cloudera.com wrote:
FYI, some time next week I'm going to try to simplify our jira role list.
When I go to
How about I make a saved jira query for people who have had jira's assigned
to them, add a link to that query for our here are the contributors
section, and then trim off from the role anyone who hasn't been assigned an
issue in the last year?
That sounds like a very fair
14 matches
Mail list logo
