2024-07-17: Device Status - Meeting Minutes

Attendees & Representation

Type @ and your name to indicate your attendance

LF Staff: na

Community: @Akos Hunyadi @Ludovic Robert @Kevin Smith @Sachin kumar @Noel Wirzius @Joachim Dahlgren @Rafal Artych @Fernando Prado Cabrillo 

Agenda

• Antitrust Policy

• Open pull requests

• Open issues

• Release management

• AOB

Minutes

Open PRs

• #191 Make device attribute optional for subscription requests

  • Not needed for subscriptions, PR & issue can be closed

• #190 Prepare release r0.7 DRAFT
  
  

  • Release numbering should start from r1.1 (not 0.7) 

  • Example changelog: https://github.com/camaraproject/ReleaseManagement/blob/main/documentation/CHANGELOG_EXAMPLE.md

• Gherkin tests
  
  

  • #186 Create Gherkin tests for device-status-reachability and device-status-roaming DRAFT

  • #187 Create Gherkin tests for device-status-subscriptions DRAFT

• New API - retrieve network type

  • #158 Create connected-network-type.yaml

  • #171 Create connected-network-type-subscriptions.yaml

  • Due to the draft state and the close deadline, it's not realistic to add the new APIs to the Fall24 release

Open issues

• #189 Make Device attribute optional for roaming and reachability subscriptions Fall24

• #184 Align subscription-APIs with guidelines for error scenarios Fall24

  • First the subscription template should be updated, including the decision, which error codes from the guideline make sense for subscriptions

• #177 Create release candidate #1 for Fall24 CAMARA release Fall24

• #176 Proposed Sub-Project Scope Enhancement: Device Quality Indicator API

• #175 Create basic Gherkin tests for the subscription APIs Fall24

• #174 Create basic Gherkin tests for the retrieve APIsFall24

• #172 Scope of DeviceStatus for Fall24 CAMARA release Fall24

  • Discussion on maturity level (initial/stable) (ref: API Release Process - CAMARA Project - Confluence)

  • Team position is for initial right now

• #169 Consolidate Common Data Types into a single YAML-File

• #167 Check the Overlap between DeviceStatus and ShutdownServiceStatus 

• #166 CloudEvent schema object in DeviceStatus OpenAPI does not match with CloudEvent schema specified in Commonalities

• #163 Change Subproject Scope

  • Feedback is requested

• #157 Simplification of Device object - short term solution

  • Team position is to make device parameter optional and keep networkAccessIdentifier with additional comment not to use it currently.

• #156 SubscriptionExpireTime in not mandatory in subscription API

• #153 GET/subscriptions - API Clarification

• #148 Extend ConnectivityStatus with UNKNOWN 

• #143 Extend: Device Status Connectivity with Standard 

  • PRs are open

• #140 Extend the possible connectivity values 

• #138 How to respond if queried device does not have an active session?

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

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

Release management

Camara Meta Release 

• See Meta-release Fall24

• M3: create the first release candidate by 21.07.2024

Release r0.6 released

•  Device Status v0.6.0.alpha.1

Meta-Release Fall24

• Scope of DeviceStatus for Fall24 CAMARA release 

AOB

• Vacation situation:

  • @Akos Hunyadi  Jul 29, 2024 to Aug 16, 2024 

  • @Ludovic Robert Jul 29, 2024 to Aug 18, 2024 

  • @Fernando Prado Cabrillo Aug 18, 2024 to Aug 31, 2024 

  • @Sachin kumar  Jul 23, 2024  to Aug 16, 2024 

Action items