[Onboarding Tracker] ConsentManagement

[albertoramosmonagas]

API Repository Information

• API Repository Name: ConsentManagement
• Sub Project (or "Independent"): Independent Sandbox
• Mailing List: wg-icm@lists.camaraproject.org
• Repository: https://github.com/camaraproject/ConsentManagement
• Wiki Page: TBD - Taxonomy (proposed): Service Management
• API Owner: @jpengar @AxelNennker @sebdewet (code owners of ICM)
• API Proposal: Add Scope Enhancement for Consent Info API (Consent Management API) — Controlled Delegation #277
• Original Approval Issue: Evolution of Consent Info API to support Controlled Delegation #276

More context:

• Minutes from ICM group, issue en el repo ConsentInfo: Evolution of Consent Info API — Controlled Consent Capture Delegation ConsentInfo#42 on ConsentInfo repo, TEF's proposal & current draft PR.
• Decision taken on the last TSC (12/18)

⚠️ 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
• 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

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 (email support@camaraproject.org, specify details)
• Confirm mailing list creation (only if Independent Sandbox) (LF Admin)
• Confirm wiki page creation (LF Admin)
• Repository created (LF Admin via automation)
• Add repository link to the API wiki page (LF Admin)
• Update README.md in the repository with API details (API owner)
• Update APIBacklog.md with status: Onboarded
  - [ ] (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)
• 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]

Hi @jpengar,

onboarding tracker created regarding with the decisions taken on the last TSC meeting (12/18). Before starting the onboarding process, we need to confirm the Gate 0 fields with you and also ask if there are any other code owners, as well as any other fields you consider relevant to the description.

[jpengar]

Hi @jpengar,

onboarding tracker created regarding with the decisions taken on the last TSC meeting (12/18). Before starting the onboarding process, we need to confirm the Gate 0 fields with you and also ask if there are any other code owners, as well as any other fields you consider relevant to the description.

@albertoramosmonagas Thanks for setting up the onboarding tracker!

The Repository Name should be ConsentManagement. This follows the convention of naming the repository after the API (the proposed API name is consent-management).

As discussed, this should be an independent repository. This approach will facilitate easier management, versioning, and releases.

Regarding Codeowners, for now, please assign the ICM (Identity and Consent Management) codeowners, similar to the setup in ConsentInfo. We can update this in the future if necessary.

Regarding the Gate 0 requirements, all the necessary checks are currently met (I think)

Please let me know if you need any specific additional information to proceed.

[hdamker]

• Create a subproject that encompasses ConsentInfo and ConsentManagement (name to be chosen and confirmed by the owner).

@albertoramosmonagas thanks for the onboarding tracker! The onboarding should be straightforward, as we can copy most from ConsentInfo. Just the note that there won't be a Sub Project for the two repositories for now, as the decision was that they are both under the supervision of the ICM working group. We can reconsider that when the API repositories enter the Incubating stage but for now I would leave it as is.

@jpengar agreed regarding gate 0, I have ticked the points off and updated the codeowners and mailing list in the description. Only open point is the wiki page, but that doesn't block me to create the repository.

[hdamker]

@jpengar Repository created: https://github.com/camaraproject/ConsentManagement. Please request the wiki page, be specific where it should be located.

[eharrison24]

Hi @jpengar - I will go ahead and create the mailing list, however please let me know where you would like the wiki page to be located. I will try my best to get both the mailing list and wiki page created for you today, but today is my last day before the holidays - won't be back until January. If I do not hear from you before EOD, at the least I will have the mailing list created.

Best,
Evan

[eharrison24]

Hi Everyone,

I must have missed a lot! I saw the most recent response from Herbert and assumed the mailing list ha not been created yet - seems like it has already been set up! Perfect! As for the wiki page - please let me know @jpengar

Best,
Evan

[hdamker]

I must have missed a lot! I saw the most recent response from Herbert and assumed the mailing list ha not been created yet - seems like it has already been set up! Perfect! As for the wiki page - please let me know @jpengar

Hi @eharrison24 you missed nothing, I suppose. The repository is under supervision of the ICM working group and is using their mailing list (same as ConsentInfo already is doing).