Searched full:maintainers (Results 1 – 25 of 38) sorted by relevance
12
| /Zephyr-Core-3.6.0/ |
| D | MAINTAINERS.yml | 24 # maintainers:
83 # * A user mentioned in 'maintainers' is added as Assignee to
86 # * Users mentioned in 'maintainers' and 'collaborators' are added as
97 # Maintainers: <list of maintainers>
98 # Collaborators: <list of sub-maintainers>
104 # Changes to MAINTAINERS.yml need to be approved as follows:
106 # * Changing the 'maintainers' for an area needs approval from the
116 maintainers:
133 maintainers:
152 maintainers:
[all …]
|
| D | CODEOWNERS | 17 # Please use the MAINTAINERS file to add yourself in an area or to add a new
19 # entries that are not covered by the MAINTAINERS file.
|
| /Zephyr-Core-3.6.0/scripts/ |
| D | get_maintainer.py | 7 Lists maintainers for files or commits. Similar in function to
9 in MAINTAINERS.yml.
11 The comment at the top of MAINTAINERS.yml in Zephyr documents the file format.
47 args.cmd_fn(Maintainers(args.maintainers), args)
60 "-m", "--maintainers",
62 help="Maintainers file to load. If not specified, MAINTAINERS.yml in "
64 "Paths in the maintainers file will always be taken as relative "
78 id_parser.set_defaults(cmd_fn=Maintainers._path_cmd)
88 commits_parser.set_defaults(cmd_fn=Maintainers._commits_cmd)
100 list_parser.set_defaults(cmd_fn=Maintainers._list_cmd)
[all …]
|
| D | set_assignees.py | 19 from get_maintainer import Maintainers
31 parser.add_argument("-M", "--maintainer-file", required=False, default="MAINTAINERS.yml",
105 for area_maintainer in area.maintainers:
118 collab += maintainer_file.areas[area.name].maintainers
126 log(f"candidate maintainers: {_all_maintainers}")
128 maintainers = list(_all_maintainers.keys())
137 if len(area.maintainers) > 0:
138 assignee = area.maintainers[0]
144 # multiple maintainers
145 if len(maintainers) > 1 and pr.user.login == assignee:
[all …]
|
| /Zephyr-Core-3.6.0/doc/project/ |
| D | project_roles.rst | 9 TSC projects generally will involve *Maintainers*, *Collaborators*, and
13 Architecture, code subsystems, etc.). Maintainers shall also serve as the
14 area’s representative on the TSC as needed. Maintainers may become voting
22 by approval of the existing Collaborators and Maintainers of the
113 Maintainers have the following rights and responsibilities,
130 GitHub user name to one or more ``maintainers`` sections of the
157 An *Assignee* is one of the maintainers of a subsystem or code being changed.
159 by the other Maintainers, the Release Engineering team can set an assignee when
164 from additional maintainers, developers and contributors
170 * Solicit approvals from maintainers of the subsystems affected
[all …]
|
| D | dev_env_and_tools.rst | 12 been reviewed, passed a series of checks (CI), and are approved by maintainers.
24 on a component basis, as defined in the :zephyr_file:`MAINTAINERS.yml` file
58 should belong to. A project maintainers or TSC member monitoring the inflow of
239 Maintainers can override the -1 in cases where the CI infrastructure
256 When reviewing a PR, if it has missing or incorrect labels, maintainers shall
339 The PR needs attention from the maintainers.
|
| D | modifying_contributions.rst | 68 Contributors should uncheck the box *“Allow Edits By Maintainers"*
|
| D | release_process.rst | 30 approval from the respective maintainers.
60 sufficiently stable (and which is accepted by the maintainers and the wide community) is
|
| /Zephyr-Core-3.6.0/doc/_extensions/zephyr/ |
| D | gh_utils.py | 54 from get_maintainer import Maintainers
56 MAINTAINERS : Final[Maintainers] = Maintainers(filename=f"{ZEPHYR_BASE}/MAINTAINERS.yml") variable
144 areas = MAINTAINERS.path2areas(rel_path)
|
| /Zephyr-Core-3.6.0/doc/contribute/ |
| D | contributor_expectations.rst | 14 - Less wasted work if reviewers or maintainers reject the direction of the
87 Maintainers have the discretion to request that contributors create an RFC for
111 and there should be tests for the behavior contracts of the API. Maintainers
137 Maintainers may request that contributors break up a PR into smaller PRs and may
168 commitment and priorities. As such, reviewers and maintainers may not get to a
211 - Resolve in the PR among assignee, maintainers and reviewer.
216 Maintainers and project stakeholders.
270 - The Zephyr Project recognizes that reviewers and maintainers have limited
|
| D | bin_blobs.rst | 150 APIs may change and such blobs cannot be modified by all project maintainers
175 project maintainers define an open source test suite that an upstream
204 maintainers may accept and attempt to resolve such issues.
206 However, some flexibility is required because project maintainers may not be
210 Blobs must have designated maintainers that must be responsive to issue reports
214 support from their maintainers. This is required to maintain project control
|
| D | external.rst | 154 This may require adding an entry in the :file:`MAINTAINERS.yml` as part of the
|
| /Zephyr-Core-3.6.0/doc/develop/api/ |
| D | api_lifecycle.rst | 164 the corresponding maintainers
217 state. The Zephyr maintainers will track usage of deprecated APIs on
232 The Zephyr maintainers will decide when to actually remove the API: this
236 If it's OK to remove the API, it will be removed. The maintainers will remove
240 If it's not OK to remove the API, the maintainers will continue to support
|
| /Zephyr-Core-3.6.0/scripts/schemas/twister/ |
| D | platform-schema.yaml | 16 "maintainers":
|
| /Zephyr-Core-3.6.0/.github/workflows/ |
| D | assigner.yml | 40 FLAGS+=" -M MAINTAINERS.yml"
|
| /Zephyr-Core-3.6.0/.github/ISSUE_TEMPLATE/ |
| D | 003_rfc-proposal.md | 12 This section targets end users, TSC members, maintainers and anyone else that might
|
| /Zephyr-Core-3.6.0/scripts/ci/ |
| D | twister_ignore.txt | 27 MAINTAINERS.yml
|
| D | check_compliance.py | 31 from get_maintainer import Maintainers, MaintainersError
1104 Check that MAINTAINERS file parses correctly.
1107 doc = "Check that MAINTAINERS file parses correctly."
1111 MAINTAINERS_FILES = ["MAINTAINERS.yml", "MAINTAINERS.yaml"]
1118 Maintainers(file)
1124 Check that all modules have a MAINTAINERS entry.
1127 doc = "Check that all modules have a MAINTAINERS entry."
1131 MAINTAINERS_FILES = ["MAINTAINERS.yml", "MAINTAINERS.yaml"]
1143 maintainers = Maintainers(maintainers_file)
1153 if area not in maintainers.areas:
|
| /Zephyr-Core-3.6.0/doc/security/ |
| D | reporting.rst | 202 - Maintainers will have access to all information within their domain
213 - As needed, release managers and maintainers may be invited to attend
|
| /Zephyr-Core-3.6.0/cmake/modules/ |
| D | version.cmake | 10 # maintainers in ``${ZEPHYR_BASE}/VERSION``
|
| /Zephyr-Core-3.6.0/include/zephyr/net/ |
| D | ieee802154.h | 70 * maintainers/contributors):
85 * with this API.** It is of interest to subsystem maintainers only.
|
| /Zephyr-Core-3.6.0/doc/services/device_mgmt/ |
| D | mcumgr_backporting.rst | 103 This chapter describes the maintainers' side of accepting and merging fixes and backports.
|
| /Zephyr-Core-3.6.0/doc/releases/ |
| D | release-notes-1.5.rst | 229 * ``ZEP-537`` - doc: create external wiki page "Maintainers"
|
| /Zephyr-Core-3.6.0/doc/safety/ |
| D | safety_overview.rst | 263 of the maintainers, reviewers and contributors and also the safety architect itself.
|
| /Zephyr-Core-3.6.0/doc/build/dts/api/ |
| D | api.rst | 376 .. Documentation maintainers: please keep this sorted by property name
|
12
