[Repository Transition → Archived]: HomeDevicesQoD

[albertoramosmonagas]

Transition Type

Sandbox → Archived

---

Problem description

This issue is raised as part of the unified clean-up process to evaluate whether the HomeDevicesQoD API repository should transition to “Archived” status (Phase D – Repository with Reviewed Release).

HomeDevicesQoD is currently a Sandbox API repository and has effectively reached end of life:

• The latest public release is v0.4.0 (r1.2), dated 6 September 2024.
• Since that release, the API has skipped at least two meta-releases (Spring 2025 and Fall 2025) without any new version or evolution.
• There is no meaningful activity in the repository after the release (no new issues or functional PRs; the last commit is a tooling/automation change).
• In the discussion on PR #75, the maintainers explicitly state that they do not plan to further evolve this API and that it is a candidate for archiving.

Given the lack of roadmap, the absence of functional activity after the last release, and the explicit statement from maintainers, HomeDevicesQoD appears to meet the criteria for Phase D in the clean-up process and to be a strong candidate for transition to “Archived”.

---

Expected action

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

1) Evaluation by API Backlog WG

Confirm that HomeDevicesQoD:

• Fits under Phase D – Repository With Reviewed Release (RC or ≥0.1.0+), and
• Meets the clean-up criteria (no post-release activity, no planned evolution, explicit maintainer statement).

If the evaluation confirms that HomeDevicesQoD qualifies as a Phase D candidate for archiving, the API Backlog WG is requested to proceed with the standard post-meta-release clean-up flow.

2) Standard post-meta-release clean-up flow

Once the evaluation is confirmed:

• Include HomeDevicesQoD in the post-meta-release clean-up review as a Phase D candidate, based on this issue.
• Notify the current code owners / maintainers via GitHub comment. Clearly state that the API is being considered for archiving under the clean-up process. Allow a 4-week window for any maintainer or CAMARA member to raise objections, propose a concrete evolution 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 alternative plan is agreed: Submit this transition request to the TSC with the recommendation to archive HomeDevicesQoD.
• Execution upon TSC approval: Once the TSC acknowledges/approves the archival decision:
  1. Archive the GitHub repository camaraproject/HomeDevicesQoD (read-only, archived badge).
  2. Update the API backlog entry for HomeDevicesQoD:
     • Change status to “Archived”.
     • Move it to the Archived section, preserving traceability.
  3. Update the CAMARA wiki page for HomeDevicesQoD:
     • Change lifecycle status from Sandbox to Archived.
     • Move or tag the page under the Archived APIs section.
  4. Update public-facing resources (API overview / resources page) so that HomeDevicesQoD is clearly marked as Archived and not presented as an active candidate for new adopters.

---

📋 Checklist for Archiving Repository

• API is no longer maintained or used
  The maintainers have explicitly stated that there are no plans to further evolve this API and that it is a candidate for archiving.

• No significant activity in the last 6–12 months (or declared sunset)
  Since the v0.4.0 release (r1.2, 6 September 2024), there has been no functional evolution of the API (only tooling/automation changes).

• A formal deprecation or retirement reason is provided
  The PR #75 discussion explicitly identifies the API as a candidate for archiving with no further evolution planned.

• Decision acknowledged by API Backlog WG

• Decision acknowledged by TSC

---

Additional context

• Repository: https://github.com/camaraproject/HomeDevicesQoD
• Latest release (v0.4.0 / r1.2): https://github.com/camaraproject/HomeDevicesQoD/releases
• PR discussion where archiving is proposed by maintainers: admin: migrate to centralized linting workflows HomeDevicesQoD#75

CC: @camaraproject/home-devices-qod_codeowners, @camaraproject/home-devices-qod_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
• No open issues or PRs to close (repository was already clean)
• Created PR for the README archival notice: Add archival notice to README HomeDevicesQoD#78

@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