Requirements for a private information in the team repo

[emilyalbini]

The rust-lang/team repository stores the team structure of the project and the contact details of everyone involved with it. Members of the core team brought up that the current everything-is-public approach might not work well in the near future, for a few reasons:

• The repository contains personal information of all the team members. While most of that data can be scraped from the git repositories people contribute to, having it in a single place makes the lifes of people who want to abuse that data way easier.
• With the creation of the Rust Foundation there might be the need to create private mailing lists or teams for the foundation (for example a mailing list for the accounting people and vendors).

We should draft a set of requirements for the future of the team repository. After that's done we should forward them to the infra team, leaving the technical design and implementation to them.

[github-actions]

This issue is an item on the Core Team's public agenda, and the team will discuss it every week during the triage meeting. The goal of the issue is to provide a public record of our discussion, so only members of the Core Team are allowed to comment here.

Please get in touch with the Core Team by emailing core-team@rust-lang.org if you have something to add!

[Manishearth]

For fixing the former problem: I hope we can do it in a way that can still allow team members to dump emails (maybe via a small service that auths to github?). I say this because Google Calendar is terrible around non-google-groups mailing lists, so the only sensible way to create team events is to dump-list and add that to the event.