Searched full:maintainers (Results 1 – 25 of 26) sorted by relevance
12
/Zephyr-Core-2.7.6/ |
D | MAINTAINERS.yml | 25 # maintainers: 84 # * A user mentioned in 'maintainers' is added as Assignee to 87 # * Users mentioned in 'maintainers' and 'collaborators' are added as 98 # Maintainers: <list of maintainers> 99 # Collaborators: <list of sub-maintainers> 105 # Changes to MAINTAINERS.yml need to be approved as follows: 107 # * Changing the 'maintainers' for an area needs approval from the 117 maintainers: 131 maintainers: 150 maintainers: [all …]
|
D | CODE_OF_CONDUCT.md | 6 contributors and maintainers pledge to making participation in our project and 36 Project maintainers are responsible for clarifying the standards of acceptable 40 Project maintainers have the right and responsibility to remove, edit, or 53 further defined and clarified by project maintainers. 66 Project maintainers who do not follow or enforce the Code of Conduct in good
|
D | CODEOWNERS | 19 /MAINTAINERS.yml @ioannisg @MaureenHelm
|
/Zephyr-Core-2.7.6/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 | checkpatch.pl | 1110 them to the maintainers. 2572 …"$realfile is marked as 'obsolete' in the MAINTAINERS hierarchy. No unnecessary modifications ple… 2581 if ($realfile !~ /^MAINTAINERS/) { 3054 # check MAINTAINERS entries 3055 if ($realfile =~ /^MAINTAINERS$/) { 3056 # check MAINTAINERS entries for the right form 3060 "MAINTAINERS entries use one tab after TYPE:\n" . $herecurr) && 3065 # check MAINTAINERS entries for the right ordering too 3079 "Unknown MAINTAINERS entry type: '$cur'\n" . $herecurr); 3083 "Misordered MAINTAINERS entry - list '$cur:' before '$prev:'\n" . $hereprev); [all …]
|
/Zephyr-Core-2.7.6/doc/development_process/ |
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 78 Maintainers have the following rights and responsibilities, 113 An *Assignee* is one of the maintainers of a subsystem or code being changed. 115 by the other Maintainers, the Release Engineering team can set an assignee when 118 * Right to dismiss stale reviews and seek reviews from additional maintainers, 124 * Solicit approvals from maintainers of the subsystems affected 130 A team of active Maintainers involved in multiple areas. [all …]
|
D | modifying_contributions.rst | 68 Contributors should uncheck the box *“Allow Edits By Maintainers"*
|
D | dev_env_and_tools.rst | 12 been reviewed, passed a series of checks (CI), and are approved by maintainers. 57 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 369 ``Needs review`` The PR needs attention from the maintainers
|
D | release_process.rst | 28 respective maintainers.)
|
/Zephyr-Core-2.7.6/doc/reference/api/ |
D | api_lifecycle.rst | 163 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-2.7.6/.github/workflows/ |
D | compliance.yml | 8 name: Check MAINTAINERS file 15 - name: Run Maintainers Script
|
/Zephyr-Core-2.7.6/scripts/ci/ |
D | twister_ignore.txt | 19 MAINTAINERS.yml
|
/Zephyr-Core-2.7.6/.github/ISSUE_TEMPLATE/ |
D | rfc-proposal.md | 12 This section targets end users, TSC members, maintainers and anyone else that might
|
/Zephyr-Core-2.7.6/doc/security/ |
D | reporting.rst | 176 - Maintainers will have access to all information within their domain 187 - As needed, release managers and maintainers may be invited to attend
|
D | security-overview.rst | 381 These reviews shall be performed by the subsystem maintainers and
|
/Zephyr-Core-2.7.6/cmake/ |
D | version.cmake | 10 # maintainers in ``${ZEPHYR_BASE}/VERSION``
|
/Zephyr-Core-2.7.6/doc/contribute/ |
D | external.rst | 106 This may require adding an entry in the :file:`MAINTAINERS.yaml` as part of the
|
/Zephyr-Core-2.7.6/doc/reference/devicetree/ |
D | api.rst | 330 .. Documentation maintainers: please keep this sorted by property name
|
/Zephyr-Core-2.7.6/doc/releases/ |
D | release-notes-1.5.rst | 229 * :jira:`ZEP-537` - doc: create external wiki page "Maintainers"
|
D | release-notes-2.4.rst | 838 system. LVGL maintainers are currently investigating ways for reducing the
|
/Zephyr-Core-2.7.6/doc/guides/ |
D | modules.rst | 179 :ref:`Maintainers <project_roles>`. 875 Maintainers from the Zephyr project will create the repository and initialize
|
/Zephyr-Core-2.7.6/doc/guides/arch/ |
D | arm_cortex_m.rst | 653 Maintainers & Collaborators 657 The updated list of maintainers and collaborators for Cortex-M can be found 658 in :file:`MAINTAINERS.yml`.
|
/Zephyr-Core-2.7.6/scripts/west_commands/completion/ |
D | west-completion.bash | 15 # © 2009-2010, Bash Completion Maintainers
|
/Zephyr-Core-2.7.6/doc/guides/dts/ |
D | intro.rst | 253 .. Documentation maintainers: If you add a property to this list,
|
/Zephyr-Core-2.7.6/doc/contribute/coding_guidelines/ |
D | index.rst | 45 For existing Zephyr maintainers and collaborators, if you are unable to
|
12