Home
last modified time | relevance | path

Searched full:guidelines (Results 1 – 25 of 71) sorted by relevance

123

/Zephyr-Core-3.7.0/doc/contribute/
Dindex.rst8 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
Dguidelines.rst3 Contribution Guidelines
355 Pull Request Guidelines
357 When opening a new Pull Request, adhere to the following guidelines to ensure
364 .. _commit-guidelines:
366 Commit Message Guidelines argument
549 Use these coding guidelines to ensure that your development complies with the
613 When there are differences between the `Coding Style`_ guidelines and the
614 formatting generated by code formatting tools, the `Coding Style`_ guidelines
616 guidelines, maintainers may decide which style should be adopted.
662 compliance with Zephyr's established guidelines and best practices. The script
[all …]
/Zephyr-Core-3.7.0/.github/workflows/
Dgreet_first_time_contributor.yml34 …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…
Dcoding_guidelines.yml1 name: Coding Guidelines
8 name: Run coding guidelines checks on patch series (PR)
/Zephyr-Core-3.7.0/
DCONTRIBUTING.rst1 Contribution Guidelines
10 Guidelines <http://docs.zephyrproject.org/latest/contribute/index.html>`_
DCODE_OF_CONDUCT.md74 ## Enforcement Guidelines
76 Community leaders will follow these Community Impact Guidelines in determining
128 Community Impact Guidelines were inspired by
/Zephyr-Core-3.7.0/doc/safety/
Dindex.rst6 These documents describe the processes, developer guidelines and requirements
Dsafety_overview.rst26 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
Dsafety_requirements.rst18 Guidelines section in Safety Requirements
21 Below are the guidelines for the requirements repository and the expectations of the safety
/Zephyr-Core-3.7.0/doc/develop/api/
Dindex.rst3 API Status and Guidelines
Doverview.rst52 guidelines above.
/Zephyr-Core-3.7.0/doc/security/
Dindex.rst6 These documents describe the requirements, processes, and developer guidelines
/Zephyr-Core-3.7.0/scripts/utils/
Dconvert_guidelines.py37 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.7.0/drivers/disk/
DKconfig.mmc24 Disk name as per file system naming guidelines.
DKconfig.sdmmc28 Disk name as per file system naming guidelines.
/Zephyr-Core-3.7.0/doc/security/standards/
Dindex.rst12 standards provide guidelines and outline requirements that products have to follow
/Zephyr-Core-3.7.0/doc/project/
Ddocumentation.rst37 Documentation Guidelines
54 for traceability reports. Here are a few guidelines to be followed:
Dindex.rst37 project's goals and guidelines for our active developer community.
Dproject_roles.rst15 members of the TSC under the guidelines stated in the project Charter.
102 not follow the :ref:`expectations <reviewer-expectations>` and the guidelines
291 Generic guidelines for deciding and filling in the Maintainers' list
363 approvals, the merge criteria is extended with the guidelines below:
405 * Coding Guidelines
/Zephyr-Core-3.7.0/samples/bluetooth/direct_adv/
DREADME.rst17 "Accessory Design Guidelines for Apple Devices".
/Zephyr-Core-3.7.0/doc/templates/
Dsample.tmpl30 ..zephyr-app-commands directive (see the doc guidelines) instead of a
/Zephyr-Core-3.7.0/doc/
Dindex.rst54 <h2>Contribution Guidelines</h2>
79 …<p>Requirements, processes, and developer guidelines for ensuring security is addressed within the…
/Zephyr-Core-3.7.0/doc/develop/languages/c/
Dminimal_libc.rst23 as defined by the :ref:`Coding Guidelines Rule A.4
/Zephyr-Core-3.7.0/scripts/pylib/twister/
Dscl.py36 https://security.openstack.org/guidelines/dg_avoid-dangerous-input-parsing-libraries.html.
/Zephyr-Core-3.7.0/doc/releases/
Drelease-notes-2.1.rst914 * :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 …]

123