zydronium/documentation
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update added Contribution Policy

Browse source 
Added content for Contribution policy Draft_0. Policy is subject to change.

Signed-off-by: Robert Wolff <robert.wolff@linaro.org>
This commit is contained in:
Robert Wolff 2016-05-17 19:59:03 -07:00
parent 9a8b824f24
commit 1696886a13
1 changed files with 10 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

11
README.md
View file

@ -15,7 +15,16 @@ Welcome to the official documentation for Linaro and the Reference Software Plat
## Contribution Policy
Coming soon...
# Contribution Policy
This guide is written by the 96Boards team at Linaro with community contributions and links to third-party content.
All documentation in this repository is written by the 96Boards team at Linaro with community contributions and links to third-party content. 96Boards openly welcomes community contributions provided the following Contribution Policy is strictly followed.
The first course of action should be to [file an issue](https://github.com/Linaro/documentation/issues) within this Github repository. Once filed, the issue will be addressed by a 96Boards/Linaro team member. This first line of interactions will determine if a pull request should be submitted, and whether or not it is likely to be accepted.
1. In every instance, **an issue MUST be filed first**. Each issue will have a Title and a Comment section, please explain the issue in as much detail as possible using these two fields. The Title is the first piece of information a maintainer will see, it should be brief, and it should address the issue in less than 10 words. The comment section should be used to explain your issue in more detail. Write out desired changes including precise steps, links, and examples. Upon review, the issue will be discussed and evaluated. If it merits a change, the status will be labeled accordingly, and it will be fixed as soon as possible by either a member of the 96Boards team or through a community issued pull request.
2. If deemed necessary (through Github issue approval), **a pull request should be submitted**. Only one Pull Request per filed issue will be accepted.
***