TSC: Difference between revisions
Armin Kuster (talk | contribs) |
Chuckwolber (talk | contribs) (Add from TSC guidance sent by Richard Purdie. Moved intent to own section in order to isolated ongoing operational tasks. Created a separate contact section at the bottom so it shows up in the table of contents. Added a section on challenges and achievements (information also provided by Richard Purdie).) |
||
| Line 7: | Line 7: | ||
The TSC does not overlap with the OpenEmbedded TSC which is a similar entity with responsibility for the OpenEmbedded Architecture and the OpenEmbedded hosted repositories and infrastructure. | The TSC does not overlap with the OpenEmbedded TSC which is a similar entity with responsibility for the OpenEmbedded Architecture and the OpenEmbedded hosted repositories and infrastructure. | ||
The YP TSC has a two year term limits. | The YP TSC has a two year term limits. The next election is May of 2025. | ||
=Members= | =Members= | ||
| Line 17: | Line 17: | ||
* Denys Dmytriyenko - OE Elected | * Denys Dmytriyenko - OE Elected | ||
The TSC can | =Intent= | ||
In addition to regular operational tasks, the TSC is intended to be an entity of last resort. It is expected that the community will reach consensus and/or individual maintainers will make decisions in the best interests of the users and overall project. The TSC will therefore only act if these processes have failed and a decision is needed. | |||
Anyone is free to approach any TSC member with any issue or concern. In turn the matter will be referred to the TSC members for discussion. The TSC members will usually try and continue public discussion as much as is practical. However, any final TSC discussions will be closed session with the aim of quickly reaching a decision, which will then be made public. | |||
Bear in mind that the TSC is not an engineering organisation, and therefore it can only pass on recommendations to the community or governing board. Individual TSC members are also free to make contributions to the project with these things in mind. | |||
=Operation= | =Operation= | ||
The TSC | The TSC meets weekly to discuss a number of topics related to ensuring project success, including the following: | ||
* Final approval of releases after they come out of QA | |||
* Preparing a summary slide for the monthly YP members meeting covering technical aspects of the project. | |||
* Review and approval of Yocto Project Compatible applications. | |||
* Review and approval for git repos, mailing lists, and autobuilder testing of layers. | |||
* Managing YP contracted technical work, such as: | |||
** Technical Writing | |||
** Build/Integration Work | |||
** Long Term Support (LTS) | |||
* Review of escalated LTS policy questions. | |||
* Prepare/propose technical work topics to the project membership. Examples include: | |||
** Sovereign Tech Fund | |||
** Layer Index | |||
** Security Work | |||
* Maintain the criteria for the YP Compatible programme. | |||
* Writing and maintaining YP technical "policy". | |||
* Handle any code of conduct issues | |||
** Note: OE has delegated this to YP to ensure clear lines of responsibility. | |||
* Develop guidance on YP infrastructure planning/issues. | |||
=Recent Achievements= | |||
* Planning and overseeing the Sovereign Tech Fund work. | |||
* Developed plans to refresh and relaunch Yocto Project Compatible v3 | |||
* Guide the migration of the infrastructure to the new Valkyrie setup. | |||
* Ensured smooth/reliable/respected LTS releases. | |||
= Processes = | =Processes= | ||
[https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS#New_Releases_process, LTS / Stable processes] | [https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS#New_Releases_process, LTS / Stable processes] | ||
| Line 39: | Line 64: | ||
[[TSC Election Process]] | [[TSC Election Process]] | ||
== | =Challenges= | ||
An incomplete list of challenges facing the TSC and the Yocto Project as a whole. | |||
* How do we improve and standardise the OE setup? | |||
* How do we scale maintainership and avoid single points of knowledge failure? | |||
* How do we embrace new ideas about communication and submission processes? | |||
* Can we attract new maintainers and retain them? | |||
[https://wiki.yoctoproject.org/wiki/Future_Directions Future Direction] | [https://wiki.yoctoproject.org/wiki/Future_Directions Future Direction] | ||
=Contact= | |||
The TSC can be contacted on address tsc@lists.yoctoproject.org. | |||
Latest revision as of 05:17, 8 March 2025
Yocto Project Technical Steering Committee
The YP TSC consists of 5 people; 3 nominated from Yocto Project Member Organizations (including the chairperson) and 2 from OpenEmbedded.
The TSC has overall responsibility for all technical aspects of the Yocto Project. This includes repositories hosted on https://git.yoctoproject.org/, the associated mailing lists, bugzilla, the testing processes and infrastructure/QA and the releases of the project.
The TSC does not overlap with the OpenEmbedded TSC which is a similar entity with responsibility for the OpenEmbedded Architecture and the OpenEmbedded hosted repositories and infrastructure.
The YP TSC has a two year term limits. The next election is May of 2025.
Members
- Richard Purdie (Linux Foundation) - TSC Chair
- Khem Raj (Comcast) - YP Membership Elected
- Ross Burton (Arm) - YP Membership Elected
- Mark Hatle - OE Elected
- Denys Dmytriyenko - OE Elected
Intent
In addition to regular operational tasks, the TSC is intended to be an entity of last resort. It is expected that the community will reach consensus and/or individual maintainers will make decisions in the best interests of the users and overall project. The TSC will therefore only act if these processes have failed and a decision is needed.
Anyone is free to approach any TSC member with any issue or concern. In turn the matter will be referred to the TSC members for discussion. The TSC members will usually try and continue public discussion as much as is practical. However, any final TSC discussions will be closed session with the aim of quickly reaching a decision, which will then be made public.
Bear in mind that the TSC is not an engineering organisation, and therefore it can only pass on recommendations to the community or governing board. Individual TSC members are also free to make contributions to the project with these things in mind.
Operation
The TSC meets weekly to discuss a number of topics related to ensuring project success, including the following:
- Final approval of releases after they come out of QA
- Preparing a summary slide for the monthly YP members meeting covering technical aspects of the project.
- Review and approval of Yocto Project Compatible applications.
- Review and approval for git repos, mailing lists, and autobuilder testing of layers.
- Managing YP contracted technical work, such as:
- Technical Writing
- Build/Integration Work
- Long Term Support (LTS)
- Review of escalated LTS policy questions.
- Prepare/propose technical work topics to the project membership. Examples include:
- Sovereign Tech Fund
- Layer Index
- Security Work
- Maintain the criteria for the YP Compatible programme.
- Writing and maintaining YP technical "policy".
- Handle any code of conduct issues
- Note: OE has delegated this to YP to ensure clear lines of responsibility.
- Develop guidance on YP infrastructure planning/issues.
Recent Achievements
- Planning and overseeing the Sovereign Tech Fund work.
- Developed plans to refresh and relaunch Yocto Project Compatible v3
- Guide the migration of the infrastructure to the new Valkyrie setup.
- Ensured smooth/reliable/respected LTS releases.
Processes
Challenges
An incomplete list of challenges facing the TSC and the Yocto Project as a whole.
- How do we improve and standardise the OE setup?
- How do we scale maintainership and avoid single points of knowledge failure?
- How do we embrace new ideas about communication and submission processes?
- Can we attract new maintainers and retain them?
Contact
The TSC can be contacted on address tsc@lists.yoctoproject.org.
