On Thu, May 3, 2018 at 4:18 PM, Doug Cutting wrote:
> Maybe we should loosen the permissions on Avro's Jira so that any user can
> assign an issue? That would make things a bit simpler. I doubt we'd see
> much if any abuse.
>
locking down issue assigning happened ASF jira wide due to spammer a
+1 for both
On Fri, May 4, 2018 at 9:54 AM, Nandor Kollar wrote:
> +1 for both, especially for removing CHANGES.txt.
>
> On Thu, May 3, 2018 at 11:18 PM, Doug Cutting wrote:
>
> > Maybe we should loosen the permissions on Avro's Jira so that any user
> can
> > assign an issue? That would make
+1 for both, especially for removing CHANGES.txt.
On Thu, May 3, 2018 at 11:18 PM, Doug Cutting wrote:
> Maybe we should loosen the permissions on Avro's Jira so that any user can
> assign an issue? That would make things a bit simpler. I doubt we'd see
> much if any abuse.
>
> Also, it's prob
Maybe we should loosen the permissions on Avro's Jira so that any user can
assign an issue? That would make things a bit simpler. I doubt we'd see
much if any abuse.
Also, it's probably time to remove CHANGES.txt and just use Jira to
generate release notes. Agreed?
Doug
On Thu, Apr 26, 2018 a
On Thu, Apr 26, 2018 at 1:43 PM, Doug Cutting wrote:
> So I guess this would be easier if we also said that contributions would
> only now be accepted via pull request. Is that too onerous? Instead of
> requiring everyone to have an Apache Jira account we require them to have a
> GitHub account
So I guess this would be easier if we also said that contributions would
only now be accepted via pull request. Is that too onerous? Instead of
requiring everyone to have an Apache Jira account we require them to have a
GitHub account.
Moving issue tracking to GitHub seems unlikely, as it's lack
so we'd still do issue tracking in JIRA, but specifically for looking at
who's contributed we'd use the github tooling?
we could do a clean cut over for that. We'd have to get more rigorous at
making sure the author on commits is the contributor. the current
discrepency is a combination of svn day
Might we instead switch from Jira to GitHub for contribution tracking?
Then we might not need to worry so much about who the Jira issue is
assigned to.
GitHub has contribution history:
https://github.com/apache/avro/graphs/contributors
Is this sufficient? It seems like it's missing a lot of old
how about we create a PMC-controlled jira account to represent "pull
request from someone without a jira ID"? then we can follow your suggestion
of "encourage the contributor to create a jira id and assign to them" and
we have a clear way to mark "you need to look at git or github to find the
autho
Hi all,
Officially, we say that we track issues using Jira: https://avro.apache.org/
issue_tracking.html and suggest contributors to manage issues on Jira. But
we receive several pull requests on github with or without corresponding
Jira tickets. What is the best way to handle them? How do other A
10 matches
Mail list logo
