Incubating Candidates Fall24
- Herbert Damker
Update from TSC 2025-02-06:
Decision will be taken in a TSC vote which ends on Feb 14, 2025. The proposed decision is
to incubate the “green” API repositories based on the available information directly
which are: CallForwardingSignal, DeviceLocation, DeviceStatus, SimpleEdgeDiscovery, NumberVerification, OTPValidation, SimSwap, KnowYourCustomer, QualityOnDemand
to ask the API Backlog Working Group to check the remaining four candidates and give a recommendation about their incubation, if possible within for the TSC meeting on February 20th
which are: CarrierBilingCheckOut, ConnectivityInsights, HomeDeviceQoD, PopulationDensityData
As of 2025-02-05:
According to TSC Minutes 2024-12-19 … all API Repositories which had a release in the yes meta-release are candidates for transition to Incubating. The criteria are defined within ProjectStructureAndRoles.md and within the upcoming “API Onboarding and Lifecyle-Management.md” (see PR #171).
The purpose of the table below is an interim overview of these candidates and to check the fulfillment of prerequisites. It is intended to be replaced by a process within the API Backlog working group. The final decision about the incubation of an API Repository is with the TSC.
API Repository Name and Link | Fall24 (1a) | Spring24 M3 (1b) | Initial version implemented (2) | Number of maintainers (3a) | Number of Codeowner (3b) | API Backlog | (Target) | TSC Approval |
|---|---|---|---|---|---|---|---|---|
v0.2.0 | complete | v0.2.0 (7) | 3 | 3 |
| Call Forwarding Signal |
| |
v0.3.0 | done | “v0.2.0-wip” (1), | 4 (5 incl GSMA) | 3 |
| Carrier Billing CheckOut |
| |
0.4.0 | to be completed | not listed on OGW | 3 | 3 |
| Connectivity Insights |
| |
Verification 1.0.0 | done | Verification 0.1.0 (4), 0.2.0 (4), 1.0.0 (1), “tbc” (6) | 6 | 3 |
| Device Location |
| |
Roaming | to be completed | Roaming 0.4.1 (2), 0.5.x (4) | 6 | 4 |
| Device Status |
| |
1.0.0 | to be completed | 0.9.3 (2), “tbc” (1) | 3 | 4 |
| Edge Cloud |
| |
0.4.0 | skipped | 0.2.0 (1) | 4 | 2 |
| Home Device QoD |
| |
1.0.0 | complete | Verify 0.3.1 (26) , 0.4.0 (2), 1.0.0 (1) | 4 | 3 |
| Number Verification |
| |
1.0.0 | complete | 0.5.0 (12) | 3 | 2 |
| Number Verification |
| |
1.0.0 | complete | 0.4.0 (32), “tbc” (6) | 3 | 2 |
| Number Verification |
| |
Match 0.2.1 | to be completed | Match 0.1.0 (2), “tbc” (1) | 5 | 3 |
| Know Your Customer |
| |
0.1.1 | to be completed | not listed on OGW | 3 | 3 |
| Population Density Data |
| |
0.11.1 | complete | 0.8.2 (2), 0.10.x (4) | 9 | 4 |
| Quality On Demand |
|
(1a) Successful participation in one of the last meta-releases with an approved public release. As of today given for all successful Fall24 participants - released API versions listed (“main” APIs, without subscription APIs)
(1b) Spring25 M3 status for information, not a prerequisite for the Fall24 participants, but could be taken as an indication. Status based on review issues in Release Management.
skipped: repository has not participated within the Spring25 cycle or withdrawn
to be completed: essential assets are yet missing, typically updated test definitions
complete: minor review comments to be addressed
done: M3 pre-release Spring25 with release candidate API versions released and created
(2) Have released at least one Initial API version which is implemented by at least one operator (technical validation of the API in real environment). Can be shown by an entry within https://open-gateway.gsma.com or confirmed statement by operators within the incubation process. Information in table from https://open-gateway.gsma.com (OGW) if not otherwise stated, in brackets the number of operators which are listed with that version, as of 2025-02-05.
(3a) Taken from MAINTAINERS.md within the API repository, only one maintainer per company counts
(3b) Taken from CODEOWNERS within the API repository, minimum of two companies
(4) Shortlink to the (closed) issue within API Backlog WG, plus either “tbd”, “ok”, “objections”. The Working Group could lock on additional criteria, e.g. continuous activity, engagement of maintainer companies, …
(5) Proposals for initial Incubation, names can be discussed, e.g. Number Verification. Joining with further API repositories can happen after the initial setup.
(6) Date of approval within TSC