...
- Call Forwarding Signal API introduction
- Meetings scheduling and setting up the work
- Requirements gathering
Minutes
- LF Policies
- Agenda approval
- Brief CAMARA introduction, intent based approach and explanation of the Camara Readiness Checklist: Commonalities/documentation/API-Readiness-Checklist.md at main · camaraproject/Commonalities (github.com)
- ( In addition, I would like to give you a reference to the Commonalities WG, where you can find the CAMARA design Guidelines and other useful information. Have a look here: https://github.com/camaraproject/Commonalities/tree/main?tab=readme-ov-file#frequently-accessed-output-documents )
- I would create a document to map the API development status according to the Camara Readiness Checklist
- Discussion on Use Cases: Provide concrete Use Cases · camaraproject/CallForwardingSignal · Discussion #3 (github.com)
- The idea is to add use cases here and discuss about them on specific Discussions. We can open here a new use case as "UseCase-x: use case name" with a description on the use case. Anyone that want to discuss about it can open a new Discussion with "UseCase-x: use case name" in the title. So we have here a clean list of the uses cases.
- Fabrizio will create the first use case, the one already described in the API home page.
- Fang Yang will propose a new Use Case
- The proposed time slot and day for the API Call was agreed, anyway it is not the best for everyone. Maybe a discussion can be open to define a better time slot
- Is the phone number, target of the call FWD, returned as an API output? There was a first discussion on this topic. A Discussion will be open on GithHub
- First discussion on Conditional and Unconditional call FWD support. A Discussion on this will be open on GithHub
- Discussion on User Consent: Consent Management · camaraproject/CallForwardingSignal · Discussion #7 (github.com)
- Robert will check with his legal office
...