Consider changing this from a wiki to a RFC-style repo

[micaeljtoliveira]

While browning the docs, I've realised that a lot of the content lacks context and there's not clear method to propose and discuss changes, specially the ones regarding policies and best-practices.

One alternative that might be worth considering is moving to a more structured way of handling changes/additions to the docs in the form of Requests For Comments (RFCs). A very good example of such a repository is the Rust RFCs project., although we probably could simplify the review process a bit.

[ccarouge]

If we go to a process with review of changes (which is probably a good idea), wouldn't it be simpler to change how we publish the dev-docs? Otherwise, are we going to end up with this type of workflow:

• copy the wiki bits we want to change from dev-docs to another .md doc in a repo "code" (likely dev-docs)
• make modif, discuss and get approval in PR
• copy the approved result back to dev-docs wiki file

The 2 copies steps are eliminated if the dev-docs are simply held in code and published through readthedocs for example.
I haven't used the RFC workflow before and I have just skeemed through the Rust page so I may have misunderstood something in the workflow.

dev-docs were started as a place to put stuff down quickly so introducing a review step goes against that. I'm not sure the current approach is promoting quicker updates of content than going through a review process though.