...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
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 | ||
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 | X | |
GSMA | GSMA Representative | X | |
GSMA | GSMA Representative | X | |
Airtel | Active Maintainer |
...
- 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
- Sub Project Lifecycle proposals
- Any Other Topics
...
- (For the list of open action items go to home page of Technical Steering Committee) - Action Items are currently not working?
- Alternatively we can look on 2024-04-18 TSC Minutes or copy them over to here
- No comments/questions
- Open Action Items from last TSC Minutes copied over and updated within Action Item section below.
- Alternatively we can look on 2024-04-18 TSC Minutes or copy them over to here
...
- 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 )
...
- https://github.com/camaraproject/Governance/issues/124 - help project to adapt to new README.md file Casey Cain (16 May 2024)
- https://github.com/camaraproject/WorkingGroups/issues/336 - create sub project repository, mailing list and wiki page for "Location Insights" Herbert Damker Casey Cain (09 May 2024)
- https://github.com/camaraproject/WorkingGroups/issues/378 - create sub project repository, mailing list and wiki page for "Network Access Management" Herbert Damker Casey Cain (09 May 2024)
- Identify & Consent Management - create scope definition and target version for M1 milestone Axel Nennker (09 May 2024)
- Project management - open a discussion issue if all CAMARA meeting should be anchored on UTC time zone Herbert Damker (16 May 2024)
...