New Participants

• 1108 1126 people from 393 396 companies have joined CAMARA
• 1658 people and 335 337 companies are in (first) talks
• Logos see landscape
• New General Member - Indykite
  • https://www.indykite.com/
    
• New Participating Organizations - LFOD and phine.tech
  • https://lfod.io
  • https://phine.tech/

Fund Updates

• Status of the technical project (same as below)
• Budget approvals

Technical Steering Committee

• EasyCLA introduction
  • EasyCLA was activated on all repositories on August 30th
  • Please test that you have a valid CLA within https://github.com/camaraproject/EasyCLA available as neutral repository where you can open a trivial PR and initiate the EasyCLA signing process.
    • Especially all Codeowners should use this opportunity to ensure that they can continue working after the project wide activation of EasyCLA.
  • The check for a signed CLA will be activate on all repositories soon. 

• New structure of Sub Projects agreed within the TSC (see PR Governance/pull/146)
  • A Sub Project can be now a set of API Repositories (one or multiple)
  • Details are described within ProjectStructureAndRoles.md
  • Opportunity for Sub Projects with multiple APIs to put them into separate repositories
    • Allows independent releases of APIs, simplifies the management of releases

• API Backlog 
• RegionUserCount got renamed into RegionDeviceCount
• ShortMessageService scope extended with "Receive SMS"
• DeviceStatus has been discussed the adoption of the two new APIs (Device Connection Quality Indicator, Device Data Volume)

• • before you need it for a contribution

• API Backlog 
• Repositories for Device Quality Indicator and Device Data Volume created, work in context of Sub Project DeviceStatus can start
• Repository for Subscription Status created, Codeowners and Maintainers have to be defined, then work in context of Sub Project KnowYourCustomer can start
• Proposal for Quality By Design approved in TSC. Repository will be created. Should be first used to describe the concept in User Stories to derive which APIs are involved, need to be changed or newly created. Repository name might get changed based on results.

• Commonalities
  • Public release r0.4.0 as part of Meta-Release Fall24 available
  • Scope definition for Spring25 release (Commonalities 0.5.0) until September 30th, see below
• Commonalities
• Release candidate of v0.4.0 available
Please consider this version for your APIs, especially the ones planned for the Meta-Release Fall24

• Identity & Consent Management (ICM)
• Release candidate of v0Public release r0.2.0Please consider this version for your APIs, especially the ones planned for the as part of Meta-Release Fall24

• Release Management 
• See below

• available
• Scope definition for Spring25 release (IdentityAndConsentManagement 0.5.0) until September 30th, see below

• Release Management 
• M4 approved by TSC on September 5th, actual M4 date of API repositories is the date of merge and release creation

• Exception decided for the "Test statement" of stable APIs in Fall24 Meta-Release. This requirement for stable APIs couldn't be met due to the tight time plan in the current release cycle. The APIs have added a footnote in the API Readiness checklist that there might be bugs within the test definitions (will be addressed by patch release as needed).

• M5 in preparation by Release Management (communication of Meta-Release)
• Slides about Meta-Release (will go into the CAMARA Project presentation of Marketing Group):
  

  View file
  name CAMARA Meta-release Fall24.pdf height 250

  
  
  

Marketing (Outreach Committee)

• CAMARA Powerpoint template available: template
  • Please use it for all external communication, but also for internal needs
• Marketing concept finalized

Marketing (Outreach Committee)

• CAMARA Powerpoint template available: template
  • Please use it for all external communication, but also for internal needs
• Marketing concept finalized: https://github.com/camaraproject/Marketing/blob/main/documentation/MarketingMaterial/CAMARA%20MarketingConcept.pptx

• 2024 event list finalized:: https://wiki.camaraproject.org/display/CAM/2024+Event+Tracker

  • CAMARA Sparring Partners webinar at 24th of July, report will follow in fall 2024
  • Next big event is Open Source Summit Europe (Shift, Digital-X, API Days, CASA24, FutureNet Asia at the same time)

• 2025 planning started

  • Review of marketing concept for 2025
  • Working on 2025 event list / prioritization

• New versions of CAMARA presentation and CAMARA onepager available on GitHub (new logos, new slides including these from the CAMARA webinars)

