OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/doc/contribute/contribute.rst

14 lines
328 B
ReStructuredText
Raw Normal View History

doc: add CONTRIBUTING.rst to project repo and docs GitHub notices a CONTRIBUTING file in a repo's root and will automatically add a link to this file on the page when a contributor creates an Issue or opens a Pull Request. (Expectation is CONTRIBUTING will have information about how to contribute to the project, format code, test fixes, and submit patches. We also want to have this document accessible from our technical docs, and not duplicate the content, so add linkage to make this work. The zephyrproject github wiki article that contributed to this new CONTRIBUTING doc will be made into a reference to this new doc once this PR is approved and merged. Replaces PR #929 Jira: ZEP-2085 Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
2017-07-28 08:04:04 +08:00
.. _contribute:
Contributing to the Zephyr Project
##################################
As an open-source project, we welcome and encourage the community to submit
patches for code, documentation, tests, and more, directly to the project.
.. toctree::
:maxdepth: 1
contribute_guidelines.rst
doc: add contributing non-Apache2.0 docs Add contribution process for including non-Apache 2.0 components as approved by the TSC. Include a README template that lists information requested by the TSC and governing board for review. Add a brief mention in the CONTRIBUTING link that appears when submitting a new PR or Issue via the GitHub web interface. Included an introduction to the process steps that includes using the zephyr devel mailing list to discuss new components. fixes #1543 Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
2017-09-20 08:23:35 +08:00
contribute_non-apache.rst