[Onboarding Tracker] NetworkServiceAreas – service-areas API

[albertoramosmonagas]

API Repository Information

• API Repository Name: NetworkServiceAreas
• Sub Project: Connectivity Quality Management (CQM)
• Mailing List: CQM Sub Project mailing list
• Repository: TBC
• Wiki Page: TBC
• API Owner: @hubertp-ericsson, @eric-murray, @Masa8106, @jlurien
• API Proposal: N/A — repository separation approved under Sub Project management (see link)
• Original Approval Issue: Separate of dedicated-networks-areas API into its own repository #325

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

---

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

Note: Proposed codeowners are existing CAMARA contributors. Gate 0 items should be largely pre-satisfied. Verify and confirm individually before proceeding.

• Code owner(s) nominated and confirmed by API Backlog WG — proposed: @hubertp-ericsson, @eric-murray, @Masa8106, @jlurien
• LF account active and Confluence access granted (verify for all four)
• Subscribed to all@lists.camaraproject.org (verify for all four)
• GitHub account active with notifications enabled (verify for all four)
• Invitation to CAMARA GitHub Organization accepted (verify — all four are existing contributors)
• EasyCLA validation successfully completed (verify — likely already valid)

Once all items are complete, repository creation can proceed.

---

GATE 1 – Repository Onboarding (infrastructure established)

• Update APIBacklog.md with status: Onboarding
• Request wiki page under CQM Sub Project (email support@camaraproject.org)
• Confirm wiki page creation (LF Admin)
• Repository created from Template_API_Repository (LF Admin via automation)
• Add repository link to the CQM Sub Project wiki page (LF Admin)
• Update README.md in the new repository with API details (API owner)
• Update APIBacklog.md with status: Onboarded
• Submit PR to update MAINTAINERS.md — proposed: @hubertp-ericsson, @eric-murray, @Masa8106, @jlurien
• Submit PR to update CODEOWNERS — proposed: @hubertp-ericsson, @eric-murray, @Masa8106, @jlurien
• Update MAINTAINERS.md in the DedicatedNetworks repository to reflect reduced scope (removal of dedicated-network-areas)

---

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 (network service area discovery)
• Migrate dedicated-network-areas API artifacts from DedicatedNetworks repository to NetworkServiceAreas, renaming to service-areas
• Update DedicatedNetworks repository to remove dedicated-network-areas API artifacts and update README.md scope accordingly
• Create the first GitHub issues (e.g. for renaming, migration validation, and Sync26 release planning)
• Announce the start of development and share planned next steps via the CQM Sub Project mailing list
• Align with Release Management on Sync26 participation: confirm new repository and API name (service-areas v0.1.0) in releases-progress.yaml

---

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

[eharrison24]

Hello @albertoramosmonagas - I have started the process of creating the Wiki page. Once the onboarding process moves further along, I can add flesh out the wiki page. QQ: will NetworkServiceAreas have its own minutes page, or will it be tied to another minutes page? Appreciate the help.

[albertoramosmonagas]

Hi @eharrison24,

Thanks for starting the process, and good point, I have the same question. I'll pass it on to the owners (@hubertp-ericsson, @eric-murray, @Masa8106, @jlurien, @tlohmar). From my perspective, I understand that it will be a separate repository within CQM, but I'm asking for confirmation.

[tlohmar]

Hello,

thanks for moving this forward.

QQ: will NetworkServiceAreas have its own minutes page, or will it be tied to another minutes page? Appreciate the help.

It will be a separate repository within the CQM umbrella. I dont expect separate meetings (CQM breakout session) for the API. Thus, no need for a separate minutes page. @hdamker wdyt?

[albertoramosmonagas]

Any blocker to continue with the creation of the repository? CC: @hubertp-ericsson, @eric-murray, @Masa8106, @jlurien. To get in touch with @eharrison24 to create the wiki page and with @hdamker regarding the repository