From f73d084b617e2e08703cefa2db12ab354fdedf1f Mon Sep 17 00:00:00 2001 From: "Ryan Scheel (Havvy)" Date: Sun, 3 Apr 2016 02:24:42 +0000 Subject: [PATCH] Explain that RFCs can be changed based on feedback in Process. --- README.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/README.md b/README.md index a46080d6075..cc04fd9bb25 100644 --- a/README.md +++ b/README.md @@ -182,6 +182,11 @@ stakeholders to discuss the issues in greater detail. * The sub-team will discuss the RFC PR, as much as possible in the comment thread of the PR itself. Offline discussion will be summarized on the PR comment thread. +* RFCs rarely go through this process unchanged, especially as alternatives and +drawbacks are shown. You can make edits, big and small, to the RFC to +clarify or change the design, but make changes as new commits to the PR, and +leave a comment on the PR explaining your changes. Specifically, do not squash +or rebase commits after they are visible on the PR. * Once both proponents and opponents have clarified and defended positions and the conversation has settled, the RFC will enter its *final comment period* (FCP). This is a final opportunity for the community to comment on the PR and is