Lines Matching full:maintainers

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
215 A team of active Maintainers involved in multiple areas.
229 * Responsibility to coordinate code merges with maintainers.
232   maintainers and follow the merge criteria of a change.
238 * Maintainers highly involved in the project may be nominated
300 MAINTAINERS File
303 Generic guidelines for deciding and filling in the Maintainers' list
306 * We should be looking for maintainers for areas of code that
309   * Un-maintained areas should be indicated clearly in the MAINTAINERS file
322 * In general, updates to the MAINTAINERS file should be
325 * Major changes to the file, including the addition of new areas with new maintainers
327 * If additional review by the TSC is required, the maintainers of the file
330   addition of new maintainers or areas.
333 * The MAINTAINERS file itself shall have a maintainer
344     maintainers but preferably collaborator/contributors
368   maintainers/collaborators would suffice.