2024-04-10: Device Status - Meeting Minutes

Attendees & Representation

Type @ and your name to indicate your attendance

LF Staff: na

Community: Ákos Hunyadi Ludovic Robert Fernando Prado Cabrillo Sachin kumar Rafal Artych, Noel Wirzius Joachim Dahlgren  

Agenda

• Antitrust Policy
• Open pull requests
• Open issues
• Release management
• AOB

Minutes

Open PRs

• #133 Prepare release 0.5.1
  • Merged during the meeting.

• #131 Update device-status.yaml
  •   PR was recreated after accedentally merging too early
  •   Planned release v0.6.0
    
    
• #123 Adding configuration for Github Actions with linting ruleset
  • No discussion
  • Reviews are missing.
  • Planned release v0.6.0
    
    
• #121 feat: add termination reason when subscription deleted
  • Should be first clarified in Commonalities: Commonalities#153    
    
    
• #112 include x-correlator and fix typo in 400 error code
  • No discussion
  • Reviews are missing
  • Planned release v0.6.0
    
    
• #108 feat: use simple String for "type" in CloudEvent
  • The enums for event-types include dots which causes problems at the code generation (Java) at DT. 
  • Additional feedback from dev teams would be helpful to priotize the issue.
  • A possible change in the design guideline could be a solution.
  • The PR has been marked as draft until an agreed solution is ellaborated.
  • An issue in Commonalities has been opened camaraproject/DeviceLocation#149

Open issues

• #136 Mandate '+' in phoneNumber

• #130 What should the API return if more than one device identifier is sent and they don't belong to the same device?

• #125 Separate endpoints into different APIs

  • Split the current API into 4 different APIs
  • Naming

• #122 Bugfix release v0.5.1

• #119 How can a provider inform the ASP/aggregator about not implemented features in advance of the API call

• #117 Send a CloudEvent when DELETE /subscriptions/{subscriptionId}

  • The corresponding PR is open: #121 feat: add termination reason when subscription deleted

• #115 /Connectivity API there is no indication for which particular subscriber event (DATA/SMS)

• #110 Request for Addition of "last_updated_timestamp" Field in CAMARA DeviceStatus API

  • The name should correlate with similar properties at other APIs

• #107 Use simple string for "type" in CloudEvent

  • The corresponding PR is open: #108 feat: use simple String for "type" in CloudEvent

• #104 Include x-correlator heade

• The corresponding PR is open: #112 include x-correlator and fix typo in 400 error code

• #102 Clarify API readiness status for v1.0.0

• #96 Path update per Design Guideline

  • The corresponding PR is open: #131 Update device-status.yaml

Release management

Release 0.5.x

• The release v0.5.0 was created on 31.01.2024
• The patch release 0.5.1 is planned #133 Bugfix release v0.5.1

Release 0.6.0

Release date: tbd

alpha1

• #131 Update device-status.yaml
• #112 include x-correlator and fix typo in 400 error code
• #123 Adding configuration for Github Actions with linting ruleset
• #136 Mandate '+' in phoneNumber

alpha2

• #125 Separate endpoints into different APIs

AOB

• Device Connection Indicator - Presentation from Noel (DT)

Action items

• Ludovic Robert Create PR for#136 Mandate '+' in phoneNumber
• Ákos Hunyadi Create issue about connectivity response extension, so that all possible cases are covered: only SMS, only DATA, SMS+DATA, none