Lines Matching +full:zephyr +full:- +full:bugs +full:-

37 * Right to report defects (bugs) and suggestions for enhancement.
46 * Responsibility for issues and bugs introduced by one’s own contributions.
51   (https://github.com/zephyrproject-rtos/zephyr/blob/main/CODE_OF_CONDUCT.md)
54 ….github.com/en/organizations/managing-access-to-your-organizations-repositories/repository-permiss…
55 access to the Zephyr GitHub repository. Specifically, at the Read access level,
58 the `Zephyr devel mailing list <https://lists.zephyrproject.org/g/devel>`_ or on
59 the `Zephyr Discord Server <https://chat.zephyrproject.org>`_.
62 level to the Zephyr GitHub repository.
80 of Zephyr source code. Their opinions weigh more when decisions are made, in a
98 the Zephyr repository.
102 not follow the :ref:`expectations <reviewer-expectations>` and the guidelines
116 directing and anticipating the needs of a given zephyr source code area.
136 :ref:`maintainers_file` in the Zephyr repository. Candidates who are neither
171   :ref:`expectations <reviewer-expectations>` from reviewers and seek reviews
175 * Responsibility to re-assign a pull request if they are the original submitter
200 .. _release-engineering-team:
215 * Right to merge code changes to the zephyr tree following the project rules.
223 * Responsibility to keep the Zephyr code base in a working and passing state
237   time-zones).
254 …stone (M3, see `program management overview <https://wiki.zephyrproject.org/Program-Management>`_.)
274 …---------------- ------------------- ----------- ---------------- ----------- ----------- --------…
276 …---------------- ------------------- ----------- ---------------- ----------- ----------- --------…
278 …---------------- ------------------- ----------- ---------------- ----------- ----------- --------…
299   * Un-maintained areas should be indicated clearly in the MAINTAINERS file
304   * Parent-area maintainer should be acting as default substitute/fallback
305     assignee for un-maintained sub-areas
306   * Area maintainer gets precedence over parent-area maintainer
308 * Pull requests may be re-assigned if this is needed or more appropriate
310   * Re-assigned by original assignee
324 * Architectures, core components, sub-systems, samples, tests
329   * May have a maintainer, shall have a higher-level platform maintainer
332   * Shall have a driver-area (and API) maintainer
335   * In the above case, platform-specific PRs may be
336     re-assigned to respective collaborator/contributor of driver