Moving this repository to kubernetes-sigs organization

[runcom]

The kubernetes-incubator project is now deprecated. Given CRI-O is considered stable at this point, with 3 major, fully supported, releases and given the users and contributors we've gathered over time, I propose to move CRI-O under the kubernetes-sigs organization on GitHub.

@mrunalp @derekwaynecarr @rhatdan @kubernetes-incubator/maintainers-cri-o et all, what do you think?

[rhatdan]

I agree.
👍

[mrunalp]

Added this to sig-node agenda for discussion next week.

[dchen1107]

I agreed.

[derekwaynecarr]

Discussed during SIG Node call on 7/10 call, I agree this should move under kubernetes-sigs org.

[mikebrow]

Some comments:
If not there.. where?
Not sure what it means to be in "kubernetes-sigs org."
The "Org for Kubernetes SIG-related work," is a bit broad.
Would be nice if we had a sig-cri and/or a sig-container-runtimes as sig-node is also a bit broad.

[derekwaynecarr]

@mikebrow

see definition of sig sponsored repositories here:
https://github.com/kubernetes/community/blob/master/github-management/kubernetes-repositories.md#sig-repositories

[runcom]

process started here kubernetes/org#60

[runcom]

👍

[mikebrow]

see definition of sig sponsored repositories here:
https://github.com/kubernetes/community/blob/master/github-management/kubernetes-repositories.md#sig-repositories

Thx @derekwaynecarr I pushed a commit to tweak the wording then as cri-o is more a runtime project than it is a "tool."

kubernetes/community#2624

Cheers!

[mikebrow]

https://github.com/kubernetes/community/pull/2624/files merged, my question resolved :-)

[runcom]

clearly done now, thanks everyone 🎉