Go through the projects in istio/ecosystem

[craigbox]

With Istio becoming part of the CNCF, we need to go through istio/ecosystem, and for each repository:

• archive it, if now irrelevant
• confirm it's currently part of the Istio project, or
• move it to its own org, if it doesn't wish to become, or doesn't qualify to be, part of the Istio project in the CNCF.

[howardjohn]

Is there anything similar to SIGS we can do? I don't think we want to move ~anything under the "istio" org since that has some implication of support

…

On Wed, Sep 28, 2022 at 6:10 PM craigbox ***@***.***> wrote: With Istio becoming part of the CNCF, we need to go through istio/ecosystem, and for each repository: - archive it, if now irrelevant - confirm it's currently part of the Istio project, or - move it to its own org, if it doesn't wish to become, or doesn't qualify to be, part of the Istio project in the CNCF. — Reply to this email directly, view it on GitHub <#805>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEYGXKIAFLOHSS2ELVUIMLWATUAPANCNFSM6AAAAAAQYJI6A4> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[craigbox]

Yes, istio-ecosystem will remain like the kubernetes-sigs repo, but we have to check the licensing of anything being brought on board, and we have to consider if Admiral wants to have its own identity.