[Onboarding Tracker] MCPEnablement_PI1

[albertoramosmonagas]

This repository is intended to host the MCP server implementation contributed by Orange in the context of the CAMARA MCP Enablement initiative.

The repository will contain a provider implementation and does not define a new CAMARA API or a normative MCP specification. The detailed scope, supported capabilities, limitations and relationship with other CAMARA MCP activities must be documented in the repository README.md.

Provider Implementation repositories are normally created as sidecars of API Repositories and named _PI or _PIn.

For this specific contribution, MCPEnablement_PI1 has been agreed as the proposed repository name because the implementation relates to the transversal CAMARA MCP Enablement topic rather than to a single API Repository.

A documentation update may be required to clarify the naming and onboarding approach for this type of transversal Provider Implementation repository.

API Repository Information

• API Repository Name: MCPEnablement_PI1
• Sub Project (or "Independent"): Not applicable
• Mailing List: TBC
• Repository: MCPEnablement_PI1 (TBC)
• Wiki Page: Not applicable
• API Owner: @bigludo7 @ylesaout
• API Proposal: Not applicable
• Original Approval Issue: TSC decision last call 06-04
• License: Apache License 2.0 — pending final confirmation by the Orange IP team

⚠️ Progress to the next gate only after completing all items in the current one.

---

GATE 0 – Codeowner Validation (must be completed before repository creation)

• Code owner(s) nominated and confirmed by API Backlog WG
• Confirm that Orange can contribute the implementation under Apache License 2.0
• LF account active and Confluence access granted
• Subscribed to all@lists.camaraproject.org
• GitHub account active with notifications enabled
• Invitation to CAMARA GitHub Organization accepted
• EasyCLA validation successfully completed via test PR in camaraproject/EasyCLA

If Apache License 2.0 is not acceptable to Orange, the code should be hosted outside the CAMARA GitHub Organization and the relevant CAMARA documentation may point to the external repository.

Once all items are complete, repository creation can proceed.

---

GATE 1 – Repository Onboarding (infrastructure established)

• Repository created (LF Admin via automation)
• Update README.md in the repository with API details (API owner)
• (Optional) Nominate initial Maintainers (API owner)
• (Optional) Submit PR to update MAINTAINERS.md and CODEOWNERS

---

GATE 2 – Initial Codeowner Tasks (first activities within the repository)

• Confirm that the CODEOWNERS file is correct and up to date
• Update the Scope section within README.md to reflect the agreed API purpose
• Create the first GitHub issues (e.g. for drafting the initial API specification or defining next milestones)

---

Notifications:
CC: @camaraproject/admins @camaraproject/api-backlog_maintainers @camaraproject/marketing_maintainers

[ylesaout]

Hi,

I confirm that Orange allows us to publish the contribution under the Apache License 2.0

[hdamker]

@ylesaout welcome! I've sent you an invitation to the camaraproject organization. Please accept it and let us know if or when you have done the points listed under "Gate 0" ... I will then create the repository as agreed.

[ylesaout]

Hello @hdamker,

I have accepted the invitation to the camaraproject organization.
I also have also done all the Gate 0 tasks except the Confluence access. Could you indicate me how to proceed for this one ?

[hdamker]

I also have also done all the Gate 0 tasks except the Confluence access. Could you indicate me how to proceed for this one ?

Confluence is unfortunately not part of the LinuxFoundation SSO. Go to https://lf-camaraproject.atlassian.net/, create an Atlassian account (if you don't have one yet), and request to get (edit) access to the wiki. Ask the team at support@camaraproject.org in case of further questions.