Backfill DCO + inbound license grant into CONTRIBUTING.md across existing tool repos #46
Description
Per standards/licensing.md, every CONTRIBUTING.md in the ecosystem must carry the inbound DCO + license grant section (verbatim grant paragraph plus Signed-off-by: guidance). The scaffold now emits this in newly created repos as of #45, but the nine existing tool repos predate that change and do not carry the section.
Affected repos
Each needs a small PR adding the DCO section to CONTRIBUTING.md:
- TMHSDigital/Plaid-Developer-Tools
- TMHSDigital/Stripe-Developer-Tools
- TMHSDigital/Cursor-IDE-Developer-Tools
- TMHSDigital/Cloudflare-Developer-Tools
- TMHSDigital/Notion-Developer-Tools
- TMHSDigital/Home-Lab-Developer-Tools
- TMHSDigital/Hugging-Face-Developer-Tools
- TMHSDigital/Microsoft-Developer-Tools
- TMHSDigital/Blender-Developer-Tools
Canonical text
The exact CONTRIBUTING.md section to copy is now in scaffold/templates/CONTRIBUTING.md.j2 after #45. Tool repos can also reference standards/licensing.md for the rationale.
Related
- Closing scaffold drift: emitted output not aligned with current ecosystem patterns #41 added DCO to the scaffold. This issue tracks ecosystem backfill.
- Some tool repos already have separate DCO bot enforcement on PRs; the textual section in CONTRIBUTING.md is the missing piece.
Estimate: ~10 minutes per repo, batchable into one tool-repo session.
Activity
TMHSDigital commentedon Apr 26, 2026
DCO and inbound license grant section backfilled across the tool repo fleet per
standards/licensing.md.Canary
Parallel batch (7 PRs, all merged)
Skipped (filed as DTD#48)
DTD#48 tracks creating CONTRIBUTING.md in those two repos with the DCO section included from the start.
Audit trail and follow-ups
DTD#47 separately tracks the systemic
paths-ignoreinconsistency that caused 6 of the 8 backfill commits to land without firing release-doc-sync. Once DTD#47 lands, the next non-md change in each silent repo will trigger release-doc-sync and the CHANGELOG will pick up the previous DCO commit by reference. In the meantime, the squash-merge SHA per repo is the durable audit record.Compliance status
Of 10 tool repos, 8 are now compliant with
standards/licensing.md(CONTRIBUTING.md contains the verbatim DCO grant + Signed-off-by guidance). 2 remain non-compliant pending DTD#48 (the file does not exist).