...
| Representative | Organization | Role | |
|---|---|---|---|
Deutsche Telekom AG | TSC Chair, Active Maintainer | ||
Deutsche Telekom AG | Active Maintainer | ||
Ericsson | Active Maintainer | ||
KDDI | Active Maintainer | ||
Orange | TSC Deputy Chair, Active Maintainer | ||
Radisys | EUC Representative | ||
Summit Tech | EUC Representative | ||
Telefonica | not Active Maintainer | ||
Tnot removedelefónica | Active Maintainer | ||
Verizon | EUC Representative | ||
Vodafone | TSC Deputy Chair | ||
Vodafone | Active Maintainer | ||
Vonage | Active Maintainer | ||
| George Glass | TM Forum | TM Forum Representative | |
TM Forum | TM Forum Representative | ||
GSMA | GSMA Representative | ||
GSMA | GSMA Representative |
LF omLF Staff:
Community:
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. |
...
- EasyCLA Introduction (Casey Cain )
- Concerns of the EasyCLA deployment have been resolved.
- Suggested that we deploy EasyCLA on or
- LF Staff will be on standby to resolve any last-minute issues
- 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
...
- Release 0.4.0-rc.1 - in preparation
- All PRs missing in alpha merged, new fixes proposed (PR#229, PR#234, PR#236, PR#238)
- Device object simplification https://github.com/camaraproject/Commonalities/pull/233:
Apply the mechanism to rely on the access_token (not providing the device object in the API request) for 3-legged access scenarios - Annex to API Design Guidelines
networkAccessIdentifier not removed from Device object, but not allowed in Commonalities 0.4.0 (Fall24 release)
- Please review this PR
- Device object simplification https://github.com/camaraproject/Commonalities/pull/233:
- Target is to agree the RC.1 during Commonalities call on 24th of June and publish it during the week.
- All PRs missing in alpha merged, new fixes proposed (PR#229, PR#234, PR#236, PR#238)
Identity & Consent Management (Jesús Peña on behalf of Axel Nennker )
...