2.6 changelog gen/version/root dir cleanup (#40421)

* patched in changelog gen stuff from stable-2.5
* Makefile updates
* release.py as single-source-of-truth
* Remove obsolete ansible-core-sitemap.xml file.
* Move ROADMAP.rst into README.rst.
* dynamic rpm changelog, zap old deb/rpm changelogs
* fix changelog in MANIFEST.in
* Remove obsolete hacking/update.sh script.
* Remove ref to deleted authors script.
* Remove ref to removed module-formatter script.
* Update headings to match script names.
* MANIFEST.in cleanup
* removed RELEASES.txt and versions.yml
* removed obsolete release generation playbook/bits (not used since 2.5)
* misc Makefile cleanup
* speculative changes to DEB versioning
* allow override of DEB_VERSION/DEB_RELEASE

27 files changed, 511 insertions, 47 deletions

diff --git a/hacking/README.md b/hacking/README.md
index 0d3b157cdb..3df98a3c8a 100644
--- a/hacking/README.md
+++ b/hacking/README.md
@@ -1,7 +1,7 @@
 'Hacking' directory tools
 =========================
 
-Env-setup
+env-setup
 ---------
 
 The 'env-setup' script modifies your environment to allow you to run
@@ -21,7 +21,7 @@ can install them from pip
 
 From there, follow ansible instructions on docs.ansible.com as normal.
 
-Test-module
+test-module
 -----------
 
 'test-module' is a simple program that allows module developers (or testers) to run
@@ -55,19 +55,7 @@ return_skeleton_generator.py
 return_skeleton_generator.py helps in generating the RETURNS section of a module. It takes
 JSON output of a module provided either as a file argument or via stdin.
 
-Module-formatter
-----------------
-
-The module formatter is a script used to generate manpages and online
-module documentation.  This is used by the system makefiles and rarely
-needs to be run directly.
-
 fix_test_syntax.py
 ------------------
 
 A script to assist in the conversion for tests using filter syntax to proper jinja test syntax. This script has been used to convert all of the Ansible integration tests to the correct format for the 2.5 release. There are a few limitations documented, and all changes made by this script should be evaluated for correctness before executing the modified playbooks.
-
-Authors
--------
-'authors' is a simple script that generates a list of everyone who has
-contributed code to the ansible repository.
diff --git a/hacking/authors.sh b/hacking/authors.sh
deleted file mode 100755
index 633240fe15..0000000000
--- a/hacking/authors.sh
+++ /dev/null
@@ -1,14 +0,0 @@
-#!/bin/sh
-# script from http://stackoverflow.com/questions/12133583
-set -e
-
-# Get a list of authors ordered by number of commits
-# and remove the commit count column
-AUTHORS=$(git --no-pager shortlog -nse --no-merges | cut -f 2- )
-if [ -z "$AUTHORS" ] ; then
-    echo "Authors list was empty"
-    exit 1
-fi
-
-# Display the authors list and write it to the file
-echo "$AUTHORS" | tee "$(git rev-parse --show-toplevel)/AUTHORS.TXT"
diff --git a/hacking/ticket_stubs/README.md b/hacking/ticket_stubs/README.md
new file mode 100644
index 0000000000..421ea5fcd5
--- /dev/null
+++ b/hacking/ticket_stubs/README.md
@@ -0,0 +1,12 @@
+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.
+
+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
diff --git a/hacking/ticket_stubs/bug_cannot_reproduce.md b/hacking/ticket_stubs/bug_cannot_reproduce.md
new file mode 100644
index 0000000000..108a124c60
--- /dev/null
+++ b/hacking/ticket_stubs/bug_cannot_reproduce.md
@@ -0,0 +1,26 @@
+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!
+
+
+
diff --git a/hacking/ticket_stubs/bug_confirmed_p1_or_p2.md b/hacking/ticket_stubs/bug_confirmed_p1_or_p2.md
new file mode 100644
index 0000000000..463a867586
--- /dev/null
+++ b/hacking/ticket_stubs/bug_confirmed_p1_or_p2.md
@@ -0,0 +1,21 @@
+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!
+
diff --git a/hacking/ticket_stubs/bug_internal_api.md b/hacking/ticket_stubs/bug_internal_api.md
new file mode 100644
index 0000000000..917ee9b651
--- /dev/null
+++ b/hacking/ticket_stubs/bug_internal_api.md
@@ -0,0 +1,16 @@
+Internal Ansible API
+====================
+
+Hi!
+
+Thanks very much for your submission to Ansible.  It sincerely means a lot to us
+to have an active community that is willing to submit feedback so that we may
+continue to make Ansible better.
+
+The internal Python API is considered an unsupported aspect of Ansible and this
+is not considered a bug unless there is an issue with an Ansible binary
+(`ansible`, `ansible-playbook`, `ansible-doc`, etc) or an issue with an external
+API such as are provided for the development of plugins (modules, dynamic
+inventories, callbacks, strategies, etc).
+
+Thank you once again for this and your interest in Ansible!
diff --git a/hacking/ticket_stubs/bug_is_really_a_question.md b/hacking/ticket_stubs/bug_is_really_a_question.md
new file mode 100644
index 0000000000..c3d9167130
--- /dev/null
+++ b/hacking/ticket_stubs/bug_is_really_a_question.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!
+
+
diff --git a/hacking/ticket_stubs/bug_misunderstanding.md b/hacking/ticket_stubs/bug_misunderstanding.md
new file mode 100644
index 0000000000..93c0e764bf
--- /dev/null
+++ b/hacking/ticket_stubs/bug_misunderstanding.md
@@ -0,0 +1,27 @@
+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!
+
diff --git a/hacking/ticket_stubs/bug_not_a_bug.md b/hacking/ticket_stubs/bug_not_a_bug.md
new file mode 100644
index 0000000000..e8c1e75565
--- /dev/null
+++ b/hacking/ticket_stubs/bug_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-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!
+
diff --git a/hacking/ticket_stubs/change_applied.md b/hacking/ticket_stubs/change_applied.md
new file mode 100644
index 0000000000..e3b28032fb
--- /dev/null
+++ b/hacking/ticket_stubs/change_applied.md
@@ -0,0 +1,16 @@
+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!
+
diff --git a/hacking/ticket_stubs/file_under_another_project.md b/hacking/ticket_stubs/file_under_another_project.md
new file mode 100644
index 0000000000..0cfec33c6e
--- /dev/null
+++ b/hacking/ticket_stubs/file_under_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!
+
+
diff --git a/hacking/ticket_stubs/great_idea.md b/hacking/ticket_stubs/great_idea.md
new file mode 100644
index 0000000000..b6f35fc10c
--- /dev/null
+++ b/hacking/ticket_stubs/great_idea.md
@@ -0,0 +1,25 @@
+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!
+
diff --git a/hacking/ticket_stubs/needs_info.md b/hacking/ticket_stubs/needs_info.md
new file mode 100644
index 0000000000..24ec4017ac
--- /dev/null
+++ b/hacking/ticket_stubs/needs_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 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!
+
diff --git a/hacking/ticket_stubs/needs_locale_info.md b/hacking/ticket_stubs/needs_locale_info.md
new file mode 100644
index 0000000000..7777510402
--- /dev/null
+++ b/hacking/ticket_stubs/needs_locale_info.md
@@ -0,0 +1,45 @@
+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=
+\`\`\`
diff --git a/hacking/ticket_stubs/needs_template.md b/hacking/ticket_stubs/needs_template.md
new file mode 100644
index 0000000000..05bb9672d1
--- /dev/null
+++ b/hacking/ticket_stubs/needs_template.md
@@ -0,0 +1,32 @@
+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.
diff --git a/hacking/ticket_stubs/no_thanks.md b/hacking/ticket_stubs/no_thanks.md
new file mode 100644
index 0000000000..35e6a4c314
--- /dev/null
+++ b/hacking/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
+
+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.
+
+Thank you once again for this and your interest in Ansible!
+
diff --git a/hacking/ticket_stubs/pr_cleanup_commits.md b/hacking/ticket_stubs/pr_cleanup_commits.md
new file mode 100644
index 0000000000..a06cb6973e
--- /dev/null
+++ b/hacking/ticket_stubs/pr_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 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!
+
diff --git a/hacking/ticket_stubs/pr_duplicate.md b/hacking/ticket_stubs/pr_duplicate.md
new file mode 100644
index 0000000000..0b4f16466a
--- /dev/null
+++ b/hacking/ticket_stubs/pr_duplicate.md
@@ -0,0 +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.
+
+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.
+
+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
+
+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.
+
+Thank you once again for this and your interest in Ansible!
+
diff --git a/hacking/ticket_stubs/pr_merged.md b/hacking/ticket_stubs/pr_merged.md
new file mode 100644
index 0000000000..5800eadd3d
--- /dev/null
+++ b/hacking/ticket_stubs/pr_merged.md
@@ -0,0 +1,16 @@
+Merged
+===================
+
+Hi!
+
+This has been merged in, and will also be included in the next major release.
+
+If you or anyone else has 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-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.
+
+Thank you!
diff --git a/hacking/ticket_stubs/pr_needs_rebase.md b/hacking/ticket_stubs/pr_needs_rebase.md
new file mode 100644
index 0000000000..f90af9940c
--- /dev/null
+++ b/hacking/ticket_stubs/pr_needs_rebase.md
@@ -0,0 +1,25 @@
+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!
+
diff --git a/hacking/ticket_stubs/pr_needs_revision.md b/hacking/ticket_stubs/pr_needs_revision.md
new file mode 100644
index 0000000000..64590cd7d8
--- /dev/null
+++ b/hacking/ticket_stubs/pr_needs_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 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!
+
diff --git a/hacking/ticket_stubs/proposal.md b/hacking/ticket_stubs/proposal.md
new file mode 100644
index 0000000000..9f4f8da638
--- /dev/null
+++ b/hacking/ticket_stubs/proposal.md
@@ -0,0 +1,15 @@
+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.
+
+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:
+
+   * #ansible-devel on Freenode
+   * https://groups.google.com/forum/#!forum/ansible-devel
+
+Thank you!
diff --git a/hacking/ticket_stubs/resolved.md b/hacking/ticket_stubs/resolved.md
new file mode 100644
index 0000000000..f71729930e
--- /dev/null
+++ b/hacking/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-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.
+
+Thank you!
+
+
diff --git a/hacking/ticket_stubs/thanks.md b/hacking/ticket_stubs/thanks.md
new file mode 100644
index 0000000000..646571d568
--- /dev/null
+++ b/hacking/ticket_stubs/thanks.md
@@ -0,0 +1,21 @@
+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!
+
diff --git a/hacking/ticket_stubs/wider_discussion.md b/hacking/ticket_stubs/wider_discussion.md
new file mode 100644
index 0000000000..ad0fc84ee4
--- /dev/null
+++ b/hacking/ticket_stubs/wider_discussion.md
@@ -0,0 +1,18 @@
+Submission Received
+===================
+
+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!
+
diff --git a/hacking/update.sh b/hacking/update.sh
deleted file mode 100755
index 5979dd0ab2..0000000000
--- a/hacking/update.sh
+++ /dev/null
@@ -1,3 +0,0 @@
-#!/bin/sh
-git pull --rebase
-git submodule update --init --recursive
diff --git a/hacking/yamlcheck.py b/hacking/yamlcheck.py
deleted file mode 100755
index 68d796cb1a..0000000000
--- a/hacking/yamlcheck.py
+++ /dev/null
@@ -1,16 +0,0 @@
-#!/usr/bin/env python
-# long version of this one liner: python -c 'import yaml,sys;yaml.safe_load(sys.stdin)' < yamltest.txt
-import yaml
-import sys
-
-if len(sys.argv) > 1:
-    check_file = open(sys.argv[1])
-else:
-    check_file = sys.stdin
-
-try:
-    yaml.safe_load(check_file)
-except yaml.scanner.ScannerError as e:
-    sys.exit('Invalid YAML:\n%s' % str(e))
-
-print('valid YAML')