[Onboarding Tracker] ConnectivityQualityManagement

[hdamker]

A working group repository for the Sub Project Connectivity Quality Management, not for API development, but for traversal topics within the Sub Project. Initially for the joint work across QualityOnDemand, QoSBooking, and DedicatedNetworks on a whitepaper.

API Repository Information

• WG Repository Name: ConnectivityQualityManagement
• Sub Project (or "Independent"): ConnectivityQualityManagement
• Mailing List: sp-cqm
• Repository: https://github.com/camaraproject/ConnectivityQualityManagement
• Wiki Page: https://lf-camaraproject.atlassian.net/wiki/x/hAClB
• Codeowner: @tlohmar @Masa8106 @albertoramosmonagas @hdamker
• API Proposal: na
• Original Approval Issue: na

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

---

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

• all nominated codeowners are already onboarded in CAMARA and have codeowner roles in other repositories

Once all items are complete, repository creation can proceed.

---

GATE 1 – Repository Onboarding (infrastructure established)

• [ ] Update APIBacklog.md with status: Onboarding
• Request wiki page and mailing list - NA, existing in Sub Project
• Confirm mailing list creation - SP mailing list
• Confirm wiki page creation (LF Admin)
• Repository created (LF Admin via automation)
• Add repository link to the API wiki page (LF Admin) - not applicable
• Update README.md in the repository with API details (API owner)
• [ ] Update APIBacklog.md with status: Onboarded
• (Optional) Nominate initial Maintainers - union of the Maintainers of CQM repositories
• (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)
• Announce the start of development and share planned next steps via the API mailing list

Additional for new Independent Sandbox repositories:

• Agree on a regular meeting schedule with your team (via mailing list or initial call)
• Request a meeting link from support@camaraproject.org to be added to your recurring calendar invite
• Review and update the repository wiki page accordingly

---

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

[albertoramosmonagas]

Added to the backlog, but as an informational item, not a decision item (https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/757170180/2026-05-14+API+Backlog+Minutes#Other-topics) and also, should we add it to APIBacklog.md? I'd say no, just like we do with PI repositories, because it doesn't have an API and is only used as a working area.

WDYT?

[hdamker]

Agree that it isn't needed in the APIBacklog.md ... have removed the entries from the checklist.