-
Notifications
You must be signed in to change notification settings - Fork 3
oss: explain empty integrations/ vs Architecture diagram #38
Copy link
Copy link
Open
Labels
developer-experienceDX / contributor toolingDX / contributor toolingdocsDocumentation improvementsDocumentation improvementsdocumentationImprovements or additions to documentationImprovements or additions to documentationgood first issueGood for newcomersGood for newcomerspriority:P3Nice-to-have with real valueNice-to-have with real value
Description
Activity
Metadata
Metadata
Assignees
Labels
developer-experienceDX / contributor toolingDX / contributor toolingdocsDocumentation improvementsDocumentation improvementsdocumentationImprovements or additions to documentationImprovements or additions to documentationgood first issueGood for newcomersGood for newcomerspriority:P3Nice-to-have with real valueNice-to-have with real value
Problem
integrations/exists but is empty.docs/ARCHITECTURE.mdlayer diagram still lists Integrations (Skills / MCP / CI). PRODUCTION_READINESS P2-7 flags this drift. Contributors open the folder and find nothing.Repository evidence
integrations/directoryWhy it matters
Honest OSS layout: either a README that says “placeholder for CI Action / MCP — see ROADMAP” or remove the empty dir until the first integration lands (related: GitHub Action issue).
Proposed direction
Add
integrations/README.mdstating intent, pointing at ROADMAP + any new Action template issue, and clarifying MCP/Skills are not shipped. Optionally adjust Architecture one-liner to “planned.”Acceptance criteria
Difficulty
XS · docs · good first issue