Formalising processes for reaching community consensus

[tombh]

What do you think about having some formal processes and or governance structures in place for making decisions in the project? This was raised in #257 with regards to camelCase versus snake_case, which although is not a seemingly significant fork in the road, it is nevertheless a great example of the kind of issues that can face a project.

This doesn't have to be anything big, for example even just using Github Issues with a Request For Comments style submission and discussion. Or it could take inspiration, albeit on a much smaller scale, from Rust's governance model. What if we required a minimum quorum of community members to vote on an issue in order for it to be acted on? How would we choose those members? Or is this all just a premature optimisation for a project that is still young and finding its way?

Pygls is not exactly the only general Language Server, but it is perhaps the most general and accesible of them. Therefore in some ways it is an ambassador to the world of Language Servers as a whole, especially as it is not directly affiliated to any of the main players.

This is a question for everyone, even if you're just a user and even if you simply don't have any opinion about the matter.