wbrawner/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Correct to development_process (#39069) (#45264)

Browse source 
(cherry picked from commit c4e298b808)
This commit is contained in:
Alicia Cozine 2018-09-05 20:52:50 -05:00 committed by GitHub
parent 38b9fee32f
commit 339d064584
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 5 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/docsite/rst/community/development_process.rst
View file

@ -1,3 +1,5 @@
.. _community_development_process:
The Ansible Development Process
===============================

6
docs/docsite/rst/community/how_can_I_help.rst
View file

@ -3,7 +3,7 @@ How To Help
.. contents:: Topics
Thanks for being interested in helping the Ansible project!
Thanks for being interested in helping the Ansible project!
There are many ways to help the Ansible project...but first, please read and understand the :ref:`code_of_conduct`.
@ -23,7 +23,7 @@ When you become a power user, your ability and opportunities to help the Ansible
Ask and answer questions online
-------------------------------
There are many forums online where Ansible users ask and answer questions. Reach out and communicate with your fellow Ansible users.
There are many forums online where Ansible users ask and answer questions. Reach out and communicate with your fellow Ansible users.
You can find the official :ref:`Ansible communication channels <communication>`.
@ -45,7 +45,7 @@ If you should discover that the bug you're trying to file already exists in an i
Review and submit pull requests
-------------------------------
As you become more familiar with how Ansible works, you may be able to fix issues or develop new features yourself. If you think you've got a solution to a bug you've found in Ansible, or if you've got a new feature that you've written and would like to share with millions of Ansible users, read all about the `Ansible development process <http://docs.ansible.com/ansible/latest/community/development_process.rst>`_ to learn how to get your code accepted into Ansible.
As you become more familiar with how Ansible works, you may be able to fix issues or develop new features yourself. If you think you've got a solution to a bug you've found in Ansible, or if you've got a new feature that you've written and would like to share with millions of Ansible users, read all about the :ref:`Ansible development process <community_development_process>` to learn how to get your code accepted into Ansible.
Another good way to help is to review pull requests that other Ansible users have submitted. The Ansible community keeps a full list of `open pull requests by file <https://ansible.sivel.net/byfile.html>`_, so if there's a particular module or plug-in that particularly interests you, you can easily keep track of all the relevant new pull requests and provide testing or feedback.