Skip to content
brxtracPublic
forked from OpenDKG/.github

About

Shared community guidelines, contributor agreements, governance policies, and development standards for open-source projects.

Resources

Contributing

Stars

0 stars

Watchers

0 watching

Forks

 
 

Repository files navigation

OpenDKG — Shared Project Policies

This repository contains organization-wide contribution, governance and licensing guidance for the volunteer developers collaborating through OpenDKG.

Scope: Current and future repositories owned by OpenDKG, subject to the published licensing and repository-adoption rules. This .github repository is itself a covered repository; third-party and previously licensed material retain their original rights.

Documents

File Purpose
CONTRIBUTING.md Default contribution guidelines, DCO workflow and review expectations
CONTRIBUTOR_AGREEMENT.md Voluntary contributor copyright/license grant, adoption and pseudonymous acceptance
DCO.md Verbatim Developer Certificate of Origin 1.1 and sign-off instructions
GOVERNANCE.md Three-maintainer decisions, succession, project assets and security
LICENSE Apache License 2.0 for this repository's properly licensed materials

Other repositories need their own LICENSE file. GitHub's .github defaults can surface contribution guidelines but do not automatically distribute these policies or grant a license for another repository's code.

Adoption — not automatic

These are proposed model terms until explicitly adopted. The three founders must separately record their agreement to the initial governance policy, and each contributor must expressly accept the Contributor Agreement, with a reference to its exact commit SHA, before its additional terms can be relied on for that person. Acceptance may be public under a pseudonymous GitHub identity; an alias alone is not identity verification.

Use a dedicated GitHub issue or pull request to record each founder's exact acceptance statement and link it as the founding roster. Do not assume a merge, issue reaction, git commit -s, or joining the GitHub organization constitutes contractual consent. Past contributions need separate, specific permission where not already properly licensed.

No company or LLC is created by these documents, and they do not provide automatic personal-liability protection or guarantee legal enforceability in every jurisdiction. Obtain legal review for the actual countries involved before relying on them as contracts.

Automated membership validation

The membership automation guide explains the GitHub Actions intake checker, version-pinned consent receipts, and required human approval before an organization invitation. Form validation is not a legal-signature or membership approval. CLA checks for pull requests still require separate configuration.

Three equal cofounders

OpenDKG was started as a joint effort of three equal cofounders. The fact that @a-51-50 currently holds the initial GitHub Organization Owner role is technical setup, not sole-founder or sole-liability status. All three must personally accept the same versioned documents from their own GitHub accounts before the full council operates under this proposed governance. The other two can accept before accepting an organizational invitation.

Future non-founder members use the separate membership form. No one is automatically promoted to admin/Owner based on a form or comment. Equal cofounder status does not automatically transfer assets or divide statutory liability.

Joining and signing

OpenDKG uses a manual pre-invitation membership gate and a separate pull-request CLA check. These processes are not active solely because the templates are published.

  • Membership procedure — applicant acceptance, founder adoption, reviewer evidence and permission rules.
  • Membership agreement form — required acknowledgments referencing a fixed v1.0 policy revision.
  • CLA Assistant setup — external GitHub authorization and required checks for contributions across covered repositories.
  • PR template — contributor checklist, not a binding signature.

Activation requires adoption by all three founding maintainers and a human owner review before sending invitations. A separate CLA Assistant setup is still needed to gate PR merges.

Source references

About

Shared community guidelines, contributor agreements, governance policies, and development standards for open-source projects.

Resources

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages