CODEOWNERS: Track owners and followers

[Ericson2314]

Motivation for this change

Let's have our cake and eat it too?

Things done

• Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
• Built on platform(s)
  • NixOS
  • macOS
  • Linux
• Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
• Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
• Tested execution of all binary files (usually in ./result/bin/)
• Fits CONTRIBUTING.md.

---

[Profpatsch]

I recently noticed that the CODEOWNERS file is more integrated into Github than I initially thought. People can request reviews from code owners, and apparently this is actively proposed by the PR process.

[Ericson2314]

@Profpatsch I believe the reviews are requested unconditionally. edit nope, the names just appear by default.

[NeQuissimus]

I am bit concerned with the maintainability of the indentation.

Is it possible to list paths twice? i.e.

=== Owners ===
lib/* @User1 @User2

===Followers===
lib/* @User3 @User4 @User5

[FRidh]

@NeQuissimus
From the example at https://help.github.com/articles/about-codeowners/

# Order is important; the last matching pattern takes the most
# precedence. When someone opens a pull request that only
# modifies JS files, only @js-owner and not the global
# owner(s) will be requested for a review.
*.js    @js-owner

[NeQuissimus]

That is unfortunate...

[Ericson2314]

NixOS/rfcs#19 however it lands will obsolete this.