A manifesto. Some disassembly required.
Your project is not a tenant.
Your code, issues, discussions, and decisions should be able to leave together. You shouldn’t have to rebuild your project’s history just to change where it lives.
Our principles ↓
The issue that explains a bug. The discussion that changed a design. The review that caught a mistake. These aren’t accessories to the project. They are part of it.
When the code can leave but the context can’t, the project isn’t really portable.
An export button is a start. It isn’t the whole answer. The useful question is whether the work can keep going somewhere else, with its context and provenance still attached.
Portability should be part of the foundation, not an emergency procedure.
Git gave developers a durable way to distribute code. Hubnot uses that foundation to exchange signed collaboration facts through ordinary Git remotes.
Keep the work and the story behind it together. Keep the transport replaceable.
We like a useful server as much as the next person. Hosting is a great convenience. It shouldn’t be a prerequisite for owning your project’s collaboration.
Use hosted services when they help. Work locally when that helps. Make the choice yours.
Reading a workflow is not permission to run it. Importing a review is not the same as granting authority. Receiving a fact is not a reason to trust it.
Hubnot’s execution and governance are explicit. Signatures establish provenance; policy determines authority.
The answer to platform dependency can’t just be another platform asking you to move in. Hubnot’s native collaboration has no Hubnot service or database at its center.
This is the direction we’re building toward, in the open. The protocol is experimental. The conviction is straightforward.
Put down the hammer. Pick up the work.
Open beta. A practical idea, getting better in the open. Read the release notes before trying it.