How does the board make its decisions?

[mr-c]

Carole Goble suggested we look at the rules used the Software Carpentry Foundation

http://software-carpentry.org/scf/
https://github.com/swcarpentry/board/blob/master/README.md
https://github.com/swcarpentry/board/blob/master/governance.md
https://github.com/swcarpentry/board/blob/master/committee-roles.md
https://github.com/swcarpentry/board/blob/master/proxy-membership.md

[stain]

Here's how Apache does voting. But most of the time there is no vote - that's just for formal things (e.g. release or new member) or if reasonable consensus is not formed.

For CWL a release would be a new version of the spec, so I guess we should keep that formal (rather than a bit of re-tagging during a BOSC session :))

A "lazy consensus" with a "just do it" default means the project can keep moving for smaller changes - with appropriate time delays to allow people to catch up if they disagree.