-
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
Reopen RFCs that were postponed until after 1.0 #1456
Comments
👍 especially interested in this postponed RFC. |
So, erhm... Any progress? |
Isn't that particular one open under #1037 @White-Oak ? Appears many are superseded if you look closely. |
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. |
@steveklabnik I've checked, and many of the postponed RFCs are not outdated, and still relevant today. |
Another possibility is to fork their repo and resend the pull request, changing things that needs update. |
@steveklabnik
+1, all the RFC texts are pretty old and require update and in many cases rework. |
Done. |
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.) |
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. |
Triage: Closing this since we didn't do it. |
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.
The text was updated successfully, but these errors were encountered: