Governance
We follow a low-overhead governance model that allows us to move quickly and creates a low hurdle for participation. We will initially model our system after concepts from Sociocracy 3.0, particularly:
- Domains and circles
- Roles
- Proposal forming pattern.
Circles
Each circle is semi-autonomous and self-governing. The members choose any policies they want to implement themselves, in collaboration with their delegator. Anything that's explicitly granted is allowed, and anything that isn't explicitly forbidden is as well. But everything the circle does has to contribute towards achieving its primary driver and any additional drivers (its purpose).
If a circle wants to suggest a larger change in how circles are set up, for example splitting or merging circles or creating new ones, their delegator should first consult with the delegator from the Governance circle. Governance can set up the appropriate tools to gather other circles' opinions, reach a decision and implement the changes.
Community
Primary Driver
Creating and sustaining a healthy community.
Purpose
- Set community standards
- Monitor and moderate community spaces
- Helping new community members get involved
Matrix Channel
#Community
Lead / Delegator
Members
Communications
Primary Driver
Handling project and product communication towards the outside world.
Purpose
- Coordinating with the Governance circle to release public statements that officially represent the project
- Creating art and design for public-facing project deliverables (website, guides, etc.)
- Running the project's public presence on any relevant platforms
- Naming of the product(s) and components
Matrix Channel
#Comms
Lead / Delegator
Members
Development
Primary Driver
Creating and maintaining a web framework.
Purpose
- Creating a fork of Ruby on Rails 8.x under the Mosscap name
- Backporting fixes from Rails 8.x to Mosscap
- Reaching and implementing software architecture decisions
Matrix Channel
#Development
Lead / Delegator
Members
- chiphead
- Christopher Araujo
- Damien Mathieu
- James Smith
- moonglum
- Robbe
- serra-allgood
- Trevor Vallender
Documentation
Primary Driver
Creating and maintaining technical documentation for Mosscap users.
Purpose
- Creating easy-to-understand guidance on changing over to Mosscap
- Forking existing Rails documentation where necessary (e.g. Rails Guides?)
- Coordinating with Development and Communications circles to share information effectively both internally and externally
Matrix Channel
#Documentation
Lead / Delegator
Members
Governance
Primary Driver
Creating a well-functioning organisation with clearly defined goals and boundaries.
Purpose
- Creation and improvement of processes
- Design and implementation of circles/domains, roles and improvement proposals
- Facilitating decision-making by organising meetings, polls, etc.
- Managing funding and raising funds
Matrix Channel
#Governance
Lead / Delegator
Members
Operations
Primary Driver
Providing build services and infrastructure to other circles.
Purpose
- Creating and maintaining infrastructure
- Automating infrastructure, builds and releases as a service circle for the Development circle
- Securing infrastructure in collaboration with the Security circle
Requirements
- Familiarity with configuration management (Chef, Puppet, Ansible, Pyinfra, Saltstack, nothing is decided yet)
- Ideally, familiarity with infrastructure as code (OpenTofu, etc.)
- Experience with some CI/CD system (GitLab CI, GitHub Actions, Travis CI, Jenkins, Circle CI, whatever)
- Optional: Familiarity with Woodpecker CI and/or Forgejo and Forgejo Actions
Matrix Channel
#Operations
Lead / Delegator
Members
Security
Primary Driver
Ensuring product security (security fixes, etc.) as well as operational security.
Purpose
- Handling of responsible disclosure responses
- Security incident tracking, response coordination, CVE management etc.
- Potentially help with triaging and backporting fixes from Rails 8.x
- Hardening of build infrastructure in collaboration with the Operations circle
- Security credential management (passwords, machine secrets/vaults)
Requirements
- Familiarity with security processes
- Willing to work and coordinate with others to cover 24h (follow the sun/multiple timezones) for disclosures
- Ideally, previous experience as CISO, in a security team or comparable
- Ideally, familiarity with the Rails codebase to more quickly judge impact of any reported issues
Matrix Channel
#Security
Lead / Delegator
Members
- James Smith
- Peter Boling