Skip to content

Add post about Cargo team changes #953

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

Merged
merged 3 commits into from
Apr 1, 2022
Merged

Conversation

ehuss
Copy link
Contributor

@ehuss ehuss commented Mar 24, 2022

This adds an internals post about some changes in the Cargo team.

cc @rust-lang/cargo

@ehuss ehuss requested a review from a team March 24, 2022 21:44
@Mark-Simulacrum
Copy link
Member

@ehuss I want to check in that we have sign-off here from @alexcrichton and @epage as they're prominently mentioned in the blog post. Did that happen at a Cargo meeting or elsewhere, either on direct text or on general idea? Want to avoid surprises.

I also think it's worth considering whether there's some slightly more positive tone we might be able to adopt towards the end -- obviously, presuming it's not misleading. Maybe we can say something about looking forward to the new team members helping to expand the review capacity as they ramp up on the full breadth of Cargo?

Copy link
Contributor

@epage epage left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm good with my part

Copy link
Member

@alexcrichton alexcrichton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indeed looks good to me!

@joshtriplett
Copy link
Member

joshtriplett commented Mar 30, 2022

@Mark-Simulacrum I think the team is comfortable with this not coming across as positive. This is intended to be concerning. I am hopeful that @epage and @weihanglo will help us on this front, but I don't expect that to put us in a position where we have the capacity for new features anytime soon.

"We appreciate people's patience as we move forward." seems like the right tone for this.

@Mark-Simulacrum
Copy link
Member

Ok! In part I bring it up as it might be a good opportunity to try to identify how we can change that (e.g., what can folks who want to help do). It's quite possible the answer is nothing yet, though; I'm not sure whether it make sense to make that more explicit than just asking for patience. (The reverse effect of people contacting in a storm asking what they can do may also be good to mitigate with slightly more explicit language).

In any case, happy to merge this when ready - I think the date will need to get bumped. Please ping on Zulip so it doesn't get lost in email.

Copy link
Contributor

@nikomatsakis nikomatsakis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor wording nit.

@ehuss ehuss requested a review from a team as a code owner March 31, 2022 23:21
@ehuss ehuss merged commit aed03ff into rust-lang:master Apr 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants