Update README with a short description of the scope of the repository · Issue #3 · camaraproject/CustomerInsights

DT, WG

ONGOING

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 Update README.md w/ Meeting information by wrathwolf · Pull Request #13 · camaraproject/CustomerInsights

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

23/JAN: Covered in PR Release 1.1 (Release candidate) by PedroDiez · Pull Request #21 · camaraproject/CustomerInsights

06/JAN: PR Release 1.1 (Release candidate) by PedroDiez · Pull Request #21 · camaraproject/CustomerInsights will be updated after merging User Stories and Baseline Proposal, so as it will be requested again to RM.

Customer Insights User Stories · Issue #9 · camaraproject/CustomerInsights

TEF

CLOSED

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.

23/JAN: Comments reviewed. PR#10 for WG review

06/JAN: Asked again for review. @Kev Scarr approved after the meeting. It is merged after the meeting and issue is closed.

Customer Insights API Baseline Proposal · Issue #11 · camaraproject/CustomerInsights

TEF

CLOSED

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 Release 2.1 by rartych · Pull Request #342 · camaraproject/Commonalities. 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”

23/JAN: Initial proposalin Customer Insights Baseline Proposal by PedroDiez · Pull Request #12 · camaraproject/CustomerInsights aligned with Commonalities r2.1. Expected to adapt once Commonalities r2.2 is in place

06/JAN: Asked again for review. @Kev Scarr approved after the meeting. It is merged after the meeting and issue is closed.

MetaRelease Spring 25 for Customer Insights API · Issue #14 · camaraproject/CustomerInsights

WG

ONGOING

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: Customer Insights API Release Tracker for MetaRelease Spring 25 · Issue #15 · camaraproject/CustomerInsights

• User Stories: Customer Insights User Stories · Issue #9 · camaraproject/CustomerInsights CLOSED

  • PR: User Stories Documentation by PedroDiez · Pull Request #10 · camaraproject/CustomerInsights

• API Spec: Customer Insights API Baseline Proposal · Issue #11 · camaraproject/CustomerInsights CLOSED

  • PR: Customer Insights Baseline Proposal by PedroDiez · Pull Request #12 · camaraproject/CustomerInsights. To be aligned with Commonalities r2.2 (done)

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

  • PR: https://github.com/camaraproject/CustomerInsights/pull/20. To generate reference to Commonalities r2.2

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

  • PR: https://github.com/camaraproject/CustomerInsights/pull/19. Check latest updates in Commonalities (PR#381, PR#386) Merged las week

23/JAN: Initial M3 RC PR in Release 1.1 (Release candidate) by PedroDiez · Pull Request #21 · camaraproject/CustomerInsights. It is needed to update PR and request again RM review by means of issue CustomerInsights r1.1 (Spring25 M3) release review camaraproject/ReleaseManagement#135. Expectation is to have RC during next week.

PRs order review

WG

N/A

Order of review of PRs:

• User Stories Documentation by PedroDiez · Pull Request #10 · camaraproject/CustomerInsights MERGED

• https://github.com/camaraproject/CustomerInsights/pull/20 ask for RM review and approval @Pedro Díez García

• Customer Insights Baseline Proposal by PedroDiez · Pull Request #12 · camaraproject/CustomerInsights MERGED

• https://github.com/camaraproject/CustomerInsights/pull/19 MERGED

• Release 1.1 (Release candidate) by PedroDiez · Pull Request #21 · camaraproject/CustomerInsights To be updated and request again RM approval for having it durign the next week.

AoB

WG

Algorithm generating the rating: TEF internally working to share an initial proposal. Expected to begin discussion on February.

Commented during the meeting TEF will make an initial proposal based on internal checking. An issue will be created to track discussión (DONE after meeting, https://github.com/camaraproject/CustomerInsights/issues/22). It is foreseen that parametrization could be different depending on line suscription (i.e. prepaid, postpaid). Initial inoput will be provided within that issue in order to begin discussion and have specific slot during the next meeting fo this discussion.