Skip to content

oss: explain empty integrations/ vs Architecture diagram #38

Description

@CodewithJha

Problem

integrations/ exists but is empty. docs/ARCHITECTURE.md layer diagram still lists Integrations (Skills / MCP / CI). PRODUCTION_READINESS P2-7 flags this drift. Contributors open the folder and find nothing.

Repository evidence

  • Empty integrations/ directory
  • ARCHITECTURE § layering Integrations row
  • ROADMAP MCP / Skills / GitHub Action (future)

Why 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.md stating 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

  • README or Architecture clarification so empty dir is intentional
  • Links to ROADMAP / CONTRIBUTING
  • No fake MCP server code

Difficulty

XS · docs · good first issue

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

developer-experienceDX / contributor toolingdocsDocumentation improvementsdocumentationImprovements or additions to documentationgood first issueGood for newcomerspriority:P3Nice-to-have with real value

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions