ansible/hacking/ticket_stubs/needs_info.md

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!
(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. 2014-08-06 00:08:31 +00:00			`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!`
Minor grammar fixes 2014-09-29 19:36:48 +00:00			`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!`
(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. 2014-08-06 00:08:31 +00:00
			`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`
Minor grammar fixes 2014-09-29 19:36:48 +00:00			`which are very active:`
(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. 2014-08-06 00:08:31 +00:00
Update response ticket stubs. 2014-08-06 22:00:10 +00:00			`* 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`
(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. 2014-08-06 00:08:31 +00:00
			`Thank you once again for this and your interest in Ansible!`