Renaming the sub-project to BrandedCalling

[olsi-korkuti]

Problem description
The current naming of the sub-project is is not comprehensive

Expected action
As the main purpose of this subproject is to Brand the calls (with naming/logos/business card) in a secure way, the name of the sub-project does not reflect it.

It was discussed in today's meeting to rename the subproject from VerifiedCaller to BrandedCalling.

Advantages to renaming:

• Branded Calling would be a more comprehensive name for both APIs

  • Service Registration
  • Verified caller/Pre-announcement

• Product/commercial teams prefer the name Branded Calling API. The name of this product is already being used in the industry as Branded Calling/Branded Call/Branded CallerID

• A more self-explanatory name of the API could lead to higher adoption by the developer community

@camaraproject/verified-caller_codeowners @camaraproject/verified-caller_maintainers

Please review and comment if you agree. If necessary you can check with the preference of your Product teams

[GillesInnov35]

@olsi-korkuti , I fully agree, clarification will be great. I'll see with my team to have a approval. Thanks

[stroncoso-quobis]

LGTM, we must to clarify that verified and branding is different, but main use case is brand

[GillesInnov35]

@stroncoso-quobis , as you said during the during the meeting (you and @olsi-korkuti ), there's a main difference between verifying and branding. Depending on what operator is able to propose, actionType is useful.
So, actionType should be optional and no more mandatory, shouldn't it ?
thanks
Gilles

[DENGYONG18]

If we want to meet the Fall25 meta-release deadline, all the release assets need to be prepared and the first API release-candidate versions are due for the M3 date (June 21st). Please refer to https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/14559630/API+Release+Process and https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/14551399/Meta-release+Process . Would changing the project name at this stage cause significant delays? Perhaps we should revisit this discussion after the alpha-release.