Now that the Go wiki content has moved to Gerrit (#61940), the cloud functions we've setup to mail wiki edits to golang-wikichanges are most likely obsolete.

In particular, this mailing list was created because there was no other way to subscribe to wiki changes, and there was no review process at all. Neither of those are true now: it's possible to subscribe to all changes using Gerrit's notification mechanism, and wiki edits use wiki-approvers for access rather than being world-editable.

This is the tracking issue to confirm and clean up accordingly.

CC @ianlancetaylor, @rsc.

Comment From: dmitshur

Discussed this with Ian. We concluded this machinery is indeed fine to remove, and then archive the golang-wikichanges mailing list. Moving to NeedsFix.

Comment From: gopherbot

Change https://go.dev/cl/600997 mentions this issue: cloudfns/{sendwikidiff,wikiwebhook}: delete

Comment From: dmitshur

For posterity and in case we need to restore this or setup something similar in the future:

  • deleted a webhook sending "Wiki" events only to https://us-central1-symbolic-datum-552.cloudfunctions.net/GitHubWikiChangeWebHook (in application/json form, with SSL)
  • also deleted a webhook sending "Issues" events to https://us-central1-symbolic-datum-552.cloudfunctions.net/GitHubIssueChangeWebHook; this was a leftover from issueswebhook deleted in CL 396477
  • both had no recent deliveries, as expected
  • deleted both GitHubWikiChangeWebHook and HandleWikiChangePubSub deployed cloud functions
  • both had no invocations in last 30 days, as expected
  • they were still deployed using the now-deprecated 1st gen cloud function environment and Go 1.20 runtime, which was sufficient until their deletion
  • deleted the github.webhooks.golang.go.wiki Pub/Sub topic used to connect the two cloud functions
  • no messages in last 30 days, as expected
  • CL 600997 deletes the cloud function code from x/build
  • removed posting permission for the account used by WikiDiffBot and updated golang-wikichanges description to note that it is obsolete
  • this seems roughly as close to archiving it as we can get short of fully deleting it