Warning
You're reading the documentation for a version of ROS 2 that has reached its EOL (end-of-life), and is no longer officially supported.
If you want up-to-date information, please have a look at Jazzy.
ROS 2 TSC applicant intake process
Objectives
Increase the pool of high quality applicants
Help applicants understand what the ROS 2 TSC expects from an application
Help ROS 2 TSC better evaluate the applicants
Process
Applicant inquires about joining TSC via info@openrobotics.org per ROS 2 Governance.
Open Robotics responds with the application questions (below).
Applicant completes and sends application to info@openrobotics.org.
Open Robotics does an initial review and gives applicant feedback if warranted. For example:
“consider developing your track record of contribution and then re-apply.”
“What you contribute to is not part of ROS 2 Common Packages (REP 2005). Consider getting it added before proceeding with application for more favorable reception.”
If application seems worthwhile, Open Robotics passes it to TSC member to “sponsor”.
Open Robotics can ask TSC for volunteer(s) per applicant or Open Robotics could have list of TSC members who already volunteered to support this function.
Sponsor arranges short 1:1 with applicant to talk about ROS 2 TSC role and responsibilities. Afterwards the applicant can:
proceed with application as-is
revise application
delay submission e.g. to develop their contribution track record
decide not to proceed.
[two weeks before TSC meeting]: applications are distributed to TSC members for independent review
If 2 TSC members respond agreeing to “sponsor” applicant then these proceed to the next step. Applicant should “minimally meet” TSC member criteria before addressing TSC.
Otherwise Open Robotics informs applicant “Not at this time, please consider applying again later with more contribution history.”
[in TSC meeting] Applicant or Sponsor can address TSC. 5 minute presentation with up to 5 additional minutes of Q&A.
[in TSC meeting]: Synchronous private/unsharable discussion of the applications after applicant(s) leave the call. TSC members are to be discrete about what has been discussed.
[after TSC meeting]: Asynchronous vote on the applicants completed in around 10 days
Open Robotics notifies applicant(s) of TSC decision.
Questionnaire for the applicant
The following is to be provided to the applicant by Open Robotics via email in response to them expressing interest in joining the ROS 2 TSC.
To which aspect(s) of ROS 2 do you plan to make open source contributions?
For example contributions to ROS 2 Common Packages.
Are you already making those contributions? Since when? Please explain your history of contribution. If you have none, consider applying after developing some history of contribution.
Are there any other kinds of contributions that you are already making or plan? Education, evangelism, et al.?
What level of effort do you plan to dedicate to making those contributions?
How many FTE (full time equivalent) people will be making those contributions?
How many FTE are already doing so?
Are these contributions already happening now, and if so, can you point to results produced so far?
For example describe or attach details of your contributions to ROS 2 Common Packages.
Links to your contributions are helpful.
How do these contributions benefit your business or organization?
Why do you do this?
Evaluation Guide for TSC members
The following is suggested guidance for TSC members to evaluate applicants:
To which aspect(s) of ROS 2 do you plan to make open source contributions?
Are the contributions useful to the community?
Are the contributions to ROS 2 Common Packages?
What level of effort do you plan to dedicate to making those contributions?
Give more credence to past contributions
Proposed future contributions are important but consider past contribution to evaluate how credible those plans are.
Are these contributions already happening now, and if so, can you point to results produced so far?
Are the contributions ones that the community and TSC values?
Are the contributions to ROS 2 Common Packages (REP 2005)?
Emphasis is on what they’ve contributed already, not what they promise to do. If they don’t have enough evidence of contribution, encourage them to apply after developing their contribution track record.
How do these contributions benefit your business or organization?
This answer helps you evaluate how much focus and investment it already has and whether it seems likely to continue.
Do you see that the applicant has a vested interest in this work and the success of ROS 2? Or does it seem they seek to join merely for prestige and marketing?