summaryrefslogtreecommitdiff
path: root/hacking/ticket_stubs/pr_duplicate.md
diff options
context:
space:
mode:
Diffstat (limited to 'hacking/ticket_stubs/pr_duplicate.md')
-rw-r--r--hacking/ticket_stubs/pr_duplicate.md16
1 files changed, 8 insertions, 8 deletions
diff --git a/hacking/ticket_stubs/pr_duplicate.md b/hacking/ticket_stubs/pr_duplicate.md
index 0b4f16466a..ef692a0b01 100644
--- a/hacking/ticket_stubs/pr_duplicate.md
+++ b/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!