SIG/WG lifecycle documents & mailing list guidelines need to be updated to reflect git.k8s.io/k8s.io and usage of kubernetes.io groups

[justaugustus]

Describe the issue

Following the approval of WG AI Gateway's creation, we (Steering) received a request from @shaneutt for guidance on mailing list creation.

Here's what I said, but our docs should reflect:

The lifecycle doc should have what you need, but let me know if you have any questions!

• https://github.com/kubernetes/community/blob/master/sig-wg-lifecycle.md#communicate
• in particular: https://github.com/kubernetes/community/blob/master/communication/mailing-list-guidelines.md#mailing-list-creation

followed by:

Hmmmm, though now that I'm looking at these, we need to update them to reflect creating groups on the kubernetes.io Google Workspace.

My suggestion here would be to clone one of the recent WG subdirs in k8s.io:

• https://github.com/kubernetes/k8s.io/tree/main/groups/wg-ai-conformance
• https://github.com/kubernetes/k8s.io/tree/main/groups/wg-ai-integration

Be sure to search/replace the relevant references in the cloned groups.yaml, OWNERS, and add the appropriate entries in OWNERS_ALIASES: https://github.com/kubernetes/k8s.io/blob/main/OWNERS_ALIASES

cc: @kaslin @mfahlandt @palnabarun @MadhavJivrajani @Priyankasaggu11929

[justaugustus]

/sig contributor-experience

[justaugustus]

/assign @mfahlandt

[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