This repository was archived by the owner on Jul 10, 2021. It is now read-only.
Pre rfc process rfc #47
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Nell Shamrell <[email protected]>
Signed-off-by: Nell Shamrell <[email protected]>
valgrimm
reviewed
Apr 10, 2020
| ## Process | ||
| * Start with an open issue and an internals thread | ||
| * If someone is interested in idea or team wants to pick it up, "liason" gets involved in the discussion and works with the people pushing the idea | ||
| * First step to opening an RFC is to get enother team member on board |
valgrimm
reviewed
Apr 10, 2020
|
|
||
| ## Process | ||
| * Start with an open issue and an internals thread | ||
| * If someone is interested in idea or team wants to pick it up, "liason" gets involved in the discussion and works with the people pushing the idea |
There was a problem hiding this comment.
How is liaison designated , someone fulfilling the requirements (maybe a link here?) just joins the conversation in the thread?
nrc
reviewed
Apr 14, 2020
|
|
||
| This RFC introduces two roles: | ||
| * **shepherd** - (add more here) | ||
| * **liason** - this is a member of the team most relevant to the proposed change. This person should be called in as needed to work with the person composing the RFC, give feedback, and provide guidance throughout the pre-RFC process. |
There was a problem hiding this comment.
Are both these roles team members from the relevant team? Why have two roles rather than one?
There was a problem hiding this comment.
Clarification is coming in the next draft :)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.