Closed stichbury closed 1 year ago
I think we should repurpose that repo into an "awesome-kedro" (https://github.com/sindresorhus/awesome/blob/main/awesome.md) so it has a more community-friendly structure.
To note: https://github.com/fkromer/awesome-kedro exists
Sent a second ping over https://github.com/fkromer/awesome-kedro, awaiting for response.
awesome-kedro has been archived.
Let's try to do this in the next sprint.
Sounds like a plan!
https://github.com/kedro-org/awesome-kedro
@kedro-org/kedro-admin could you please enable issues there?
And maybe even create a Advocacy
team including @yetudada, @stichbury, and I with more permissions over
(And while you're at it, could you change the YouTube link to https://www.youtube.com/@kedro-python in https://github.com/kedro-org?)
@astrojuanlu I've done three changes:
I want to archive Kedro-Community for you but I think we should let people know on the README.md that we're doing this. I also looked into creating teams with different access levels for different repos and it's not possible on our account because it's an enterprise feature.
Thanks a lot @yetudada and sorry I dragged so long on this - taking over from here.
I want to archive Kedro-Community for you but I think we should let people know on the README.md that we're doing this.
Yep, I'll make an edit to the README ahead of doing that.
I also looked into creating teams with different access levels for different repos and it's not possible on our account because it's an enterprise feature.
Interesting - isn't this what https://github.com/orgs/kedro-org/teams/kedro-developers/repositories and https://github.com/orgs/kedro-org/teams/kedro-framework/repositories do for example?
Merged this repo with awesome-kedro
at https://github.com/kedro-org/awesome-kedro/pull/1
Remaining tasks:
This is a general "housekeeping" ticket to work out how we use
kedro-community
better so it's up to date and useful.