Pull Ourselves Up By Our Bootstraps #7
Description
This is based on the list of things from the Bootstrapping Gem Cooperative Governance document.
- Martin Emde gives Mike McQuaid write access to https://github.com/gem-coop/governance
- Mike McQuaid commits to
maintheREADME.mdfile for this repository - Mike McQuaid opens a pull request adding all other files to this repository (Add Initial Gem.coop Governance #1)
- A subset of existing RubyGems maintainers will be added to the
gem-coopGitHub organisation to discuss the governance pull request(s) - These maintainers can propose their own pull requests to files (Add Initial Gem.coop Governance #1, formatting, text clarifications, etc #2, Governance tweaks #3, Use last year contributions according to homebrew tooling for initial voting #4, Clarify distinction between gem.coop (the service) and Gem Cooperative (the group) and gem-coop (GitHub organization) #5)
- Mike McQuaid finalises the initial governance documents once a majority voted in favour
- Mike McQuaid makes the governance repository public
- Mike McQuaid will leave the GitHub organisation
- Candidates for the Project Leader and Project Leadership Committee will put their names forward for election
- Everyone with RubyGems maintainer contributions in the last year (https://mikemcquaid.com/rubygems-contribution-data-with-homebrews-tooling/) will be given a vote
- Someone will setup the voting using OpaVote, tally and announce the results
- When a Project Leader and Project Leadership Committee have been appointed, they will in turn appoint the maintainers and, from them, the Technical Steering Committee
- Everyone who voted will be made a Member and granted a vote in the following year
- Everyone else will be removed from the GitHub Organisation
- The Gem Cooperative governance documents will apply from this point
Unresolved things not in that list:
- Contact everyone who will be given a vote.
- Determine when the vote will happen.