Merge Issues in a centralized place?

[shinebayar-g]

cdk8s has many repositories. For easier visibility and usability, could we close Issues tab on sub repositories and manage them here? Because from the end user perspective it's just cdk8s and it's not clear to which repository they should check and search for issues or submit them. By default, they come here, but there are some good discussions going on sub repos. It feels like things are all over the place between these repos.
https://github.com/cdk8s-team/cdk8s/issues
https://github.com/cdk8s-team/cdk8s-core/issues
https://github.com/cdk8s-team/cdk8s-cli/issues
Maintainers could apply appropriate labels to distinguish them when necessary.

[iliapolo]

@shinebayar-g apologies for the long delay in responding to this. But I'm actually open to the idea and wanted to bring it up for discussion with the team and in our slack channel.

Are you still interested in this?

[shinebayar-g]

No worries, it's just a suggestion. I think it would make yours/maintainers' life easier, win/win for everyone.

[iliapolo]

I actually like the idea. Lets see what folks think of this. I'll reach out on slack.

[shinebayar-g]

Hey @iliapolo , I remember the poll was voted "yes" for the majority. Could you please reconsider this suggestion?
You could tag issues with the appropriate labels in the cdk8s-team/cdk8s repo like cli or component:cli etc..
It's getting tricky to keep track of all the reported issues across multiple repositories.

[iliapolo]

@shinebayar-g Done.

[shinebayar-g]

Awesome. That's very nice you were able to link to the https://github.com/cdk8s-team/cdk8s/issues/new/choose

I noticed that GitHub Community Support option could be linked to the cdk8s-team/cdk8s repository as well. What do you think?