...
| Name | Organization | ||||
|---|---|---|---|---|---|
| AT&T | x | ||||
| Deutsche Telekom | x | ||||
| Deutsche Telekom | x | ||||
| Former user (Deleted)Herbert Damker | Deutsche Telekom | x | |||
| Ericsson | x | ||||
| KDDI | |||||
Masaharu Hattori | KDDI | x | |||
| Huub Appelboom | KPN | x | |||
| Nokia | x | ||||
| Orange | Patrice Conilx | ||||
| Orangex | |||||
| SingTel | |||||
| Ramesh Shanmugasundaram | SpryFoxNetworks | x | |||
| Telefonica | x | ||||
| Telefonica | x | ||||
| Telus | |||||
| TMUS | x | ||||
| Vodafone | |||||
| Vodafone | x | Masaharu Hattori | 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. |
...
Release 0.4.0 planning
- Scope: Issue #175
- The proposed list of topics will be reviewed by TCS on 18/04
- Comments on the topics are welcome in the issue
- At the next Commonalities meeting (29/04) the scope should be agreed to reach M1
Current Discussions
Not discusses at the meeting
PRs review
- PR #168 Remove pattern UUID for x-correlator
- to be merged
- PR #169 [Bugfix]: Linting rules problem with Traffic Influence API
- to be merged
- PR #145 Added 501 Not Supported error response
- Covered by issue #127, the same approach should be used here
- PR #120 Update CAMARA_common.yaml: add Device headers, fix address
- Kevin Smith will be asked to reply
- Pedro Díez García will prepare change suggestion
- PR #170 x-correlator_support_guidelines_in_notifications
- to be merged
- PR #174 CAMARA_common.yaml bugs and typos fix
- to be reviewed
- Error responses should be aligned with the changes proposed in Issue #180
- PR #177 update-design-doc-with-explicit-sub-scope-changes
- to be discussed on dedicated meeting on subscription model
Issues review
- Issue #127 Which error send back when Device Identifier not supported by API Server?
- the way of implementing the agreed solution is related to Issue #180 Revision of Chapter 6 Error Responses in API Design Guidelines
- Issue #179 Is "application" relevant for Camara?
- Is identifier for application useful in multiple subprojects and should be defined in Commonalities - discussion is open
- Is simple application API relevant for CAMARA ?
- Edge Cloud APIs use App Id
- Issue #178 Introducing product categories
- some technical solutions are proposed to indicate categories
- the source question is on naming YAML files in Device Status to be unique across CAMARA
- Issue #176 Align Common Design Model for Cloud Event specversion field in APIs Design
PR will be prepared to mandate the use of enum for specversion
- the changes need to be implemented by subprojects using CloudEvents
- Issue #171 Revise the device object definition to simplify it
- More opinions are expected
AOB
The next meeting is on April 29th 2024 using https://zoom-lfx.platform.linuxfoundation.org/meeting/91016460698?password=d031b0e3-8d49-49ae-958f-af3213b1e547
...