Searched full:contributing (Results 1 – 16 of 16) sorted by relevance
3 Contributing to Zephyr27 Learn about the overall process and guidelines for contributing to the Zephyr project.61 as a standalone effort, contributing documentation is particularly valuable to the project.101 in binary form, this page describes the process and guidelines for :ref:`contributing binary
3 Contributing External Components218 Contributing External Tooling
93 this contributing and review process for imported components.653 When contributing to the Zephyr Project, it is also important you provide as much879 Follow the guidelines in the :ref:`modules` section for contributing
9 this contributing and review process for imported components.
179 * CONTRIBUTING.rst and Contribution Guide material added240 * ``ZEP-2085`` - Add CONTRIBUTING.rst to root folder w/contributing guidelines
263 * Updated contributing guidelines646 * :github:`6188` - doc: Merge non-apache contributing into CONTRIBUTING
305 * :github:`4772` - doc: add contributing info about shippable failures400 * :github:`5717` - CONTRIBUTING instructions are Linux-specific and don't work for Windows
503 * :github:`6811` - Add ReST/Sphinx usage guide to our contributing documentation
1970 * :github:`6777` - Add copyright handling to contributing doc
1042 tagging requirements, contributing guidelines, doc guidelines,
21 * For example, if thread A has two mutexes contributing to the raising of its
46 A ``<VENDOR>`` subdirectory is mandatory if contributing your SoC
242 A ``<VENDOR>`` subdirectory is mandatory if contributing your board303 of your board. You only need this if you're :ref:`contributing-your-board` to906 Contributing your board
173 Contributing to Zephyr modules244 Contributing changes to modules261 detail the process of contributing changes to module repositories.266 Contributing to Zephyr modules shall follow the generic project
1005 - CONTRIBUTING.rst
1191 This section describes a few tings to consider when contributing to or using LE Audio in Zephyr.