The Tekton Governing Board (GB) is the governing body of the Tekton open source project. It's an elected group that represents the contributors to the project, and has oversight on governance and technical matters.
The Governing Board adopts a principle of maximum representation, which avoids any company representing more than 40% of the GB.
The Tekton GB defines and maintains the project contributor ladder, which identifies several roles for contributors, the requirements and responsibilities of each role and how to transition between them.
Tekton is made up of several sub-projects. Each sub-project either adopts the complete contributor ladder, or in some the project may adopt a simplified contributor ladder, which is done for instance by the teams that maintains the website and the CI/CD infrastructure.
All communication happens in the open, working group meetings are public and recorded.
The decision-making process is formalised through the "Tekton Enhancement Proposal" (TEP) process. Approvals are required by representatives of at least two different companies, to ensure vendor neutrality.
More details are available in the governance documentation and the community repository.
Maintainer List: the org yaml defines all GitHub teams which include maintainers and reviewers. The mapping between GitHub IDs and affiliation is maintained through the "devstats" repo. The affiliation is documented in the PRs that add individuals to the org yaml as well
How your project is making decisions: Tekton design decisions happen in the open through the TEP proposal process, which ensures vendor neutrality by requiring approvals from two different companies
How and when contributors are moving through the contributor ladder (e.g. becoming a maintainer): Community members may play different roles as described in the contributor ladder. The ladder also describes promotions, demotions and removals, whether voluntary or by inactivity.
Who owns what code and docs: OWNERS and OWNERS_ALIASES files in sub-projects (links are for pipeline). The pipeline project also has a topical ownership document.
Meeting recordings: All recordings are stored in a shared drive. The drive is shared with members of the tekton-dev and tekton-users groups, which are open for anyone to join, no process or approval required
Governance Evolution
The governance has evolved over time, here are some changes that happened:
Any specific aspects of your governance structure are you seeking feedback on?
Nothing specifically.
Do you have any concerns or specific areas where you feel your governance could be improved?
No response
Additional notes and resources
The reason for this governance review request is "CNCF Incubation acceptance application".
Tekton application on the TOC repo: https://github.com/cncf/toc/issues/1310
aliok
commented
2 months ago
Project Name
Tekton
Project Website
https://tekton.dev
Contact Details 1
@afrittoli
Contact Details 2
@dibyom
Links to communication channels
https://github.com/tektoncd/community/blob/main/contact.md
Reason for governance review request
Other (please specify in the “Additional Notes” input at the end of this form)
Are there any sub-projects, plugins, and related?
Tekton is made of several subprojects: pipeline, triggers, cli, dashboard, operator, chains, catalog
Governance model
The Tekton Governing Board (GB) is the governing body of the Tekton open source project. It's an elected group that represents the contributors to the project, and has oversight on governance and technical matters. The Governing Board adopts a principle of maximum representation, which avoids any company representing more than 40% of the GB. The Tekton GB defines and maintains the project contributor ladder, which identifies several roles for contributors, the requirements and responsibilities of each role and how to transition between them. Tekton is made up of several sub-projects. Each sub-project either adopts the complete contributor ladder, or in some the project may adopt a simplified contributor ladder, which is done for instance by the teams that maintains the website and the CI/CD infrastructure. All communication happens in the open, working group meetings are public and recorded. The decision-making process is formalised through the "Tekton Enhancement Proposal" (TEP) process. Approvals are required by representatives of at least two different companies, to ensure vendor neutrality. More details are available in the governance documentation and the community repository.
Governance documents
CONTRIBUTING.mdfile that describes how to contribute to the project. Common contribution guidelines across all repos are documented in the community repo and linked to by sub-projects. Example: https://github.com/tektoncd/pipeline/8450e1b2f3776fcba7b9267d6590b2e5e36496ea/main/CONTRIBUTING.mdOWNERSandOWNERS_ALIASESfiles in sub-projects (links are for pipeline). The pipeline project also has a topical ownership document.Governance Execution Examples
Governance Evolution
The governance has evolved over time, here are some changes that happened:
Any specific aspects of your governance structure are you seeking feedback on?
Nothing specifically.
Do you have any concerns or specific areas where you feel your governance could be improved?
No response
Additional notes and resources
The reason for this governance review request is "CNCF Incubation acceptance application". Tekton application on the TOC repo: https://github.com/cncf/toc/issues/1310