Wow! I checked out the link you provided, and this is a great approach to better manage the kinds of "Issues" that get created on the repo.
Nice work. As for whether the dev mailing list should be on that page under some category...to me, it feels like it should. I guess I'd kinda expect to see it under a category that is something like ".NET specific API improvements" maybe with a description like "Please discuss all .NET specific API improvements on the Lucene.NET developer mailing list. This provides an opportunity for the community to way in and helps us gauge the level of interest in the proposed improvement." -Ron Clabo Apache Lucene.NET Committer -----Original Message----- From: Shad Storhaug <s...@shadstorhaug.com> Sent: Friday, October 20, 2023 3:31 AM To: d...@lucene.apache.org Cc: dev@lucenenet.apache.org Subject: Where do we send users who want to request changes to the Lucene application API or design? Hello, We on the Lucene.NET project are setting up issue templates for GitHub to put some guardrails in place about submitting design changes that are not specific to the .NET platform, but more general about Lucene. We are thinking of dropping a link to you, but not sure whether to suggest using the Lucene dev mailing list, the "Enhancement Request/Suggestion" category on GitHub Issues, or somewhere else. Please advise. This is a work in progress, but here is what it looks like so far: https://github.com/NightOwl888/lucenenet-issue-template-demo/issues/new/choo se Thank you, Shad Storhaug Project Chairperson - Lucene.NET
