DRAFT AGENDA
...
| 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 | ||
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 | X |
TM Forum | TM Forum Representative | ||
GSMA | GSMA Representative | X | |
GSMA | GSMA Representative | X | |
Airtel | Active Maintainer |
...
Community: Ming Hui Pierre Close Tanja de Groot Laszlo Suto Uwe Rauschenbach Ramesh Shanmugasundaram
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. |
...
- Initial content:
- PR121 https://github.com/camaraproject/IdentityAndConsentManagement/pull/121 merge is currently pending due to the purpose issue discussion. WG-Members are currently planning to setup an adhoc call to discuss this in detail on the possible solutions/options available. Axel Nennker is on vacation until 01.05. He will reach out to setup a slot after he is back.
- Discussion: No comments.
Release Management (Tanja de Groot Samuel Adeyemo )
- Initial content:
- M0: was approved on 2024-04-18, but announcement still needs to be sent. Check draft M0 announcement here: Release Management announcements - sending of the M0 announcement is dependent on the finalization of the API release tracker page.
- M1: Proposal to shift by 2 weeks to 2024-05-15, but this is maybe not sufficient as holidays in many countries. Means one month delay wrt standard schedule.
- This is challenging as we do not have yet PR for some main commonalities point as Test Definition topic.
- Request to Kevin Smith to create a specific repository for SimpleEdgeDiscovery API from Edge Cloud project.
- M2 will likely also shift by 2 weeks
- M3: shifts with the M1 date
- Other milestones: no change
- API Sub-projects should start to prepare the release assets for their APIs for release and align with Commonalities and ICM AS OF TODAY. When can an alpha release for Commonalities & ICM be created ?
- Commonalities & ICM are asked to create an alpha-release at least two weeks before the release candidate at M2 milestone.
- In the general meta-release schedules: moved M2 one week earlier and M3 one week later.
- Process definition status:
- Updates the milestone table with new format and clarified actions - near final
- Update of process descriptions near final;
- API readiness checklist to be finalized .(will be done in Release Management repository)
- Discussion:
- One stop documentation is the Release Management home page here: Release Management Working Group - CAMARA Project - Confluence
Sub Project Lifecycle proposals (Herbert Damker )
...