OpenDKG is a small, independent open-source initiative building useful software, connectors, automation, bots and tools that make existing technologies easier to use. DKG, Blackbox and other integrations are optional, where they provide a practical benefit.
This repository contains public project-wide policies and contribution guidance. Internal working drafts, founder finances, meeting notes and planning belong in the private OpenDKG/handbook repository, not here.
| Document | Purpose |
|---|---|
| GOVERNANCE.md | Founding governance and project decision rules |
| CONTRIBUTOR_AGREEMENT.md | Contributor rights and permissions |
| CONTRIBUTING.md | How to contribute code, documentation and tests |
| DCO.md | Developer Certificate of Origin and sign-off text |
| MEMBERSHIP.md | How new non-founder members request access |
| LICENSE | License for the applicable material in this repository |
The three original founders (@a-51-50, @dreddster and @brxtrac) recorded their personal acceptance of Governance and Contributor Agreement v1.0 at the pinned revision in Issue #3. That issue is closed with the founders:agreement-complete label. This records GitHub-account declarations; it is not independent legal identity verification or a cross-border legal contract.
- Submit a pull request: Read CONTRIBUTING.md, check the target repository's own license, and follow its review and CLA/DCO requirements.
- Apply to become an organization member: Follow MEMBERSHIP.md. Applications are public GitHub issues; never post private identification, contact or financial details.
- Configure CLA checks as a maintainer: See CLA_SETUP.md. This is a technical setup guide, not a replacement for consent or human review.
No repository or contributor automatically gains extra rights through an organizational link. Each project retains its own license and documented maintainer responsibilities.
GitHub Actions may validate the format of membership acknowledgments and monitor changes to the founding acceptance evidence; they do not grant permissions or make legal determinations. Project owners manually approve access.
Changes to already accepted governance or contributor terms require a separately agreed and clearly versioned update. Older accepted documents and GitHub records must not be silently replaced.