...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Attendees & Representation
...
| Representative | Organization | Role | |
|---|---|---|---|
Deutsche Telekom AG | TSC Chair, Active Maintainer | x | |
Deutsche Telekom AG | Active Maintainer | x | |
Ericsson | Active Maintainer | x | |
KDDI | Active Maintainer | x | |
Orange | TSC Deputy Chair, Active Maintainer | x | |
Radisys | EUC Representative | x | |
Summit Tech | EUC Representative | ||
Telefonica | Active Maintainer | x | |
Telefónica | Active Maintainer | x | |
Verizon | EUC Representative | x | |
Vodafone | TSC Deputy Chair | x | |
Vodafone | Active Maintainer | ||
Vonage | Active Maintainer | x | |
| George Glass | TM Forum | TM Forum Representative | |
TM Forum | TM Forum Representative | ||
GSMA | GSMA Representative | ||
GSMA | GSMA Representative | x |
...
- Review and approval of previous meeting minutes
- Action Items Review
- General Topics
- Governance & project management issues
- API Backlog
- Commonalities
- Identity & Consent Management
- Release Management
- Specific Topics
- ...
- Any Other Topics
...
- New proposal how to manage "API Families" as Sub Projects with one lead repository and multiple API "family member" repositories (#142)
- Herbert Damker Proposal changed based on the feedback within the comments: no "lead repository" for a Sub Project, but a Sub Project / API Family will be a set of 1 to n equal repositories to describe, develop, document and test the APIs (family members). The link between the repositories is the home page of the Sub Project within the wiki
- Pull request to be reviewed: https://github.com/camaraproject/Governance/pull/146
- Ask for formal vote from the TSC: No... but we keep it open for next week. Will be merged by end of next week if no objections arise.
- Proposal for new API Project lifecycle approach (Sandbox + Incubated) (#129)
- Herbert reminds us the advantages of this proposal to have some flexibility to onboard easily new project.
- Next step: details out this.
- Herbert reminds us the advantages of this proposal to have some flexibility to onboard easily new project.
...
- 15 APIs proposed for the Fall24 meta release so far. All are currently target initial versions (v0.x) as public release. Possibly 1 or 2 may be proposed as stable public releases (NumberVerification and SimSwap)
- Third candidate for stable: OTPvalidationAPI
- Jose Luis Urien Pinedo : We will have a discussion also in device location for some API to promote for stable.
- Herbert: We can decide moving forward during the release cycle.
- Tanja: till we can decide to promote or not to stable
- Promoted API to stable should have live implementation (of previous released version) as listed here, and only reasonable amount of changes since then
- As a reminder checklist table is within GitHub (API-Readiness-Checklist.md) and more details here within wiki.
- Updated CHANGELOG_TEMPLATE and example PR available for review: https://github.com/camaraproject/ReleaseManagement/pull/36
- Question: How to proceed with the existing template in Commonaltities? Herbert's proposal: proceed as same way as we did it for the checklist
- Release management issues closed. One pending PR review, one issue as backlog item remaining.
- Tanja de Groot added that we can create 'public release' outside of meta release → This possibility has been documented.
- Upcoming tasks: start looking at the APIs proposed for the meta-release.
...