I recommend people take a look at the now deprecated helm project. It was very difficult to land PRs because they had so much governance and automation. For a data store as mature as SOLR, I would suggest it is needed.
Many issues are worth a read: https://github.com/helm/helm On Tue, May 10, 2022 at 10:16 AM Gus Heck <gus.h...@gmail.com> wrote: > > > On Tue, May 10, 2022 at 10:40 AM Houston Putman <hous...@apache.org> > wrote: > >> >>> >> Most modern open source projects use Github Issues for their issue >> tracking, so it's definitely doable, and really what new >> users/contributors will be expecting. Also I see that much discussion is >> already done on PRs, and JIRAs are mainly there just for >> bureaucratic purposes. So I think it would be a wonderful direction to go >> in. >> >> > On that note, many such projects I find it more difficult to get clarity > on whether or not I'm affected by the issue, or in what version it was > resolved. Usually i can be achieved by clicking on the referenced commit, > and then inspecting what tags are on that commit, but it's several clicks > and a minute or two vs just looking at the field in Jira... > > This can be made easier by using milestones as seen here (random example, > used gradle because it's a very large, healthy project): > https://github.com/gradle/gradle/issues/20182 > > But I've seen a lot of projects that don't do that... which probably > colors my view a bit. > > -Gus > > -- > http://www.needhamsoftware.com (work) > http://www.the111shift.com (play) > -- Marcus Eagan
