Lines Matching full:tsc
3 TSC Project Roles
9 TSC projects generally will involve *Maintainers*, *Collaborators*, and
12 **Maintainer**: lead Collaborators on an area identified by the TSC (e.g.
14 area’s representative on the TSC as needed. Maintainers may become voting
15 members of the TSC under the guidelines stated in the project Charter.
18 May become a Maintainer with approval of existing TSC voting members.
137 the TSC
147 Contributors nor Collaborators must be approved by the TSC before they can
159 may be requested by the TSC to retire from the role they are elected.
160 * Such a request needs to be raised as a motion in the TSC and be
161 approved by the TSC voting members.
162 By approval of the TSC the individual is considered to be retired
164 * The above applies to elected TSC Project roles that may be defined
201 * Responsibility to alert TSC if any issues are not adequately addressed by the
220 team and are approved by the TSC.
221 * The team reports directly into the TSC.
228 * Responsibility to take directions from the TSC and follow them.
239 by a TSC voting member to join the Release Engineering team.
241 existing TSC voting members.
242 * To ensure a functional Release Engineering team the TSC shall
257 * TSC has to approve a release manager.
326 should come in as standalone pull requests and require TSC review.
327 * If additional review by the TSC is required, the maintainers of the file
328 should send the requested changes to the TSC and give members of the TSC two
331 * Path, collaborator and name changes do not require a review by the TSC.
332 * Addition of new areas without a maintainer do not require review by the TSC.