The RFC Steering Committee has started using an `RFCSC:` prefix to their messages posted on behalf of the committee to provide indication between personal opinion and communication from the committee. This updates the canned messages to include that prefix for consistency.
* Update the RFC process documentation
- Nudge authors towards using Semantic Line Breaks for writing the RFC text
- Nudge authors towards posting their text as pre-RFC in the forum first
- Tweak wording around who declares FCP slightly
- Make clear that the shepherds have to announce FCP, and when exactly the period officially starts
- Be more open about when to do the implementation work relative to the RFC, and reflect the current practice of starting implementation work early
- Make more clear that RFCs should not be amended, and that important information should live e.g. in documentation instead.
* RFC template: Use semantic line breaks
Given the short text this may not make a huge difference, but given
that every RFC starts with a copy of that template, the hope is that
it will nudge people to continue writing in that style.
* RFC template: Add "Prior art" section
This is mostly inspired by Rust's RFC template.
Also added a couple of words to the "Alternatives" section,
similarly inspired by Rust's template.
* fixup! Update the RFC process documentation
* fixup! Update the RFC process documentation
Co-authored-by: 7c6f434c <7c6f434c@mail.ru>
* fixup! Update the RFC process documentation
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
---------
Co-authored-by: 7c6f434c <7c6f434c@mail.ru>
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
The main sections are largely copy+pasted from the RFC text itself. Minor modifications were made to integrate into the existing document.
- Change to future tense to reflect what actions will be taken in each scenario.
- Fix up some links to be relative to this document.
- Update template message to be a codeblock for easy copy+pasting when used.
* Expand the RFC acronym at least once
While it is probably know to most it should also be documented what we expand RFC to.
* Capitalize "RFC"
Co-authored-by: zimbatm <zimbatm@zimbatm.com>
Co-authored-by: Eelco Dolstra <edolstra@gmail.com>
Co-authored-by: zimbatm <zimbatm@zimbatm.com>
This paragraph seems to be a leftover or copy-pasta from the RFC template. It doesn't really fit into the flow of the text, so I think it was included or left here by mistake.
