👥 Please add CoC WG to CODEOWNERS file

[jefftriplett]

This is partially in response to the change in #1808, which is a good change, but it brings up the point that the CoC WG should be given a heads-up on all enforcement or CoC changes, big and small. The easiest way to make this maintainable for everyone would be to add our GitHub Group to a CODEOWNERS file.

I looked for our CODEOWNERS and didn't see one, so this is also a good excuse to create a CODEOWNERS if anyone else thinks this is a good idea. (or maybe I missed it)

[bmispelon]

That's neat, I didn't know about CODEOWNERS. This seems like a good technical solution for this.

A few questions before the PR can be made:

1. What's the name of the github org that should be notified?
2. Should we set up the project to require a review by the CoC WG, or is a notification enough (I believe that's the default)
3. Which paths should be monitored? Initially I thought of djangoproject/templates/conduct/*, is there anything else?

[jefftriplett]

Testing @django/coc-committee to see if everyone gets the bat signal.

[jefftriplett]

#1 - should work with @django/coc-committee
#2 - a notification is 💯
#3 - what you just proposed is a great start. We can update it if more pop up.
#4 - 🙏

[thibaudcolas]

👋 code owners sounds great to me, if we want the CoC WG to be involved in all changes we should also update Django Code of Conduct - Changes, particularly:

changes that don't affect the intent (typo fixes, re-wordings, etc.) can be made immediately

Something like:

changes that don't affect the intent (typo fixes, re-wordings, etc.) only require confirmation from the conduct committee.