Add initial CODEOWNERS with me

[thejcannon]

Looking for sign-off on the idea and the preamble.

If you want your name on the file itself, let me know. You can open a follow-up PR as well.

[thejcannon]

There's also https://github.com/gagoar/codeowners-generator if y'all wanna go that route.

[benjyw]

Maybe this should be in the root, where it's more obvious (github supports this).

It's too bad there can't be local CODEOWNERS that override the values for the dirs they're in. But I bet they will add this some time.

[thejcannon]

It's too bad there can't be local CODEOWNERS that override the values for the dirs they're in.

Have you seen https://github.com/gagoar/codeowners-generator?

[benjyw]

Interesting, although probably overkill for us for now. I'd just move it to the repo root though.

[kaos]

Not familiar with CODEOWNERS in particular, but this looks interesting.

[thejcannon]

If it's all the same, I prefer this location because I dislike the proliferation of root-level files

[thejcannon]

Merged. I hope to see more PRs come in as people claim more sections of the repo 🎉

[benjyw]

Up to you, but FWIW I disagree: this is exactly the kind of file we should want at the root level.

[thejcannon]

Can you elaborate, I'm missing the "why"

[benjyw]

Because .github is an obscure hidden directory, and I will not think to look in it for anything. But it's fine this way too, if it becomes a problem we can move it in the future.

[thejcannon]

Does someone normally go sniffing in CODEOWNERS files for info?

I like this isolated in .github because it is 100% a GitHub-only feature

[benjyw]

I dunno, TBH, I've never used CODEOWNERS before. But I imagine it could be useful to manually figure out who owns a piece of code, e.g., who to ask questions. But then maybe this is more useful with codeowners-generator source files than with this regex-based thing.

[kaos]

I dunno, TBH, I've never used CODEOWNERS before. But I imagine it could be useful to manually figure out who owns a piece of code, e.g., who to ask questions. But then maybe this is more useful with codeowners-generator source files than with this regex-based thing.

I have no hard preference either way here, but for this particular point I think a sensible answer would be to reach out on Slack #development possibly tagging someone, but open for anyone to jump in as well. Need more than that there's also git blame.

I consider this file to be for tooling, and if you want to consume it for other purposes that's fine too, but doesn't make sense to influence its life over (to me).