| /Zephyr-Core-3.7.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:
130 maintainers:
149 maintainers:
[all …]
|
| /Zephyr-Core-3.7.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",
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-Core-3.7.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
118 Maintainers have the following rights and responsibilities,
135 GitHub user name to one or more ``maintainers`` sections of the
162 An *Assignee* is one of the maintainers of a subsystem or code being changed.
164 by the other Maintainers, the Release Engineering team can set an assignee when
170 from additional maintainers, developers and contributors
175 * 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
241 Maintainers can override the -1 in cases where the CI infrastructure
258 When reviewing a PR, if it has missing or incorrect labels, maintainers shall
341 - 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.7.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.7.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
113 and there should be tests for the behavior contracts of the API. Maintainers
139 Maintainers may request that contributors break up a PR into smaller PRs and may
170 commitment and priorities. As such, reviewers and maintainers may not get to a
213 - Resolve in the PR among assignee, maintainers and reviewer.
218 Maintainers and project stakeholders.
272 - 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
|
| /Zephyr-Core-3.7.0/doc/develop/api/ |
| D | api_lifecycle.rst | 184 the corresponding maintainers
244 state. The Zephyr maintainers will track usage of deprecated APIs on
259 The Zephyr maintainers will decide when to actually remove the API: this
263 If it's OK to remove the API, it will be removed. The maintainers will remove
267 If it's not OK to remove the API, the maintainers will continue to support
|
| /Zephyr-Core-3.7.0/soc/ |
| D | Kconfig.v2 | 10 # they offer board maintainers the possibility to use board scheme v2.
|
| /Zephyr-Core-3.7.0/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-Core-3.7.0/.github/workflows/ |
| D | assigner.yml | 40 FLAGS+=" -M MAINTAINERS.yml"
|
| D | codecov.yaml | 204 -m MAINTAINERS.yml \
|
| /Zephyr-Core-3.7.0/scripts/ci/ |
| D | twister_ignore.txt | 27 MAINTAINERS.yml
|
| D | check_compliance.py | 32 from get_maintainer import Maintainers, MaintainersError
1324 Check that MAINTAINERS file parses correctly.
1327 doc = "Check that MAINTAINERS file parses correctly."
1331 MAINTAINERS_FILES = ["MAINTAINERS.yml", "MAINTAINERS.yaml"]
1338 Maintainers(file)
1344 Check that all modules have a MAINTAINERS entry.
1347 doc = "Check that all modules have a MAINTAINERS entry."
1351 MAINTAINERS_FILES = ["MAINTAINERS.yml", "MAINTAINERS.yaml"]
1363 maintainers = Maintainers(maintainers_file)
1373 if area not in maintainers.areas:
|
| /Zephyr-Core-3.7.0/scripts/schemas/twister/ |
| D | platform-schema.yaml | 16 "maintainers":
|
| /Zephyr-Core-3.7.0/.github/ISSUE_TEMPLATE/ |
| D | 003_rfc-proposal.md | 13 This section targets end users, TSC members, maintainers and anyone else that might
|
| /Zephyr-Core-3.7.0/lib/posix/options/ |
| D | Kconfig.toolchain | 7 # for toolchain integrators, C library maintainers, etc, and is not intended for general users.
|
| /Zephyr-Core-3.7.0/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-Core-3.7.0/include/zephyr/net/ |
| D | ieee802154.h | 72 * maintainers/contributors):
89 * with this API.** It is of interest to subsystem maintainers only.
|
| /Zephyr-Core-3.7.0/scripts/west_commands/ |
| D | blobs.py | 137 the maintainers of the module so that they can check
|
| /Zephyr-Core-3.7.0/cmake/modules/ |
| D | version.cmake | 10 # maintainers in ``${ZEPHYR_BASE}/VERSION``
|
| /Zephyr-Core-3.7.0/doc/services/device_mgmt/ |
| D | mcumgr_backporting.rst | 103 This chapter describes the maintainers' side of accepting and merging fixes and backports.
|