• Content is moved in dedicated Marketing repository: https://github.com/camaraproject/Marketing

• /blob/main/documentation/MarketingMaterial/CAMARA%20MarketingConcept.pptx

• 2024 event list finalized:: https://wiki.camaraproject.org/display/CAM/2024+Event+Tracker

  • Next big event is Open Source Summit Europe (Shift, Digital-X, API Days, CASA24, FutureNet Asia at the same time)

• 2025 planning started

  • Review of marketing concept for 2025
  • Working on 2025 event list / prioritization

• New versions of CAMARA presentation and CAMARA onepager available latest 13 Sept 2024  on GitHub (new logos, new APIs, new slides including release management / meta release)

• Content is moved in dedicated Marketing repository: https://github.com/camaraproject/Marketing

Release Management

• Meta-release schedule (see Meta-release Fall24 plan)

  • M4 - declared at TSC meeting on Sept 5th. Actual API release publications finished on 2024-09-11.

  • M5 - Fall24 meta-release publication: planned for 2024-09-15

  • M6 - meta-release retrospective: planned for 2024-09-30

  • M0 - Spring25 meta-release kick-off: planned for 2024-09-30

• Meta-release APIs - 25 APIs in total:
  • 5 stable APIs (version = 1.0.0) released with exception on the "Test statement". This requirement for stable APIs couldn't be met due to the tight time plan in the current release cycle. The APIs have added a footnote in the API Readiness checklist that there might be bugs within the test definitions (will be addressed by patch release as needed).
  • 20 initial APIs (version = 0.y.z) released of which
    • 9 updated APIs from deployed previous initial API releases
    • 11 newAPIs (6 request-response APIs and 5 event notification APIs)
  • 21 additional initial APIs are in progress but are not part of this meta-release.

• Next steps

  • M6: Retrospective: feedback can be provided 1) as Release Management GitHub issues, 2) by editing the Meta-release feedback page, or 3) by email to wg-release-management@lists.camaraproject.org

  • M6: Release of the Release Management documentation in GitHub (for M6)
  • Prepare Spring25 meta-release
    • Release Management: M0 kickoff preparation
    • Commonalities & ICM: define scope and start alpha release development
• Supporting documentation (for reference)
  • One stop documentation is here: Release Management

Release Management

• Meta-release schedule (see Meta-release Fall24 plan)
  • M1 - Declared at TSC on 2024-07-04 for Commonality alpha release available at 2024-06-10. Decision to skip the M1 for ICM and go directly to the first release-candidate for M2. 
  • M2 - Declared at TSC on 2024-07-11. Release-candidates of Commonalities and ICM are available.
  • A second release-candidate for both Commonalities and ICM are available and need to be checked by the Sub Projects
  • M3 - 20 release-candidates APIs by 14 Sub Projects have been provided and are under release management review.
  • 1 SimpleEdgeClous API and 4 DeviceStatus APIs have passed M3. M3 pre-releases can be used by implementors for testing and feedback.
  • M3 cut-off date for review requests of API release PRs is Aug 10th. 
  • M4 - Sub Projects can start to prepare their final release PR for the public API versions. M4 target date: 08-30.
• Next steps
  • All Sub Projects that want to participate in the meta-release are asked to prepare their release PR, including
    • creating API release trackers for their APIs under their wiki pages,
    • preparing their API readiness checklist items
    • requesting release PR review by the Release Mgmt team by including "@release-management_maintainers" in the PR as a reviewer 
  • The Release Management team is progressing the release PR review. You can check the status in the review issue linked to your release PR.
  • Please bear with the reviewers due to holiday times and missing release managers.
• Supporting documentation (for reference)
  • One stop documentation is here: Release Management Working Group
  • API release documentation is available in GitHub: ReleaseManagement/documentation/API_Release_Guidelines.md
  • ReleaseManagement/documentation/API-Readiness-Checklist.md
  • ReleaseManagement/documentation/CHANGELOG_TEMPLATE.md
  • An example CHANGELOG.md: ReleaseManagement/documentation/SupportingDocuments/CHANGELOG_EXAMPLE.md
  • Reminder: API versioning guidelines are provided in the API Design Guidelines (Chapter 5), further details are within the wiki.
  • API versioning guidelines are provided in the Commonalities API Design Guidelines (Chapter 5), further details are within the Release Management wiki.

