michaelh/zephyr
1
0
Fork 0
Code Releases Activity

doc: contribution guidelines: Specify roles and responsibilies

Browse source 
Clarify the roles and responsibilities of the Zephyr community
and contributors with respect to PRs, Bugs, and Features.

Signed-off-by: David Leach <david.leach@nxp.com>
This commit is contained in:
David Leach 2019-09-30 21:00:15 -05:00 • committed by Maureen Helm
commit 4eddc394a3
2 changed files with 24 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

19
doc/contribute/index.rst
View file

@ -761,3 +761,22 @@ Code component README template
============================== ==============================
.. literalinclude:: code_component_README .. literalinclude:: code_component_README
Contribution Roles and Responsibilities
***************************************
The Zephyr project defines a development process workflow using GitHub
**Issues** to track feature, enhancement, and bug reports together with GitHub
**Pull Requests** (PRs) for submitting and reviewing changes. Zephyr
community members work together to review these Issues and PRs, managing
feature enhancements and quality improvements of Zephyr through its regular
releases, as outlined in the
`program management overview <https://wiki.zephyrproject.org/Program-Management>`_.
We can only manage the volume of Issues and PRs, by requiring timely reviews,
feedback, and responses from the community and contributors, both for initial
submissions and for followup questions and clarifications. Read about the
project's :ref:`development processes and tools <dev-environment-and-tools>`
and specifics about :ref:`review timelines <review_time>` to learn about the
project's goals and guidelines for our active developer community.

8
doc/development_process/dev_env_and_tools.rst
View file

@ -171,7 +171,7 @@ dismissed by the assignee or an owner of the repository. Reviews will be
dismissed following the criteria below: dismissed following the criteria below:
- The feedback or concerns were visibly addressed by the author - The feedback or concerns were visibly addressed by the author
- The reviewer did not revisit the pull request after 1 week and multiple pings - The reviewer did not revisit the pull request after 2 week and multiple pings
by the author by the author
- The review is unrelated to the code change or asking for unjustified - The review is unrelated to the code change or asking for unjustified
structural changes such as: structural changes such as:
@ -190,8 +190,10 @@ Closing Stale Issues and Pull Requests
Use the mailing lists for discussions. Use the mailing lists for discussions.
- In case of both issues and pull-requests the original poster needs to respond - In case of both issues and pull-requests the original poster needs to respond
to questions and provide clarifications regarding the issue or the change. to questions and provide clarifications regarding the issue or the change.
Failing to do so, an issue or a pull request will be closed automatically After one week without a response to a request, a second attempt to elicit
after 6 months. a response from the contributor will be made. After one more week without a
response the item may be closed (draft and DNM tagged pull requests are
excluded).
Continuous Integration Continuous Integration
*********************** ***********************