You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucenenet.apache.org by "SIBTAIN-ASAD (via GitHub)" <gi...@apache.org> on 2026/10/21 17:59:54 UTC
[PR] Update issue templates for Discussions and issue types [lucenenet]
SIBTAIN-ASAD opened a new pull request, #1506:
URL: https://github.com/apache/lucenenet/pull/1506
Fixes #1505
## Description
I updated the contributor entry points so usability and project questions route to the repository's enabled GitHub Discussions area instead of Stack Overflow. The contributor guide now gives the same guidance as the issue chooser.
Each issue form also sets the matching organization issue type: Bug, Feature, or Task. Documentation improvements use Task because the organization currently exposes Task, Bug, and Feature.
## Verification
- Parsed every issue-form YAML file with Ruby's YAML parser
- Confirmed Discussions is enabled and the referenced issue types exist through the GitHub API
- `git diff --check`
## Checklist
- [x] I read the contributor guide and Code of Conduct.
- [x] Tests are not applicable to this contributor-documentation change.
- [x] Inline API documentation is not applicable.
- [x] Issue #1505 tracks this change.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@lucenenet.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Update issue templates for Discussions and issue types [lucenenet]
Posted by "NightOwl888 (via GitHub)" <gi...@apache.org>.
NightOwl888 commented on code in PR #1506:
URL: https://github.com/apache/lucenenet/pull/1506#discussion_r4340270093
##########
.github/ISSUE_TEMPLATE/30_task.yml:
##########
@@ -9,7 +10,7 @@ body:
If you believe you have an issue that affects the SECURITY of the platform, please do NOT create an issue and instead follow the [ASF vulnerability reporting process](https://apache.org/security/#reporting-a-vulnerability). This is a project of the [Apache Software Foundation](https://apache.org) and follows the ASF [vulnerability handling process](https://apache.org/security/#vulnerability-handling).
- For other types of questions, consider using [StackOverflow](https://stackoverflow.com) and applying the tags `lucene.net` AND `lucene` or join the [Lucene.NET user mailing list](https://lucenenet.apache.org/contributing/index.html#ask-a-question).
+ For other types of questions, use [GitHub Discussions](https://github.com/apache/lucenenet/discussions) or join the [Lucene.NET user mailing list](https://lucenenet.apache.org/contributing/index.html#ask-a-question).
Review Comment:
Please do not remove the link for StackOverflow. We only want to add the new link for GitHub Discussions. StackOverflow is still a useful place to get how-to advice.
##########
.github/ISSUE_TEMPLATE/10_bug_report.yml:
##########
@@ -9,7 +10,7 @@ body:
If you believe you have an issue that affects the SECURITY of the platform, please do NOT create an issue and instead follow the [ASF vulnerability reporting process](https://apache.org/security/#reporting-a-vulnerability). This is a project of the [Apache Software Foundation](https://apache.org) and follows the ASF [vulnerability handling process](https://apache.org/security/#vulnerability-handling).
- For other types of questions, consider using [StackOverflow](https://stackoverflow.com) and applying the tags `lucene.net` AND `lucene` or join the [Lucene.NET user mailing list](https://lucenenet.apache.org/contributing/index.html#ask-a-question).
+ For other types of questions, use [GitHub Discussions](https://github.com/apache/lucenenet/discussions) or join the [Lucene.NET user mailing list](https://lucenenet.apache.org/contributing/index.html#ask-a-question).
Review Comment:
Please do not remove the link for StackOverflow. We only want to add the new link for GitHub Discussions. StackOverflow is still a useful place to get how-to advice.
##########
.github/ISSUE_TEMPLATE/config.yml:
##########
@@ -4,8 +4,8 @@ contact_links:
url: https://lucene.apache.org/core/discussion.html
about: Please discuss platform-agnostic design proposals of the API or features on the Lucene developer mailing list. These types of changes need to go through Lucene's design review before they can be ported from Java to Lucene.NET in a later version.
- name: Ask a How-To Question
- url: https://stackoverflow.com/questions/tagged/lucene.net
- about: Please ask usability questions on StackOverflow. Consider including BOTH the lucene.net tag and the lucene tag. Alternatively, join the Lucene.NET user mailing list by sending an email to user-subscribe@lucenenet.apache.org. Once signed up, you can submit your question to user@lucenenet.apache.org.
+ url: https://github.com/apache/lucenenet/discussions
+ about: Please ask usability and project questions in GitHub Discussions. Alternatively, join the Lucene.NET user mailing list by sending an email to user-subscribe@lucenenet.apache.org. Once signed up, you can submit your question to user@lucenenet.apache.org.
Review Comment:
Please do not remove the info for StackOverflow. We only want to add the new link for GitHub Discussions. StackOverflow is still a useful place to get how-to advice.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@lucenenet.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Update issue templates for Discussions and issue types [lucenenet]
Posted by "NightOwl888 (via GitHub)" <gi...@apache.org>.
NightOwl888 commented on code in PR #1506:
URL: https://github.com/apache/lucenenet/pull/1506#discussion_r4347732194
##########
.github/ISSUE_TEMPLATE/10_bug_report.yml:
##########
@@ -9,7 +10,7 @@ body:
If you believe you have an issue that affects the SECURITY of the platform, please do NOT create an issue and instead follow the [ASF vulnerability reporting process](https://apache.org/security/#reporting-a-vulnerability). This is a project of the [Apache Software Foundation](https://apache.org) and follows the ASF [vulnerability handling process](https://apache.org/security/#vulnerability-handling).
- For other types of questions, consider using [StackOverflow](https://stackoverflow.com) and applying the tags `lucene.net` AND `lucene` or join the [Lucene.NET user mailing list](https://lucenenet.apache.org/contributing/index.html#ask-a-question).
+ For other types of questions, use [GitHub Discussions](https://github.com/apache/lucenenet/discussions) or join the [Lucene.NET user mailing list](https://lucenenet.apache.org/contributing/index.html#ask-a-question).
Review Comment:
Agreed. StackOverflow should be listed after GitHub Discussions and the mailing lists.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@lucenenet.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Update issue templates for Discussions and issue types [lucenenet]
Posted by "SIBTAIN-ASAD (via GitHub)" <gi...@apache.org>.
SIBTAIN-ASAD commented on PR #1506:
URL: https://github.com/apache/lucenenet/pull/1506#issuecomment-6351318005
Thanks for clarifying the preferred order. I restored Stack Overflow after GitHub Discussions and the mailing list in both issue-form guidance blocks, and added it as a separate contact link after those two options in `config.yml`. The update is in 2a03ccf9b; all issue-template YAML parses and `git diff --check` passes.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@lucenenet.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Update issue templates for Discussions and issue types [lucenenet]
Posted by "paulirwin (via GitHub)" <gi...@apache.org>.
paulirwin commented on code in PR #1506:
URL: https://github.com/apache/lucenenet/pull/1506#discussion_r4340689793
##########
.github/ISSUE_TEMPLATE/10_bug_report.yml:
##########
@@ -9,7 +10,7 @@ body:
If you believe you have an issue that affects the SECURITY of the platform, please do NOT create an issue and instead follow the [ASF vulnerability reporting process](https://apache.org/security/#reporting-a-vulnerability). This is a project of the [Apache Software Foundation](https://apache.org) and follows the ASF [vulnerability handling process](https://apache.org/security/#vulnerability-handling).
- For other types of questions, consider using [StackOverflow](https://stackoverflow.com) and applying the tags `lucene.net` AND `lucene` or join the [Lucene.NET user mailing list](https://lucenenet.apache.org/contributing/index.html#ask-a-question).
+ For other types of questions, use [GitHub Discussions](https://github.com/apache/lucenenet/discussions) or join the [Lucene.NET user mailing list](https://lucenenet.apache.org/contributing/index.html#ask-a-question).
Review Comment:
Yeah, as I noted, I'm fine with leaving SO for now. But Discussions should at least be listed first. It is part of Apache Infra, after all, while SO is not.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@lucenenet.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Update issue templates for Discussions and issue types [lucenenet]
Posted by "paulirwin (via GitHub)" <gi...@apache.org>.
paulirwin merged PR #1506:
URL: https://github.com/apache/lucenenet/pull/1506
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@lucenenet.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Update issue templates for Discussions and issue types [lucenenet]
Posted by "paulirwin (via GitHub)" <gi...@apache.org>.
paulirwin commented on code in PR #1506:
URL: https://github.com/apache/lucenenet/pull/1506#discussion_r4340539025
##########
.github/ISSUE_TEMPLATE/10_bug_report.yml:
##########
@@ -9,7 +10,7 @@ body:
If you believe you have an issue that affects the SECURITY of the platform, please do NOT create an issue and instead follow the [ASF vulnerability reporting process](https://apache.org/security/#reporting-a-vulnerability). This is a project of the [Apache Software Foundation](https://apache.org) and follows the ASF [vulnerability handling process](https://apache.org/security/#vulnerability-handling).
- For other types of questions, consider using [StackOverflow](https://stackoverflow.com) and applying the tags `lucene.net` AND `lucene` or join the [Lucene.NET user mailing list](https://lucenenet.apache.org/contributing/index.html#ask-a-question).
+ For other types of questions, use [GitHub Discussions](https://github.com/apache/lucenenet/discussions) or join the [Lucene.NET user mailing list](https://lucenenet.apache.org/contributing/index.html#ask-a-question).
Review Comment:
So, I don't disagree with adding it back, at least for now, but... I could see a path where we want to remove it as a suggestion.
Stack Overflow has had a precipitous decline in the AI era, as more people move their questions to AI chat agents. It is starting to feel a bit like a ghost town over there.
GitHub Discussions, on the other hand, achieves all of the goals with fewer compromises. It gives people a focused place to ask questions related to our project. Importantly, we get email notifications posted to our mailing list when people do so, because it's integrated into the ASF yaml stuff. Since it's part of our project, it makes things like issue links trivial. And the GitHub editing experience is subjectively (IMO) superior.
We (as a project) are not notified when someone posts a question on SO. I was able to set up some notifications there, but it's not the easiest thing to do, and you have to do it manually. It also requires separate user accounts, etc.
Honestly, if we wanted to just drop the suggestion to go to SO, I would be in favor of it. Users could still go and do that on their own, of course. But if they want the team's attention, they should probably use GitHub Discussions now.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@lucenenet.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Update issue templates for Discussions and issue types [lucenenet]
Posted by "NightOwl888 (via GitHub)" <gi...@apache.org>.
NightOwl888 commented on code in PR #1506:
URL: https://github.com/apache/lucenenet/pull/1506#discussion_r4340648525
##########
.github/ISSUE_TEMPLATE/10_bug_report.yml:
##########
@@ -9,7 +10,7 @@ body:
If you believe you have an issue that affects the SECURITY of the platform, please do NOT create an issue and instead follow the [ASF vulnerability reporting process](https://apache.org/security/#reporting-a-vulnerability). This is a project of the [Apache Software Foundation](https://apache.org) and follows the ASF [vulnerability handling process](https://apache.org/security/#vulnerability-handling).
- For other types of questions, consider using [StackOverflow](https://stackoverflow.com) and applying the tags `lucene.net` AND `lucene` or join the [Lucene.NET user mailing list](https://lucenenet.apache.org/contributing/index.html#ask-a-question).
+ For other types of questions, use [GitHub Discussions](https://github.com/apache/lucenenet/discussions) or join the [Lucene.NET user mailing list](https://lucenenet.apache.org/contributing/index.html#ask-a-question).
Review Comment:
While you are right in that StackOverflow is on the decline, historically we haven't been the best at being able to answer usability questions. But adding the templates has cut down on a lot of the unwanted noise in the issues lists.
I am not strictly opposed to removing the StackOverflow link, but my fear is that the GitHub Discussions may end up being another ghost town like StackOverflow and the mailing list. IMO, it is sensible to remind people that is an option, especially if they don't get a reply on GitHub Discussions.
I am not sure what the reason is, but our user mailing list has also received much less traffic lately. I suspect that AI is answering a lot of those questions, as well. Maybe we should just add AI to the list of options to answer "how-to" questions, since a prompt reply is guaranteed. Although, by now I am pretty sure most developers are aware that using AI for such things is extremely helpful, so maybe it is not necessary to add a reminder.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@lucenenet.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org