Test 2 Take 2

[allanice001]

Author: Your Name <@yourGHid> IRC: handle (if different)

Date: 2017/{mm}/{dd}

Status:

• New
• Approved
• Pending
• Complete

Proposal type:

• Core
• Design
• Process
• Other

Targeted Release: <future release #, ex. 2.4>
Associated PR: <link to GH PR in ansible/proposals if PR was submitted>
Estimated time to implement: <X days, weeks, etc.>

Proposal Meeting:

• Tuesday @ 19:00 UTC
• Thursday @ 15:00 UTC

Deadline for final submission of questions:

• 2 Weeks
• 3 Weeks
• 4 Weeks
• 5 Weeks (With Core agreements)

Motivation

Describe the reasons for this proposal.

Problems

What problems exist that this proposal will solve?

• Problem Test #1
• Problem Test2 #2
• Or just describe the problem if there is just one.
  • If possible add ansible/ansible#PR or ansible/ansible#ISSUE of where this problem is listed
  • Example YAML inventory format should support 'children' groups like INI format can ansible/ansible#150

Solution proposal

• Describe your suggested solution here.
• Insert code in snippets if you would like as shown.

    - include: main.yml
      vars:
         var1: val1

• Be sure to explain how this solves problems.

Dependencies (optional)

Explain any dependencies. This section is optional but could be helpful.

• Dependency Test #1
• Dependency Test2 #2

Assistance

• Do you require assistance on this project
• If so, what is required?
  • Coding
  • Testing
  • Community wrangling
  • Core adoption

Testing (optional)

Does / should this require testing, and if so, how? Describe here. This section is optional but could be helpful.

Documentation (optional)

Does / should this require documentation? If so, describe here. This section is optional but could be helpful.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• I have added my proposal to the core agenda

Coding Checklist

• Python-2.4 or greater support
• Python-2.6 or greater support
• Python-3.5 or greater support

Anything else?

If you'd like to add anything else beyond the above required and optional sections, you are welcome to do so.