2024-07-02 CFS Minutes
- fabrizio moggio
Attendees & Representation
Type @ and your name to indicate your attendance
LF Staff:
Community:
Name | Organization | Present |
|---|---|---|
Fabrizio Moggio (Chair) | TIM | x |
Robert Ludovic | INNOV/NET | x |
Fan Yang | China Unicom | |
Rafalย Artych | T-Mobile | x |
Enlai Chu | x | |
Stefano Falsetto | CK Hutchison | x |
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. |
Last Meeting Report Approval
Linting tool
Meta Release
Intent-2: outputs proposal
Draft Test Case
Readiness Checklist
Optional Operations
Next Steps
Action Items
Minutes
Last meeting minutes approved.
Linting tool merged. Activity closed. Maybe some further update will come according to some update from Commonalities.
We are aligned with the Readiness Checklist. Some Error code maybe is changed. Before creating the Alpha release the Guidelines must be checked again.
"Intent 2: output proposal" (https://github.com/camaraproject/CallForwardingSignal/discussions/31#discussioncomment-9795447)
agreement on the new output parameters proposed ('conditional_busy', 'conditional_unavailable', conditional_no-reply')
no target phone number returned
discussion on Voice Mail (Voice Mail FWD ยท camaraproject/CallForwardingSignal ยท Discussion #4 (github.com)) to be open again. Anyway we will move to Alpha even if this discussion is not closed.
Meta-release: we can go for Fall 24.
"Intent 2: output proposal" must be implemented.
we go for "release-candidate", the following releases (e.g. "public-release stable") can be for Fall25
according to the readiness Check list (New readiness checklist by FabrizioMoggio ยท Pull Request #43 ยท camaraproject/CallForwardingSignal (github.com))
"Basic API test cases & documentation" are needed
"Test result statement" are optional so we can create a "release-candidate" without an actual test result statement.
Test Case: the initial draft seams fine in the content, maybe it is not in the "style". We need to check it for example against: DeviceLocation/code/Test_definitions/location-verification.feature at ae00b2009069c3f1aa7ca15d627c57061025ca03 ยท camaraproject/DeviceLocation (github.com)
Optional Operation: the discussion Commonalities is not yet closed, anyway we will adopt a solution for Alpha with the proper documentation (e.g. 404 "operation not implemented")
next call: 16/07/2024
Task report
The work is progressing according to the scheduling