(A) Fix a bug in the doc generator that was clobbering the force parameter for the copy module.

(B) This is a work in progress but the idea is to have text snippets where we can respond to tickets with a bit more helpful info.
Not active just yet.

lib/ansible/utils/module_docs.py

@@ -85,7 +85,9 @@ def get_docstring(filename, verbose=False):
                             if not doc.has_key(key):
                                 doc[key] = value
                             else:
-                                doc[key].update(value)
+                                # not sure this is the only example but don't do this for the copy module
+                                if key != 'force':
+                                    doc[key].update(value)
 
                 if 'EXAMPLES' in (t.id for t in child.targets):
                     plainexamples = child.value.s[1:]  # Skip first empty line

ticket_stubs/another_project.md

@@ -0,0 +1,23 @@
+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!
+
+

ticket_stubs/cleanup_commits.md

@@ -0,0 +1,26 @@
+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 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-devel - for user questions, tips, and tricks
+   * https://groups.google.com/forum/#!forum/ansible-project - 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

@@ -0,0 +1,23 @@
+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 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-devel - for user questions, tips, and tricks
+   * https://groups.google.com/forum/#!forum/ansible-project - 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

@@ -0,0 +1,23 @@
+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 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-devel - for user questions, tips, and tricks
+   * https://groups.google.com/forum/#!forum/ansible-project - for strategy, future planning, and questions about writing code
+
+Thank you once again for this and your interest in Ansible!
+

ticket_stubs/no_thanks.md

@@ -0,0 +1,20 @@
+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.
+
+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
+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!
+
+   * https://groups.google.com/forum/#!forum/ansible-devel - for user questions, tips, and tricks
+
+In the future, sometimes starting a discussion on the development list prior to implenting a feature can make getting things included a little easier, but it's not always neccessary.
+
+Thank you once again for this and your interest in Ansible!
+

ticket_stubs/not_a_bug.md

@@ -0,0 +1,21 @@
+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-devel - for user questions, tips, and tricks
+   * https://groups.google.com/forum/#!forum/ansible-project - 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!
+

ticket_stubs/questions_to_list.md

@@ -0,0 +1,17 @@
+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.freenode.net   
+   * 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!
+
+

ticket_stubs/resolved.md

@@ -0,0 +1,20 @@
+Closing This Ticket
+===================
+
+Hi!
+
+We believe recent commits (likely detailed above) 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:
+
+   * 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
+
+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.
+
+Thank you!
+
+

ticket_stubs/thanks.md

@@ -0,0 +1,21 @@
+Submission Recieved
+===================
+
+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 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-devel - for user questions, tips, and tricks
+   * https://groups.google.com/forum/#!forum/ansible-project - for strategy, future planning, and questions about writing code
+
+Thank you once again for this and your interest in Ansible!
+