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 at 11:51 AM Sean Busbey <[email protected]> wrote: > On Thu, Apr 26, 2018 at 1:43 PM, Doug Cutting <[email protected]> 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. > > > > > I take it the github contributor summary doesn't work for emails that > aren't associated with a github id? > > What about jumping on the Apache Kibble train? They're trying to make > similar "project observability" widgets as what github provides. > > > > > Moving issue tracking to GitHub seems unlikely, as it's lacking a lot of > > features we depend on from Jira. > > > > > I don't like the idea of moving from JIRA to GitHub issues, but I think GHI > has all the features we'd need to do so, FYI. Or atleast, I can't think of > any we use that don't have a mapping to something. > > > -- > busbey >
