DRAFT AGENDA
Attendees & Representation
TSC Members may indicate their attendance by marking an X in the column to the right.
Community members may use @name tag to mark their attendance below the table.
Representative | Organization | Role | |
---|---|---|---|
Deutsche Telekom AG | TSC Chair, Active Maintainer | ||
Deutsche Telekom AG | Active Maintainer | ||
Ericsson | Active Maintainer | ||
KDDI | Active Maintainer | ||
Orange | TSC Deputy Chair, Active Maintainer | ||
Radisys | EUC Representative | ||
Summit Tech | EUC Representative | ||
Telefonica | Active Maintainer | ||
Telefónica | Active Maintainer | ||
Verizon | EUC Representative | ||
Vodafone | TSC Deputy Chair | ||
Vodafone | Active Maintainer | ||
Vonage | Active Maintainer | ||
George Glass | TM Forum | TM Forum Representative | |
TM Forum | TM Forum Representative | ||
GSMA | GSMA Representative | ||
GSMA | GSMA Representative |
LF Staff:
Community:
Agenda
The project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF. |
- Review and approval of previous meeting minutes
- Action Items Review
- General Topics
- Governance & project management issues
- Release Management
- API Backlog
- Commonalities
- Identity & Consent Management
- Specific Topics
- Arazzo Specification discussion (Kevin Smith)
- Any Other Topics
Minutes
Review and approval of previous meeting minutes
- Minutes of previous TSC meeting: 2024-09-05 TSC Minutes
- ...
Action Item Review
- See home page Technical Steering Committee
- ...
Governance & Project Management issues
- Migration of wiki.telekom.de into Atlassian Cloud
- Was tentatively scheduled for August 29th ... any update? (Casey Cain )
- Sandbox/Incubated/Graduated/Archived proposal - new proposal for the lifecycle of API Repositories
- Issue in Governance to comment: https://github.com/camaraproject/Governance/issues/159
- Detailed proposal within Wiki: https://wiki.camaraproject.org/x/2IBFAg
- Comments from Jorge Garcia Hospital :
- Concern about the mix/confusion (outside of the CAMARA community) we can have between the status of the project vs the status of the API crafted.
- Need clarification of the role of supporter and then maintainer/codeowner. Jorge Garcia Hospital point is that we can have supporter and then no commitment to have Maintainers - project have the risk to stay stuck.
- Comments from Jorge Garcia Hospital :
Release Management (Tanja de Groot)
- Meta-release Fall24 - CAMARA Project - Confluence
- M5 declared, as announced on all mailing lists (https://lists.camaraproject.org/g/all/topic/camara_fall24_meta_release/108462715)
- Next release cycle ("Spring25") starts at September 30th (M0 - Kickoff)
- ....
API Backlog (patricia.serranogonzalez@telefonica.com Jorge Garcia Hospital )
- Repository for QualityByDesign created (as decided last meeting)
- ...
Commonalities (Rafal Artych )
- An issue is open to discuss the scope of the next version: Commonalities/issues/273 - scope should be closed for
- ...
Identity & Consent Management (Axel Nennker )
- An issue is open to discuss the scope of the next version: IdentityAndConsentManagement/issues/193 - scope should be closed for
- Chris Howell asked for more feedback on 'Replace Frontend Flow to unify consent collection and reduce latency' GitHub Issue
Specific Topic: Arazzo Specification discussion (Kevin Smith )
Any Other Business
- ...
Next Meeting
- Next TSC Meeting would be on October 3rd at 10:00 CEST / 8:00 UTC / 01:00 PST
- Specific agenda topics (backlog):
- ...
Action items
- ...