Update response ticket stubs.

ticket_stubs/cleanup_commits.md

@@ -19,8 +19,8 @@ We'll work things in priority order, so just wanted you to be aware of the queue
 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 is very active:
 
-   * https://groups.google.com/forum/#!forum/ansible-devel - for user questions, tips, and tricks
-   * https://groups.google.com/forum/#!forum/ansible-project - for strategy, future planning, and questions about writing code
+   * 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!
 

ticket_stubs/great_idea.md

@@ -0,0 +1,25 @@
+Submission Recieved
+===================
+
+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 forgot 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 is 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!
+

ticket_stubs/need_info.md

@@ -16,8 +16,8 @@ We'll work things in priority order, so just wanted you to be aware of the queue
 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 is very active:
 
-   * https://groups.google.com/forum/#!forum/ansible-devel - for user questions, tips, and tricks
-   * https://groups.google.com/forum/#!forum/ansible-project - for strategy, future planning, and questions about writing code
+   * 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!
 

ticket_stubs/need_revision.md

@@ -16,8 +16,8 @@ We'll work things in priority order, so just wanted you to be aware of the queue
 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 is very active:
 
-   * https://groups.google.com/forum/#!forum/ansible-devel - for user questions, tips, and tricks
-   * https://groups.google.com/forum/#!forum/ansible-project - for strategy, future planning, and questions about writing code
+   * 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!
 

ticket_stubs/not_a_bug.md

@@ -12,8 +12,8 @@ We're not sure this is a bug, and we don't mean for this to be confrontational.
 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-devel - for user questions, tips, and tricks
-   * https://groups.google.com/forum/#!forum/ansible-project - for strategy, future planning, and questions about writing code
+   * 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.
 

ticket_stubs/resolved.md

@@ -9,8 +9,8 @@ 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:
 
-   * https://groups.google.com/forum/#!forum/ansible-devel - for user questions, tips, and tricks
-   * https://groups.google.com/forum/#!forum/ansible-project - for strategy, future planning, and questions about writing code
+   * 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 made on closed tickets, but the mailing list is a great way to ask questions, or post if you don't think this particular
 issue is resolved.

ticket_stubs/thanks.md

@@ -14,8 +14,8 @@ We'll work things in priority order, so just wanted you to be aware of the queue
 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 is very active:
 
-   * https://groups.google.com/forum/#!forum/ansible-devel - for user questions, tips, and tricks
-   * https://groups.google.com/forum/#!forum/ansible-project - for strategy, future planning, and questions about writing code
+   * 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!
 

ticket_stubs/wider_discussion.md

@@ -0,0 +1,18 @@
+Submission Recieved
+===================
+
+Hi!
+
+Thanks very much for your submission to Ansible.  It sincerely means a lot to us.
+
+We are interested in this idea and would like to see a wider discussion on it
+on one of our lists.  Reasons for this include:
+
+   * INSERT REASONS!
+
+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
+
+Thank you once again for this and your interest in Ansible!
+