Open ehuss opened 1 year ago
And are there people we would want to consider "part of the project" that aren't on a team? For the purposes of consulting people about a decision?
I believe rfcs#3392 is somewhat explicit about ensuring that everyone is part of the project through a team because this makes answering a question of why they are part of the project much more straightforward. If we ever want a "group of people whose opinions we value" we should make that a team and have explicit criteria for inclusion.
And are there people we would want to consider "part of the project" that aren't on a team? For the purposes of consulting people about a decision?
I guess that depends on whether we think a Working Group is a Team? The Rust Embedded Working Group is in the teams repo, but sits under the Launching Pad team.
https://github.com/rust-lang/rfcs/pull/3392 considers working groups teams in the wider sense of the word (i.e., a governance structure). Everyone considered a part of the Rust project is a member of a governance structure (i.e., a team, subteam, working group, project group) that ultimately "reports up" through a top-level team into the Council. The RFC was purposefully worded as such to avoid any "dangling" members - i.e., there should never be anyone in the Project who does not have Council representation and Council representation is determined by the Council rep for the top-level team the governance structure(s) the person is on reports up through.
This is a bit nebulous, but the overall idea is to:
I seem to recall there are some ambiguities, but I don't remember what they were exactly.
See also #32 for specific considerations of the top-level team arrangement.