Skip to content
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

Reopen RFCs that were postponed until after 1.0 #1456

Closed
HeroesGrave opened this issue Jan 10, 2016 · 12 comments
Closed

Reopen RFCs that were postponed until after 1.0 #1456

HeroesGrave opened this issue Jan 10, 2016 · 12 comments
Labels
T-core Relevant to the core team, which will review and decide on the RFC.

Comments

@HeroesGrave
Copy link

There seems to be a few RFCs that have fallen under the radar since they were postponed until after 1.0.

It would probably be a good idea to reopen some/most/all of them.

@White-Oak
Copy link

👍 especially interested in this postponed RFC.

@ticki
Copy link
Contributor

ticki commented Jan 10, 2016

@White-Oak
Copy link

So, erhm... Any progress?

@burdges
Copy link

burdges commented Jan 22, 2016

Isn't that particular one open under #1037 @White-Oak ?

Appears many are superseded if you look closely.

@steveklabnik
Copy link
Member

I don't think just opening RFCs again is always useful; the authors may not care about / be involved anymore. Plus, things may have changed since then, which requires a lot of re-writing, which basically is a new RFC anyway.

I would suggest either 1) writing new RFCs and linking to the postponed ones or 2) if the RFC still fits as today and the author wants it re-opened, comment and we can do it.

@ticki
Copy link
Contributor

ticki commented Jan 22, 2016

@steveklabnik I've checked, and many of the postponed RFCs are not outdated, and still relevant today.

@ticki
Copy link
Contributor

ticki commented Jan 22, 2016

Another possibility is to fork their repo and resend the pull request, changing things that needs update.

@petrochenkov
Copy link
Contributor

@steveklabnik
Could you remove the postponed label from #867, #933 and #94?
They are all implemented now.

I would suggest either 1) writing new RFCs and linking to the postponed ones

+1, all the RFC texts are pretty old and require update and in many cases rework.

@steveklabnik
Copy link
Member

Done.

@glaebhoerl
Copy link
Contributor

I think we should have some sort of process innovation around postponement, such as automatically re-opening for consideration a fixed time (perhaps chosen at the time of postponement) afterwards, even if the decision at that time is only to re-postpone, as a form of triage, because in many cases the practical outcome of postponement seems to be not very different from that of rejection.

(Was originally going to write this in #1303 before I remembered about this issue.)

@nrc
Copy link
Member

nrc commented Aug 18, 2016

Anyone is free to open an RFC at any time, including re-opening a postponed one. If there is no-one motivated to do that, then that seems an indication that the RFC is not ready to be re-opened automatically.

@nrc nrc added the T-core Relevant to the core team, which will review and decide on the RFC. label Aug 18, 2016
@Centril
Copy link
Contributor

Centril commented Apr 26, 2018

Triage: Closing this since we didn't do it.

@Centril Centril closed this as completed Apr 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-core Relevant to the core team, which will review and decide on the RFC.
Projects
None yet
Development

No branches or pull requests

9 participants