Home
last modified time | relevance | path

Searched refs:maintainers (Results 1 – 25 of 28) sorted by relevance

12

/Zephyr-latest/scripts/
Dcheck_maintainers.py33 maintainers = Maintainers(args.maintainers)
39 for area in maintainers.areas.values():
40 gh_users = list(set(gh_users + area.maintainers + area.collaborators))
Dset_assignees.py102 for area_maintainer in area.maintainers:
115 collab += maintainer_file.areas[area.name].maintainers
134 if len(area.maintainers) > 0:
135 tmp_assignees = area.maintainers
136 if pr.user.login in area.maintainers:
141 assignees = area.maintainers
255 for maintainer in area.maintainers:
260 for areas, maintainers in dict(label_to_maintainer).items():
263 label_to_maintainer[tuple([area])] = maintainers
302 maintainers = maintainers_file.areas[area].maintainers
[all …]
Dget_maintainer.py47 args.cmd_fn(Maintainers(args.maintainers), args)
190 area.maintainers = area_dict.get("maintainers", [])
286 if args.maintainer in area.maintainers:
287 print("{:25}\t{}".format(area.name, ",".join(area.maintainers)))
289 print("{:25}\t{}".format(area.name, ",".join(area.maintainers)))
303 maintainers = set()
307 maintainers = maintainers.union(set(area.maintainers))
315 print('{:14}\t{}'.format('maintainers:', len(maintainers)))
412 ", ".join(area.maintainers),
/Zephyr-latest/doc/project/
Dproject_roles.rst135 GitHub user name to one or more ``maintainers`` sections of the
164 An *Assignee* is one of the maintainers of a subsystem or code being changed.
172 from additional maintainers, developers and contributors
177 * Solicit approvals from maintainers of the subsystems affected
219 * Responsibility to coordinate code merges with maintainers.
222 maintainers and follow the merge criteria of a change.
296 * We should be looking for maintainers for areas of code that
315 * Major changes to the file, including the addition of new areas with new maintainers
317 * If additional review by the TSC is required, the maintainers of the file
320 addition of new maintainers or areas.
[all …]
Ddev_env_and_tools.rst12 been reviewed, passed a series of checks (CI), and are approved by maintainers.
58 should belong to. A project maintainers or TSC member monitoring the inflow of
258 When reviewing a PR, if it has missing or incorrect labels, maintainers shall
341 - The PR needs attention from the maintainers.
Drelease_process.rst30 approval from the respective maintainers.
60 sufficiently stable (and which is accepted by the maintainers and the wide community) is
/Zephyr-latest/soc/
DKconfig.v210 # they offer board maintainers the possibility to use board scheme v2.
/Zephyr-latest/.github/ISSUE_TEMPLATE/
D003_rfc-proposal.md13 This section targets end users, TSC members, maintainers and anyone else that might
/Zephyr-latest/doc/contribute/
Dbin_blobs.rst151 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
Dcontributor_expectations.rst14 - Less wasted work if reviewers or maintainers reject the direction of the
170 commitment and priorities. As such, reviewers and maintainers may not get to a
213 - Resolve in the PR among assignee, maintainers and reviewer.
272 - The Zephyr Project recognizes that reviewers and maintainers have limited
Dguidelines.rst624 guidelines, maintainers may decide which style should be adopted.
1041 Project maintainers should use good judgement and prioritize the Zephyr
/Zephyr-latest/doc/develop/api/
Dapi_lifecycle.rst184 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/scripts/ci/coverage/
Dcoverage_analysis.py28 self.maintainers_file = self.get_maintainers_file( args.maintainers)
41 def get_maintainers_file(self, maintainers): argument
43 with open(maintainers, 'r') as file:
/Zephyr-latest/lib/posix/options/
DKconfig.toolchain7 # for toolchain integrators, C library maintainers, etc, and is not intended for general users.
/Zephyr-latest/cmake/modules/
Dversion.cmake10 # maintainers in ``${ZEPHYR_BASE}/VERSION``
/Zephyr-latest/doc/services/device_mgmt/
Dmcumgr_backporting.rst103 This chapter describes the maintainers' side of accepting and merging fixes and backports.
/Zephyr-latest/doc/security/
Dreporting.rst215 - As needed, release managers and maintainers may be invited to attend
Dsecurity-overview.rst377 These reviews shall be performed by the subsystem maintainers and
/Zephyr-latest/doc/develop/test/
Dbsim.rst164 The rationale is that it is easier and faster for the maintainers to perform tree-wide updates for
/Zephyr-latest/scripts/ci/
Dcheck_compliance.py1459 maintainers = Maintainers(maintainers_file)
1469 if area not in maintainers.areas:
/Zephyr-latest/doc/safety/
Dsafety_overview.rst281 of the maintainers, reviewers and contributors and also the safety architect itself.
/Zephyr-latest/doc/build/dts/api/
Dapi.rst378 .. Documentation maintainers: please keep this sorted by property name
/Zephyr-latest/doc/build/dts/
Dintro-syntax-structure.rst221 .. Documentation maintainers: If you add a property to this list,
/Zephyr-latest/doc/hardware/arch/
Darm_cortex_m.rst685 The updated list of maintainers and collaborators for Cortex-M can be found
/Zephyr-latest/doc/hardware/porting/
Dboard_porting.rst433 This allows board maintainers to write a base devicetree file for the board

12