Cleanup of cannned responses (#76689)

* removed those made obsolete by bot
 * tried to rephrase to be more informative and require less updates in the future

Co-authored-by: Sandra McCann <samccann@redhat.com>
Co-authored-by: John R Barker <john@johnrbarker.com>
Co-authored-by: Alicia Cozine <879121+acozine@users.noreply.github.com>

hacking/ticket_stubs/README.md

@@ -1,12 +1,6 @@
-Ticket Stubs 
-============
-
 What's this?
 
 This is a directory of common responses to save some typing when responding to GitHub tickets to avoid
-some carpal tunnel syndrome events as Ansible takes off into stratosphere territory.
+some carpal tunnel syndrome events as Ansible maintainers deal with the ticket influx.
-
-These are actually on GitHub so it's easy for people to make these snippets of text even more helpful
-or to correct typos. 
 
-For how to use these see https://github.com/ansible/ansible/tree/devel/ticket_stubs
+They are present in the project git repo (on GitHub) so it's easy for people to share and update these snippets of text.

hacking/ticket_stubs/bug_cannot_reproduce.md

@@ -1,26 +0,0 @@
-Cannot Reproduce
-================
-
-Hi!
-
-Thanks very much for your submission to Ansible.  It sincerely means a lot to us. 
-
-Testing this on the version you have specified, we cannot reproduce this problem.
-
-Our reasons and evidence for this are:
-
-   * INSERT HERE
-
-And we suggest that:
-
-   * INSERT THINGS TO DO HERE
-
-As such, we are most likely going to close this ticket.  Should you disagree with this conclusion, you may also wish to join our mailing lists, which are very active:
-
-   * https://groups.google.com/forum/#!forum/ansible-project - for user questions, tips, and tricks
-   * https://groups.google.com/forum/#!forum/ansible-devel - for strategy, future planning, and questions about writing code
-
-Thank you once again for this and your interest in Ansible!
-
-
-

hacking/ticket_stubs/bug_confirmed_p1_or_p2.md

@@ -1,21 +0,0 @@
-Confirmed, Thanks!
-==================
-
-Hi!
-
-Thanks very much for your submission to Ansible.  It sincerely means a lot to us.
-
-We've confirmed this is an issue and have marked as a high priority item to resolve.
-
-Additionally:
-
-   * INSERT REASONS!
-
-We will definitely see your comments on this issue when reading this ticket, but may not be able to reply promptly.  You may also wish to join one of our two mailing lists
-which are very active:
-
-   * https://groups.google.com/forum/#!forum/ansible-project - for user questions, tips, and tricks
-   * https://groups.google.com/forum/#!forum/ansible-devel - for strategy, future planning, and questions about writing code
-
-Thank you once again for this and your interest in Ansible!
-

hacking/ticket_stubs/bug_internal_api.md

@@ -1,16 +1,23 @@
-Internal Ansible API
-====================
-
 Hi!
 
-Thanks very much for your submission to Ansible.  It sincerely means a lot to us
+Thanks very much for your submission to Ansible.  It means a lot to us
-to have an active community that is willing to submit feedback so that we may
+to have an active community that is willing to submit feedback so that we can
 continue to make Ansible better.
 
-The internal Python API is considered an unsupported aspect of Ansible and this
+The Ansible Python API is considered internal and an unsupported aspect of Ansible,
-is not considered a bug unless there is an issue with an Ansible binary
+as such this is not considered a bug unless it causes an issue with Ansible command line tools
-(`ansible`, `ansible-playbook`, `ansible-doc`, etc) or an issue with an external
+(`ansible`, `ansible-playbook`, `ansible-doc`, etc).
-API such as are provided for the development of plugins (modules, dynamic
+
-inventories, callbacks, strategies, etc).
+We do support the provided API for use in developing plugins (modules, dynamic inventories, callbacks, strategies, etc),
+but this does not seem to match that case.
+
+If you really need a stable API target to use Ansible, consider using ansible-runner:
+
+   * https://github.com/ansible/ansible-runner
+
+Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time.
+If you or anyone else has any further questions, please let us know by using any of the communication methods listed in the page below:
+
+   * https://docs.ansible.com/ansible/latest/community/communication.html
 
 Thank you once again for this and your interest in Ansible!

hacking/ticket_stubs/bug_is_really_a_question.md

@@ -1,17 +0,0 @@
-List Information
-================
-
-Hi!
-
-Thanks very much for your interest in Ansible.  It sincerely means a lot to us. 
-
-This appears to be a user question, and we'd like to direct these kinds of things to either the mailing list or the IRC channel.
-
-   * IRC: #ansible on [irc.libera.chat](https://libera.chat/)
-   * mailing list: https://groups.google.com/forum/#!forum/ansible-project
-
-If you can stop by there, we'd appreciate it.  This allows us to keep the issue tracker for bugs, pull requests, RFEs and the like.
-
-Thank you once again and we look forward to seeing you on the list or IRC.  Thanks!
-
-

hacking/ticket_stubs/bug_misunderstanding.md

@@ -1,27 +0,0 @@
-Possible Misunderstanding
-=========================
-
-Hi!
-
-Thanks very much for your submission to Ansible.  It sincerely means a lot to us.
-
-We believe the ticket you have filed is being somewhat misunderstood, as one thing works a little differently than stated.
-
-In particular, we believe you have said:
-
-   * THING ONE
-
-However, however what is happening is that:
-
-   * THING TWO
-
-We would suggest:
-
-   * THING THREE
-
-In the future, this might be a topic more well suited for the user list, which you can also post here if you'd like some more help with the above.
-   
-   * https://groups.google.com/forum/#!forum/ansible-project
-
-Thank you once again for this and your interest in Ansible!
-

hacking/ticket_stubs/bug_not_a_bug.md

@@ -1,21 +0,0 @@
-Is This A Bug?
-==============
-
-Hi!
-
-Thanks very much for your submission to Ansible.  It sincerely means a lot to us.
-
-We're not sure this is a bug, and we don't mean for this to be confrontational.  Let's explain what we're thinking:
-
-   * INSERT ITEM HERE
-
-As such, we're going to close this ticket.  However, we're open to being corrected, should you wish to discuss.  You can stop by one of our two mailing lists 
-to talk about this and we might be persuaded otherwise.
-   
-   * https://groups.google.com/forum/#!forum/ansible-project - for user questions, tips, and tricks
-   * https://groups.google.com/forum/#!forum/ansible-devel - for strategy, future planning, and questions about writing code
-
-Comments on closed tickets aren't something we monitor, so if you do disagree with this, a mailing list thread is probably appropriate.
-
-Thank you once again for this and your interest in Ansible!
-

hacking/ticket_stubs/bug_wrong_repo.md

@@ -0,0 +1,38 @@
+Hi!
+
+Thanks very much for your interest in Ansible.  It means a lot to us.
+
+This appears to be something that should be filed against another project or bug tracker. Here's why:
+
+   * FILL IN
+
+<< CHOOSE AS APPROPRIATE >>
+
+   * https://github.com/ansible-community/ansible-lint
+   * https://github.com/ansible/ansible-runner
+   * https://github.com/ansible/ansible-navigator
+   * https://github.com/ansible-community/antsibull
+   * https://github.com/ansible-community/ara
+   * https://github.com/ansible/awx
+   * https://github.com/ansible-collections/community.general
+   * https://github.com/ansible-community/molecule
+   * For AAP or Tower licensees report issues via your Red Hat representative or https://issues.redhat.com 
+
+If you can stop by the tracker or forum for one of those projects, we'd appreciate it.
+
+Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time.
+Should you still wish to discuss things further, or if you disagree with our thought process, please stop by one of our two mailing lists:
+
+   * https://groups.google.com/forum/#!forum/ansible-devel
+   * Matrix: [#devel:ansible.im](https://matrix.to/#/#devel:ansible.im)
+   * IRC: #ansible-devel on [irc.libera.chat](https://libera.chat/)
+
+We'd be happy to discuss things.
+
+See  this page for a complete list of communication channels and their purposes:
+
+   * https://docs.ansible.com/ansible/latest/community/communication.html
+
+Thank you once again!
+
+

hacking/ticket_stubs/change_applied.md

@@ -1,16 +0,0 @@
-Change Applied
-==============
-
-Hi!
-
-A change has been applied for this ticket, which should resolve this item for you.
-
-If you believe this ticket is not resolved, or have further questions, please let us know by stopping by one of the two mailing lists, as appropriate:
-
-   * https://groups.google.com/forum/#!forum/ansible-project - for user questions, tips, and tricks
-   * https://groups.google.com/forum/#!forum/ansible-devel - for strategy, future planning, and questions about writing code
-
-Because this project is very active, we're unlikely to see comments on closed tickets, though the mailing list is a great way to get involved or discuss this one further.
-
-Thanks!
-

hacking/ticket_stubs/collections.md

@@ -1,14 +1,16 @@
 Hi!
 
-Thank you very much for your submission to Ansible. It sincerely means a lot to us that you've taken the time to contribute.
+Thank you very much for your submission to Ansible. It means a lot to us that you've taken the time to contribute.
 
-Per recent announcements at AnsibleFest Atlanta 2019, going forward we are no longer accepting new one off modules/plugins, or modules/plugins that create a new category.
+Since Ansible 2.10 we are no longer accepting new modules/plugins into Ansible core.  However, we recommend looking into providing this functionality through Ansible Galaxy via Ansible Collections. You can find more information about collections at:
 
-However, we recommend looking into providing this functionality through Ansible Galaxy via Ansible Collections. You can find more information about collections at https://docs.ansible.com/ansible/devel/dev_guide/developing_collections.html.
+   * https://docs.ansible.com/ansible/devel/dev_guide/developing_collections.html.
 
-Thank you once again for this and your interest in Ansible!
+Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time.
+The mailing list and irc are great ways to ask questions, or post if you don't think this particular issue is resolved.
+
+See  this page for a complete and up to date list of communication channels and their purposes:
 
-If you have further questions please stop by IRC or the mailing list:
+   * https://docs.ansible.com/ansible/latest/community/communication.html
 
-   * IRC: #ansible on [irc.libera.chat](https://libera.chat/)
+Thank you once again for this and your interest in Ansible!
-   * mailing list: https://groups.google.com/forum/#!forum/ansible-project

hacking/ticket_stubs/file_under_another_project.md

@@ -1,23 +0,0 @@
-Should This Be Filed Elsewhere?
-===============================
-
-Hi!
-
-Thanks very much for your interest in Ansible.  It sincerely means a lot to us. 
-
-This appears to be something that should be filed against another project or bug tracker, and let us explain our reasons for thinking this:
-
-   * FILL IN
-
-If you can stop by the tracker or forum for one of those projects, we'd appreciate it.  
-
-Should you still wish to discuss things further, or if you disagree with our thought process, please stop by one of our two mailing lists:
-
-  * https://groups.google.com/forum/#!forum/ansible-project
-  * https://groups.google.com/forum/#!forum/ansible-devel
-
-We'd be happy to discuss things.
-
-Thank you once again!
-
-

hacking/ticket_stubs/great_idea.md

@@ -1,25 +0,0 @@
-Submission Received
-===================
-
-Hi!
-
-Thanks very much for your submission to Ansible.  It sincerely means a lot to us.
-
-We really like this idea, particularly:
-
-   * INSERT REASONS!
-
-It might take us a little while to get to this one.  Just as a quick reminder of things, this is a really busy project.  We have over 800 contributors and to manage the queue effectively
-we assign things a priority between P1 (highest) and P5.  
-
-We may also ask some questions and it may be a while before we can get to this, but we'd like to thank you very much for your time!  
-We'll work things in priority order, so just wanted you to be aware of the queue and know we haven't forgotten about you!
-
-We will definitely see your comments on this issue when reading this ticket, but may not be able to reply promptly.  You may also wish to join one of our two mailing lists
-which are very active:
-
-   * https://groups.google.com/forum/#!forum/ansible-project - for user questions, tips, and tricks
-   * https://groups.google.com/forum/#!forum/ansible-devel - for strategy, future planning, and questions about writing code
-
-Thank you once again for this and your interest in Ansible!
-

hacking/ticket_stubs/guide_newbie_about_gh_and_contributing_to_ansible.md

@@ -12,4 +12,10 @@ gathered for you:
 • https://opensource.guide/how-to-contribute/
 • https://docs.ansible.com/ansible/devel/community/
 
+Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time.
+
+If you or anyone else has any further questions, please let us know by using any of the communication methods listed in the page below:
+
+  https://docs.ansible.com/ansible/latest/community/communication.html
+
 Have a nice day!

hacking/ticket_stubs/needs_info.md

@@ -1,23 +0,0 @@
-Information Request
-===================
-
-Hi!
-
-Thanks very much for your submission to Ansible.  It sincerely means a lot to us. 
-
-We have some questions we'd like to know about before we can get this request queued up.   If you can help answer them, we'd greatly appreciate it:
-
-   * (A) INSERT QUESTION HERE
-
-Just as a quick reminder of things, this is a really busy project.  We have over 800 contributors and to manage the queue effectively
-we assign things a priority between P1 (highest) and P5.  We'd like to thank you very much for your time!  
-We'll work things in priority order, so just wanted you to be aware of the queue and know we haven't forgotten about you!
-
-We will definitely see your comments on this issue when reading this ticket, but may not be able to reply promptly.  You may also wish to join one of our two mailing lists
-which are very active:
-
-   * https://groups.google.com/forum/#!forum/ansible-project - for user questions, tips, and tricks
-   * https://groups.google.com/forum/#!forum/ansible-devel - for strategy, future planning, and questions about writing code
-
-Thank you once again for this and your interest in Ansible!
-

hacking/ticket_stubs/needs_locale_info.md

@@ -1,45 +0,0 @@
-This issue may be related to locale or text encoding. To help troubleshoot and reproduce the issue, we need some additional information.
-
-If running ansible from the command line, try to gather this information from the same shell and terminal.
-
-To collect the locale, language and text encoding settings, use the ```locale``` command:
-``` shell
-    locale
-```
-
-That output should look something like:
-```
-LANG="en_US.UTF-8"
-LC_COLLATE="en_US.UTF-8"
-LC_CTYPE="en_US.UTF-8"
-LC_MESSAGES="en_US.UTF-8"
-LC_MONETARY="en_US.UTF-8"
-LC_NUMERIC="en_US.UTF-8"
-LC_TIME="en_US.UTF-8"
-LC_ALL=
-```
-
-If 'sudo' or similar tools are being used, we will need the locale info from a sudo shell as well.
-For example:
-``` shell
-sudo locale
-```
-
-Also include the value of the ```TERM``` environment variable. To get the info, paste the output of echoing the ```TERM``` variable from a shell like:
-``` shell
-echo $TERM
-```
-
-Cut & paste the output from those commands into a comment here. To preserve the original
-formatting, use \`\`\` around the text, for example:
-
-\`\`\`
-    LANG="en_US.UTF-8"
-    LC_COLLATE="en_US.UTF-8"
-    LC_CTYPE="en_US.UTF-8"
-    LC_MESSAGES="en_US.UTF-8"
-    LC_MONETARY="en_US.UTF-8"
-    LC_NUMERIC="en_US.UTF-8"
-    LC_TIME="en_US.UTF-8"
-    LC_ALL=
-\`\`\`

hacking/ticket_stubs/needs_template.md

@@ -1,32 +0,0 @@
-Can You Help Us Out?
-====================
-
-Thanks for filing a ticket!
-
-It looks like you might not have filled out the issue description based on our standard issue template.  You might not have known about that, and that's ok too, we'll tell you how to do it.
-
-We have a standard template because Ansible is a really busy project and it helps to have some standard information in each ticket, and GitHub doesn't yet provide a standard facility to do this like some other bug trackers.  We hope you understand as this is really valuable to us!.
-
-Solving this is simple: please use the issue template provided when you open a new issue. That's it!
-
-If You Had A Question To Ask Instead
-====================================
-
-If you happened to have a "how do I do this in Ansible" type of question, that's probably more of a user-list question than a bug report, and you should probably ask this question on the project mailing list instead.
-
-However, if you think you have a bug, the report is the way to go!  We definitely want all the bugs filed :)  Just trying to help!
-
-Mailing Lists
-=============
-
-If you have concerns or questions, you're welcome to stop by the ansible-project or ansible-development mailing lists, as appropriate.  Here are the links:
-
-  * https://groups.google.com/forum/#!forum/ansible-project - for discussion of bugs and how-to type questions
-  * https://groups.google.com/forum/#!forum/ansible-devel - for discussion on how to implement a code change, or feature brainstorming among developers
-
-Thanks again for the interest in Ansible!
-
-Closing this ticket
-===================
-
-If you still feel like this should be a ticket, please reopen a new one and properly fill in the template.

hacking/ticket_stubs/no_thanks.md

@@ -1,18 +1,17 @@
-Question About This One
-=======================
-
 Hi!
 
-Thanks very much for your submission to Ansible.  It sincerely means a lot to us that you've taken time to contribute.
+Thanks very much for your submission to Ansible.  It means a lot to us that you've taken time to contribute.
 
-Unfortunately, we're not sure if we want this feature in the program, and I don't want this to seem confrontational.  Our reasons for this are:
+Unfortunately, we're not sure if we want this feature in the program, and I don't want this to seem confrontational.
+Our reasons for this are:
 
    * (A) INSERT ITEM HERE
 
-However, we're absolutely always up for discussion.  Since this is a really busy project, we don't always see comments on closed tickets, but want to encourage
+However, we're absolutely always up for discussion.
-open dialog.  You can stop by the development list, and we'd be glad to talk about it - and we might even be persuaded otherwise!
+Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time.
+If you or anyone else has any further questions, please let us know by using any of the communication methods listed in the page below:
 
-   * https://groups.google.com/forum/#!forum/ansible-devel
+   * https://docs.ansible.com/ansible/latest/community/communication.html
 
 In the future, sometimes starting a discussion on the development list prior to implementing a feature can make getting things included a little easier, but it's not always necessary.
 

hacking/ticket_stubs/pr_cleanup_commits.md

@@ -1,26 +0,0 @@
-Cleanup Request
-===============
-
-Hi!
-
-Thanks very much for your submission to Ansible.  It sincerely means a lot to us. 
-
-We do require submissions to be free of merge commits, which cause difficulties in reviewing and merging code, and also affect the history of the source tree.
-To resolve this problem, it may be helpful to create a new branch and cherry-pick commits onto it.
-
-   * In general, always start a "topic branch" named after each thing you would like to contribute
-   * use "git pull --rebase" vs "git pull" to stay in tune with upstream, as well as "git rebase" vs "git merge"
-   * if you have things broken out over many commits, consider submitting just one squashed commit that keeps the history concise
-
-Just as a quick reminder of things, this is a really busy project.  We have over 800 contributors and to manage the queue effectively
-we assign things a priority between P1 (highest) and P5.  We'd like to thank you very much for your time!  
-We'll work things in priority order, so just wanted you to be aware of the queue and know we haven't forgotten about you!
-
-We will definitely see your comments on this issue when reading this ticket, but may not be able to reply promptly.  You may also wish to join one of our two mailing lists
-which are very active:
-
-   * https://groups.google.com/forum/#!forum/ansible-project - for user questions, tips, and tricks
-   * https://groups.google.com/forum/#!forum/ansible-devel - for strategy, future planning, and questions about writing code
-
-Thank you once again for this and your interest in Ansible!
-

hacking/ticket_stubs/pr_duplicate.md

@@ -1,21 +1,21 @@
-Possible Duplicated Efforts
-===========================
-
 Hi!
 
-Thanks very much for your submission to Ansible.  It sincerely means a lot to us that you've taken time to contribute.
+Thanks very much for your submission to Ansible.  It means a lot to us that you've taken time to contribute.
 
 It looks like the work from this pull request is a duplicate of the following PR(s):
 
    * INSERT PR(S) HERE
 
-Based on this, we are going to close this PR in favor of the above.
+Based on this, we are going to close this PR in favor of the above as a consolidated location to keep track of the issue.
 
-However, we're absolutely always up for discussion.  Since this is a really busy project, we don't always see comments on closed tickets, but want to encourage open dialog.  You can stop by the development list, and we'd be glad to talk about it - and we might even be persuaded otherwise!
+However, we're absolutely always up for discussion.
+In the future, sometimes starting a discussion on the development list prior to implementing a feature
+ can make getting things included a little easier, but it's not always necessary.
 
-   * https://groups.google.com/forum/#!forum/ansible-devel
+Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time.
+If you or anyone else has any further questions, please let us know by using any of the communication methods listed in the page below:
 
-In the future, sometimes starting a discussion on the development list prior to implementing a feature can make getting things included a little easier, but it's not always necessary.
+  * https://docs.ansible.com/ansible/latest/community/communication.html
 
 Thank you once again for this and your interest in Ansible!
 

hacking/ticket_stubs/pr_merged.md

@@ -1,16 +1,15 @@
-Merged
-===================
-
 Hi!
 
 This has been merged in, and will also be included in the next major release.
+For more info on our process see https://docs.ansible.com/ansible/devel/reference_appendices/release_and_maintenance.html#ansible-core-workflow
+
+If you or anyone else has any further questions, please let us know by stopping by one of the mailing lists or chat channels, as appropriate.
 
-If you or anyone else has any further questions, please let us know by stopping by one of the two mailing lists, as appropriate:
+Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time.
+The mailing list and irc are great ways to ask questions, or post if you don't think this particular issue is resolved.
 
-   * https://groups.google.com/forum/#!forum/ansible-project - for user questions, tips, and tricks
+See  this page for a complete and up to date list of communication channels and their purposes:
-   * https://groups.google.com/forum/#!forum/ansible-devel - for strategy, future planning, and questions about writing code
 
-Because this project is very active, we're unlikely to see comments made on closed tickets, but the mailing list is a great way to ask questions, or post if you don't think this particular
+   * https://docs.ansible.com/ansible/latest/community/communication.html
-issue is resolved.
 
 Thank you!

hacking/ticket_stubs/pr_needs_rebase.md

@@ -1,25 +0,0 @@
-Rebase Request
-==============
-
-Hi!
-
-Thanks very much for your submission to Ansible.  It sincerely means a lot to us. 
-
-It looks like the code underneath has changed since this was submitted.  Can you take care of rebasing this for us?
-
-   * You should be able to run "git rebase" against this branch to bring it up to date
-   * Resolve any merge conflicts and test changes
-   * Push to the same branch and github should update the pull request automatically.
-
-Just as a quick reminder of things, this is a really busy project.  We have over 800 contributors and to manage the queue effectively
-we assign things a priority between P1 (highest) and P5.  We'd like to thank you very much for your time!  
-We'll work things in priority order, so just wanted you to be aware of the queue and know we haven't forgotten about you!
-
-We will definitely see your comments on this issue when reading this ticket, but may not be able to reply promptly.  You may also wish to join one of our two mailing lists
-which are very active:
-
-   * https://groups.google.com/forum/#!forum/ansible-project - for user questions, tips, and tricks
-   * https://groups.google.com/forum/#!forum/ansible-devel - for strategy, future planning, and questions about writing code
-
-Thank you once again for this and your interest in Ansible!
-

hacking/ticket_stubs/pr_needs_revision.md

@@ -1,23 +0,0 @@
-Revision Request
-================
-
-Hi!
-
-Thanks very much for your submission to Ansible.  It sincerely means a lot to us. 
-
-We'd like to see a few things tweaked if you don't mind.  If you can help resolve these items, we'd greatly appreciate it:
-
-   * (A) INSERT ITEM HERE
-
-Just as a quick reminder of things, this is a really busy project.  We have over 800 contributors and to manage the queue effectively
-we assign things a priority between P1 (highest) and P5.  We'd like to thank you very much for your time!  
-We'll work things in priority order, so just wanted you to be aware of the queue and know we haven't forgotten about you!
-
-We will definitely see your comments on this issue when reading this ticket, but may not be able to reply promptly.  You may also wish to join one of our two mailing lists
-which are very active:
-
-   * https://groups.google.com/forum/#!forum/ansible-project - for user questions, tips, and tricks
-   * https://groups.google.com/forum/#!forum/ansible-devel - for strategy, future planning, and questions about writing code
-
-Thank you once again for this and your interest in Ansible!
-

hacking/ticket_stubs/proposal.md

@@ -1,15 +1,19 @@
-Switch to Proposal
-===================
-
 Hi!
 
-As of April of 2016, we have started using the Ansible Proposal process for large feature ideas or changes in current functionality, such as this. If you are still interested in seeing this new feature get into Ansible, please submit a proposal for it using this process.
+Ansible has a Proposal process for large feature ideas or changes in current design and functionality, such as this.
+If you are still interested in seeing this new feature get into Ansible, please submit a proposal for it using this process.
 
 https://github.com/ansible/proposals/blob/master/proposals_process_proposal.md
 
-If you have any further questions, please let us know by stopping by our devel mailing list, or our devel IRC channel:
+Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time.
+The mailing list and irc are great ways to ask questions, or post if you don't think this particular issue is resolved.
 
    * #ansible-devel on [irc.libera.chat](https://libera.chat/)
    * https://groups.google.com/forum/#!forum/ansible-devel
 
+
+Or check this page for a more complete list of communication channels and their purposes:
+
+   * https://docs.ansible.com/ansible/latest/community/communication.html
+
 Thank you!

hacking/ticket_stubs/question_not_bug.md

@@ -0,0 +1,19 @@
+Hi!
+
+Thanks very much for your interest in Ansible.  It means a lot to us.
+
+This appears to be a user question, and we'd like to direct these kinds of things to either the mailing list or the IRC channel.
+
+   * IRC: #ansible on [irc.libera.chat](https://libera.chat/)
+   * mailing list: https://groups.google.com/forum/#!forum/ansible-project
+
+See  this page for a complete and up to date list of communication channels and their purposes:
+
+   * https://docs.ansible.com/ansible/latest/community/communication.html
+
+Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time.
+If don't you think this particular issue is resolved, you should still stop by there first, we'd appreciate it.
+This allows us to keep the issue tracker for bugs, pull requests, RFEs and the like.
+
+Thank you once again and we look forward to seeing you on the list or IRC.  Thanks!
+

hacking/ticket_stubs/resolved.md

@@ -1,20 +1,16 @@
-Closing This Ticket
-===================
-
 Hi!
 
-We believe recent commits (likely detailed above) should resolve this question or problem for you.
+We have ascertained that the following PR/commits should resolve this question or problem for you.
-
-This will also be included in the next major release.
 
-If you continue seeing any problems related to this issue, or if you have any further questions, please let us know by stopping by one of the two mailing lists, as appropriate:
+<< INSERT SHA/PR LINK HERE >>
 
-   * https://groups.google.com/forum/#!forum/ansible-project - for user questions, tips, and tricks
+This should be included newer releases starting with << RELEASE/the next [major] release(s) >>.
-   * https://groups.google.com/forum/#!forum/ansible-devel - for strategy, future planning, and questions about writing code
 
-Because this project is very active, we're unlikely to see comments made on closed tickets, but the mailing list is a great way to ask questions, or post if you don't think this particular
+Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time.
-issue is resolved.
+The mailing list and irc are great ways to ask questions, or post if you don't think this particular issue is resolved.
 
-Thank you!
+See  this page for a complete list of communication channels and their purposes:
 
+   * https://docs.ansible.com/ansible/latest/community/communication.html
 
+Thank you!

hacking/ticket_stubs/thanks.md

@@ -1,21 +0,0 @@
-Submission Received
-===================
-
-Hi!
-
-Thanks very much for your submission to Ansible.  It sincerely means a lot to us.
-
-Just as a quick reminder of things, this is a really busy project.  We have over 800 contributors and to manage the queue effectively
-we assign things a priority between P1 (highest) and P5.  
-
-We may also ask some questions and it may be a while before we can get to this, but we'd like to thank you very much for your time!  
-We'll work things in priority order, so just wanted you to be aware of the queue and know we haven't forgotten about you!
-
-We will definitely see your comments on this issue when reading this ticket, but may not be able to reply promptly.  You may also wish to join one of our two mailing lists
-which are very active:
-
-   * https://groups.google.com/forum/#!forum/ansible-project - for user questions, tips, and tricks
-   * https://groups.google.com/forum/#!forum/ansible-devel - for strategy, future planning, and questions about writing code
-
-Thank you once again for this and your interest in Ansible!
-

hacking/ticket_stubs/wider_discussion.md

@@ -1,18 +1,26 @@
-Submission Received
-===================
-
 Hi!
 
-Thanks very much for your submission to Ansible.  It sincerely means a lot to us.
+Thanks very much for your submission to Ansible.  It means a lot to us.
 
-We are interested in this idea and would like to see a wider discussion on it
+We are interested in this idea and would like to see a wider discussion on it on one of our lists.
-on one of our lists.  Reasons for this include:
+Reasons for this include:
 
    * INSERT REASONS!
 
+Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time.
 Can you please post on ansible-development list so we can talk about this idea with the wider group?
 
    * https://groups.google.com/forum/#!forum/ansible-devel
+   * Matrix: [#devel:ansible.im](https://matrix.to/#/#devel:ansible.im)
+   * #ansible-devel on [irc.libera.chat](https://libera.chat/)
+
+Or bring up in one of the weekly Matrix/IRC meetings with the core group:
+
+   * https://github.com/ansible/community/issues?q=is:open+label:meeting_agenda+label:core
+
+For other alternatives, check this page for a more complete list of communication channels and their purposes:
+
+   * https://docs.ansible.com/ansible/latest/community/communication.html
 
 Thank you once again for this and your interest in Ansible!