https://github.com/camaraproject/CustomerInsights/issues/3

DT, WG

28/NOV: This issue is to be managed after Zoom meetings are in place and initial API information can be provided. With that a PR can be generated

12/DIC: Partially covered with https://github.com/camaraproject/CustomerInsights/pull/13

07/JAN: Pending to update README.md. Trigger PR in the next days

https://github.com/camaraproject/CustomerInsights/issues/8

TEF, WG

28/NOV: Issue will be kept open until Zoom Meetings are managed
12/DIC: To be closed when Zoom Meetings Link are already managed. Meetings are already managed by Zoom so it will be closed and documented in the next meeting

09/JAN: Zoom Meetings already managed. Set as closed. https://github.com/camaraproject/CustomerInsights/issues/8#issuecomment-2539810180

https://github.com/camaraproject/CustomerInsights/issues/9

TEF

28/NOV: Issue to cover initial User Stories. Related PR#10 created
Explained during the meeting the rationale of the Use cases. To be checked offline and provide comments. Other Use case are welcome to be gathered now or in the future. This document is mandatory for the MetaRelease
12/DIC: Commented during the meeting to receive comments if any or give OK. We should have this initial PR merged for the fist half of January

09/JAN: Comments provided by Rafal Artych at the end of last year. Pedro will review them. Rafal also comments Kevin can take a look for using the better Englixh wording as possible.

https://github.com/camaraproject/CustomerInsights/issues/11

TEF

28/NOV: Issue to cover Baseline API proposal for discussion. Related PR#12 created

Main Points indicated:

• Algorithm generating the rating: Kev Scarr indicates we would need to agree on an aligned algorithm rules to generate analogous ratings from Telco Operators. Pedro Díez García indicates this is not part of the design but the underlying BE logic that provide the score. And yes, we need to talk about that in order to reach an alignment.
  VF is beginning to work in solutions for this kind of solutions. TEF has a pilot in VIVO (BR) and will compile information to check solution in place. DT has solutions in some central European countries and also check internally

• Rating Models: Two initial Models presented, other model could also be incorporated by other Operators based on their business needs. At least TEF is using the “veritasIndex” Model (solution in BR)

  • WG agrees that a future discussion, not in terms of definition, but in the context of GSMA OGW is to have alignment in the (minimum) set of models to be supported by a Telco operator for interoperability purposes.

• Error Model: Initial approach but that will have to be enhanced / corrected with the upcoming agreements from Commonalities within MetaRelease Spring 25.

• Regulations Constraints: Rafal Artych comments that internally each telco review the wording used within the context of the API to check if any legal regulation problem could exist, and based on that make some rewording. to be checked internally by all.

PR will be reviewed offline and provide comments

12/DIC: FollowUp discussion. Commenting around summary and comments given by Kev Scarr. Pedro will provide feedback during the ongoing week. Other point for the API Spec is the alignment of the specification with Commonalities and ICM guidelines. Regarding Commonalities, Release 2.1 has been delivered last week https://github.com/camaraproject/Commonalities/pull/342. Also Rafal Artych has elaborated a document under TSC request to easy the understanding an identification of breaking changes. https://lf-camaraproject.atlassian.net/wiki/x/jIAQAw that aims to indicate breaking changes and also suggest subprojects what they need to update in API definitions.

09/JAN: Main pending points are Commonalities and ICM aligment. Also to propose a generic wording for the term “Scoring”

https://github.com/camaraproject/CustomerInsights/issues/14

WG

12/DIC: “parent” issue to compile MetaRelease Spring 25 actions:

• API release tracker

• User Stories

• API Spec

• API Readiness Checklist

• API testing

Next Step is to generate child issues. Commented during the meeting the actions to be performed on each of them. Work will be documented within them as far as it is progressing on it.

09/JAN: Child Issues available. Prioritize work on updating PR for M3 Milestone.

• API release tracker: https://github.com/camaraproject/CustomerInsights/issues/15

• User Stories: https://github.com/camaraproject/CustomerInsights/issues/9

• API Spec: https://github.com/camaraproject/CustomerInsights/issues/11

• API Readiness Checklist: https://github.com/camaraproject/CustomerInsights/issues/17

• API testing: https://github.com/camaraproject/CustomerInsights/issues/18

  • Covering functional testing and also error scenarios.

AoB

WG

Algorithm generating the rating: TEF internally working to share a proposal. Checking with TEF Telco Operators. Expected to be ready to share an initial proposal during February. Kev Scarr comments about providing some information to business partners about how algorithm is peformed. Commented within the WG that we will need to talk about that. It is clear that for implementation alignment is required and in order to provide some public hints we will have to achieve some consensus about which and how some information can be provided not colliding with provacy nor legal considerations. Taken note of this point when entering in this specific discussion.