Add RFC combining Infra and Release teams by rylev · Pull Request #3533 · rust-l...
source link: https://github.com/rust-lang/rfcs/pull/3533
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Conversation
This RFC proposes combining the Infra and Release teams into one team. This change has very little impact outside of the removal of the Release Council representative. Release team interests will be represented by the Infra team representative.
added the T-leadership-council Relevant to the Leadership Council, which will review and decide on this RFC. label
Contributor
|
Unless I'm mistaken, seems like we can FCP merge? @rfcbot merge |
|
Team member @jackh726 has proposed to merge this. The next step is review by the rest of the tagged team members: No concerns currently listed. Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
added proposed-final-comment-period Currently awaiting signoff of all team members in order to enter the final comment period. disposition-merge This RFC is in PFCP or FCP with a disposition to merge it.
labels
The Infrastructure team's Council representative would continue to serve on the Council while the Release representative would immediately stop counting as a representative for all purposes.[^plan] |
||
As part of this change, wg-triage will move out from under the Release team and move to be a part of Launching Pad until a more appropriate home for the working group can be found. |
Contributor
@jonathanpallant - This means bringing another team under Launching Pad. Given that the goal of Launching Pad is to not exist anymore, are you okay with having another group come under its purview?
This RFC proposes merging the Release team into the Infrastructure team as a subteam. The membership of the Infrastructure and Release teams proper remain the same.[^subteam] |
||
[^subteam]: Note: Members of subteams are not automatically members of their parent team. So Release members will be part of the Infra team family but *not* members of the team proper. |
Contributor
| [^subteam]: Note: Members of subteams are not automatically members of their parent team. So Release members will be part of the Infra team family but *not* members of the team proper. | |
| [^subteam]: Note: Members of subteams are not automatically full members of their parent team. So Release members will be part of the Infra team family but *not* members of the team proper. For example, they Release members would not get checkbox authority for Infra, but Release members could serve as the Leadership Council representative for Infra. |
Even though we don't have real clear terminology and definitions around here, I think it'd be good to highlight some of the practical implications of the arrangement.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
No one assigned
None yet
No milestone
Successfully merging this pull request may close these issues.
None yet
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK