Add initial code owners configuration

[swissspidy]

Moving checks into separate folders per category makes it easy to set up code owners.

Feel free to submit suggestions to the CODEOWNERS file if you like to be included/excluded.

See #448

[joemcgill]

I think this is a great idea. To make management easier, we could consider assigning teams like @WordPress/performance-admins to the Performance section. Not sure if other community teams have similar groups that could be used.

Some practical questions/concerns:

1. This should include a changelog entry, since several namespaces are changing.
2. There a chance that someone is already extending this plugin with their own custom checks. Do we need to be concerned about adding backcompat support for the previous names, or is adding documentation to the release notes enough?

[swissspidy]

We can create new teams for each category or something if we want, e.g. @WordPress/plugin-check-plugins-team, @WordPress/plugin-check-performance. Don't want to use that existing team though, as it includes too many people who aren't contributing this plugin and would just unnecessarily get pinged because of it (like right now :)).

(Edit: also keep in mind mentioning/assigning teams doesn't work for people not in the org or when logged out of GitHub)

Not worried about back compat, a changelog entry should be enough.

[mukeshpanchal27]

Thanks, @swissspidy, for the PR. Overall, it looks good to me. I've left one nit-pick and a couple of questions:

• Who is responsible for the other checks and other infrastructure-related files?
• The documentation at https://github.com/WordPress/plugin-check/tree/trunk/docs should be updated to reflect the new changes related to checks.

[swissspidy]

Who is responsible for the other checks and other infrastructure-related files?

Everyone and no one :) Something we can define as we go. Suggestions welcome if you think we should define all of that already.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: swissspidy <[email protected]>
Co-authored-by: joemcgill <[email protected]>
Co-authored-by: westonruter <[email protected]>
Co-authored-by: mukeshpanchal27 <[email protected]>
Co-authored-by: adamsilverstein <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[adamsilverstein]

Looks great and this will let individual teams iterate more rapidly. +1.