...
Community members may use @name tag to mark their attendance below the table.
| Representative | Organization | Role | |
|---|---|---|---|
Deutsche Telekom AG | TSC Chair, Active Maintainer | x | |
Deutsche Telekom AG | Active Maintainer | x | |
Ericsson | Active Maintainer | ||
KDDI | Active Maintainer | x | |
Orange | TSC Deputy Chair, Active Maintainer | x | |
Radisys | EUC Representative | ||
Summit Tech | EUC Representative | ||
Telefonica | Active Maintainer | x | |
Telefónica | Active Maintainer | x | |
Verizon | EUC Representative | ||
Vodafone | TSC Deputy Chair | x | |
Vodafone | Active Maintainer | x | |
Vonage | Active Maintainer | ||
| George Glass | TM Forum | TM Forum Representative | |
TM Forum | TM Forum Representative | ||
GSMA | GSMA Representative | x | |
GSMA | GSMA Representative | x |
LF Staff:
Community: Axel Nennker Ming Hui Foo Pierre Close Bart van Kaathoven Guang-Han Ma Rafal Artych Ricardo Serrano Gutierrez Samuel Adeyemo Laszlo Suto
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
- API Backlog
- Commonalities
- Identity & Consent Management
- Release Management
- Specific Topics
- ...
- Any Other Topics
...
- Minutes of previous TSC meeting: 2024-05-16 TSC Minutes
- ...No comments - Approved
Action Item Review
- See home page Technical Steering Committee and 2024-05-16 TSC Minutes
...
- EasyCLA vs Developer Certificate of Origin (DCO) (Casey Cain )
- Debrief from CAMARA Board Meeting and leadership call CAMARA / LF / GSMA
- GSMA / LF Catch-up (June 5th) - push to use EasyCLA but no decision at this stage. We need
- "Codeowner" and "Maintainer" for the Governance repository (#138) (Herbert Damker)
- Process to change content in https://github.com/camaraproject/Governance is currently not defined, especially for important changes of ProjectCharter and other Governance documents
- Nevertheless it is clear that changes are in the responsibility of the TSC
- Proposal:
- Chair and Co-Chair of TSC as "Codeowners"
- All TSC Participants as "Maintainers", following the same rules like in Sub Projects
- Creating a GitHub team "TSC_participants" for this purpose (which can be used to request input on issues or reviews on relevant PRs)
- Process to change content in https://github.com/camaraproject/Governance is currently not defined, especially for important changes of ProjectCharter and other Governance documents
...
- Release 0.4.0-alpha.1 - https://github.com/camaraproject/Commonalities/pull/222
- API testing guidelines
- Device object definition - https://github.com/camaraproject/Commonalities/issues/171
...
- Progress of meta-release plan: Meta-release Fall24. 1 API was added2 APIs were added.
- Commonalities and ICM M1 shifting into June; M2 still kept on 15/06
- Commonalities and ICM may have to prioritize the closing of main functional/technical issues or decide to move to next meta-release in order to reach an alpha release ASAP.
- Release Management issues status: see 2024-06-04 Release WG Minutes
- The API release tracking page has been added to all API Sub Projects (thanks to Casey)
- For new Sub Projects this page will be automatically created in the Confluence page structure. The RM documentation needs to be updated accordingly.
- API Sub Projects can create their API tracker(s) by clicking on the button on the API Release Tracking page and following the guidelines. There should be one tracker for each API and its version they plan to publish in the meta-release
- Updated API-Readiness-Checklist PR available for review: Add API-Readiness-Checklist.md to RM project
...