Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Working GroupsGeneral Updates
Table of Contents | ||||||
---|---|---|---|---|---|---|
|
Working Groups
Table of Contents | ||||||
---|---|---|---|---|---|---|
|
Sub Projects
Table of Contents | ||||
---|---|---|---|---|
|
Sub Projects
Table of Contents | ||||
---|---|---|---|---|
|
Children Display |
---|
General Updates
Working Group Updates
Technical Steering Committee
- EasyCLA introduction
- 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.
- https://github.com/camaraproject/EasyCLA available as neutral repository where you can open a trivial PR and initiate the EasyCLA signing process.
- 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)
- 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 v0.2.0
- Please consider this version for your APIs, especially the ones planned for the Meta-Release Fall24
- Release Management
- See below
- 1126 people from 396 companies have joined CAMARA
- 1658 people and 337 companies are in (first) talks
- Logos see landscape
- New General Member - Indykite
- New Participating Organizations - LFOD and phine.tech
Updated:
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 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
- Identity & Consent Management (ICM)
- Public release r0.2.0 as part of Meta-Release Fall24 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:
Updated
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 under TSC review till 2024-07-10. Release PRs will be merged and announced shortly on the Meta-release Fall24 plan. M2 will be declared after that.
- 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 release number of 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 do 1 or more x.y.z-alpha.n releases as needed for teh API development, but you can also go from the current release directly to the first release-candidate by M3. 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-alpha.1 of Commonalities was published on 10th of June
- Current PRs
Further topics for the v0.4.0 release
Proposal to simplify device object and improve interoperability- Enhance API-Testing-Guidelines.md
- Alignment with Release Management
- Alignment with Identity and Consent Management
- Error model alignment - chapter 6 of API Design Guidelines
- Annoucements
This version introduces Event Subscription model based on CloudEvents Subscriptions API draft
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
#60 (Dedicated Networks),
- Scope Enhancement: #45 (KYC-Match API - Scoring Logic), #48 (RegionUserCount) Governance:
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:
Created new subproject/repos:
Verified Caller → #27 (China Telecom, ZTE, China Unicom, Huawei, China Mobile)
Tenure → #2 (Vodafone, Telefonica, Orange, DT)
Updated:
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
IdentityAndConsentManagement
Deliverable
Expand | |
---|---|
|
|
N/A yet.
If identified, a proposal will be made once core issues are clarified and closed.
|
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.
|
|
|
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
|
Updated:
CallForwardingSignal
BlockchainPublicAddress
Expand | |||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
|
Updated:
CarrierBillingCheckOut
Expand | ||
---|---|---|
|
CallForwardingSignal
Expand | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
Updated:
ClickToDial
CarrierBillingCheckOutExpand | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
@Hanbai
ConnectivityInsights
Expand | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
Updated:
DeviceIdentifier
ClickToDialExpand | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
DeviceLocation
Updated:
@Hanbai
Expand | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
|
Updated:
DeviceStatus
DeviceIdentifierExpand | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
DeviceSwap
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
@Wassam
EdgeCloud
Expand | |||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
HomeDevicesQoD
Updated:
Expand | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
@Noel
|
Updated:
KnowYourCustomer/Tenure
DeviceSwapExpand | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
@Wassam
EdgeCloud
Deliverable | R/O | Current status / Achievements |
API Definition | R | •Traffic Influence – 0.9.5-wip :PR for v0.9.6-wip: addition of the "sourceTrafficFilters" object to help identify the traffic flow to influence. Minor updates following commonalities. •Edge Application Management – 0.9.3-wip:A couple of PRs have been created to improve the onboarding of an Application using K8s. •Application Endpoint Discovery: Update the device object according to the commonalities v0.4.0 definition and improve the API documentation to clarify its scope. |
API doc/user stories/testcases | R | •The documentation was provided according to Commonalities v0.3.0 but will be updated according to the new requirements of Commonalities v.0.4.0. •Edge Cloud User Story now available to understand the relationship of the 4 current APIs |
Implementation | R | No provider implementation (PI) available yet.However: •Traffic Influence: Implementation under validation by Telecom Italia (TIM): •Simple Edge Discovery: Partly validated (Vodafone and Telstra). |
API Reviews and extensions | O | Exposure and Experience Management API:This API has recently received a contribution and has been renamed the Edge Service Discovery API. As the name suggests, the API has discovery functionalities but does not overlap with the current APIs but has advanced functionalities that can enhance Simple Edge and App Endpoint Discovery. We are discussing next steps. |
Updated:
HomeDevicesQoD
Deliverable | R/O | Current status / Achievements |
API Definition | R | Current API Spec release is v0.3.0 |
API doc/user stories/testcases | R | Existing test definitions are available in the repository. |
Implementation | R | N/A |
API Reviews and extensions | O |
|
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#81.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 Score 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 Score function was agreed as optional function, and to create KYC Match v0.2.0 including Match Score function, PR #104 has been approved and merged.
- KYC Match Score: 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 owned by the MNO/CSP are will be calculated and returned.
- Meta Release Fall-24 candidate is being discussed; Plans to include KYC Match v0.2 (basic Match + Match Score) and KYC Fill-in v0.1 (basic Fill-in). Issue
|
Updated:
LocationInsights
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
NetworkAccessManagement
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
- 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:
NetworkSliceBooking
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
NumberVerification
Expand | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
OTPValidationAPI
Expand | |||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
PopulationDensityData
Expand | |||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
QualityOnDemand
Expand | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
RegionDeviceCount
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
ShortMessageService
Expand | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
SimSwap
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
SiteToCloudVPN
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
@Dan Xu
|
Updated:
SimpleEdgeDiscovery
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
SimSwap
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
SiteToCloudVPN
VerifiedCallerExpand | |||||||
---|---|---|---|---|---|---|---|
|
Updated:
@Dan Xu
WebRTC
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
|
Updated:
@Dan Xu
VerifiedCaller
NetworkAccessManagementExpand | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
WebRTC
LocationInsightExpand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
SimpleEdgeDiscovery
|
Updated:
Deliverable
R/O
Current status / Achievements
API Definition
API doc/user stories/testcases
Implementation
API Reviews and extensions
Updated:
Tenure
Deliverable
R/O
Current status / Achievements
API Definition
API doc/user stories/testcases
Implementation
API Reviews and extensions