-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Amend RFC 1242 to require an RFC for deprecation of crates from the nursery #1983
Conversation
I think this generally comes under the 1.0-level crates objective of the 2017 roadmap or maybe the high quality crates goal rooted in the Rust platform discussion. An approach might be to open a well informed "What do we want for 1.0 discussion?" issue on each of the nursery crates named in this RFC, and link them from the 1.0-level crates objective issue. Is a As an aside, I'd suspect the name "nursery" would be inappropriate for crates the language developers view as stable and ship with the compiler. There is no breaking change in merely moving a crate from the nursery to another github url though. |
text/0000-nursery-deprecation.md
Outdated
|
||
Acceptance into the nursery could be hindered if it is believed it could be | ||
hard to reverse course later due to the required RFC being percieved as an | ||
obstacle. On the other hand, RFCs with broad concensus do not generally impose |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo: s/concensus/consensus/
text/0000-nursery-deprecation.md
Outdated
Acceptance into the nursery could be hindered if it is believed it could be | ||
hard to reverse course later due to the required RFC being percieved as an | ||
obstacle. On the other hand, RFCs with broad concensus do not generally impose | ||
a large procedural burden, and if there is no concensus it might be too early |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo: s/concensus/consensus/
I've been hearing rumors about a "big rewrite/redesign" for quite a while now, but nothing seems to actually be happening on that front. |
cc @rust-lang/libs: TL;DR, require an RFC to deprecate nursery crates. I agree with the rationale here; since the whole point of rust-lang crates is to put these libraries under full community governance, that should certainly apply to deprecation too. @rfcbot fcp merge |
Team member @aturon has proposed to merge this. The next step is review by the rest of the tagged teams: No concerns currently listed. Once these reviewers reach consensus, 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. |
What happens if an RFC to deprecate a nursery crate is rejected? Does the libs team have some kind of SLA on maintenance of a library none of them want to maintain? |
@jethrogb a rand overhaul is blocked on someone with the time and interest stepping up and owning the design and implementation. |
@sfackler Keep in mind that it's the libs team that would make the decision on such RFCs. So it's really more about consulting the broader community and opening up a discussion, ensuring that it's not a "libs team against the world" type situation. I would imagine these RFCs would be pretty short, but that in at least some cases discussion would lead to discovery of people who do want to maintain the library (in the case that it's not being deprecated in favor of something else). |
So the only real change here is adding a ~month to the time it takes from our decision to do this to actually making the move? I don't really see a world in which there's some huge outcry that we have to continue maintaining something. |
@aturon proposal cancelled. |
I'm going to propose to close this RFC, for two reasons:
In any case, any move to deprecate any of the existing crates will certainly involve public discussion. @rfcbot fcp close |
Team member @aturon has proposed to close this. The next step is review by the rest of the tagged teams: Concerns:
Once these reviewers reach consensus, 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. |
Has there been any discussion on this change? I understand that the libs team is very busy and the community can't just expect the libs team to do everything we throw at them. Therefore it's entirely reasonable that the libs team changes the way they operate if they think that will balance their workload. I do think it's important that if the libs team wants to make those changes that there is some public discussion about this, so that the community can see if there's any slack left that needs to be picked up elsewhere. One main question I have is: what will be the process to move things into Please elaborate on https://twitter.com/fitzgen/status/889980459953692674 with regards to your earlier statement.
This is basically all that this RFC proposes to change, so why not just merge? |
Is there a counter-proposal (#1983 (comment)) yet? I would be inclined to accept the RFC. So far the main argument against sounds like "we will never again deprecate anything from the nursery" which I don't find compelling.
I don't expect a practical difference between how people treat a deprecation announcement without this RFC, vs a deprecation RFC per this RFC. People who care will take either as an indication to look for an alternative library—or raise concerns that a suitable alternative does not exist, which the RFC provides a place to do. @rfcbot concern let's do it |
@rfcbot fcp cancel |
@aturon proposal cancelled. |
Alright, after talking last week in the libs team, we're just gonna go forward with this. Several of the nursery crates are being tackled as part of the Blitz, and are expected to head toward rust-lang proper. The others, we'll probably propose deprecation for in a single RFC. @rfcbot fcp merge |
Team member @aturon has proposed to merge this. The next step is review by the rest of the tagged teams: No concerns currently listed. Once these reviewers reach consensus, 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. |
(I ticked everyone's boxes based on the discussion in the meeting.) |
🔔 This is now entering its final comment period, as per the review above. 🔔 |
The final comment period is now complete. |
This RFC has now been merged. Thanks @jethrogb! |
Rendered