Skip to content

Bitcoin accepted at checkout  |  Ships from Laval, QC, Canada  |  Expert support since 2016

Contribute to DCENT_OS & the D-Central Open-Source Stack

Quick answer

How do I contribute to DCENT_OS?

We build on open protocols and open predecessors, so our own firmware and tools are open too. If you want to shape where DCENT_OS goes, the door is open — and being early is an advantage, not a barrier.

The repos

Everything lives under github.com/DCentralTech, GPL-3.0:

How to send a change

  1. Read the repo’s CONTRIBUTING.md and CODE_OF_CONDUCT.md — and GOVERNANCE.md / SECURITY.md if your change touches process or security.
  2. Fork the repo and clone your fork, then branch off main:
git clone https://github.com/<you>/DCENT_OS
cd DCENT_OS
git checkout -b my-fix
  1. Build and test it yourself — the README has a tiered “test it yourself” path and platform docs. If you can flash it in the browser at /flash/, you can validate a firmware change end-to-end.
  2. Commit, push your branch, and open a pull request against main describing what and why.
  3. Found a bug you can’t fix? Open an issue on the repo — a clear, reproducible report is a real contribution.

Licensing & credit

DCENT_OS is GPL-3.0: contributions are licensed under the same terms as the project (inbound = outbound), and upstream projects we build on are credited in each repo’s THIRD_PARTY_NOTICES.md. Security issues: use the repo’s SECURITY.md process rather than a public issue. Not a coder? The most useful non-code contribution is a precise bug report or a field report from real hardware.

Open the GitHub org →

Related: Build With D-Central (API + data + OSS index) · DCENT_OS · web flasher · the sovereign stack.