Searched full:guidelines (Results 1 – 25 of 61) sorted by relevance
123
| /Zephyr-Core-3.6.0/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
443 Use these coding guidelines to ensure that your development complies with the
463 When there are differences between the guidelines above and the formatting
464 generated by code formatting tools, the guidelines above take precedence.
647 agreement with the :ref:`DCO`. See the :ref:`commit-guidelines` section for
648 specific guidelines for writing your commit messages.
730 .. _commit-guidelines:
732 Commit Message Guidelines
966 Follow the guidelines in the :ref:`modules` section for contributing
|
| /Zephyr-Core-3.6.0/.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-Core-3.6.0/ |
| 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-Core-3.6.0/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
119 Coding Guidelines
122 The coding guidelines are the basis to a common understanding and a unified ruleset and development
123 style for industrial software products. For safety the coding guidelines are essential and have
130 standards / guidelines to reduce likelihood of errors.
262 **TODO:** Find and define ways, guidelines and processes which minimally impact the daily work
|
| /Zephyr-Core-3.6.0/doc/develop/api/ |
| D | index.rst | 3 API Status and Guidelines
|
| D | design_guidelines.rst | 3 API Design Guidelines
|
| /Zephyr-Core-3.6.0/doc/security/ |
| D | index.rst | 6 These documents describe the requirements, processes, and developer guidelines
|
| D | security-overview.rst | 180 concrete and detailed guidelines need to be developed and aligned with
244 include coding guidelines and development processes that can be roughly
371 - **Adherence to Deployment Guidelines** is required to ensure
491 The general guidelines above shall be accompanied by an architectural
609 management process, and learnings shall be formulated as guidelines and
|
| /Zephyr-Core-3.6.0/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-Core-3.6.0/drivers/disk/ |
| D | Kconfig.mmc | 23 Disk name as per file system naming guidelines.
|
| D | Kconfig.sdmmc | 27 Disk name as per file system naming guidelines.
|
| /Zephyr-Core-3.6.0/doc/project/ |
| D | documentation.rst | 37 Documentation Guidelines
54 for traceability reports. Here are a few guidelines to be followed:
|
| D | index.rst | 35 project's goals and guidelines for our active developer community.
|
| D | project_roles.rst | 15 members of the TSC under the guidelines stated in the project Charter.
100 not follow the :ref:`expectations <reviewer-expectations>` and the guidelines
286 Generic guidelines for deciding and filling in the Maintainers' list
358 approvals, the merge criteria is extended with the guidelines below:
400 * Coding Guidelines
|
| /Zephyr-Core-3.6.0/samples/bluetooth/direct_adv/ |
| D | README.rst | 17 "Accessory Design Guidelines for Apple Devices".
|
| /Zephyr-Core-3.6.0/doc/templates/ |
| D | sample.tmpl | 30 ..zephyr-app-commands directive (see the doc guidelines) instead of a
|
| /Zephyr-Core-3.6.0/doc/ |
| D | index.rst | 54 <h2>Contribution Guidelines</h2>
79 …<p>Requirements, processes, and developer guidelines for ensuring security is addressed within the…
|
| /Zephyr-Core-3.6.0/doc/develop/languages/c/ |
| D | minimal_libc.rst | 23 as defined by the :ref:`Coding Guidelines Rule A.4
|
| /Zephyr-Core-3.6.0/scripts/pylib/twister/ |
| D | scl.py | 36 https://security.openstack.org/guidelines/dg_avoid-dangerous-input-parsing-libraries.html.
|
| /Zephyr-Core-3.6.0/doc/releases/ |
| D | release-notes-2.1.rst | 914 * :github:`9249` - Get non ST, STM32 Based boards compliant with default configuration guidelines
915 * :github:`9248` - Get Olimex boards compliant with default configuration guidelines
916 * :github:`9245` - Get TI SoC based boards compliant with default configuration guidelines
917 * :github:`9244` - Get SILABS board compliant with default configuration guidelines
918 * :github:`9243` - Get NXP SoC based boards compliant with default configuration guidelines
919 * :github:`9241` - Get ATMEL SoC based boards compliant with default configuration guidelines
920 * :github:`9240` - Get ARM boards compliant with default configuration guidelines
921 * :github:`9239` - Get NIOS boards compliant with default configuration guidelines
922 * :github:`9237` - Get RISCV boards compliant with default configuration guidelines
923 * :github:`9236` - Get X86 boards compliant with default configuration guidelines
[all …]
|
| /Zephyr-Core-3.6.0/drivers/flash/ |
| D | flash_simulator_native.c | 14 * coding guidelines rule A.4&5 which applies to the embedded code using embedded libraries
|
123
