kubernetes / community

Kubernetes community content
Apache License 2.0
11.9k stars 5.15k forks source link

Mailing list migration tool #7009

Closed cblecker closed 1 year ago

cblecker commented 1 year ago

Describe the issue

SIGs that wish to migrate their mailing list need a way to do so in an automated way.

The groups tool (https://git.k8s.io/k8s.io/groups) can sort of do this, but it requires the entire mailing list's membership to be published in git. It's also easily rate limited when doing the number of calls required.

I had previously hacked up a version of this tool to migrate the kubernetes dev mailing list, but it was fragile, hacky, and only functioned on my local system. We really need a safer, fully functional tool to be able to do this en masse.

cblecker commented 1 year ago

cc @mrbobbytables @jberkus @nikhita @detiber @Priyankasaggu11929 @MadhavJivrajani

detiber commented 1 year ago

/assign

detiber commented 1 year ago

/milestone v1.27

k8s-ci-robot commented 1 year ago

@detiber: You must be a member of the kubernetes/community-milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Community Milestone Maintainers and have them propose you as an additional delegate for this responsibility.

In response to [this](https://github.com/kubernetes/community/issues/7009#issuecomment-1359664064): >/milestone v1.27 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
mrbobbytables commented 1 year ago

/milestone v1.27

detiber commented 1 year ago

/area community-management

k8s-triage-robot commented 1 year ago

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

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

You can:

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

/lifecycle stale

detiber commented 1 year ago

/remove-lifecycle stale

k8s-triage-robot commented 1 year ago

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

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

You can:

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

/lifecycle stale

k8s-triage-robot commented 1 year ago

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

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

You can:

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

/lifecycle rotten

nikhita commented 1 year ago

/remove-lifecycle stale

/unassign @detiber please re-assign if you have bandwidth :)

Priyankasaggu11929 commented 1 year ago

Following up from the discussion on the k8s Slack (thread) -

Earlier, we had a limitation in exporting the list of members from a mailing list, if it exceeded a certain size. However, recently, @mrbobbytables was able to do a successful export of the contribex ML members list (PSA: here) (which was not the case before, due to the above stated limitation)

Taking the migration of the SIG Contribex Mailing List as a positive test, we don't need a tool for migration atm, but will reconsider if a need arises in the future.

Closing the issue. Thanks!

/close

k8s-ci-robot commented 1 year ago

@Priyankasaggu11929: Closing this issue.

In response to [this](https://github.com/kubernetes/community/issues/7009#issuecomment-1689339857): >Following up from the discussion on the k8s Slack ([thread](https://kubernetes.slack.com/archives/C1TU9EB9S/p1689772149747609?thread_ts=1689751207.392949&cid=C1TU9EB9S)) - > >Earlier, we had a limitation in exporting the list of members from a mailing list, if it exceeded a certain size. >However, recently, @mrbobbytables was able to do a successful export of the contribex ML members list (PSA: [here](https://groups.google.com/a/kubernetes.io/g/dev/c/wETk0QU0ZSI/m/47GFK_PPAwAJ)) >(which was not the case before, due to the above stated limitation) > >Taking the migration of the SIG Contribex Mailing List as a positive test, we don't need a tool for migration atm, but will reconsider if a need arises in the future. > >Closing the issue. Thanks! > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.