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

Give pre-RFC suggestions and clarify PR process #506

Merged
merged 3 commits into from
Dec 11, 2014
Merged

Conversation

brson
Copy link
Contributor

@brson brson commented Dec 8, 2014

Based on workweek discussions here are some minor updates to the RFC process.

TL;DR is that we are no longer going to do RFC approvals at the meeting, are going to try to have more ad-hoc meetings involving a wider group of contributors, will insist on summaries of those meetings being delivered back to the PR threads, core team will make final decisions based on discussion in the thread.
We will try to invite community stakeholders to more weekly meetings to discuss their RFCs as needed. I've also added some text about how to properly prepare before submitting an RFC.

@steveklabnik
Copy link
Member

👍

stamp, and in particular still does not mean the feature will ultimately
be merged; it does mean that in principle all the major stakeholders
have agreed to the feature and are amenable to merging it.
Once an RFC becomes active then authors may implement it and submit
Copy link
Member

Choose a reason for hiding this comment

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

While we're updating this, it may be worth clarifying if the author of the RFC is expected to implement the feature or not. Maybe there should at least be some understanding of who's going to implement it and when? There are some accepted RFCs that have just been sitting there without an implementation for a while now.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I was considering that, but didn't know quite what to write. It's best if the author is capable of and willing to implement the RFC, but it's not a requirement.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Added some text about this.

@emberian
Copy link
Member

👍

brson added a commit that referenced this pull request Dec 11, 2014
Give pre-RFC suggestions and clarify PR process
@brson brson merged commit 3436244 into rust-lang:master Dec 11, 2014
@Centril Centril added the A-meta Proposals about how we make proposals label Nov 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-meta Proposals about how we make proposals
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants