Contributing
PLANET is a cooperative project. Every contribution matters — code, design, writing, testing, ideas, introductions, or simply telling someone you trust about what we're building.
What you can do
It depends on how deep you want to go.
Anyone can report issues, suggest improvements, share PLANET with people who'd care about it, or fund features via Open Collective.
Members can participate in governance decisions on Loomio, give feedback on specs and designs, and test demos and prototypes.
Contributors can write or improve documentation, design UX flows and interfaces, write code, create content (blog posts, explainers, videos), or help with community organising and outreach.
All of these matter equally. The person who translates a page into another language is contributing as meaningfully as the person who writes a protocol implementation.
How we work
Working drafts live in Google Docs — ask for access in the contributor Signal group. When a doc is stable, it gets promoted to the docs site via a pull request to the docs repo. Specs and architecture decisions live in the planet repo under specs/ and adr/.
Code goes through pull requests with at least one review. Write clear commit messages. If you're unsure about something, open an issue to discuss before building — it saves time.
Real-time coordination happens in Signal groups (contributor access). Task tracking and technical discussion happen in GitHub Issues. Governance decisions happen on Loomio. Finances are transparent on Open Collective.
You can use AI tools to accelerate your work. Most of us do. When you do, review the output before committing — you own the quality. Note in pull requests if substantial portions were AI-assisted, and share useful prompts or approaches with other contributors. We're building a cooperative; that includes sharing how we work.
How we treat each other
Be kind. Be honest. Assume good faith. Remember we're building infrastructure for future generations — act accordingly.
Treat all contributors with respect regardless of experience level. Give constructive feedback, not personal criticism. Keep discussions focused and productive. Respect the time people are volunteering. If you disagree, propose an alternative rather than just objecting.
Getting started
Read the docs site to understand the vision, if you haven't already, then sign up as a member. Browse open issues for something that interests you. Comment on an issue to signal you'd like to work on it. Feel free to ask questions. We look forward to collaborating with you.