lib.teams.llvm: create

[sternenseemann]

As a first stop towards getting a bit more organized for #171047, add a maintainer team and add myself and John Ericson as new members.

A second step could be creating a github team additionally.

cc @Ericson2314 @primeos @dtzWill @lovek323 @7c6f434c. LMK if anyone wants out.

@inclyc if you want to join, you'd need to do so in a follow up PR, as you have no entry in lib.maintainers yet, so it is difficult for me to include you.

Description of changes

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 23.05 Release Notes (or backporting 22.11 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
  • (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes
• Fits CONTRIBUTING.md.

[inclyc]

if you want to join, you'd need to do so in a follow up PR, as you have no entry in lib.maintainers yet, so it is difficult for me to include you.

That's fine, I'm not weigh enough at this area.

A second step could be creating a github team additionally.

If there are LLVM-related issues, I hope to subscribe to them. After I am familiar enough in this area, I will submit a PR application to become a maintainer.

[7c6f434c]

I so sometimes merge things in the intersection of very unlikely to break stuff, no feedback from people who are actually competent, clear benefit; but I am not really up to date to what happens with LLVM or LLVM packaging, so maybe it's better to drop me.

ETA w/o spamming: Thanks!

[sternenseemann]

@7c6f434c done!

[primeos]

Thanks a lot @sternenseemann and @Ericson2314 (also in general for your work on LLVM) and sorry for my late reply.
Definitely a +1 from me - this feels long overdue :)

I'll likely remove myself from the team after a while as I do currently lack the time to work on LLVM and don't have much to contribute to discussions but I'm still keeping a bit of an eye on LLVM changes/notifications (due to the importance for Chromium).

[github-actions]

Successfully created backport PR for release-22.11:

• [Backport release-22.11] lib.teams.llvm: create #213093