Attendees & Representation
Type @ and your name to indicate your attendance
LF Staff:
Community:
| Name | Organization | |
|---|---|---|
| AT&T | x | |
| Deutsche Telekom | x | |
| Deutsche Telekom | ||
| Deutsche Telekom | x | |
| Ericsson | x | |
| KDDI | ||
@Masaharu Hattori | KDDI | x |
| KPN | ||
| Nokia | x | |
| Orange | x | |
| Orange | x | |
| SingTel | x | |
| SpryFoxNetworks | ||
| Telefonica | ||
| Telefonica | ||
| Telus | ||
| TMUS | ||
| Vodafone | ||
| Vodafone | x | |
| GSMA | x | |
| CableLabs | x | |
| GSMA | x | |
Ola A | 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. |
- Roll Call
- Action Items Review
- Agenda Bashing
- General Topics
- Closed issues and merged PRs
- Release 0.4.0 scope
- Discussions
- PRs
- Issues
- Any Other Topics
Minutes
Action Item Review
Task report
Looking good, no incomplete tasks.
Review of previous Minutes:
Closed issues
Merged PR
Release 0.4.0 scope
Topic | Issue | PR | Status |
|---|---|---|---|
| Error responses | https://github.com/camaraproject/Commonalities/issues/127 https://github.com/camaraproject/Commonalities/issues/180 | 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/198 https://github.com/camaraproject/Commonalities/pull/189 https://github.com/camaraproject/Commonalities/pull/177 - merged | Please review PRs 189 & 198 ConnectivityInsights is requested to align on this topic. |
| 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. | To be checked in this section: |
| Enhance test def | Enhancement of the Testing Guidelines #158 | Dedicated meeting scheduled for 16 of May : https://lists.camaraproject.org/g/wg-commonalities/message/13 | |
| Linting ruleset update | https://github.com/camaraproject/Commonalities/issues/188 | PR will be created (most likely by Rafal/DT) | |
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 Affects QoD, Connectivity Insights and Scam signal | https://github.com/camaraproject/Commonalities/issues/137 | No PR raised yet | It is proposed to add the recommendation in https://github.com/camaraproject/Commonalities/blob/main/documentation/API-design-guidelines.md#115-data-definitions The issue https://github.com/camaraproject/Commonalities/issues/93 may be addressed within the same PR. |
Cloud Event datacontenttype field | https://github.com/camaraproject/Commonalities/issues/192 | https://github.com/camaraproject/Commonalities/pull/193 | Please review this PR. |
X-Correlator to x-correlator | https://github.com/camaraproject/Commonalities/issues/191 | https://github.com/camaraproject/Commonalities/pull/194 | Please review this PR. |
Remove basePath in servers.url as variable | https://github.com/camaraproject/ReleaseManagement/issues/17 | The resolution will be proposed by Release Management group |
PRs review
Issues review
- New issue: #195 Is there a need for association of API definition (yaml) to Commonalities, ICM or Meta Release version?
- The issue will be resolved within Release Management versioning guidelines
- New issue: #196 Specify allowed values for error status and code in the error schema
- Should be covered by https://github.com/camaraproject/Commonalities/issues/180 (Chapter 6 of API Design Guidelines)
- Changes proposed by G. Murat Karabulut in:
AOB
Commonalities alpha release should be ready 2 weeks before M2 - see the table in Meta-release Fall24
The next meeting is on May 27th 2024 using https://zoom-lfx.platform.linuxfoundation.org/meeting/91016460698?password=d031b0e3-8d49-49ae-958f-af3213b1e547