Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Cooperative Development Guidelines

Templates, guides and values to structure our spaces by-and-for us, the community, with a dynamic structure (without hierarchies or voting) and participatory processes (plurality, diversity, platforming, etc.)

The core structure and processes (in the Foundation Folder) are community agnostic and can be used with any community of reasonable size or structure. Guides on how to adopt it are inside the Adoption folder (TBD.) and reading material for the Community are in the Community Folder (TBD.)

We are also writing an evolution of the Free Software Denifition and the Open Source Definition with the aims of:

  • giving power to people using the software (not just developers) with participatory development
  • code of ethics (privacy, accessibility, permacomputing, consent, etc.) and a guide to write software that can be used and improved by others (reproducibility, easy building process, etc.)
  • Ubuntu - “I am because we are”. Meaning we are not individual “islands” but instead we all have responsibilities and obligations to each other so that we can all build software we like together. Each of us can help make the other person safe and comfortable in our communities.
  • Pave the way to a new Digital Commons where there is no single upstream (“gatekeeper”), rights and obligations to be part of the Digital Commons and a diverse ecosystem of software variants that are customized for purpose.

Communities that use these guidelines

Document Metadata

All documents have on top the metadata that are defined in the RFC template in the Governance document. This is done because all documents double as RFCs, and we follow our own guidelines, which means the Cooperative Development Guidelines are “self-hosted”.

Social Rules

Our Code of Conduct

Contact

Vojkruco Lounge