Commonalities

• Release Version 0.4.0-rc.1 of Commonalities was published on 11th of July
  • Please provide feedback on needed corrections for final release.
• New issues:

  • Request body is required but all properties are optional #247

  • Add rules in design guideline about multi-endpoint API design & implementation requirement #246

  • How to inform API consumer about unprocessable subscription request in Async mode #243

  • Add an “Area” data-type into CAMARA_common.yaml #242

• published  23 Aug 2024 
• New issues:

  • Corrections agreed during release preparation: #284 #285

  • Test Definition template for explicit subscription API #293

  • Subscriptions enhancements #295 #296 #299 #300 
• Announcements

  • M0 for Spring25 meta-release is on 30-09-2024

  Announcements

  • See the Release 0.4.0-rc.1 Changelog

  • M0 for Spring25 meta-release is on 30-09-2024 

    • Please indicate the topics to be included in 

      Please indicate the topics to be included in

      Commonalities v.0.5.0 cf.

      0 

      Issue #273

APIBacklog

• Documents

  • Live table for API backlog availablehere. Stable version.

  • Accepted API proposals stored here. 

• New Issues
• Discussion

• OGW Drop #4 APIs:  #35 (5G New Calling), #34 (Shutdown Service Status), #41 (Telco Scoring), #50 (Device Management), #54 (Number Recycling), #63 (IMEI Fraud)

• Other APIs:  #17 (Consent and Measurement),  

#18

• #23 (

Receive SMS),  #23 (Carrier

• Carrier Wholesale Pricing),  #24 (Steering of Roaming Information), #60 (Dedicated Networks), 61 (network Info)

Governance:

• , 

#4

• 68 (

Structures and roles, RACI, Maintainers initiative), #53 (Scope Enhancement API Template)
• PRs
  • Application templates for those API proposals which have not been discussed yet in TSC.
• Announcements

  • API Backlog will be held from then to now in a separate GitHub Repo and migration of issues have been completed. Active PRs will be moved to the new repo

  • Changes in the way of approving new API proposals are under review

  • Closing issues being treated in the TSC:

    • #20 (Best Interconnection), #22 (Capability and Runtime Restrictions), #19 (Device Quality Indicator), #28 (Device Data Volume)

  • Proposals to be discussed in next TSC: 

    • Number Recycling → #54 (KDDI, Vodafone, DT)

  • Ongoing discussions. Proposals to be included under family....
    • DeviceStatus → #19 (Device Quality Indicator), #28 (Device Data Volume), #61 (network Info)
    • KYC → #54 (Number Recycling), #34 (Shutdown Service Status), #2 Tenure

IdentityAndConsentManagement

• Release of v0.2.0-rc.1 of IdentityAndConsentManagement was published on 11th of July
  • Please provide feedback on needed corrections for final release.
• Release of r0.2.0-rc.2 of IdentityAndConsentManagement was published.
  • This is a bug fix release. 
  • Please provide feedback on needed corrections for final release.

• Resource URL) #83 #85 #86 #87 (Model as a Service)

• Governance: #4 (Structures and roles, RACI, Maintainers initiative)

