Move under Kubernetes SIGs org?

[skl]

A thread in sig-instrumentation slack asks about moving kubernetes-mixin to the Kubernetes SIGs org, what do the current org members think about this?

@tomwilkie @metalmatze @csmarchbanks @paulfantom @brancz

[povilasv]

Sounds good to me

[skl]

FYI #1173

Many thanks to @csmarchbanks for the early contributions to the project!

[tomwilkie]

I'm 👍 on this.

[brancz]

Already commented on the slack thread, but works for me as well

[metalmatze]

I don't really care. We can move it if it makes people's life easier.

[skl]

The KEP is open for review. There's a suggestion from @TheRealNoob about doing a repo transfer rather maintaining a mirror, feedback welcome!

[rexagod]

PTAL at kubernetes/org#6129,

Please see the KEP here: kubernetes/enhancements#5906 for details. I created this because unlike migrating a personal repository, as in case of prometheus-adapter, the existing repository has already been extensively used over the years within the ecosystem, so users may want details on why the migration took place.

If that's the case, we'd be okay with deferring this request until the KEP is merged.

[skl]

So kubernetes/org#6129 talks about migrating but kubernetes/enhancements#5906 talking about mirroring.

If we migrate, we don't need to mirror because GitHub will handle all the redirects automatically and there will just be a single repo. If we mirror, we will have two repos that will need to be kept in sync.

So I think the request here is to clarify about the approach on migrating vs mirroring, as this seems inconsistent between the org issue and the KEP atm.