WG Naming Dissolution

[Stephen Augustus]

Hello all,

You are receiving this email because you are a member of one of WG Naming's stakeholder SIGs (or you are a member of Steering). We are writing to inform you that the leads of WG Naming (Stephen Augustus, Celeste Horgan, Jaice Singer DuMars) would like to dissolve the WG.

The work we started in WG Naming (and continue in Inclusive Naming Initiative) meets the goals stated in our charter. Our dissolution criteria are mostly met, with two exceptions:

1. A timeline on which to replace component names in the kubernetes/kubernetes codebase:

1. While developing the recommendations workflow, it was decided that once a recommendation was accepted and recorded, areas in scope would become responsible for implementation.

2. Defined long-term ownership of the policies and processes this WG creates:

1. It is our sentiment that long-term ownership of language replacement and evaluation within the project lies as a shared responsibility between the groups on this email.

For the sponsoring governance groups, we’re requesting feedback on:

1. Any additional next steps that you would like us to consider

2. A clear understanding of future ownership for language evaluation/replacement (SIG ContribEx? SIG Docs? SIG Arch?)

Thank you,

Celeste Horgan

Stephen Augustus

Jaice Singer DuMars

[Stephen Augustus]

I think it's reasonable for Release Managers (SIG Release / RelEng) to take this one, since we'll want to coordinate around lulls in the release cycle.

-- Stephen

On Mon, Jul 12, 2021, 18:48 Josh Berkus <jbe...@redhat.com> wrote:

On 7/12/21 3:16 PM, Stephen Augustus wrote:
> #

>
> A timeline on which to replace component names in the
> kubernetes/kubernetes codebase:
>

>  1.
>
>     While developing the recommendations workflow
>     <https://github.com/kubernetes/community/blob/master/wg-naming/workflow.md#implementation>,

>     it was decided that once a recommendation was accepted and recorded,
>     areas in scope would become responsible for implementation.
>

Who should own renaming the master branch in K/K?  Infra WG?

--
-- Josh Berkus
    Kubernetes Community Architect
    OSPO, OCTO

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-contribex" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-con...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-contribex/c5ca0335-f39b-0d1f-3d87-c71baa458158%40redhat.com.

[Celeste Horgan]

Hi all,

Do you need anything else from Stephen or myself to move this forward?

Cheers,

Celeste Horgan

You received this message because you are subscribed to the Google Groups "kubernetes-sig-docs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-docs/CAOqU-DQ4GqRf-6rgCVjfyw%2B1mQOW%3Dyafqztp3j_142_tevJ-Ow%40mail.gmail.com.

--

---

Celeste Horgan

Senior Technical Writer, CNCF

Time Zone: PST/Vancouver

[Bob Killen]

Hey folks,

Following up from today's Steering Meeting, there are a few items that should be kicked off as part of turning down the working group.

- The docs and process for the language evaluation framework should be moved over to sig-arch for long-term stewardship, Jordan will follow up with updating the API convention docs to reference it going forward

- Issues should be created for any follow up items - e.g. the tracking issue for master -> main, specifically for k/k a comment there stating sig-release's volunteer ownership or a separate issue linking back would be good

- I'll reach out separately to help spin the other various stuff down (mailing list etc)

With that, just wanted to say thanks for all your leadership in this space <3 It's been great to see the evolution of the group :)

- Bob

On Mon, Aug 2, 2021 at 11:47 AM 'Jordan Liggitt' via steering <stee...@kubernetes.io> wrote:

Apologies for the slow response... I've added this to the agenda for today's steering meeting, will circle back this afternoon

You received this message because you are subscribed to the Google Groups "kubernetes-sig-architecture" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-arch...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-architecture/CAEeQiMXNj%3DQOiKFx_H315zep-ub6GW%2Bqh%2BjA0Y58NttbKLhB7A%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "steering" group.
To unsubscribe from this group and stop receiving emails from it, send an email to steering+u...@kubernetes.io.
To view this discussion on the web visit https://groups.google.com/a/kubernetes.io/d/msgid/steering/CAMBP-pJqjweFUuy4z3W2EOcciVMzorZdbEB9bqnrL-_qTFj1mQ%40mail.gmail.com.

[Celeste Horgan]

Thanks for the follow-up, y'all!

We'll get on it :)

Celeste