Versions Compared

Old Version 6

changes.mady.by.user Chris Howell

Saved on

compared with

New Version Current

changes.mady.by.user Herbert Damker

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

DRAFT

...

MINUTES

Attendees & Representation

...

Action Item Review

API Backlog (Ricardo Serrano Gutierrez Jorge Garcia Hospital )

  • Patricia Serrano introduction - Patricia steps in for Ricardo. Welcome !
  • Info: New repositories for DeviceQualityIndicator, DeviceDataVolume, SubscriptionStatus are created
  • New API proposal brought to TSC: QualityByDesign
    • See message https://lists.camaraproject.org/g/tsc/message/223
    • Proposal supported by Charter, Liberty Global, Vodafone
      • This API would be part of the Connectivity Insights API Family
      • ... but separate repository
    • API Proposal: Link
    • Discussion on the name of the API - Chris Howell raised that Quality by Design is probably too marketing
      • Consider to rename it.
      • Herbert Damker Discussion of an user story under this title make sense, but "QualityByDesign" will be a larger story, involving several APIs, including the QualityOnDemand family.
    • Discussion about how the QoS score could be computed
    • Next steps:
      • (question)  Do we create a repo with current name? or another name? QualityInsights? QualityAction?
      • TSC Proposal:
        1.  Herbert Damker creates the repo QualityByDesign 
        2.  Ben Hepworthprovides user story/ies, 
        3. (Project team) Discuss the concept & propose rename
        4. (TSC) Adjust the name
      • (Regarding execution of 2- 4.: Herbert Damker will create an issue within the new Repository which will point this out)

Release Management (Tanja de Groot Initial content by Herbert Damker on behalf)

  • Meta-release Fall24 - CAMARA Project - Confluence
    • M4 Release Pull Requests available for 25 APIs which will be in the Meta-Release
    • Release PR with Stable APIs - all reviews are almost done
    • All five Stable APIs are blocked by the same issue: the mandatory Test Statement has not been done
      • See issue #89 in ReleaseManagement: Clarify how to proceed with requirement "Test result statement" for stable APIs 
      • What is the requirement: "Statement in a discussion issue of the API Sub Project by at least one of the API Sub Project members that the Gherkin feature files have been successfully executed against their (lab) API implementation." 
      • We need a decision here in the TSC if and how we exempt the Stable API candidates in the Fall24 Meta-Release from this requirement
        • Tanja de Groot raised the point about our confidence to release these APIs in stable without performing complete testing
        • Herbert Damker not an example but we should let go. These APIs have been implemented already in several countries. 
          • If we have issue in the test definition we can have a patch version
          • We have to add a sentence to warn about this point.
          • in the checklist table we fill a link in the column & and redirect to the footnote
    • TSC Approval of M4 (all release PRs of Sub Project reviewed by Release Management)
      • We can merge PR release PRs and create the releases when review completed
      • M4 Release tracker date:  date when the merged is done by the project
    • Next Steps for M5 (all release PRs merged and public releases created)
  • Next release cycle ("Spring25") starts at September 30th (M0 - Kickoff)
  • Herbert Damker shared a slide deck introducing the CAMARA release management
    • Attached to the minutes below.

...

...

  • Public Release r0.4.0 available since August 23rd
  • An issue is open to discuss the scope of the next version: Commonalities/issues/273 - scope should be closed for
  • ...

API Backlog (Ricardo Serrano Gutierrez Jorge Garcia Hospital )

  • Patricia Serrano introduction - Patricia steps in for Ricardo. Welcome !
  • Info: New repositories for DeviceQualityIndicator, DeviceDataVolume, SubscriptionStatus are created
  • New API proposal brought to TSC: QualityByDesign
  • See message https://lists.camaraproject.org/g/tsc/message/223
  • Proposal supported by Charter, Liberty Global, Vodafone
    • This API would be part of the Connectivity Insights API Family
    • ... but separate repository
  • API Proposal: Link
  • Discussion on the name of the API - Chris Howell raised that Quality by Design is probably too marketing
    • Consider to rename it.
    • Herbert Damker Discussion an user story under this title make sense, but "QualityByDesign" will be a larger story, involving several APIs, including the QualityOnDemand family.
  • Discussion about how the QoSscore could be computed
    • Next steps:
  • (question)  Do we create a repo with current name? or another name? QualityInsights? QualityAction?
    • TSC Proposal: Herbert Damker creates the repo QualityByDesign 
  •  Ben Hepworthprovides user story/ies, 
  • (Project team) Discuss the concept & propose rename
  •  (TSC) Adjust the name

Governance & Project Management issues

...

  • Migration of wiki.telekom.de into Atlassian Cloud
    • Was tentatively scheduled for August 29th ... any update? (Casey Cain )

Any Other Business

  • ...none

Next Meeting

Action items

  •  Type your task here, using "@" to assign to a user and "//" to select a due dateHerbert Damker create repository for QualityByDesign, including issue about potential renaming  
  •  Tanja de Groot will propose a footnote and provide information on issue #89 in Release Management (done)