Or the committer can create it if the issue is truly trivial... Also, one of the things that folks who contribute may gain is learning about development process. That aspect was extremely helpful to me when I made my first contributions to Ant many years ago. Not everyone who contributes is an expert.
On Mon, Jun 10, 2019 at 3:33 AM Varun Thacker <[email protected]> wrote: > 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 <[email protected]> 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 >> >> -- http://www.needhamsoftware.com (work) http://www.the111shift.com (play)
