Automated RFC workflow

[Jazcash]

Ideally, submitting a proposal should be as simple as writing the markdown document and clicking a button. The current workflow is a little too involved for non-techy users or even just people unfamiliar with the process here. It leaves too much room for potential mess such as:

• Incorrectly submitted RFCs (e.g. to the wrong directory)
• Inconsistent filenames and titles
• Lack of or mis-linked discussions and fully rendered proposal links
• People discussing the proposal in PR comments instead of in the discussion

Ultimately, I think we'd want to create a simple frontend for people submitting, editing and viewing proposal documents, but it would still use this repo behind the scenes. Devs would continue to use github for reviewing, discussing and managing RFCs.

[drivver44]

i think that we should consider a few things

1. allowance of time for a person to correct mistakes and fully develop the PR
   a. in my case i didnt full fledge out the PR and i was aware that there are going to be issues with the PR

people do need to be walked through github as most people do not use github
the reliance of github as a means to handle this system is both a benifet and an issue at the same time

[Teifion]

I see using github as something to remove low effort submissions. If it's a simple change then a suggestions thread would be fine, for something more involved there should be more effort put into it.

[drivver44]

@Teifion the same issue applies to people being aware of what is going on with the project
they have to now go on github RFC's to be aware of what is going on and how the conversations are proceeding
however i do think to a degree the github part of the project will somewhat resolve itself

[Jazcash]

At the very least, I'd like to try and automate the discussion and rendered proposal links in the PR descriptions because I don't think anybody has got them right yet 😅