Lines Matching refs:project

34 `Zephyr project charter`_. The board will automatically reject licenses that
41 .. _Zephyr project charter:
56 comes from an existing project, there are additional questions that must be
60 into the project:
62 - Is this the most optimal way to introduce the functionality to the project?
65 - Is the external project being actively maintained? This is particularly
68   Are there other open source project that implement the same functionality?
80 The first way to integrate external source code into the project is to simply
86 - The code adheres to the project's :ref:`coding_guidelines`
99 The second way of integrating external source code into the project is to import
100 the whole or parts of the third-party open source project into a separate
113 The integration of modules in this group is validated by the Zephyr project CI,
142 Similar to optional modules, but added to the Zephyr project as an entry in the
144 Zephyr project manifest with documentation instructing users and developers how
162 Before external source code can be included in the project, it must be reviewed
167 issue in the Zephyr project issue tracking system on GitHub with details
168 about the source code and how it integrates into the project.
222 Zephyr project, where tooling is defined as software that assists the
227 project in the main :file:`west.yml` manifest. Therefore, this section does not
236 another project can be integrated either in the main tree or as a :ref:`west
237 project <west-workspace>`. Note that in this case the corresponding west project
244 If the tool is integrated as a west project, then the project repository can be
246 project is made optional via the ``group-filter:`` field in the main