Lines Matching refs: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.
127 the TSC
137 Contributors nor Collaborators must be approved by the TSC before they can
149 may be requested by the TSC to retire from the role they are elected.
150 * Such a request needs to be raised as a motion in the TSC and be
151 approved by the TSC voting members.
152 By approval of the TSC the individual is considered to be retired
154 * The above applies to elected TSC Project roles that may be defined
191 * Responsibility to alert TSC if any issues are not adequately addressed by the
210 team and are approved by the TSC.
211 * The team reports directly into the TSC.
218 * Responsibility to take directions from the TSC and follow them.
229 by a TSC voting member to join the Release Engineering team.
231 existing TSC voting members.
232 * To ensure a functional Release Engineering team the TSC shall
247 * TSC has to approve a release manager.
316 should come in as standalone pull requests and require TSC review.
317 * If additional review by the TSC is required, the maintainers of the file
318 should send the requested changes to the TSC and give members of the TSC two
321 * Path, collaborator and name changes do not require a review by the TSC.
322 * Addition of new areas without a maintainer do not require review by the TSC.