Searched full:contributions (Results 1 – 22 of 22) sorted by relevance
| /Zephyr-latest/doc/contribute/ |
| D | index.rst | 6 Contributions from the community are the backbone of the project. Whether it is by submitting code,
34 Code contributions are expected to follow a set of coding guidelines to ensure consistency and
77 :ref:`external-contributions`
|
| D | external.rst | 1 .. _external-contributions:
47 By carefully reviewing potential contributions and also enforcing a :ref:`DCO`
172 #. Make sure to read through the :ref:`external-contributions` section in
|
| D | guidelines.rst | 59 By carefully reviewing potential contributions and also enforcing a
64 See :ref:`external-contributions` for more information about
168 Any contributions made as part of submitted pull requests are considered free
178 around working with contributions submitted by other developers.
992 <external-contributions>`, the commit message shall contain details regarding
1012 Contributions to External Modules
1024 This section describes contributions that are treewide changes and some
|
| /Zephyr-latest/samples/ |
| D | index.rst | 10 We welcome contributions of new samples to the project and you are encouraged to read more about
|
| /Zephyr-latest/ |
| D | CONTRIBUTING.rst | 22 contributions, and documented with a ``Signed-off-by`` line in commits.
|
| D | LICENSE | 130 5. Submission of Contributions. Unless You explicitly state otherwise,
136 with Licensor regarding such Contributions.
145 Contributor provides its Contributions) on an "AS IS" BASIS,
|
| D | CODE_OF_CONDUCT.md | 47 comments, commits, code, wiki edits, issues, and other contributions that are
|
| /Zephyr-latest/doc/project/ |
| D | project_roles.rst | 38 * Right to participate in the process of reviewing contributions by others.
46 * Responsibility for issues and bugs introduced by one’s own contributions.
49 discussions and in the review of contributions.
128 * Responsibility to ensure all contributions of the project have been reviewed
220 * Responsibility to merge all contributions regardless of their
373 * Release engineers may make exceptions for areas with contributions primarily
|
| D | modifying_contributions.rst | 3 Modifying Contributions made by other developers
|
| D | tsc.rst | 31 including feature proposals, code contributions, and community initiatives.
|
| D | dev_env_and_tools.rst | 251 daily and long-term work and contributions to the Zephyr project. We use
|
| /Zephyr-latest/doc/develop/manifest/ |
| D | index.rst | 8 See :ref:`external-contributions` for more information about
|
| /Zephyr-latest/.github/workflows/ |
| D | greet_first_time_contributor.yml | 58 contributions in the future! ��
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | features.rst | 11 particular, on Bluetooth Low Energy (BLE). Through the contributions of
|
| /Zephyr-latest/drivers/disk/nvme/ |
| D | nvme_namespace.h | 6 * with contributions from Alexander Motin and Wojciech Macek
|
| D | nvme.h | 6 * with contributions from Alexander Motin and Wojciech Macek
|
| D | nvme_cmd.h | 6 * with contributions from Alexander Motin and Wojciech Macek
|
| D | nvme_controller.c | 6 * with contributions from Alexander Motin, Wojciech Macek, and Warner Losh
|
| D | nvme_cmd.c | 6 * with contributions from Alexander Motin, Wojciech Macek, and Warner Losh
|
| /Zephyr-latest/doc/introduction/ |
| D | index.rst | 99 architectures and developer tools. Contributions have added support
|
| /Zephyr-latest/doc/security/ |
| D | secure-coding.rst | 190 primary developer would typically make a number of contributions over
|
| /Zephyr-latest/doc/contribute/coding_guidelines/ |
| D | index.rst | 56 why you can't obtain one through other options and expected contributions
|