• PRs
  • Application templates for those API proposals which have not been discussed yet in TSC + new API Backlog table with reduction of columns (New APIbacklog.md by TEF-RicardoSerr · Pull Request #80 · camaraproject/APIBacklog · GitHub).
• Announcements

  • API Backlog will be held from then to now in a separate GitHub Repo and migration of issues have been completed. Active PRs will be moved to the new repo

  • Changes in the way of approving new API proposals are under review

  • Closing issues being treated in the TSC:

  • #20 (Best Interconnection), #22 (Capability and Runtime Restrictions), #19 (Device Quality Indicator), #28 (Device Data Volume), #18 (Receive SMS), 70 (Quality by Design)

  • Proposals to be discussed in next TSC: 

    • Dedicated Networks

    • Telco Scoring
  • Info: New repositories for DeviceQualityIndicator, DeviceDataVolume, SubscriptionStatus and QualityByDesign are created

IdentityAndConsentManagement

• Public release r0.2.0 as part of Meta-Release Fall24 available
• Scope definition for Spring25 release (IdentityAndConsentManagement 0.5.0) until September 30th
  • Please indicate the topics to be included https://github.com/camaraproject/IdentityAndConsentManagement/issues/193

BlockchainPublicAddress

CallForwardingSignal

CarrierBillingCheckOut

CallForwardingSignal

CarrierBillingCheckOut

ClickToDial

Expand

Deliverable R/O Current status / Achievements API Definition R Device Identifier API: Initial public release 0.1.0 now available API specification now being reviewed for compliance with updated Commonalities and Identity & Consent Management guidelines Rename X-Correlator to x-correlator Simplification of Device object Repository, Mailing list have been set up.  API Definition - Draft version available Subsequent modifications and improvements will be made. API doc/user stories/testcases R Device Identifier API: API doc - First version contributed TBD part will be added in next version. Use Cases - First version available TBD part will be added in next version, format needs to be adjusted.            Test Cases - Work in progress Documentation embedded within OAS definition User Stories now added Test cases under development Implementation RChina Unicom No implementation available yet API Reviews and extensions O IMEI Fraud API: API removed from scope of Sub-Project for now, but has been resubmitted to API Backlog WG by Chenosis (see Issue #63)

ConnectivityInsights

Expand

Deliverable R/O Current status / Achievements API Definition R PR ready (pending on Release Management approval) for API family release: r1.1, including Public release of r1.2 of Connectivity Insights now available which includes 3 APIs:   Connectivity Insights v0.4 location-verification v1.0 .0 -rc1location-retrieval Connectivity Insights Subscriptions v0. 3 4.0 -rc.1geofencing-subscriptions Application Profile v0.3.0 -rc.1 API doc/user stories/testcases R All API documentation consolidated within spec. Documentation is now available as part of the yaml user stories available. test cases available for each of the API.  PR includes test plans for location-verification and location-retrieval. geofencing-subscriptions tdb prior to M4  Implementation RNo contribution  yet Not Yet API Reviews and extensions O PR for r1.1 PRs with (very basic) proposal for test definitions for geofencing-subscriptions Rest of issues and PRs on hold until end of meta-release Fall24

DeviceIdentifier

Expand

Deliverable R/O Current status / Achievements API Definition R Target for version Device Identifier API: Initial public release 0.6.0  - separated endpoints1.0 now available Working towards v0.2.0-alpha.1 Incorporate Commonalities WG recommendations on Simplification of Device object Remove format: uuid  requirement for x-correlator Update info.description device-roaming-status v0.6.0 device-reachability-status v0.6.0 device-roaming-status-subscriptions v0.6.0 device-reachability-status-subscriptions v0.6.0 API doc/user stories/testcases RDrafts prepared according to API Testing Guidelines Device Identifier API: Documentation embedded within OAS definition User Stories now added Additional user stories proposed: EUDI Wallet Device-Binding User Story Mobile Device Insurance User Story Test cases under development Implementation RNo implementation available yet China Unicom API Reviews and extensions O Alignment to Commonalities 0.4Ongoing review for compliance with Commonalities 0.4.0 and Identity & Consent Management 0.2.0

DeviceLocation

DeviceStatus

DeviceSwap

Expand

Deliverable R/O Current status / Achievements API Definition R Pre-release r1.1 of API version 0.4.0-rc.1 is now available (review completed at HomeDevicesQoD/pull/68). Release tracking page: https://wiki.camaraproject.org/display/CAM/home-devices-qod+v0.4.0Work to be started API doc/user stories/testcases R Implementation R Existing test definitions for v0.4.0 are available in the repository. Implementation R N/A API Reviews and extensions O The 0.4.0 API version is only intended to conform previous 0.3.0 version to the Commonalities and ICM guidelines included in the Meta Release "Fall24". No new features are added.

EdgeCloud

HomeDevicesQoD

KnowYourCustomer/Tenure

LocationInsights

NetworkAccessManagement

NetworkSliceBooking

NumberVerification

OTPValidationAPI

OTPvalidationAPI

PopulationDensityData

QualityOnDemand

RegionDeviceCount

ShortMessageService

SimpleEdgeDiscovery

SimSwap

SiteToCloudVPN

VerifiedCaller

VerifiedCaller

WebRTC