I have to deal with a repository, which means dealing with github, forks, git commands, etc. This is something I dread having to deal with just so I can write some text. Some people will probably be too lazy to actually do this to write an RFC. Especially people who don’t have a github account already.
I had to actually create a new RFC because I tried to update an old RFC, but then I’d need huonw to pull my changes. This means I have to split up the discussion between https://github.com/rust-lang/rfcs/pull/886 and https://github.com/rust-lang/rfcs/pull/1940
Can’t we just use a wiki? Then anyone can change parts of the RFC without having to submit PRs to the original author. Furthermore, you don’t have to clone the repo, manage several branches, etc. Since wiki software is already made to keep revisions of formatted text. You can see how your changes look instead of having to write in Markdown and hoping it renders okay.
I don’t know which wiki software does a good job with making line notes on each “article”. That’s probably the best feature of github PRs in regard to RFCs.
People yelled at me in IRC because I didn’t know git well, that I’m supposed to keep the git history clean without merges, it’s very frustrating.