| /Zephyr-latest/doc/contribute/ |
| D | index.rst | 8 lists useful resources and guidelines to help you in your contribution journey.
10 General Guidelines
17 guidelines.rst
23 Learn about the overall process and guidelines for contributing to the Zephyr project.
34 Code contributions are expected to follow a set of coding guidelines to ensure consistency and
37 This page describes these guidelines and introduces important considerations regarding the use of
54 documentation/guidelines.rst
58 This page provides some simple guidelines for writing documentation using the reSTructuredText
88 in binary form, this page describes the process and guidelines for :ref:`contributing binary
|
| D | guidelines.rst | 3 Contribution Guidelines
364 Pull Request Guidelines
366 When opening a new Pull Request, adhere to the following guidelines to ensure
373 .. _commit-guidelines:
375 Commit Message Guidelines argument
557 Use these coding guidelines to ensure that your development complies with the
621 When there are differences between the `Coding Style`_ guidelines and the
622 formatting generated by code formatting tools, the `Coding Style`_ guidelines
624 guidelines, maintainers may decide which style should be adopted.
670 compliance with Zephyr's established guidelines and best practices. The script
[all …]
|
| /Zephyr-latest/cmake/sca/eclair/ |
| D | sca_options.cmake | 6 option(ECLAIR_RULESET_STU "Selection of the projects coding guidelines, which can be verified
9 option(ECLAIR_RULESET_STU_HEAVY "Selection of complex STU project coding guidelines that
11 option(ECLAIR_RULESET_WP "All whole program project coding guidelines ('system' in MISRA's
13 option(ECLAIR_RULESET_STD_LIB "Project coding guidelines about the C Standard Library" OFF)
|
| /Zephyr-latest/doc/develop/sca/ |
| D | eclair.rst | 60 Zephyr's guidelines selection
64 * first_analysis (default): a tiny selection of the projects coding guidelines to verify that
67 * STU: Selection of the projects coding guidelines, which can be verified by analysing the single
70 * STU_heavy: Selection of complex STU project coding guidelines that require a significant amount
73 * WP: All whole program project coding guidelines ("system" in MISRA's parlance).
75 * std_lib: Project coding guidelines about the C Standard Library.
88 If you want to use your own defined ruleset instead of the predefined zephyr coding guidelines
|
| /Zephyr-latest/.github/workflows/ |
| D | greet_first_time_contributor.yml | 34 …k at [our commit message guidelines](https://docs.zephyrproject.org/latest/contribute/guidelines.h…
35 …ontribution workflow](https://docs.zephyrproject.org/latest/contribute/guidelines.html#contributio…
|
| D | coding_guidelines.yml | 1 name: Coding Guidelines
8 name: Run coding guidelines checks on patch series (PR)
|
| /Zephyr-latest/ |
| D | CONTRIBUTING.rst | 1 Contribution Guidelines
10 Guidelines <http://docs.zephyrproject.org/latest/contribute/index.html>`_
|
| D | CODE_OF_CONDUCT.md | 74 ## Enforcement Guidelines
76 Community leaders will follow these Community Impact Guidelines in determining
128 Community Impact Guidelines were inspired by
|
| /Zephyr-latest/doc/safety/ |
| D | index.rst | 6 These documents describe the processes, developer guidelines and requirements
|
| D | safety_overview.rst | 26 This document is a living document and may evolve over time as new requirements, guidelines, or
137 Coding Guidelines
140 The coding guidelines are the basis to a common understanding and a unified ruleset and development
141 style for industrial software products. For safety the coding guidelines are essential and have
148 standards / guidelines to reduce likelihood of errors.
280 **TODO:** Find and define ways, guidelines and processes which minimally impact the daily work
|
| D | safety_requirements.rst | 18 Guidelines section in Safety Requirements
21 Below are the guidelines for the requirements repository and the expectations of the safety
|
| /Zephyr-latest/doc/develop/api/ |
| D | index.rst | 3 API Status and Guidelines
|
| D | overview.rst | 52 guidelines above.
|
| /Zephyr-latest/doc/security/ |
| D | index.rst | 6 These documents describe the requirements, processes, and developer guidelines
|
| /Zephyr-latest/scripts/utils/ |
| D | convert_guidelines.py | 37 print('Appendix A Summary of guidelines', file=outputfile)
132 help="Path to rst input source file, where the guidelines are written down."
140 …help="Path to output file, where the converted guidelines are written to. If outputfile is not spe…
|
| /Zephyr-latest/cmake/sca/eclair/ECL/ |
| D | analysis_first_analysis.ecl | 11 -doc_begin="Selection of guidelines from
|
| D | analysis_heavy_STU.ecl | 11 -doc_begin="Selection of guidelines from
|
| D | analysis_std_lib.ecl | 10 -doc_begin="Selection of guidelines from
|
| D | analysis_WP.ecl | 11 -doc_begin="Selection of guidelines from
|
| /Zephyr-latest/doc/security/standards/ |
| D | index.rst | 12 standards provide guidelines and outline requirements that products have to follow
|
| /Zephyr-latest/doc/project/ |
| D | documentation.rst | 37 Documentation Guidelines
54 for traceability reports. Here are a few guidelines to be followed:
|
| D | index.rst | 37 project's goals and guidelines for our active developer community.
|
| /Zephyr-latest/samples/bluetooth/direct_adv/ |
| D | README.rst | 18 "Accessory Design Guidelines for Apple Devices".
|
| /Zephyr-latest/doc/templates/ |
| D | sample.tmpl | 30 ..zephyr-app-commands directive (see the doc guidelines) instead of a
|
| /Zephyr-latest/doc/ |
| D | index.rst | 68 <p>Security processes and guidelines</p>
80 <h2>Contribution Guidelines</h2>
|
