Searched full:collaborators (Results 1 – 12 of 12) sorted by relevance
| /Zephyr-latest/ |
| D | MAINTAINERS.yml | 17 # The area gets odd fixes and may have collaborators.
28 # collaborators (not to be confused with the GitHub collaborator role):
72 # this would be sub-areas which add extra fields (for ex. more `collaborators`
86 # * Users mentioned in 'maintainers' and 'collaborators' are added as
98 # Collaborators: <list of sub-maintainers>
109 # * Changing the 'collaborators' lines requires the maintainer and
110 # collaborators of that area to agree (or vote on it)
134 collaborators:
148 collaborators:
169 collaborators:
[all …]
|
| /Zephyr-latest/scripts/ |
| D | get_maintainer.py | 125 help="Count areas, unique maintainers, and / or unique collaborators")
133 "--count-collaborators",
135 help="Count the number of unique collaborators")
191 area.collaborators = area_dict.get("collaborators", [])
302 collaborators = set()
310 collaborators = collaborators.union(set(area.collaborators))
317 print('{:14}\t{}'.format('collaborators:', len(collaborators)))
369 collaborators:
370 List of collaborators. Empty if the area has no 'collaborators' key.
413 ", ".join(area.collaborators),
[all …]
|
| D | check_maintainers.py | 40 gh_users = list(set(gh_users + area.maintainers + area.collaborators))
63 print('The following GitHub user accounts are not collaborators:')
|
| D | set_assignees.py | 112 # Create a list of collaborators ordered by the area match
116 collab += maintainer_file.areas[area.name].collaborators
191 log(f"Skip '{collaborator}': not in collaborators")
307 collaborators = maintainers_file.areas[area].collaborators
309 log(f"Found {area}, maintainers={maintainers}, collaborators={collaborators}")
338 for collaborator in area.collaborators:
|
| /Zephyr-latest/doc/project/ |
| D | project_roles.rst | 9 TSC projects generally will involve *Maintainers*, *Collaborators*, and
12 **Maintainer**: lead Collaborators on an area identified by the TSC (e.g.
21 documentation to the project. Contributors may become Collaborators
22 by approval of the existing Collaborators and Maintainers of the
93 Collaborators have the following rights and responsibilities,
107 name to one or more ``collaborators`` sections of the :ref:`maintainers_file` in
129 in addition to those listed for Contributors and Collaborators:
134 in conjunction with the collaborators and submitters.
144 Contributors or Collaborators are promoted to the Maintainer role by adding the
147 Contributors nor Collaborators must be approved by the TSC before they can
[all …]
|
| D | working_groups.rst | 22 :ref:`Collaborators <collaborator>`; however, working groups may impose
|
| D | release_process.rst | 141 - All collaborators can add or remove blocking labels.
|
| /Zephyr-latest/.github/ISSUE_TEMPLATE/ |
| D | 007_ext-source.md | 29 choose to identify a single maintainer only or add collaborators as well
|
| /Zephyr-latest/doc/contribute/ |
| D | modifying_contributions.rst | 9 Zephyr contributors and collaborators are encouraged to assist
|
| /Zephyr-latest/doc/develop/ |
| D | modules.rst | 187 for example, for adding individuals as Collaborators in the repository
199 * request additional collaborators to be added to the repository, as
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | arm_cortex_m.rst | 681 Maintainers & Collaborators
685 The updated list of maintainers and collaborators for Cortex-M can be found
|
| /Zephyr-latest/doc/contribute/coding_guidelines/ |
| D | index.rst | 16 For existing Zephyr maintainers and collaborators, if you are unable to
|
