1Contribution Guidelines
2#######################
3
4As an open-source project, we welcome and encourage the community to submit
5patches directly to the project.  In our collaborative open source environment,
6standards and methods for submitting changes help reduce the chaos that can result
7from an active development community.
8
9This document briefly summarizes the full `Contribution
10Guidelines <http://docs.zephyrproject.org/latest/contribute/index.html>`_
11documentation.
12
13* Zephyr uses the permissive open source `Apache 2.0 license`_
14  that allows you to freely use, modify, distribute and sell your own products
15  that include Apache 2.0 licensed software.
16
17* There are some imported or reused components of the Zephyr project that
18  use other licensing and are clearly identified.
19
20* The Developer Certificate of Origin (DCO) process is followed to
21  ensure developers are following licensing criteria for their
22  contributions, and documented with a ``Signed-off-by`` line in commits.
23
24* Zephyr development workflow is supported on Linux, macOS, and Windows,
25  (with a few exceptions).
26
27* Source code for the project is maintained in the GitHub repo:
28  https://github.com/zephyrproject-rtos/zephyr
29
30* Issue and feature tracking is done using GitHub issues in this repo.
31
32* A Continuous Integration (CI) system runs on every Pull Request (PR)
33  to verify several aspects of the PR including Git commit formatting,
34  Coding Style, sanity checks builds, and documentation builds.
35
36* The `Zephyr devel mailing list`_ is a great place to engage with the
37  community, ask questions, discuss issues, and help each other.
38
39.. _Zephyr devel mailing list: https://lists.zephyrproject.org/g/devel
40