Move TSC into docs (#2491)

README.md

@@ -72,7 +72,7 @@ Kedro is built upon our collective best-practice (and mistakes) trying to delive
 
 ## The humans behind Kedro
 
-The [Kedro product team](https://docs.kedro.org/en/stable/faq/faq.html#who-maintains-kedro) and a number of [open source contributors from across the world](https://github.com/kedro-org/kedro/releases) maintain Kedro.
+The [Kedro product team](https://docs.kedro.org/en/stable/contribution/technical_steering_committee.html#kedro-maintainers) and a number of [open source contributors from across the world](https://github.com/kedro-org/kedro/releases) maintain Kedro.
 
 
 ## Can I contribute?

docs/source/contribution/technical_steering_committee.md

@@ -1,13 +1,16 @@
 # Join the Technical Steering Committee
 
-The term "Technical Steering Committee" (TSC) describes the group of Kedro maintainers.
+In the Kedro project's latest iteration it is an incubating project within [LF AI & Data](https://lfaidata.foundation/).
 
-The TSC is responsible for the project's future development; you can read about our duties in our [Technical Charter](https://github.com/kedro-org/kedro/blob/main/kedro_technical_charter.pdf). We accept new members into the TSC to fuel Kedro's continued development. We list [Kedro's current and past maintainers](https://github.com/kedro-org/kedro/blob/main/README.md#the-humans-behind-kedro) on GitHub.
+The term "Technical Steering Committee" (TSC) describes the group of Kedro maintainers. We list [Kedro's current and past maintainers](#kedro-maintainers) on this page.
 
-In this section, we describe:
+The TSC is responsible for the project's future development; you can read about our duties in our [Technical Charter](https://github.com/kedro-org/kedro/blob/main/kedro_technical_charter.pdf). We are happy to accept new members into the TSC to fuel Kedro's continued development.
+
+On this page we describe:
 
 - [Responsibilities of a maintainer](#responsibilities-of-a-maintainer)
 - [Requirements to become a maintainer](#requirements-to-become-a-maintainer)
+- [Kedro maintainers](#kedro-maintainers)
 - [Application process](#application-process)
 - [Voting process](#voting-process)
 
@@ -22,8 +25,8 @@ In this section, we describe:
 
 ### Community management
 
-- Make sure that ongoing pull requests are moving forward at the right pace or closing them
-- Guide the community to use the right channel:
+- Ensure that ongoing pull requests are moving forward at the right pace or closing them
+- Guide the community to use our various communication channels:
 
   - [GitHub issues](https://github.com/kedro-org/kedro/issues) for feature requests and bug reports
   - [GitHub discussions](https://github.com/kedro-org/kedro/discussions) to discuss the future of the Kedro project
@@ -34,34 +37,85 @@ In this section, we describe:
 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:
+We look for commitment markers who can do 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
+- Write high-quality code and collaborate with the team and community
+- Understand the project's code base and internals
+- Make pull requests from our backlog or roadmap; maintainers need to work towards a common goal
+- Learn how the team works, including processes for testing, quality standards and code review
+- Show 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
+- Show excitement about the future of Kedro
+- Build a collaborative relationship with the existing team
+
+## Kedro maintainers
+
+<!-- DO NOT EDIT THIS AND MERGE A PR WITHOUT A VOTE TO SIGN OFF ANY CHANGES -->
+
+Kedro was originally designed by [Aris Valtazanos](https://github.com/arisvqb) and [Nikolaos Tsaousis](https://github.com/tsanikgr) at QuantumBlack to solve challenges they faced in their project work. Their work was later turned into an internal product by [Peteris Erins](https://github.com/Pet3ris), [Ivan Danov](https://github.com/idanov), [Nikolaos Kaltsas](https://github.com/nikos-kal), [Meisam Emamjome](https://github.com/misamae) and [Nikolaos Tsaousis](https://github.com/tsanikgr).
+
+
+Currently, the core Kedro team consists of:
+
+[Ahdra Merali](https://github.com/AhdraMeraliQB),
+[Andrew Mackay](https://github.com/Mackay031),
+[Ankita Katiyar](https://github.com/ankatiyar),
+[Antony Milne](https://github.com/AntonyMilneQB),
+[Deepyaman Datta](https://github.com/deepyaman),
+[Huong Nguyen](https://github.com/Huongg),
+[Ivan Danov](https://github.com/idanov),
+[Jannic Holzer](https://github.com/jmholzer),
+[Jo Stichbury](https://github.com/stichbury),
+[Joel Schwarzmann](https://github.com/datajoely),
+[Juan Luis Cano](https://github.com/astrojuanlu),
+[Merel Theisen](https://github.com/merelcht),
+[Nero Okwa](https://github.com/NeroOkwa),
+[Nok Lam Chan](https://github.com/noklam),
+[Rashida Kanchwala](https://github.com/rashidakanchwala),
+[Sajid Alam](https://github.com/SajidAlamQB),
+[Stephanie Kaiser](https://github.com/stephkaiser),
+[Tynan DeBold](https://github.com/tynandebold) and
+[Yetunde Dada](https://github.com/yetudada).
+
+Former core team members with significant contributions include:
+
+[Andrii Ivaniuk](https://github.com/andrii-ivaniuk),
+[Anton Kirilenko](https://github.com/Flid),
+[Cvetanka Nechevska](https://github.com/cvetankanechevska),
+[Dmitrii Deriabin](https://github.com/dmder),
+[Gabriel Comym](https://github.com/comym),
+[Gordon Wrigley](https://github.com/tolomea),
+[Hamza Oza](https://github.com/hamzaoza),
+[Ignacio Paricio](https://github.com/ignacioparicio),
+[Jiri Klein](https://github.com/jiriklein),
+[Kiyohito Kunii](https://github.com/921kiyo),
+[Laís Carvalho](https://github.com/laisbsc),
+[Liam Brummitt](https://github.com/bru5),
+[Lim Hoang](https://github.com/limdauto),
+[Lorena Bălan](https://github.com/lorenabalan),
+[Nasef Khan](https://github.com/nakhan98),
+[Richard Westenra](https://github.com/richardwestenra),
+[Susanna Wong](https://github.com/studioswong) and
+[Zain Patel](https://github.com/mzjp2).
+
 
 ## Application process
 
-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.
+Every quarter year, existing maintainers will collect 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
-and the `kedro-team` channel on the Kedro Slack organisation.
+and the `kedro-team` channel on the Kedro Slack organisation, and listed as [Kedro maintainers](#kedro-maintainers).
 
 ## Voting process
 
-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.
+Voting can change project maintainers and decide on the future of Kedro. The TSC leads the process as voting maintainers of Kedro. The voting period is one week and via a GitHub discussion 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**.
+[Kedro's GitHub discussions](https://github.com/kedro-org/kedro/discussions) section 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](https://github.com/kedro-org/kedro/blob/main/README.md#the-humans-behind-kedro).
+The act of adding or removing maintainers onto the list requires a pull request against the [Kedro maintainers section of this page](#kedro-maintainers).