Move the Crates.io Team under the Dev Tools team #3595
Conversation
carols10cents
force-pushed
the
move-crates-io-under-dev-tools
branch
from
4bb8ff9
to
9a1603e
Compare
carols10cents
added
the
T-leadership-council
|
@rfcbot fcp merge As there haven't been any objections or other discussion, I'm proposing to merge this! |
|
Team member @carols10cents 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. |
rfcbot
added
proposed-final-comment-period
|
Although I don't think there will be any objections, I would like to also have a clear approval from the devtools team as well. We don't have a formal process for adding teams, but I think just making checkboxes here should suffice. I'm checking @Manishearth's box since there is already an approval above. |
|
|
||
| ## Be a subteam of both Dev tools and Infra | ||
|
|
||
| The Types team provides precedence for this; technically the Types team is a subteam of both the Compiler and Lang teams. However, the teams repo doesn't really support multiple inheritance. The Crates.io team would like to cultivate a closer relationship with the Cargo team especially, and thinks the relationship with the Infra team could be continued in the current manner. |
There was a problem hiding this comment.
The Crates.io team would like to cultivate a closer relationship with the Cargo team
I feel like this is the key argument for why this RFC proposes T-DevTools as the parent rather than T-Infra. Infra seemed like the obvious choice to me, so I was confused as to why DevTools. Being able to foster closer collaboration between cargo and crates.io makes sense.
rfcbot
added
the
final-comment-period
|
🔔 This is now entering its final comment period, as per the review above. 🔔 |
rfcbot
removed
the
proposed-final-comment-period
rfcbot
added
finished-final-comment-period
|
The final comment period, with a disposition to merge, as per the review above, is now complete. As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed. This will be merged soon. |
|
Thanks everyone! The @rust-lang/leadership-council has decided to accept this RFC. @carols10cents can you follow up with updating the team repo whenever you have a chance? It should look something like rust-lang/team#1228. I can help if needed. |
This implements [RFC#3595], which entails: - Moving the crates.io team to be a subteam of devtools - Removing @carols10cents from Leadership Council [RFC#3595]: rust-lang/rfcs#3595
Done! rust-lang/team#1439 |
This implements [RFC#3595], which entails: - Moving the crates.io team to be a subteam of devtools - Removing @carols10cents from Leadership Council [RFC#3595]: rust-lang/rfcs#3595
This RFC proposes moving the Crates.io Team under the Dev Tools Team. This change has very little impact outside of the removal of the Crates.io Council representative. Crates.io Team interests will be represented by the Dev Tools team representative.
Rendered