Re: Giving credit for contributions through Github Pull Requests

2018-04-26 Thread Sean Busbey
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

Re: Giving credit for contributions through Github Pull Requests

2018-04-26 Thread Doug Cutting
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

Re: Giving credit for contributions through Github Pull Requests

2018-04-26 Thread Sean Busbey
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

Re: Giving credit for contributions through Github Pull Requests

2018-04-26 Thread Doug Cutting
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

Re: Giving credit for contributions through Github Pull Requests

2018-04-26 Thread Sean Busbey
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