...
- Testing and voting on a release
- Performing detailed and thorough review of all the contributions coming into the subproject(s)
- Actively participating in technical discussions in online and offline channels
- Provide content update and documentation for the project itself and its wiki
- Help manage project website and other collateral such as its social media
- Answer user questions on Slack, mailing list and other communication channels
- Diligently providing stewardship of project's IP
- Monitoring and maintaining the project's CI/CD pipeline and other infrastructure
- Present at technical conferences, meetup and other events
- Build something on top of the project and actively share your experience (or better yet help polish all the rough edges you bumped into int the project itself)
Since none of these responsibilities require a special committer status, it is expected that those Contributors who would like to become Committers demonstrate them ahead of time in order to trigger change of their status. In other words: the best way to apply for a job is to already be doing it.
...
coordinating the technical direction of the Project, including the architecture and development tasks needed to achieve the mission and scope of the Project;
approving project proposals (including, but not limited to, incubation, deprecation and changes to the Project’s charter or scope);
coordinating technical community engagement with the community of Users (as defined in Section 6 of Project Charter), especially with respect to requirements, high level architecture, implementation experiences, use cases, etc.;
communicating with external and industry organizations concerning Project technical matters;
appointing representatives to work with other open source or standards communities;
establishing community norms, workflows or policies for releases;
discussing, seeking consensus, and where necessary, voting on technical matters relating to the code base that affect multiple projects;
establishing election processes for Contributors, Committers, TSC members or other leadership roles in the technical community that are not within the scope of any single project; and
- conducting regular TSC meetings
...
The amount of time one can dedicate to an open source project tends to ebb and flow. While this is totally OK for almost any role, participation in the TSC requires at least an amount of time appropriate for intelligently casting votes. If that becomes a problem and then an existing TSC member may decide to transition to the Emeritus status. At that point the person is no longer considered a TSC member for the purposes of quorum or majority votes, but can transition back to a full TSC member status by simply emailing the TSC mailing list and asking for it.