Lines Matching full:project

39 The Zephyr Project does not host binary blobs in its Git repositories or
118 be unconditionally accepted by the project; any blob may be rejected for other
130 meets these requirements. The project may remove a blob from the upstream
150   APIs may change and such blobs cannot be modified by all project maintainers
161 can be linked by a toolchain supported by the Zephyr Project.  This is required
175 project maintainers define an open source test suite that an upstream
187 At the discretion of the release team, the project may remove support for a
193 The Zephyr Project is not expected to be responsible for the maintenance and
195 Zephyr Project release team, and on a case-by-case basis:
199 - Such issues may be closed as out of scope of the Zephyr project
203 code path that is difficult or impossible to trigger without a blob. Project
206 However, some flexibility is required because project maintainers may not be
212 of the Zephyr Project release team, module revisions referencing blobs may be
214 support from their maintainers. This is required to maintain project control
221 project's CI infrastructure that builds and optionally executes tests and samples
231 For references to binary blobs to be included in the project, they must be
237 issue in the Zephyr project issue tracking system on GitHub with details
238 about the blobs and the functionality they provide to the project.