Lazy consensus means that when you are convinced that you know what the community would like to see happen, you can assume that you have consensus in favor of the proposed work and and get on with it. You don’t have to insist people discuss and/or approve your plan, and you certainly don’t need to call a vote to get approval. You just assume you have the community’s support unless someone says otherwise.
Lazy consensus works only if you communicate with enough advance notice, and with enough details that people who would object have the time and the necessary information to do so. Generally speaking, it’s better to over-communicate.
How to work on issues
The group is still getting started in terms of developing and prioritizing our backlog. We’re using Github projects for that.
The process of selecting and replacing working group leaders is still to be formally decided. For now, election of new leaders is made by lazy consensus (see above).
Working group membership is not binary – we are not a political party. Instead, we value concrete contributions, such as bug reporting, fixing, release testing, documentation efforts, etc. Below we list people who made significant contributions to the past named releases.