-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Find homes for launching pad teams #118
Comments
I might note that this is loosely related to #91, because the launching pad has the bulk of working groups. I don't think it is a blocker, but the answers there might influence what we do here. |
Making a list of teams under launching-pad (Team)
This is essentially my todo list of teams to find homes for, or to determine if they should be closed. |
For reference, here's the full team structure generated by my script (as of 2024-12-02): Full project structure according to the teams repo
|
IMHO, the book team, twir team, web-presence team, social-media team, and wg-rust-by-example are all community related. From what I gather, the community team has been shut down, but maybe it is possible to revive it as a top-level team containing the teams I mentioned, in addition to the community team's subteams that are still active? As I'm not a member of the project, I don't have a say in this, but I think the community work is really valuable and deserves representation on the council. |
Looking at the teams to be re-homed, there may be a couple groups that I can start to see: Documentation and Teaching Material Related teams
"Project Services" Related teams |
RFC 3392 intended for launching pad teams to be temporary, and that it is the responsibility of the council to find more permanent homes for those teams in the org. Additionally, the council is supposed to be reviewing those launching pad teams every 6 months. Unfortunately we haven't made much progress on figuring this out, yet. This issue is for tracking and figuring out how to kick off this process, and to find homes for the current set of teams.
The text was updated successfully, but these errors were encountered: