| /Zephyr-latest/scripts/ |
| D | check_maintainers.py | 10 from get_maintainer import Maintainers
21 "-m", "--maintainers",
23 help="Maintainers file to load. If not specified, MAINTAINERS.yml in "
25 "Paths in the maintainers file will always be taken as relative "
33 maintainers = Maintainers(args.maintainers)
39 for area in maintainers.areas.values():
40 gh_users = list(set(gh_users + area.maintainers + area.collaborators))
|
| 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",
102 for area_maintainer in area.maintainers:
115 collab += maintainer_file.areas[area.name].maintainers
123 log(f"candidate maintainers: {_all_maintainers}")
134 if len(area.maintainers) > 0:
135 tmp_assignees = area.maintainers
136 if pr.user.login in area.maintainers:
141 assignees = area.maintainers
179 # do not attempt to add them again based on MAINTAINERS file.
[all …]
|
| /Zephyr-latest/ |
| 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:
131 maintainers:
145 maintainers:
[all …]
|
| /Zephyr-latest/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
128 Maintainers have the following rights and responsibilities,
145 GitHub user name to one or more ``maintainers`` sections of the
174 An *Assignee* is one of the maintainers of a subsystem or code being changed.
176 by the other Maintainers, the Release Engineering team can set an assignee when
182 from additional maintainers, developers and contributors
187 * 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
231 Maintainers can override the -1 in cases where the CI infrastructure
248 When reviewing a PR, if it has missing or incorrect labels, maintainers shall
331 - The PR needs attention from the maintainers.
|
| /Zephyr-latest/doc/_extensions/zephyr/ |
| D | gh_utils.py | 52 from get_maintainer import Maintainers
55 MAINTAINERS : Final[Maintainers] = Maintainers(filename=f"{ZEPHYR_BASE}/MAINTAINERS.yml") variable
143 areas = MAINTAINERS.path2areas(rel_path)
|
| /Zephyr-latest/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
160 The final commit history should be easy to understand for future maintainers. Logical units of
165 and there should be tests for the behavior contracts of the API. Maintainers
198 Maintainers may request that contributors break up a PR into smaller PRs and may
229 commitment and priorities. As such, reviewers and maintainers may not get to a
272 - Resolve in the PR among assignee, maintainers and reviewer.
277 Maintainers and project stakeholders.
|
| D | bin_blobs.rst | 151 APIs may change and such blobs cannot be modified by all project maintainers
176 project maintainers define an open source test suite that an upstream
205 maintainers may accept and attempt to resolve such issues.
207 However, some flexibility is required because project maintainers may not be
211 Blobs must have designated maintainers that must be responsive to issue reports
215 support from their maintainers. This is required to maintain project control
|
| D | modifying_contributions.rst | 68 Contributors should uncheck the box *“Allow Edits By Maintainers"*
|
| D | reviewer_expectations.rst | 9 - The Zephyr Project recognizes that reviewers and maintainers have limited
|
| /Zephyr-latest/doc/develop/api/ |
| D | api_lifecycle.rst | 184 the corresponding maintainers
245 state. The Zephyr maintainers will track usage of deprecated APIs on
260 The Zephyr maintainers will decide when to actually remove the API: this
264 If it's OK to remove the API, it will be removed. The maintainers will remove
268 If it's not OK to remove the API, the maintainers will continue to support
|
| /Zephyr-latest/soc/ |
| D | Kconfig.v2 | 10 # they offer board maintainers the possibility to use board scheme v2.
|
| /Zephyr-latest/scripts/ci/coverage/ |
| D | coverage_analysis.py | 28 self.maintainers_file = self.get_maintainers_file( args.maintainers)
41 def get_maintainers_file(self, maintainers): argument
43 with open(maintainers, 'r') as file:
228 print("ERROR: Fail while parsing MAINTAINERS file at %s", component_name)
284 json_component["Comment"] = "Missed in maintainers.yml file."
521 …parser.add_argument('-m','--maintainers', help='Path to maintainers.yml [Required]', required=True)
|
| /Zephyr-latest/.github/workflows/ |
| D | assigner.yml | 39 FLAGS+=" -M MAINTAINERS.yml"
|
| /Zephyr-latest/scripts/ci/ |
| D | twister_ignore.txt | 27 MAINTAINERS.yml
|
| D | check_compliance.py | 34 from get_maintainer import Maintainers, MaintainersError
1534 Check that MAINTAINERS file parses correctly.
1537 doc = "Check that MAINTAINERS file parses correctly."
1541 MAINTAINERS_FILES = ["MAINTAINERS.yml", "MAINTAINERS.yaml"]
1548 Maintainers(file)
1554 Check that all modules have a MAINTAINERS entry.
1557 doc = "Check that all modules have a MAINTAINERS entry."
1561 MAINTAINERS_FILES = ["MAINTAINERS.yml", "MAINTAINERS.yaml"]
1573 maintainers = Maintainers(maintainers_file)
1583 if area not in maintainers.areas:
|
| /Zephyr-latest/.github/ISSUE_TEMPLATE/ |
| D | 003_rfc-proposal.md | 13 This section targets end users, TSC members, maintainers and anyone else that might
|
| /Zephyr-latest/scripts/schemas/twister/ |
| D | platform-schema.yaml | 23 "maintainers":
|
| /Zephyr-latest/lib/posix/options/ |
| D | Kconfig.toolchain | 7 # for toolchain integrators, C library maintainers, etc, and is not intended for general users.
|
| /Zephyr-latest/doc/contribute/style/ |
| D | index.rst | 87 guidelines, maintainers may decide which style should be adopted.
|
| /Zephyr-latest/doc/security/ |
| D | reporting.rst | 204 - Maintainers will have access to all information within their domain
215 - As needed, release managers and maintainers may be invited to attend
|
| /Zephyr-latest/include/zephyr/net/ |
| D | ieee802154.h | 72 * maintainers/contributors):
89 * with this API.** It is of interest to subsystem maintainers only.
|
| /Zephyr-latest/scripts/west_commands/ |
| D | blobs.py | 136 the maintainers of the module so that they can check
|
| /Zephyr-latest/cmake/modules/ |
| D | version.cmake | 10 # maintainers in ``${ZEPHYR_BASE}/VERSION``
|
