Update CoC report contacts

[johnzhou721]

Describe the bug

The newly updated CoC reporting contacts located at "Reporting an Issue" in https://beeware.org/community/behavior/code-of-conduct/ does not match the gutter at https://beeware.org/community/behavior/making-a-coc-report/

Steps to reproduce

Go to https://beeware.org/community/behavior/making-a-coc-report/

Expected behavior

Matching contacts, with https://beeware.org/community/behavior/making-a-coc-report/ updated

Screenshots

No response

Environment

Irrelevant

Logs

Additional context

No response

[mhsmith]

If this requires the code of conduct to be updated again, may I suggest that instead of creating another 25 PRs to copy the content to every repository, we just replace all of those locations with a link to the canonical location on the website, so they'll never need to be updated again?

[freakboy3742]

The decision to duplicate was deliberate, based on a conversation with @kattni.

The idea behind copying is that CoC is similar to a license, in that it's a foundational document that needs to be completely unambiguous. There's also the issue of people not following links.

The CoC hasn't been updated for almost 10 years; and won't see frequent updates, so I'm not overly concerned about "25 PR churn".

In the case of this specific issue, it's the website content that needs to be updated, because it's not being automatically updated by the rollout (because the structure on the current website doesn't really match the new CoC content. That will be addressed by the website rebuild that Kattni is currently working on. A short term fix to the contact list is definitely called for, though.

[mhsmith]

Since we're talking about an update for another reason (beeware/.github#293), can we make this update the last one that needs to be multiplied by 25? A file containing nothing but a link is already unambiguous, and if someone chooses not to follow it, that's their problem.

[freakboy3742]

The update being discussed on beeware/.github#293 is twofold - a re-rollout because the previous rollout script inadvertently had a 30 repo cap (and we have something like 40 active repos); and a minor formatting cleanup to keep rumdl happy. We (and have) worked around the latter in the website rebuild, but given a re-rollout is needed because of the missing repos, it makes sense to fix the other problem while we're at it.

The intention is that this will be the last update we'll need to make for a while.

As for "if someone chooses not to follow it, that's their problem" - that's not entirely true. It's also our problem, because we may have people in our community who are unaware of our expectations.

License text is also duplicated across every repo, specifically to avoid any ambiguity. The CoC is in a similar category to LICENSE IMHO.

[freakboy3742]

This has been resolved by the move to the new MkDocs site.