[ML Migration] Post migration: kdev mailing list

[parispittman]

Umbrella #5877

Things to do once the group has been created.

1. run a cs.k8s.io on k-dev@ and kubernetes-dev@ and change all respective instances to dev@kubernetes.io (https://groups.google.com/a/kubernetes.io/group/dev)
   1.5 also google it to see what comes up and make the changes to the front page search results
   -pull for community repo Changed all instances of k-dev@ and kubernetes-dev@ to dev@kubernetes.io #6311
   -need to look at all repos
   -need to look at google search results

2. have leads change all docs starting most notably with meeting invites and any open work collaboration docs
   -have leads also check that contributors@ is the owner
   -if contributor@ is already an owner, we can help add to docs

3. Forward any active conversations to the new list

what else?

[parispittman]

/sig contributor-experience

[jberkus]

2. is going to be a HUGE effort. Don't forget that many, many docs don't belong to current leads. We need to treat that task as the major, months-long effort that it will be; we need a team in charge of it.

[jberkus]

Also:

What about ownership of calendar items?

[parispittman]

@jberkus calendar invites should be owned by the SIGs shared calendar for events https://github.com/kubernetes/community/blob/master/communication/calendar-guidelines.md#establishing-a-new-meeting

and then shared with contributors@ with full access to change

[parispittman]

/help-wanted

[parispittman]

/help

[k8s-ci-robot]

@parispittman:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[parispittman]

/good-first-issue

[k8s-ci-robot]

@parispittman:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[chetak123]

Hey @parispittman I have changed all instances of k-dev@ and kubernetes-dev@ to dev@kubernetes.io in Kubernetes/community. If this is ok then I will start changing in other repositories
Thanks.

[chetak123]

/assign @chetak123

[mrbobbytables]

@parispittman I think this is safe to close now? Are there any follow up AIs?

[parispittman]

@mrbobbytables - need to audit #2 for meeting agendas at the very least but then I'll close

[parispittman]

we are officially good with this!! 🚀