Summary
Two of the seven full-plugin-style tool repos do not carry a CONTRIBUTING.md file at all:
- TMHSDigital/CFX-Developer-Tools
- TMHSDigital/Unity-Developer-Tools
The remaining seven plugin-style tool repos (Blender, Docker, Home-Lab, Mobile-App, Monday, Plaid, Steam-Cursor) and the steam-mcp companion repo all have one. The scaffold under Developer-Tools-Directory now emits a complete CONTRIBUTING.md (post-DTD#41), so any new repo created from the scaffold will land with the file. The two missing repos are pre-scaffold-update legacy state.
Surfaced during
DTD#46 parallel batch. The session backfills the DCO + inbound license grant section into every tool repo's CONTRIBUTING.md per standards/licensing.md. CFX and Unity have no file to backfill into.
Why this is its own issue
Creating a CONTRIBUTING.md from scratch is a separate scoping question from "add a section to an existing one." Decisions needed:
- Use the scaffold's CONTRIBUTING.md.j2 as the source of truth, render it for each repo, and commit the rendered output. Pros: byte-for-byte alignment with the new ecosystem standard. Cons: each rendered file inherits scaffold-default sections (Adding a Skill, Adding a Rule, MCP-tool patterns) that may not be accurate for repo-specific content patterns.
- Hand-author a minimal CONTRIBUTING.md per repo, including only the DCO section + repo-specific contribution flow. Pros: accurate to each repo's actual patterns. Cons: per-repo design work, drift risk vs the scaffold over time.
- Render scaffold default and then hand-edit per repo. Hybrid; closest to what the scaffold would produce for a brand-new repo, then trimmed to fit reality.
Recommend Option 3, but the choice should be made deliberately, not as a side-effect of DTD#46.
Scope
- Decide on Option 1, 2, or 3 above.
- Render or hand-author CONTRIBUTING.md for CFX-Developer-Tools.
- Same for Unity-Developer-Tools.
- Two PRs, can be canary-then-parallel since the diff template is identical once Option chosen.
- Confirm DCO section in both matches the verbatim text from
standards/licensing.md.
Out of scope
- DTD#46 (DCO backfill across repos that already have CONTRIBUTING.md). That session proceeds without CFX/Unity.
- DTD#47 (paths-ignore correction). Independent.
- steam-mcp's missing release.yml. Different structural question.
Estimate
~30 to 45 minutes once the Option 1/2/3 decision is made. The actual file-creation is small; the design call is the slow part.
Summary
Two of the seven full-plugin-style tool repos do not carry a
CONTRIBUTING.mdfile at all:The remaining seven plugin-style tool repos (Blender, Docker, Home-Lab, Mobile-App, Monday, Plaid, Steam-Cursor) and the steam-mcp companion repo all have one. The scaffold under Developer-Tools-Directory now emits a complete CONTRIBUTING.md (post-DTD#41), so any new repo created from the scaffold will land with the file. The two missing repos are pre-scaffold-update legacy state.
Surfaced during
DTD#46 parallel batch. The session backfills the DCO + inbound license grant section into every tool repo's CONTRIBUTING.md per
standards/licensing.md. CFX and Unity have no file to backfill into.Why this is its own issue
Creating a CONTRIBUTING.md from scratch is a separate scoping question from "add a section to an existing one." Decisions needed:
Recommend Option 3, but the choice should be made deliberately, not as a side-effect of DTD#46.
Scope
standards/licensing.md.Out of scope
Estimate
~30 to 45 minutes once the Option 1/2/3 decision is made. The actual file-creation is small; the design call is the slow part.