SIG Node: complete migration to kubernetes.io mailing lists

[SergeyKanzhelev]

This issue outlines action items needed to migrate SIG Node mailing lists to kubernetes.io.

/sig node
/cc @kubernetes/sig-node-leads
/assign

Context

• Existing SIG Node mailing lists:
  • https://groups.google.com/g/kubernetes-sig-node
  • https://groups.google.com/g/kubernetes-sig-node-test-failures
• New mailing lists:
  • https://github.com/kubernetes/k8s.io/blob/main/groups/sig-node/groups.yaml
• Example notification: https://groups.google.com/a/kubernetes.io/g/sig-apps/c/GeL5shs1nRY/m/9Lybuv8lAQAJ?utm_medium=email&utm_source=footer
• Instructions: https://kubernetes.slack.com/archives/CD6LAC15M/p1732010989229329?thread_ts=1731973436.629349&cid=CD6LAC15M

Action items

1. Migrate users to the new mailing list (from Slack):
   1. SIG exports mailing list as CSV
   2. Import mailing list a google sheet
   3. filter columns and delete all rows that have a bounce status
   4. filter columns and remove anyone that has the OWNER role (they'll have that already)
   5. create new sheet (new tab) - add these columns
      Group Email [Required] Member Email Member Type Member Role
   6. copy email column from exported list to the Member Email column
   7. For every row the group email should be the name of the mailing list e.g. sig-cluster-lifecycle@kubernetes.io, Member Type should be USER Member Role should be MEMBER
   8. Save this as a csv
   9. here steering should import the prepared CSV
   10. remove calendar@kubernetes.io from old list (this will prevent duplicate events appearing on the calendar)
2. Update google docs with the new mailing list links and permissions
   1. sig-node weekly meeting
   2. Kubernetes SIG-Node CI subgroup notes
3. Update mailing lists referenced from test-infra repository for test failure notifications
4. Update all calendar events to invite new mailing list
5. update sigs.yaml and other mentions: https://github.com/search?type=code&q=kubernetes-sig-node%40googlegroups.com+org%3Akubernetes
6. send comms to mailing list with notification of new list, lock the list, prevent new members from joining or sending email.

[SergeyKanzhelev]

@kubernetes/steering-committee I have two mailing list that needs to be migrated. Can someone help to import CSVs?

[pacoxu]

Maciej will help in this case.

[soltysh]

Maciej will help in this case.

This was already handled offline :)

[SergeyKanzhelev]

Started replacing old mentions from this repository.

Still a lot of mentions across other repos:

• https://github.com/search?q=org%3Akubernetes-sigs+kubernetes-sig-node&type=code
• https://github.com/search?q=org%3Akubernetes+kubernetes-sig-node&type=code&p=1

[SergeyKanzhelev]

I think I covered all mentions of this group which are in active pages, repositories, and code.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale