-
Notifications
You must be signed in to change notification settings - Fork 926
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Affiliation of Kedro TSC members is not clear #3039
Comments
Sort of agree but I also like the flat equality of our alphabetical list. I guess it was obvious in the early days because we were all QB but maybe as time goes by there's more of a need to show this. I don't particularly like assigning focal areas though, but WDYT? |
I think alphabetical + organization (no need for focal areas) would work? |
Yeah the Delta was just an example, I don't think we need focal areas either |
For future reference, #3046 (comment) some discussion about how to structure this. |
This is now done. |
Description
Kedro prouds itself on being a Linux Foundation AI & Data multi-stakeholder project, but the question of who those stakeholders are is difficult to answer by looking at our current docs or website.
Expected Result
Something similar to what Delta Lake does: https://delta.io/community/
Actual Result
https://docs.kedro.org/en/stable/contribution/technical_steering_committee.html#kedro-maintainers
The text was updated successfully, but these errors were encountered: