Join the Technical Steering Committee¶
The term “Technical Steering Committee” (TSC) describes the group of Kedro maintainers.
The TSC is responsible for the project’s future development; you can read about our duties in our Technical Charter. We accept new members into the TSC to fuel Kedro’s continued development. We list Kedro’s current and past maintainers on GitHub.
In this section, we describe:
Responsibilities of a maintainer¶
Be available for at least one full day per week to help with product development
Attend community meetings to discuss the project plans and roadmap
Be proactive about project maintenance including security, updates, CI/CD, builds and infrastructure
Prioritise the work following the product roadmap to move the project forward
Make sure that ongoing pull requests are moving forward at the right pace or closing them
Guide the community to use the right channel:
GitHub issues for feature requests and bug reports
GitHub discussions to discuss the future of the Kedro project
Slack for questions and to support other users
Requirements to become a maintainer¶
Just contributing does not make you a maintainer; you need to demonstrate commitment to Kedro’s long-term success by working with existing maintainers for a period of time.
We look for commitment markers with the following:
Being able to write solid code and collaborate with the team and community
Understanding the project’s code base and internals
Doing pull requests from our backlog or roadmap; maintainers need to work towards a common goal
Learning how the team works, including processes for testing, quality standards and code review
Evidence of already having started pull requests and code reviews under the guidance of maintainers; including asking for help where needed
Showing excitement about the future of Kedro
Building a collaborative relationship with the existing team
Quarterly, existing maintainers will curate a list of contributors that have shown regular activity on the project over the prior months and want to become maintainers. From this list, maintainer candidates are selected and proposed for a vote.
Following a successful vote, candidates are added to the
kedro-developers team on the Kedro GitHub organisation
kedro-team channel on the Kedro Slack organisation.
Voting can change project maintainers and decide on the future of Kedro. The TSC leads it as voting maintainers of Kedro. The voting period is one week and is either performed on GitHub discussions or through a pull request.
Other issues or proposals¶
GitHub discussions is used to host votes on issues, proposals and changes affecting the future of Kedro, including amendments to our ways of working described on this page. These votes require a 1/2 majority.
Adding or removing maintainers¶
The decision to add or remove a maintainer is made based on TSC members votes in that pull request. Additions and removals of maintainers require a 2/3 majority.
The act of adding or removing maintainers onto the list requires a pull request against Kedro’s README.md file.