cabal is built and maintained exclusively by a community of volunteers.

together, we're creating a new platform for communities to stay empowered and connected. there are many ways you can get involved.

make a donation

cabal is a grassroots community project. donations from our community help to support our work and enable ongoing development. you can make a donation through our Open Collective page.

donate

cabal welcomes collaboration with funders who are aligned with our mission and values. please get in touch for more information.

contact

guiding principles

we use these principles to guide us when considering any changes to cabal.

  1. small trusted groups cabal prioritizes features that serve small, trusted groups of people (eg. 2-25). this also means prioritizing security, safety, and privacy.

  2. sustainability we are attentive to the sustainability of the code as well as the personal relationships of maintainers. we want to keep a functional set of features that are maintainable (e.g. tested) as well as a respectful community.

  3. separation of concerns cabal is built in clear layers (protocol, library, clients).

  4. accessibility from an end-user point of view, cabal works where people are, from in the terminal to on mobile devices. it should also be easy to work with from a developer point of view (e.g. documented, simple, enjoyable).

  5. aesthetics cabal's clients appeal to their audiences through well-chosen features and simple design.

  6. minimize waste cabal runs quickly and smoothly, even on older hardware.

help build cabal

developers can join in by contributing to one of the clients on github. please read the contribution guidelines above before you get started.

issue tracker

we also welcome contributions from non-coders, such as people with translation, UX, or design skills. please reach out if you have an idea about how you could help.

contact

documentation

cabal is currently undergoing updates, and for us this currently means implementing a new protocol we designed. it is called cable. you can read the specifications comprising cable in the specs section.

if reading specifications directly feels too heavy, you might instead be interested in comparisons of our protocol to others, browsing a lightweight guide for new protocol implementors, or reading a general introduction to the cable protocol - you can find all of these in our documentation section.