Contributing

Cobblr is source-available and contributions are welcome, whether that's a doc fix, a bug fix, or a new driver.

One thing to know before writing code: Cobblr is built to unusually specific design rules (module isolation chief among them), and contributions are reviewed against them. The code contribution guide is the checklist.

How changes get in

Open a pull request on GitHub and it's reviewed there like anywhere else.

For the docs, accepted PRs are merged normally.

For the core platform, the public repo is a released snapshot of a canonical repo we develop in. So an accepted PR is imported into that canonical repo, keeping you as the author, and ships in the next release rather than being merged directly on GitHub. If your PR is closed with a note that it landed in a release, that's the expected flow, not a rejection. You're credited as a co-author on the release and in the notes.

Include a Signed-off-by line on your commits (git commit -s), which is a Developer Certificate of Origin sign-off saying you have the right to contribute the change.

License

The Cobblr platform is under the Functional Source License (FSL-1.1-MIT). You can use, self-host, and modify it freely for any purpose except offering it as a competing hosted service, and each release converts to the MIT license two years after it ships.

The edge bridge and the driver template are plain MIT, so you can build and ship machine drivers with no strings attached.