RFC 86 Phase 5: Future Governance (DCO + License Scanning)

[jjgao]

Phase 5: Future Governance & Sustainability

Part of: #8
Phase 5 is post-switch governance (begins after Phase 4 #6). Exception: the DCO setup/enforcement task is pulled forward and tracked as a pre-switch gate item in #5, so no post-switch Apache-licensed commit lands without inbound sign-off.

Goal

Prevent the need for another relicensing effort. Establish lightweight, automated processes to protect the Apache 2.0 license going forward.

Tasks

• Developer Certificate of Origin (DCO) — enforce at or before the switch: Add a DCO check as a required branch-protection status check before merging the Switch Commit, or before accepting any further Apache-licensed contributions. Otherwise post-switch Apache-licensed commits can land without inbound sign-off. (Tracked as a gate item in RFC 86 Pre-Switch Sign-off Gate (blocks Phase 4) #5.)
  • Recommended tool: DCO GitHub App
  • Document sign-off flows for: command line, GitHub web edits, squash/rebase merges, and maintainer-applied patches.
• Automated license scanning — define the policy, not just the tool: Integrate FOSSA or Snyk into CI, and specify: scopes, allowed/denied licenses, transitive-dependency handling, exception-approval process, the responsible owner, and failure severity.
• Per-file SPDX / REUSE metadata + CI validation so mixed-license / vendored / generated files stay auditable over time.
• Update CONTRIBUTING.md: Document the DCO requirement and explain how to sign commits (git commit -s).
• Update PR template: Add a checklist item reminding contributors about DCO sign-off.
• Announce governance changes to the community.

Definition of Done

DCO check is live in CI and blocking merges without sign-off (in place by the Switch Commit, per #5). License scanning is active with a documented policy. Per-file SPDX/REUSE metadata is validated in CI. CONTRIBUTING.md and PR template are updated.

[jjgao]

Process review note: I’d move at least DCO enforcement before or into Phase 4, not after it. Otherwise there can be post-switch Apache-licensed commits without inbound sign-off.

Suggested additions:

• make DCO a required branch-protection status check before merging the switch commit or before accepting further Apache-licensed contributions
• document sign-off flows for command line, GitHub web edits, squash/rebase merges, and maintainer-applied patches
• define license-scanning policy, not just tool choice: scopes, allowed/denied licenses, transitive dependency handling, exception approvals, responsible owner, and failure severity
• consider per-file SPDX/REUSE metadata plus CI validation so mixed-license/vendor/generated files stay auditable