2024-04-11 API backlog minutes
Attendees
Organization | Name |
Orange | @Ludovic Robert @Sylvain MOREL |
Charter Communications | @Christopher Aubut |
Telefonica | @Jorge Garcia Hospital Ignacio Dominguez |
Vodafone | @Eric Murray |
Vodafone | @Kevin Smith |
Ericsson | @Jan Friman |
AT&T | @Pierre Close |
DT | Noel Wirzius |
Agenda Proposal
Approval of minutes of last conf. call
Recent Updates & Recap
Review of Action Points
Discussion
OGW Drop #3 APIs: #375 (Device Quality Indicator)
Other APIs: #351 (Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement), #372 (Receive SMS), #395 (Carrier Wholesale Pricing), #395 (Steering of Roaming Information)
Governance: #367 (Structures and roles, RACI, Maintainers initiative)
Closing Issues
Action Points
AOB
Q&A
Antitrust Policy
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 LinusFoundation. |
 |
New Procedures in API Backlog WG meetings
A number of improvements are under discussion with leadership team of OGW project (Henry), CAMARA Project (Markus), Product Definition WS (Helene) and TSC (Herbert). As of today, the WG adopted agreements are three:
To close the agenda SEVEN DAYS BEFORE the conf. call.
In case a WG participant wants to include a point in the agenda (e.g., present a new API proposal), this participant shall ensure the corresponding issue is opened in Github by then.
Exceptional situations will be treated separately.
New schedule of conf. calls **The meetings are to be held by Linux Foundation (Links available at GitHub and Confluence Backlog front pages)
2nd Thursday of the month (10-11 CET)
4th Thursday of the month (15-16 CET)
Send agenda to TSC mail list, to encourage more TSC member companies to join the call and provide comments when they identify APIs which are of interest for them.
Meeting Minutes within Wiki instead of Github
CAMARA community agreed that meeting minutes would only be recorded in the wiki
Approval of minutes of last conf. call
Minutes of last API backlog WG call available here
DECISION: Approved
Recent Updates & Recap
TSC meeting 5th April:
The API Backlog subgroup will have its own github repo. Initial Maintainers have been requested. Those of you that have been active within the last meetings have received an email requesting for comitment/refusal:
There was no time to treat the API proposals.
Only CPE management: Need to decide the name and transmit this to the TSC for the subproject to be created (offline) → The TSC is aware of the proposal: Home Devices - Network Access Management
Other topics
In the sake of the health of the CAMARA group, so that the projects do not lose their activity as soon as they are born, it will be proposed that in order to approve new API proposals, these must be supported by at least 3 companies (MNO or suppliers indistinctly). An issue will be opened within governance encompassing this.
Backlog table
Table updated in PR#406
Review of Action Points
AP # | AP Owner | AP description | Related issue | Due date | Status |
20230208-02 | WG delegates | Delegates from interested parties to prepare a list of questions for this API, for Nick to answer them. | 2024/02/21 | Open | |
20230208-01 | Centilion | To draft a simple figure illustrating the API logic with a high-level workflow, and attach it to the PR. | 2024/02/21 | Open | |
20240314-01 | Governance | Ricardo to share the RACI in the issue 367 comments, after making CAMARA specific document and validation by TSC | 2024/03/14 | Open | |
20240327-01 | Telefonica | Jorge to reopen the PR#337 and change the Proposal name (Most Frequent Location) and add the new supporters (TIM) | Mar 27, 2024 | Closed | |
20240327-02 | Ricardo | Propose to SMS (ShortMessageService) Subproject-owners integrating ReceiveSMS API proposal in the existing SMS (ShortMessageService) Subproject to create a new API family before moving to tsc | Mar 27, 2024 | Done within Issue #9 · camaraproject/ShortMessageService |
Discussion
Current Issues
Centillion | New Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement | The issue was not treated in this conference call
The issue is not eligible to be closed yet. DECISION: not treated | |
Governance | Adapt Project StructuresAndRoles.MD to changes in API backlog table (reduction of comments) | The RACI was presented to the TSC and there was no objection anyhow explicit approval is not reflected in the TSC Minutes 21/03 It is assumed RACI and so new WoW as approved This way of work have been firstly adopted by the QoD subgroup which is proposing a scope change in the Working Group issues (#404 and #403) which may be treated in the next conference call The API Backlog subgroup will have its own github repo. Initial Maintainers have been requested. Those of you that have been active within the last meeting have received an email requesting for commitment/refusal: Ricardo is currently working on modeling a new table The issue is not eligible to be closed yet. | |
Totogi | New Proposal: Receive SMS |
The issue is not eligible to be closed yet. DECISION: not treated | |
Deutsche Telekom | New Proposal: Device Quality Indicator | Noel proposed Device Status subgroup to integrate their APIs within Noel's. Noel to make the proposal to the API Backlog and provide update The issue is not eligible to be closed yet. ACTION: AP: Noel updating proposal with new fields. Start in parallel while device status API is split | |
TelecomsXChange | New Proposal: Carrier Wholesale Pricing First YAML avaliable here | The issue was not treated in this conference call The issue is not eligible to be closed yet. DECISION: not treated | |
Netfocusin Technologies | New Proposal: Steering of Roaming Management | Does not seem to be in the Scope of Camara. DECISION: Discuss this in the next meeting (whenever Netfocusin Technologies is able to connect) | |
Telefonica&DT | Scope Change: QoD API The API template is available in PR#403 | Noel: (mobileQoD to QoD change) Consider the combination or relationship between QoD and CPE/Home Devices subproject Eric: (provision) difficult to ensure a pfile characteristic (throughput, latency) for a long time. Let's discuss in the subgroup. Also, shall same mechanism apply to HomeQoD? to be brought tto Home QoD subgroup. DECISION: Both approved |
Closing Issues
China Unicom | New API proposal: Device Visit Location | China Unicom and Telefonica to create a single family for both API: Location Insights, Use historical informations to manage location information of the user. LOCATION INSIGHTS FAMILY:
| |
Telefónica | New API proposal: OGW Home Location Verification | China Unicom and Telefonica to create a single family for both APIs: Location Insights, Use historical informations to manage location information of the user. TIM is supporting Home Location Verification but changing the name so to reach a wider scope.
| |
Deutsche Telekom | Best Interconnection | The issue was not treated in this conference call. Noel aplogized in advance and suggested to wait till April first week TSC meeting to move on with this API DECISION: Move to TSC | |
Charter Communications | CPE management | CPE Management API proposal was approved by TSC. Ricardo has to provide the CODEOWNERS and initial MAINTAINERS to the TSC. This have been provided within Issue#378_comment HomeDevicesQoD owners queried to have this API in a separated github project despite having regular meetings to align common terms (API Family). This involves having more than one CODEOWNER for this API (no further problem) New github subproject to be created: Home Devices - Network Access Management DECISION: GiutHub repo name approved | |
T-Mobile US | Capability and Runtime Restrictions | It was accepted by the TSC to treat this as a new API intitial YAML files to be included in the API TEMPLATE The issue was not treated in this conference call |
New Issues
Action Points
AP # | AP Owner | AP description | Related issue | Due date | Status |
20240411-01 | Deustche Telekom | Noel updating proposal with new fields. Start in parallel while device status API is split | Apr 11, 2024 | Open | |
20240411-02 | API Backlog Governance | Approve ScopeEnhancementAPI proposal for QoD (PR#403) | Apr 11, 2024 | Open | |
20240411-03 | Telefonica&DT | Modify the README for the QualityOnDemand subproject and include the new Scope enhancement | Apr 11, 2024 | Open |
Decision Points
AoB
Next Backlog conf. call: 25th April, 15-16 CET.
Next TSC conf. call: 18th April, 17-18 CET
Q&A
How does CAMARA API pipeline work?
The pipeline consists of FOUR stages:
A. Submission of the API proposal.
B. Evaluation of the API proposal.
C. API proposal voting & decision.
D. Sub-Project setup.
The following clauses provides details on individual stages.
Stage A: Submission of the API proposal
Participants: API owner.
Description: The proccess is detailed here. To proceed with the submission, the API owner shall follow these steps:
Fill in the template available here and save it with the following name: "APIproposal_<APIname>_<owner>. md" locally.
Create a new issue in the API Backlog Working Group repository, labeled with "API Backlog".
Upload the filled-in template to GitHub repository folder for API proposals via Pull Request. This Pull Request shall be associated to the issue created in the previous step.
Stage B: Evaluation of the API proposal
Participants: API owner, API backlog WG.
Description: The proccess is detailed here. Upon submission, the API owner will present the proposal in the next API backlog WG meeting, to socialize it with the rest of partners. In paralell..
The WG chair checks that the template is duly filled in. Otherwise, the API owner is requested to provide missing information.
After this sanity check, each WG participant declares their support. If a company wants to become supporter of an API, then a delegate of this company needs to add the company's name in the 'supporters' column in the API backlog table. The more support an API proposal gets, the better (it may get more traction).
When the API owner considers the API proposal is in good shape to go for approval, it informs the WG chair accordingly.
Upon receiving this information, the WG chair merges the Pull Request into the main branch, and sends the API proposal to the Technical Steering Committee (TSC) of CAMARA. This action shall be completed at least one week prior to the TSC meeting where the API proposal will be voted upon.
The whole procedure (steps 1-4) should be done within 2 regular meetings of the API Backlog WG. Nonetheless, it is up to the API owner to decide if it wants to shorten or extend this time period.
Stage C: API proposal & voting decision