DRAFT
Attendees & Representation
...
Deutsche Telekom | x | |
Deutsche Telekom | ||
Ericsson | ||
KDDI | ||
@Masaharu Hattori | KDDI | x |
KPN | ||
Nokia | x | |
Orange | x | |
Orange | x | |
SingTel | x | |
SpryFoxNetworks | ||
Telefonica | x | |
Telefonica | ||
Telus | ||
TMUS | x | |
Vodafone | ||
Vodafone | 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. |
...
Review of previous Minutes:
Closed issues
Merged PR
- PR #168 Remove pattern UUID for x-correlator
- PR #169 [Bugfix]: Linting rules problem with Traffic Influence API
- PR #170 x-correlator_support_guidelines_in_notifications
- PR #187 guideline_for_specversion_cloudevent_concept_as_enum
- PR#174 Bug-fix common.yaml
...
Topic | Issue | PR | Status |
---|---|---|---|
Error responses | https://github.com/camaraproject/Commonalities/issues/127 | Looks like a good proposal https://github.com/camaraproject/Commonalities/issues/127#issuecomment-2044670552 Cleanup and alignment of design guidelines Error response guidelines | Pedro: TEF will align internally and make a proposal for the PR. |
Subscription | https://github.com/camaraproject/Commonalities/issues/185 | https://github.com/camaraproject/Commonalities/pull/189 Draft-PR for subscription-scope description in design guidelines - https://github.com/camaraproject/Commonalities/pull/177 | Review ongoing for Ludovic's PR. After feedback for this PR, Ludovic will update the design guidelines accordingly. ConnectivityInsights is requested to align on this topic. Shilpa will update the draft PR for scope and offer it for review. |
Wildcard scope | https://github.com/camaraproject/Commonalities/issues/184 | Will document what exists today based on ICM doc. We need feedback from participants if the wildcard scope needs to be documented in the API spec files We also need feedback if participants think this can have an impact on the explicit subscriptions API where we intend to have more granular scopes which include even types in the scope-names Please add your comments, which can then be incorporated in the PR if needed. | PR needed (Shilpa will create the PR) |
Enhance test def | Enhancement of the Testing Guidelines #158 | TEF will schedule an adhoc call to detail out the proposal and get feedback. Intend to keep this PR a part of meta-release. | |
Linting ruleset update | https://github.com/camaraproject/Commonalities/issues/188 | PR will be created (most likely by Rafal/DT) | |
Phone number not supported Not supported method/operation for phone number | https://github.com/camaraproject/Commonalities/issues/138 | https://github.com/camaraproject/Commonalities/pull/145/ | Please review this PR. The case is different from what is covered in issue 127. Contributors of error response and Ming Hui also please align here. |
Format for duration Afects Affects QoD, Connectivity Insights nad Scam signal | https://github.com/camaraproject/Commonalities/issues/137https://github.com/camaraproject/Commonalities/pull/145 | No PR raised yet | All: Please provide feedback to this issue and review the PR. We try to get feedback & a possible consensus until EOW and if not, we postpone for next release |
Cloud Event datacontenttype field | https://github.com/camaraproject/Commonalities/issues/192 | Pedro will create a PR | |
X-Correlator to x-correlator | https://github.com/camaraproject/Commonalities/issues/191 | TEF will create PR. |
...