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

Update README to describe champions process #232

Merged
merged 1 commit into from Oct 1, 2014

Conversation

Projects
None yet
3 participants
@nikomatsakis
Copy link
Contributor

nikomatsakis commented Sep 10, 2014

No description provided.

@alexcrichton alexcrichton force-pushed the rust-lang:master branch from 6357402 to e0acdf4 Sep 11, 2014

@aturon aturon force-pushed the rust-lang:master branch from 4c0bebf to b1d1bfd Sep 16, 2014

@nrc

This comment has been minimized.

Copy link
Member

nrc commented Sep 23, 2014

Since a 'champion' does not have to actually approve of an RFC, only look after it and ensure it gets a fair hearing at a meeting, we should s/champion/shepherd.

@nikomatsakis

This comment has been minimized.

Copy link
Contributor Author

nikomatsakis commented Sep 25, 2014

agreed

@nrc nrc merged commit b40aeb0 into rust-lang:master Oct 1, 2014

@nrc

This comment has been minimized.

Copy link
Member

nrc commented Oct 1, 2014

Merged as 9f7b8db

@Centril Centril added the A-meta label Nov 23, 2018

wycats pushed a commit to wycats/rust-rfcs that referenced this pull request Mar 5, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.