Conversation
|
this seems pretty long 😅, I'm working on rendering the RFCs in the docs website, depending on frontmatter support or other formats I would love to use something like that |
|
Not sure how the length of the RFC would affect how we render things? |
|
that comment has two points:
|
|
take a look at #6, that's roughly how proposals should be formatted |
|
actually lets merge #7 first |
|
@AdamGS I'm not sure how the formatting of the current template is special? It looks like normal markdown to me (other than the header). Also, I would far prefer a lengthy template to a short one because it gives the writer an idea of how to structure it. We don't necessarily have to require everyone to follow the exact template but it should be a good starting point. Or AFAICT none of the things that we probably want RFCs on would be sufficiently described with anything less than this... |
|
yeah I was (and now @a10y) figuring out formatting, nothing is special. I don't really feel strongly about this template, lets ship it |
|
how does the CI work here? Seems like the build is getting blocked. I'll also update the header |
1222fb3 to
d0ece9c
Compare
|
oh I guess I don't need to make a specific header anymore? Also when I run |
|
It pulls the author from git history. The user who committed the file is marked as the author. |
Signed-off-by: Connor Tsui <connor.tsui20@gmail.com>
d0ece9c to
d4cb849
Compare
This is loosely based off of the Rust project's RFCs template, which you can find here: https://github.com/rust-lang/rfcs/blob/master/0000-template.md