Searched full:guidelines (Results 1 – 25 of 49) sorted by relevance
12
1 Contribution Guidelines10 Guidelines <http://docs.zephyrproject.org/latest/contribute/index.html>`_
1 name: Coding Guidelines8 name: Run coding guidelines checks on patch series (PR)
9 guidelines.rst
3 API Status and Guidelines
3 API Design Guidelines
3 Contribution Guidelines443 Use these coding guidelines to ensure that your development complies with the462 When there are differences between the guidelines above and the formatting463 generated by code formatting tools, the guidelines above take precedence.636 agreement with the :ref:`DCO`. See the :ref:`commit-guidelines` section for637 specific guidelines for writing your commit messages.719 .. _commit-guidelines:721 Commit Message Guidelines959 Follow the guidelines in the :ref:`modules` section for contributing
6 These documents describe the requirements, processes, and developer guidelines
180 concrete and detailed guidelines need to be developed and aligned with246 include coding guidelines and development processes that can be roughly373 - **Adherence to Deployment Guidelines** is required to ensure493 The general guidelines above shall be accompanied by an architectural611 management process, and learnings shall be formulated as guidelines and
25 This document covers guidelines for the `Zephyr Project`_, from a221 guidelines.
23 Disk name as per file system naming guidelines.
27 Disk name as per file system naming guidelines.
37 Documentation Guidelines54 for traceability reports. Here are a few guidelines to be followed:
35 project's goals and guidelines for our active developer community.
15 members of the TSC under the guidelines stated in the project Charter.254 Generic guidelines for deciding and filling in the Maintainers' list335 * Coding Guidelines
17 "Accessory Design Guidelines for Apple Devices".
28 ..zephyr-app-commands directive (see the doc guidelines) instead of a
54 <h2>Contribution Guidelines</h2>79 …<p>Requirements, processes, and developer guidelines for ensuring security is addressed within the…
23 as defined by the :ref:`Coding Guidelines Rule A.4
31 https://security.openstack.org/guidelines/dg_avoid-dangerous-input-parsing-libraries.html.
914 * :github:`9249` - Get non ST, STM32 Based boards compliant with default configuration guidelines915 * :github:`9248` - Get Olimex boards compliant with default configuration guidelines916 * :github:`9245` - Get TI SoC based boards compliant with default configuration guidelines917 * :github:`9244` - Get SILABS board compliant with default configuration guidelines918 * :github:`9243` - Get NXP SoC based boards compliant with default configuration guidelines919 * :github:`9241` - Get ATMEL SoC based boards compliant with default configuration guidelines920 * :github:`9240` - Get ARM boards compliant with default configuration guidelines921 * :github:`9239` - Get NIOS boards compliant with default configuration guidelines922 * :github:`9237` - Get RISCV boards compliant with default configuration guidelines923 * :github:`9236` - Get X86 boards compliant with default configuration guidelines[all …]
122 self.case = TestCase(type(self).name, "Guidelines")190 …doc = "See https://docs.zephyrproject.org/latest/contribute/guidelines.html#coding-style for more …471 check Kconfig guidelines.717 …doc = "See https://docs.zephyrproject.org/latest/contribute/guidelines.html#coding-style for more …839 …doc = "See https://docs.zephyrproject.org/latest/contribute/guidelines.html#commit-guidelines for …939 …doc = "See https://docs.zephyrproject.org/latest/contribute/guidelines.html#commit-guidelines for …
49 **Guidelines for Samples:**
74 Implementation guidelines
