comutability

Get involved

You do not need to code to make something better.

Ideas, research, writing, design, reviews and code all count. Everything happens in public on GitHub, where anyone can read along and anyone with a free account can join in.

Choose how to help

What would you like to do?

Showing next steps for: Suggest an idea

Suggest an idea

Describe a problem that you or other people have with software. Every project starts as a public conversation.

  1. Search the existing issues first, in case someone has already raised it.
  2. Open a new issue explaining the problem, who it affects and what you have already tried.
  3. Say why existing tools fall short. That helps people decide whether to build something new or improve something that exists.
Browse community issues (on GitHub)Open a new issue (on GitHub)

You will need: A free GitHub account to open or comment on an issue. Reading needs no account. Issues and comments are public, so never share personal information.

Come and talk with us.

The Comutability community meets on Commonveil, the first application built on Secure Net. The invitation is open to anyone. You will be asked to create a Commonveil account, which is separate from GitHub.

Commonveil is early software and has not been independently security-audited. Please do not rely on it for anything your safety depends on.

Join the community on Commonveil (on commonveil.online)

Getting help

Stuck, or have a question?

Ask in public, so the answer helps the next person. There is no private support desk, and nobody is paid to answer, so replies may take a while.

Found a security problem?

Please do not post the details in public. Email contact@comutability.org and say only that you have a report to make. Ordinary email is not end-to-end encrypted, so a person will arrange a private way to receive the details.

New to GitHub?

GitHub is where our code, conversations and decisions live. Here is how to find your way around.

  1. Step 1: Create a free GitHub account

    You only need one to comment or propose changes. Everything is readable without an account.

    Sign up on GitHub (on GitHub)

  2. Step 2: Visit the Community repository

    Start with the README and the Founding Charter. They explain what we are and how we work.

    Open the Community repository (on GitHub)

  3. Step 3: Read the open issues

    Issues are public conversations about problems, ideas and questions. Join one, or start your own.

    Browse issues (on GitHub)

  4. Step 4: Comment on proposals

    Pull requests are proposed changes. Draft policies are open pull requests that anyone can review.

    See pull requests (on GitHub)

  5. Step 5: Propose a change

    When you are ready, open a pull request. A human maintainer reviews it before anything is merged.

Roles in the community

Proposed in the draft governance guidance. Not yet ratified. Read the proposal (on GitHub)

Founding coordinator
Coordinates the first roadmap, access, infrastructure and decision log. Initially the founder.
Maintainers
Review and merge changes to specific projects, oversee testing and handle releases under published policies.
Contributors
Suggest ideas, report problems, review, design, write, test, translate and code.
Community participants
Take part in public discussions without being repository maintainers.

Roles are responsibilities, not ownership of anyone's work. No one gets a role just by opening a pull request.

Joining the GitHub organisation

You never need to be a member of the organisation to contribute. Anyone with a GitHub account can open issues, comment and propose changes.

For now, the founder coordinates access to the organisation, as the charter describes. How future maintainers are chosen, replaced or removed is an open question in the draft governance proposal, which says community-wide rules should go through public consultation before they are adopted.

Until a process is agreed, the draft guidance sets the tone: roles are responsibilities rather than rewards, decisions about them are recorded publicly in the decisions folder, and conflicts of interest must be disclosed.

Writing a good issue or pull request

Based on the draft contributing guidance.

  • Look for an existing issue or discussion before opening a new one.
  • Explain the real problem and who it affects, not just a solution.
  • Keep changes small and focused, and link them to the issue they address.
  • For code, include how you tested it and any significant risks or dependencies.
  • Say when you used AI substantially, so reviewers know what needs closer checking.
  • Never post passwords, API keys, personal information, or material you do not have permission to share.
  • Challenge ideas, not people. Make room for newcomers and explain technical terms.

Respect and safety

A code of conduct is proposed: treat people respectfully, offer constructive feedback, make room for newcomers, and challenge ideas without attacking people. Harassment, discrimination and exposing private information are not acceptable.

A private way to report problems has not been published yet. Until it exists, please do not post sensitive complaints or personal details in public issues.