...
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 |
LF Staff:
Community: Ming Hui Foo Pierre Close Tanja de Groot Laszlo Suto Uwe Rauschenbach
...
- CAMARA Board Meeting on April 25th - short debrief (Herbert Damker )
- No questions or feedback about API backlog, Commonalities, Identity & Consent Management
- Release Management - Herbert mentioned need for additional Community Release Manager(s)
- API Sub Project Lifecycle - shortly introduced issues #122 and #129 - the Board general expressed support for the lifecycle stages
- EasyCLA vs Developer Certificate of Origin (DCO) - options presented and discussed, Board asked for time until next meeting
- In consequence EasyCLA deactivated also on QualityOnDemand repository (was activated for test purposes)
- Tendance is to go to DCO but not yet formal decision. Mark Cornall from GSMA recommends DCO has we know how it works already in several projets.
- DCO is not usual as several open source projets moved to this.
- New way to manage Maintainers of Sub project in teams and as members of github.com/camaraproject
- Aim is to improve the management of access rights regarding effort and reliability
- Proposed way, tested for QualityOnDemand
- Maintainers of all Sub Projects will be invited as members to the CAMARA GitHub organization
- For each Sub Project there will be a GitHub team
- can be mentioned in GitHub as @camaraproject/<respository-name>_maintainers
- can be added as reviewers to PRs within the Sub Project
- will have "triage" access within the Sub Project (only code owners have "write" access)
- The parent of all these teams is @camaraproject/maintainers
- Further changes to support the above:
- The CAMARA admin team will get owner of all MAINTAINERS.md and CODEOWNERS files
- A change of these will be approved and merged if the majority of the existing Maintainers in a Sub Project have approved the change request (exceptions for new Sub Projects)
- The MAINTAINERS.md files will get a new column "GitHub Name"
- Discussion
- Probably good opportunity to update the Maintainers list for each projet. This update will be done with a PR on all MAINTAINERS.md file.
API Backlog (Ricardo Serrano Gutierrez )
- Initial content:
- Status of migration to https://github.com/camaraproject/APIBacklog
- Active Issues have been migrated
- Old PRs will remain in the old repo and Ricardo will move them to the new one once approved and merged
- New PRs and Issues must be opened in the new repo (GSMA is aware of this)
- APIs in Pipeline
- No APIs for approval this time
- Update API-onboarding.md Governance PR#130 Will review the file and provide a new version with the upcoming updates
- API Backlog new table format APIBacklog issue#4 Ricardo is working on this
- Status of the setup of approved APIs (Most Frequent LocationMostFrequentLocation, DeviceVisitLocation, NetworkAccessManagement)?
- Herbert Damker regarding MostFrequentLocation & DeviceVisitLocation, there was in last TSC the decision to have two repositories, but on call/wiki page. https://lists.camaraproject.org/g/tsc/message/175 ist is stating that this was a misunderstanding. Proposal: create one Sub Project "LocationInsights" for both APIs as proposed in the message (the Sub Project can later decide if they need to carve out the APIs).
- Herbert Damker NetworkAccessManagement was waiting for confirmation of the Sub Project name. It this is given, the repository can be created tomorrow.
- Status of migration to https://github.com/camaraproject/APIBacklog
- Discussion:
- No opposition to "LocationInsights"& "NetworkAccessManagement" names from TSC
- Eric Murray On "IMEI Fraud", Helene from OGW Product team informed. If it will come back with support, it should go into an own repository. Henry Calvert will get into touch with the original API proposal owner.
- Device Swap work should begin shortly has we have a list of contributors. First task is to updated the MAINTAINERS.md file.
Commonalities (Shilpa Padgaonkar on behalf of Rafal Artych )
- Initial content:
- In the commonalities call on 29.04 2024-04-29 Commonalities WG Minutes, the scope of 0.4.0 has been finalized and includes the below topics
- Error responses
- Enhancement of Test Definitions
- Subscriptions
- Linting ruleset update
- Wildcard scopes
- Few other smaller issues
- Some issues have been labelled as backlog to keep them out of scope of 0.4.0
- Request to Camara members to actively participate in the call being arranged by TEF to discuss test definition enhancement. Slots have been added to Slack comms-wg channel https://camara-project.slack.com/archives/C063F56KT38/p1714469868024789.
- Request to Camara members to review the subscriptions PR
- In the commonalities call on 29.04 2024-04-29 Commonalities WG Minutes, the scope of 0.4.0 has been finalized and includes the below topics
- Discussion:
- Need to update the issue containing the scope (Herbert Damker to support here in absence of Rafal).
Identity & Consent Management (Axel Nennker )
...