Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
General Updates
Table of Contents | ||||||
---|---|---|---|---|---|---|
|
Working Groups
Table of Contents | ||||||
---|---|---|---|---|---|---|
|
Sub Projects
Table of Contents | ||||
---|---|---|---|---|
|
Sub Projects
Table of Contents | ||||
---|---|---|---|---|
|
Children Display |
---|
General Updates
New Participants
- 1091 1126 people from 386 396 companies have joined CAMARA
- 1318 1658 people and 221 337 companies are in (first) talks
- Logos see landscape
- New General Member - Indykite
- New Participating Organizations - LFOD and phine.tech
Updated: Jul
Fund Updates
- Status of the technical project (same as below)
- Budget approvals
Updated
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
Updated
Working Group Updates
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 webinar at 12th of June and 10th of July with outstanding registration and participation: https://understandingnetworkapis.com/
- CAMARA presentations at Open Telco LATAM Summit and MWC Shanghai
- Next big event is Open Source Summit Europe
2025 planning started
- Review of marketing concept for 2025
- Working on 2025 event list / prioritization
New versions of CAMARA presentation and CAMARA onepager coming soon (new logos, new slides including these from the CAMARA webinars)
- Content is moved in dedicated Marketing repository: https://github.com/camaraproject/Marketing
Release Management
- Meta-release schedule
- M1 - Declared at TSC of 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 - Release candidates of Commonalities and ICM are available, see Meta-release Fall24 plan.
- M3 - First release-candidates of API Sub Projects to be provided by 07-21.
- M4 - Final release candidates of API Sub Projects: target 08-30.
- Supporting documentation:
- One stop documentation is here: Release Management Working Group
- API release documentation is available in GitHub:
- Reminder: API versioning guidelines are provided in the API Design Guidelines (Chapter 5), further details are within the wiki.
- Next steps
- All Sub Projects are asked to prepare for the meta-release, including creating API release trackers for their APIs under their wiki pages, preparing their release-candidate API version and their API readiness checklist items.
- Reminder: the API version number within this first pre-release shall have the format x.y.z-rc.1 for the targeted release of API version x.y.z in the meta-release
- Before M3 you may release 1 or more x.y.z-alpha.n versions as needed for the API development, but you can also go from the current release directly to the first release-candidate by M3. (Pre-)release numbering starts at r1.1. Please reflect this in the CHANGELOG.md.
- Milestone timeline is here: Meta-release Fall24.
- The Release Management team will start checking APIs and highlighting any points related to the release process where needed using the API Sub Project's issues list to help in the meta-release progress.
- All Sub Projects are asked to prepare for the meta-release, including creating API release trackers for their APIs under their wiki pages, preparing their release-candidate API version and their API readiness checklist items.
Updated:
Commonalities
- Release 0.4.0-rc.1 of Commonalities was published on 11th of July
- Please provide feedback on needed corrections for final release.
- New issues:
- 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 Commonalities v.0.5.0
Updated:
APIBacklog
DocumentsLive table for API backlog availablehere. Stable version.Accepted API proposals stored here.
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 (Receive SMS), #23 (Carrier Wholesale Pricing), #24 (Steering of Roaming Information), #60 (Dedicated Networks), 61 (network Info)
Governance: #4 (Structures and roles, RACI, Maintainers initiative), #53 (Scope Enhancement API Template)
- Application templates for those API proposals which have not been discussed yet in TSC.
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:
Proposals to be discussed in next TSC:
Number Recycling → #54 (KDDI, Vodafone, DT)
- Ongoing discussions. Proposals to be included under family....
- 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
Updated
Working Group Updates
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
- 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 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 Working Group
- API release documentation is available in GitHub: ReleaseManagement/documentation
- API versioning guidelines are provided in the Commonalities API Design Guidelines (Chapter 5), further details are within the Release Management wiki.
Updated:
Commonalities
- Version 0.4.0 of Commonalities published
- New issues:
- Announcements
M0 for Spring25 meta-release is on 30-09-2024
Please indicate the topics to be included in Commonalities v.0.5.0 cf. Issue #273
Updated:
APIBacklog
- Documents
- 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), #23 (Carrier Wholesale Pricing), #24 (Steering of Roaming Information), #60 (Dedicated Networks), 61 (network Info), 68 (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
Updated:
Sub Project Updates
BlockchainPublicAddress
Updated:
IdentityAndConsentManagement
Deliverable | R/O | Current status / Achievements |
API Definition | R | N/A yet. If identified, a proposal will be made once core issues are clarified and closed. |
API doc/user stories/testcases | R | New CAMARA "Security and Interoperablitity" profile created Existing CAMARA "API access and user consent management document" updated according to the new profile. New CAMARA ICM examples file created. OpenAPI securitySchemes ICM guidelines relevant information included in Commonalities API Design Guidelines documentation. |
Implementation | R | N/A yet |
API Reviews and extensions | O | Release 0.2.0 scope definition for Fall 24 CAMARA meta-release is defined and available in IdentityAndConsentManagement/issues/146. Only one issue still under discussion to close all items under the scope of the meta-release. |
Updated:
Sub Project Updates
BlockchainPublicAddress
Deliverable
R/O
Current status / Achievements
API Definition
R
Working in next release: v0.2.0-wip
- No additional Business Requirements so far.
- ON-HOLD: Working in technical enhancements in the meantime (see latest section)
API doc/user stories/testcases
R
API Doc
Full API documentation pending to be consolidated under API Spec
Use Cases - First version available
Implementation
R
Not yet
API Reviews and extensions
O
Pending Points:
- Issue #16 - Discussion about consent management considerations in retrieval of blockchain public addresses ON-HOLD
- Issue #51 - Avoiding the use of "plain" phoneNumber as filter criteria of blockchain retrieval
- Issue #52 - Enhancement of blockchainPublicAddress belongs to the user whose phoneNumber is indicated to set-tp the binding relationship
Updated:
Expand | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
CallForwardingSignal
Updated:
Expand | |||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
CarrierBillingCheckOut
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated: Updated: 08 Jul
ClickToDial
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
@Hanbai
ConnectivityInsights
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated: Jul
DeviceIdentifier
Expand | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated: Updated: 10 Jul
DeviceLocation
Expand | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated: Jul
DeviceStatus
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
DeviceSwap
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
@Wassam
EdgeCloud
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated: Updated: 11 Jul
HomeDevicesQoD
Expand | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
KnowYourCustomer
Deliverable
R/O
Current status / Achievements
API Definition
R
Work in progress on KYC Match API, KYC Fill-in API, Age Verification API
KYC Match and KYC Fill-in: release v0.1.0 is available here
- KYC Match: provides the customer with the ability to compare information it has for a particular user with that owned by MNO
- KYC Fill-in: provides the customer with the ability to request to MNO and receive KYC information for a particular user
- KYC Match and Fill-in: upgrade to v0.1.1 with some corrections → Approved PR #100 (June 18, 2024)
Age Verification: release v0.1.0 discussion ongoing
- provides the customer with the ability to check age information for a particular user with MNO data
- discussion on going, Issue #46, PR #50(initial API definition proposal)API doc/user stories/testcases
R
- KYC Match / Fill-in v0.1.1: API doc embedded in YAML, user stories available, testcases not yet available.
- Age Verification v0.1.0: User story is being discussed, in alignment with API definition discussion; Issue
|
Updated:
KnowYourCustomer/Tenure
Expand | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
Implementation
R
- Not yet
API Reviews and extensions
O
- KYC Match and KYC Fill-in v0.2.0: work in progress for enhancements; Issues #38 #39, #47, #65, #66, #71, #77, #85, #86, #87, #88, #89, #90, #91, #95, #96, and PRs #43, and some others.
- KYC Match Scoring function has been discussed on #85 since June 2024, which is in line with KYC Match enhancement proposal approved in API Backlog WG. → KYC Match Scoring function was agreed as optional function, and to create KYC Match v0.2.0 including Match Scoring function, PR #104 has been approved and merged.
- KYC Match Scoring: if Match result for a string-type attribute is 'false', a score on how close the string sent by the API request and the data stored in the MNO/CSP database are will be calculated and returned.
- Meta Release Fall-24 candidate is being discussed; Plans to include KYC Match v0.2 (basic Match + Match Scoring) and KYC Fill-in v0.1 (basic Fill-in). Issue#75- Note: Tenure API is in KnowYourCustomer Family. Tenure API will share some resources, e.g. meeting slots, with other KYC-SP APIs. In addition, API Backlog WG is discussing on whether two new APIs, NumberRecycling API and ShtudownServiceStatus API, can fit in KnowYourCustomer Family.
Updated: 11 Jul
LocationInsights
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
NetworkAccessManagement
Expand | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated: 13 Jun
Christopher Aubut @Justin Pace Randy Levensalor
NetworkSliceBooking
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
NumberVerification
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
OTPValidationAPI
Expand | |||
---|---|---|---|
|
OTPvalidationAPI
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
PopulationDensityData
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated: 08 Jul
QualityOnDemand
Expand | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated: Jul
RegionDeviceCount
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
ShortMessageService
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
SimpleEdgeDiscovery
Expand | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
SimSwap
Expand | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
SiteToCloudVPN
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated: 13 Jun
@Dan Xu
VerifiedCaller
Expand | |||||||
---|---|---|---|---|---|---|---|
|
Updated:
|
VerifiedCaller
Expand | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
13 Jun@Dan Xu
WebRTC
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|