Whether to adopt a proposals process?

[mpickering]

In the cabal developers meeting last night we discussed the idea of a proposals process. The two main goals of a process would be to

• Enable developers to feel more able to make bigger decisions and changes to the project
• Better document bigger changes and overall project direction

It was generally agreed by those in the meeting that a process could work well to help those two goals but also some concerns about introducing too much bureaucracy. We need to draft something together which will work out well and can revisit the process later if it's not working for the developers.

The proposed process is designed to closely following existing development practices within the cabal ecosystem, and the main principles are:

• It is light-weight, a PR is opened and discussed on a repo with a fixed discussion period.
• It is developer-led, final decisions are made by developers at the Cabal developers meeting.
• It is flexible, there is no formal voting procedure, decisions are made by rough consensus.

The current draft of that process can be modified at this PR - #11006