I love the work on the https://s.apache.org/lucenenet-issue which I stated in my other response. But I have mixed feelings about the about the PR checklist.
On one hand, the checklist is not unreasonable, but on the other hand, it's likely to reduce contributions, and I think in general we'd like to increase community contributions if we can get the community focused on the actual work that needs to be done. Especially in light of the new guidance being given on issues I feel like it might be good to give a bit of time to see how that improves things before rolling the https://s.apache.org/lucenenet-pr checklist approach. Just a thought. -Ron Clabo Apache Lucene.NET Committer -----Original Message----- From: Shad Storhaug <s...@shadstorhaug.com> Sent: Friday, October 20, 2023 7:45 AM To: dev@lucenenet.apache.org Subject: GitHub Issue/PR Templates Hello all, I have been working on setting up some issue and PR templates in GitHub so we don't have people submitting "How-To" questions and PRs for features from newer versions of Lucene - issues that eat up a lot of our time to review. https://s.apache.org/lucenenet-issue https://s.apache.org/lucenenet-pr Let's consider this a draft. I am just looking for some feedback from the Lucene.NET committers (and community) to make sure the templates fit in with our goals and Apache policies before we add them to our repository. I took a lot of pointers from both the Lucene repository and ASP.NET Core repository. https://github.com/apache/lucene/issues/new/choose https://github.com/dotnet/aspnetcore/issues/new/choose Please let me know if you think there are things that need polishing, categories to be added, or language that needs to be softened or made more inclusive. Thanks, Shad Storhaug Project Chairperson - Apache Lucene.NET
