2024-03-14 API backlog minutes
- Ricardo Serrano Gutierrez
- Javier Villa
- Kevin Smith
Attendees
GSMA | Helene Vigue |
Charter Communications | Chris Aubut, Justin Pace |
Ericsson | Jan Friman |
Nokia | Tanja De Groot |
Telefónica | Ricardo Serrano Gutierrez (Chairing) Ignacio Dominguez Martinez Jorge Garcia Hospital Javier Villa Labarra
|
Vodafone | Kevin Smith |
T-Mobile US | Karabulut, Murat |
Netcheck | Sanjeev Shankar |
Huawei | Kai Zhang |
IPification | Alex |
AT&T | Pierre Close |
Orange | Ludovic Robert |
ZTE | Hans Neff |
Vonage | James Emerson |
Agenda Proposal
Approval of minutes of last conf. call
Recent Updates & Recap
Review of Action Points
Discussion
OGW Drop 3 APIs: 336, 375, 376
Other APIs: 330, 351, 372, 378, 383, 395
Governance: 367
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
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: minutes are aproved.
Recent Updates & Recap
Backlog table
Table updated in PR#396
Review of Action Points
AP # | AP Owner | AP description | Related issue | Due date | Status |
20230208-04 | Charter Communications | Check potential relationship of this API proposal with existing HomeDevicesQoD, draw conclusions and propose a way forward. | 2024/02/21 | Closed | |
20230208-03 | Charter Communications | Re-assess how much essential is to include site info in the API, and if this info can be removed. | 2024/02/21 | Closed | |
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 | |
20240222-01 | Topogi | To fill the API template and create the Proposal PR. Backlog Governance to review colissions on this API. | 2024/03/13 | Closed |
Discussion
Current Issues
China Unicom | New API proposal: Device Visit Location | The issue was not treated in this conference call The issue is not eligible to be closed yet.
| |
Telefónica | New API proposal: OGW Home Location Verification | The issue was not treated in this conference call The issue is not eligible to be closed yet. | |
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. | |
Governance | Adapt Project StructuresAndRoles.MD to changes in API backlog table (reduction of comments) | Progress ongoing, and offline discussion on RACI matrix to WoW among OGW Product, CAMARA APIBacklog and CAMARA TSC. PR pending submission. It was socialized the WoW RACI. From the RACI shared in the meeting it mainly aplies the step 7 and the three colums from the right (CAMARA). The main idea is that any change in the scope of the APIs is brought to the Backlog WG for approval (shame process as if it was a new API) as the scope is responsibility of the Backlog (in the aproval and in the ongoing of the working group). This RACI will be brough to TSC for validation. ACTION: Ricardo to share the RACI in the issue 367 comments, after making CAMARA specific document and validation by TSC The issue is not eligible to be closed yet. | |
Totogi | New Proposal: Receive SMS |
The issue was not treated in this conference call The issue is not eligible to be closed yet. | |
Deutsche Telekom | Device Quality Indicator | 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 after name harmonization (This was done before the Call ended) | |
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 | Charter Communications provided comments to the PR regarding the scope (scope will be the use cases proposed in these comments) ACTION: Write in the API template the scope of the API that have been provided as a comment in the PR#379. DECISION: Move to TSC once the template is completed with the previous AP | |
T-Mobile US | Capability and Runtime Restrictions |
Is is better to treat this in the commonalities SG as this may affect to all the APIs? DECISION: Bring this issue to the TSC for discussion The issue is not eligible to be closed yet. |
Closed Issues
New Issues
Action Points
AP # | AP Owner | AP description | Related issue | Due date | Status |
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 | |
20240314-02 | Charter Communications | Write in the API template the scope of the API that have been provided as a comment in the PR#379. | 2024/03/14 | Open |
Decision Points
DP # | DP description | Related issue |
20240314-01 | CPE management API proposal to move foward TSC once the template is compliance with the AP 20240314-02 | |
20240314-02 | Bring this issue to the TSC for discussion as it may fit in the commonalities WG | |
20240222-01 | Device Quality Indicator to move foward to TSC for aproval (wait till April 4th) | |
20240222-02 | Best Interconnection to move foward to TSC for aproval (wait till April 4th) |
AoB
Next Backlog conf. call: 27th March, 15-16 CET.
Next TSC conf. call: 21st March, 16-15 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
Participants: TSC.
Description: The proccess is detailed here. Upon receiving the API proposal and notification from the API backlog WG chair, the TSC studies the proosal and votes it at the next TSC meeting.
NOTE 1: Possible decisions outcomes:
Not Accepted: The API proposal is rejected, and thus will not be included in any API Sub-Project. The TSC will need to inform the API backlog WG of this decision, and clarify next steps: either (1) remove this API proposal from backlog, with objecting companies providing justifications why; or (2) ask for changes (e.g., clarifications, corrections, gaps to be addressed) required in order for the API to be re-submitted by the API supporters.
Accepted: In this case, the TSC shall specify whether the API proposal is to be hosted by a new or existing Sub Project.
NOTE 2: The TSC may also propose changes to an API proposal and take the decision considering these changes. The TSC documents the decision in the CAMARA API overview list (fills in columns TSC date and TSC decision / Sub Project; in case of a No-Go "Rejected" is documented there).
Stage D: Sub-Project setup
Participants: API backlog WG, TSC, CAMARA admin team
Description: If an API proposal is accepted and there is a neeed to open a new Sub-Project, the following steps are needed:
Supporting companies propose their initial maintainers to be added for the Sub-Project. The API backlog WG chair centralizes this information, and sends it to the TSC.
The TSC will use this input to oficially nominate the initial maintainers by next TSC meeting.
The CAMARA admin team creates the Sub-Project repository.
NOTE: After the initial maintainers are nominated, the criteria for further maintainers would be three months of active contribution to the sub project. Code owners are to be decided by the maintainers within the subproject.