I think D is important for making the barrier low for new contributors to get started.
It won't be great as we'll have two places to look a CHANGES entry against but I'll be okay with that. Today a new contributor creates a PR and a committer can even merge the PR from the github interface. But in between those 2 steps we have to tell the contributor to go create a placeholder Jira. Imagine if this new contributor just wants to fix one typo from the ref guide. The overhead involved will shun quite a lot of folks? On Sat, Jun 8, 2019 at 2:22 PM Jan Høydahl <jan....@cominvent.com> wrote: > Jira has become very heavy-weight over the years and I'm not sure we need > all those features. > I think Github issues are a bit too lightweight perhaps, so I'm not > actively promoting option E, just lifting it up as a real alternative. > > As an example how would you implement the security issue visibility with > original poster and PMC able to see it in github? > > > Think they have something in the makings for this, see > https://github.com/apache/lucene-solr/security/policy > Have no idea if you can limit the group who sees them to PMC members > though. > > -- > Jan Høydahl, search solution architect > Cominvent AS - www.cominvent.com > >
