Single source of truth for the established community teams

[thufschmitt]

Is your feature request related to a problem? Please describe.

The “teams” in the community can be described both on the website (sometimes), in GitHub teams, or in ad-hoc places. These can (and do) obviously drift out of sync. It makes it impossible to really know who belongs to which team. People who want to establish and advertise new working groups and teams also can't know where and how to do it, etc.

Describe the solution you'd like

Have a single source of truth (ideally a file somewhere in a GitHub repository) which can be used as the canonical place for defining the existing teams, their members, their communication channels, and so on.
That source of truth can then be used to populate the relevant places where it needs to be reflected (GitHub teams and the website in particular).

Describe alternatives you've considered

Enforce a manual synchronisation. But this is probably not workable in the long run.

Additional context

(Probably) blocked by #310
Relates to NixOS/foundation#21

[zimbatm]

Good idea. This is sorely needed. Especially for newcomers, it makes it unnecessarily hard for them to navigate the ecosystem.

I don't know if we can map all the teams using #310 because, for example, the nixpkgs-maintainers team is getting auto-populated from nixpkgs' maintainers.nix file. We might want to do the same for nixpkgs teams at some point. So I see #310 as the over-arching tool, and then, we might have dedicated tools per project.

For the website, I would suggest querying and extracting the information from the GitHub teams. That way those two automatically stay in sync. This is something more of the purview of the @NixOS/marketing-team .

[thufschmitt]

the nixpkgs-maintainers team is getting auto-populated from nixpkgs' maintainers.nix file

Oh, is it? I didn't know. Do you have the pointer to where it's defined and the code that populates it, that would be nice to look at.

For the website, I would suggest querying and extracting the information from the GitHub teams

The website will probably need more than just a list of GitHub handles (stuff like names, discourse handles, maybe emails, …). But we can probably find something

[garbas]

With the recent work on the website we'll be able to more easily inject the list of team members wherever they are stored.

[zimbatm]

Oh, is it? I didn't know. Do you have the pointer to where it's defined and the code that populates it, that would be nice to look at.

See https://github.com/NixOS/rfc39

[thufschmitt]

Oh, is it? I didn't know. Do you have the pointer to where it's defined and the code that populates it, that would be nice to look at.

See https://github.com/NixOS/rfc39

Aaah thanks. I mistook it for the nixpkgs-architecture team, my bad