[Repository Transition → Archived]: SiteToCloudVPN

[albertoramosmonagas]

Transition Type

Sandbox → Archived

---

Problem description

This issue is raised as part of the unified clean-up process to evaluate whether the SiteToCloudVPN API repository should be considered a Phase C – Repository With Partial Progress candidate for archiving or reassignment.

SiteToCloudVPN shows the following characteristics:

• Repository status

  • The repository camaraproject/SiteToCloudVPN exists with README, CODEOWNERS, and a YAML/API draft present.
  • The YAML has not undergone validation or formal review and remains in draft state.
  • The API has never participated in any CAMARA meta-release (no tagged releases, no meta-release alignment).

• PR and issue activity

  • There are 3 open pull requests, dated: 17 June 2024, 18 November 2024, and a later PR from an admin/bot (migration/automation), with no functional impact on the API definition.
  • There are 5 open issues in the repository.
  • Across these PRs and issues, there has been no substantive response or follow-up from the working group or the listed code owners.

• Working Group engagement

  • There is no observable activity from the WG (no feedback on issues/PRs, no visible progress on validation or design).
  • No evidence of SiteToCloudVPN being referenced in meta-release planning, validation tracks, or operator adoption.

In practice, SiteToCloudVPN is a repository with partial progress: the basic structure and YAML draft exist, but there is no validation, no release, no WG engagement, and no clear roadmap. This matches the criteria for Phase C – Repository With Partial Progress in the clean-up process and makes it a candidate for either archiving or transfer of ownership if a new sponsor steps in with a concrete evolution plan.

---

Expected action

This issue is intended first as an evaluation request and then as the trigger for the formal Phase C clean-up governance flow.

1) Evaluation by API Backlog WG

Confirm that SiteToCloudVPN:

• Fits under Phase C – Repository With Partial Progress (YAML present, but no release, no validation/evidence, no WG engagement).
• Meets the clean-up criteria for Phase C (inactivity, no validation assets, no meta-release participation, maintainers unresponsive).

The API Backlog WG is requested to evaluate whether:

• There is a realistic path forward (e.g. a new owner and concrete evolution plan), or
• The repository should be proposed for archiving under the unified clean-up process.

2) Standard post-meta-release clean-up flow for Phase C

Once the evaluation confirms that SiteToCloudVPN qualifies as a Phase C candidate:

• Post meta-release review: Include SiteToCloudVPN in the post-meta-release clean-up review as a Phase C repository with partial progress.
• Notification to code owners / maintainers:
  • Notify the current code owners / maintainers via GitHub comment (linking this issue).
  • Clearly state that the API is being considered for archiving or reassignment under the clean-up process.
• 4-week response window Allow for: Raise objections, propose a concrete evolution and validation plan, or take over ownership of the API. If no viable evolution plan or new ownership is proposed within that period, the archival recommendation stands.
• Escalation to TSC: After the 4-week window, and assuming no credible plan is agreed: Submit this transition request and the Phase C evaluation to the TSC with the recommendation to proceed with archiving SiteToCloudVPN.
• Execution upon TSC approval
  • Once the TSC acknowledges/approves the decision (archive vs. reassign):
    • If archived:
      1. Archive the GitHub repository camaraproject/SiteToCloudVPN (read-only, archived badge).
      2. Update the API backlog entry for SiteToCloudVPN:
         • Change status to “Archived”.
         • Move it to the Archived section, preserving traceability.
      3. Update any related CAMARA wiki page(s) for SiteToCloudVPN:
         • Change lifecycle status to Archived.
         • Move or tag the page under the Archived APIs section.
      4. Ensure public-facing resources clearly mark SiteToCloudVPN as Archived (or remove it from active API listings).
    • If reassigned: Document the new owners and agreed evolution plan in this issue and in MAINTAINERS.md, and keep the repo active, with updated roadmap and milestones.

---

📋 Checklist for Archiving Repository (Phase C candidate)

• API is no longer maintained or used
  There is no ongoing development, no responses from the working group or code owners to open PRs/issues, and no visible roadmap or validation activity.
• No significant activity in the last 6–12 months (or declared sunset)
  The last non-administrative PRs date back to mid/late 2024, and there has been no substantial progress on validation, releases, or WG alignment since then.
• A formal deprecation or retirement reason is provided
  The de-facto reason is lack of ownership, no WG engagement, no validation, and no meta-release participation. This issue documents that the API currently has no active sponsor or evolution path and is therefore being proposed as a candidate for archiving under the unified clean-up process.
• Decision acknowledged by API Backlog WG
• Decision acknowledged by TSC

---

Additional context

• Repository: https://github.com/camaraproject/SiteToCloudVPN
• Status summary:
  • YAML / API draft present but unvalidated
  • No releases tagged
  • No meta-release participation
  • 3 open PRs (no WG/owner response), 5 open issues (no WG/owner response)

CC: @camaraproject/site-to-cloud-vpn_codeowners, @camaraproject/site-to-cloud-vpn_maintainers, @camaraproject/admins, @camaraproject/api-backlog_maintainers, @camaraproject/marketing_maintainers

[albertoramosmonagas]

Decision accepted and adopted at the TSC meeting on 15 January 2026 with no objections.

[hdamker]

Progress update on archival preparation:

• Repository topic updated: added archived-api-repository, removed sandbox-api-repository
• Closed 6 stalled issues (new API proposal for Device management #30, NEW API Proposal _ Device Data Volume  #28, New API proposal-Verified Caller #27, Scope change for QoD API - Enhancement with provision mode #26, New Proposal - Steering of Roaming Management #24, New Proposal: Best Interconnection  #20) and 3 stalled PRs (New API proposal-Call Status API #29, Scope change within QualityOnDemand sub project - removed initial limitation to mobile #25, New Proposal - Customer Premise Equipment Management #21) with reference to this archival decision (this was done as preparation for a clean archival, not originally part of the checklist)
• Created PR for the README archival notice: Add archival notice to README SiteToCloudVPN#31

@albertoramosmonagas please review the PR and approve, I will merge and archive the repository. remaining afterwards are the update of APIBacklog.md and the move in the wiki