DRAFT MINUTES
Attendees & Representation
TSC Members may indicate their attendance by marking an X in the column to the right.
Community members may use @name tag to mark their attendance below the table.
| Representative | Organization | Role | |
|---|---|---|---|
Deutsche Telekom AG | TSC Chair, Active Maintainer | x | |
Deutsche Telekom AG | Active Maintainer | ||
Ericsson | Active Maintainer | x | |
KDDI | Active Maintainer | x | |
Orange | TSC Deputy Chair, Active Maintainer | x | |
Radisys | EUC Representative | ||
Summit Tech | EUC Representative | x | |
Telefonica | Active Maintainer | x | |
Telefónica | Active Maintainer | x | |
Verizon | EUC Representative | x | |
Vodafone | TSC Deputy Chair | x | |
Vodafone | Active Maintainer | x | |
Vonage | Active Maintainer | ||
| George Glass | TM Forum | TM Forum Representative | x |
TM Forum | TM Forum Representative | ||
GSMA | GSMA Representative | x | |
GSMA | GSMA Representative |
LF Staff: Rafal Artych Axel Nennker Murat Karabulut Nicholas Venezia Patricia Serrano Jorge Garcia Hospital
Community: Casey Cain
Agenda
The project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF. |
- Review and approval of previous meeting minutes
- Action Items Review
- General Topics
- Governance & project management issues
- Commonalities
- Identity & Consent Management
- Release Management
- API Backlog
- Specific Topics
- Update on Sandbox/Incubated/Graduated proposal
- Any Other Topics
Minutes
Review and approval of previous meeting minutes
- Minutes of previous TSC meeting: 2024-08-01 TSC Minutes
- No comment frome the team
Action Item Review
- See home page Technical Steering Committee
- Information about the migration of the Wiki into the Atlassion Cloud has been communicated during the meeting (thanks Casey Cain )
Governance & Project Management issues
- EasyCLA Introduction (Casey Cain Herbert Damker )
- People from multiple companies have done successful test PRs on https://github.com/camaraproject/EasyCLA
- Including Deutsche Telekom, Orange, KDDI, Vodafone, Telefonica, T-Mobile
- Please use the chance to ensure that you have a signed CLA before it will get activated on all repositories, by opening a short test PR here
- In case of any problem reach out to Casey Cain
- Activation on September 2nd (according to last TSC)
- Casey Cain will be available if support is required
- People from multiple companies have done successful test PRs on https://github.com/camaraproject/EasyCLA
- Release announcement will be prepared by Marketing Working Group in cooperation with Release Management working group
- There will be a Press Release, an announcement within the keynote of Arpit Joshipura, and slides about the Meta Release within the CAMARA presentation
Commonalities (Rafal Artych )
- Release r0.4.0-rc.2 as second release candidate with bug fixes created on August 9th
- Fixed bugs as listed in Commonalities/issues/253
- Minor changes since then:
- Broken links replaced with relative links in API-linting-Implementation-Guideline.md Commonalities/pull/274
- Links between Commonalities documents set to relative (in API Design Guidelines, Issue and PR template Howto, Linting-rules) Commonalities/pull/283
- Filename boilerplate changed to kebab-case to match examples in API-Testing-Guidelines.md Commonalities/pull/281
- Pull request for the public release - to be approved today: Commonalities/pull/286
- Related review issue in Release Management: ReleaseManagement/issues/75
- Request to TSC to approve: Approved ! - No objection
An issue is open to discuss the scope of the next version: Commonalities/issues/273 - scope should be closed for
Identity & Consent Management (Axel Nennker )
- Release r0.2.0-rc.2 as second release candidate with bug fixes created on August 1st
- Change of mandatory text has been addressed across all API release candidates
- No further changes since then
- Pull request for public release to be approved today: IdentityAndConsentManagement/pull/192
- Related review issue in Release Management: ReleaseManagement/issues/76
- Request to TSC to approve: Approved ! - No objection
- An issue is open to discuss the scope of the next version - scope should be closed for
Release Management (Initial content by Herbert Damker on behalf )
- Meta-release Fall24 - CAMARA Project - Confluence
- M3 Milestone (release candidate of APIs) achieved for 21 APIs (as of August 21st)
- Overview of the available release candidates (as of August 16th):
- Stable APIs (target v1.0 version, previous API versions launched by operators):
location-verification, number-verification, one-time-password-sms, simple-edge-discovery, sim-swap - APIs with updated initial versions (previous launched by operators):
carrier-billing, device-reachability-status, device-roaming-status, home-devices-qod, kyc-fill-in, kyc-match, quality-on-demand - "New APIs" (some with previous initial versions or split out of other APIs):
call-forwarding-signal, carrier-billing-refund, device-reachability-status-subscriptions, device-roaming-status-subscriptions, geofencing-subscriptions, population-density-data, qod-provisioning, qos-profiles
- Stable APIs (target v1.0 version, previous API versions launched by operators):
- One open review issue of a release candidate (ConnectivityInsights) with connectivity-insights, application-profiles (as of August 21st)
- Proposal to still include (hopefully done as of TSC time)
- Additional candidate (almost ready and within SimSwap repository): sim-swap-subscriptions
- Excluded from Fall24 meta-release: network-slice-booking (no YAML yet), network-access-management (not time to address review results, will go for Spring25), WebRTC (no release tracker, no response during M3)
- Overview of the available release candidates (as of August 16th):
- M4 Milestone (Public releases) - next steps and dates
- August 26th (M4 release PRs available): Sub Projects should have prepared the release PRs for the public API version(s), including the release notes in CHANGELOG.md which are reflecting all changes since the last public release. Invite camaraproject/release-management_maintainers for review, don't merge before have the approval
- If there are outstanding PRs (e.g. with test definition files) anticipate them and add remark within the release PR description that these have to be merged before
- August 30th (M4 date): all outstanding PRs merged which have to done before the creation of the public release (e.g. test definition files)
- September 5th (Approval of M4): all release PRs of Sub Project reviewed by Release Management, final approval of the Fall24 participating API releases within the TSC.
- August 26th (M4 release PRs available): Sub Projects should have prepared the release PRs for the public API version(s), including the release notes in CHANGELOG.md which are reflecting all changes since the last public release. Invite camaraproject/release-management_maintainers for review, don't merge before have the approval
- M5 Milestone: all release PRs merged and public releases created.
- After M5 we have a retrospective time to collect team feedback - Do not hesitate to already create issue to log comments/ideas
- M3 Milestone (release candidate of APIs) achieved for 21 APIs (as of August 21st)
- Next release cycle ("Spring25") starts at September 30th (M0 - Kickoff)
API Backlog (Ricardo Serrano Gutierrez )
- New repositories still to be created (by CAMARA Admins, not yet done):
- Device Quality Indicator (Sub Project DeviceStatus)
- Device Data Volume (Sub Project DeviceStatus)
- New proposal approved by API Backlog Working Group
- Subscription Status (Sub Project KnowYourCustomer), see message https://lists.camaraproject.org/g/tsc/topic/new_api_proposal_taken_for/108016665
- Provide information about active/inactive service subscription (voice/SMS/data for example) for a given mobile line
- No objection from the TSC - Approved
- Subscription Status (Sub Project KnowYourCustomer), see message https://lists.camaraproject.org/g/tsc/topic/new_api_proposal_taken_for/108016665
Update on Sandbox/Incubated/Graduated proposal (Herbert Damker )
- New proposal for the lifecycle of API Repositories
- Issue in Governance to comment: https://github.com/camaraproject/Governance/issues/159
- Detailed proposal within Wiki: https://wiki.camaraproject.org/x/2IBFAg
- Jorge Garcia Hospital Question about process - What are the rules to evolve from Sandbox to Incubated and then Graduated
- Be sure an api did not get 'stuck' in Sandbox stage for example
- Herbert will take a look on this proposal and see how it reflect with our current API proposal
- Eric Murray Question about github visibility for the api 'stage'
- Not easy - Could be in a README on the organization level
- Casey Cain is working on this topic, reported that beside a README the use of 'topics' (kind of labels), filters on them and links to the filtered lists are the main options
- Herbert requested comment on the proposal, especially the criteria for incubation, for next TSC on the Confluence page or within the issue.
- Jorge Garcia Hospital Question about process - What are the rules to evolve from Sandbox to Incubated and then Graduated
Any Other Business
- Casey provided the information about the upcoming Wiki migration into the Atlassian cloud with a mail to the all mailing list (cf https://lists.camaraproject.org/g/all/topic/camara_confluence_migration/108039662)
Next Meeting
- Next TSC Meeting would be on September 5th at 10:00 CEST / 08:00 UTC / 01:00 PST
- For those TSC participants being on the OGW F2F meeting, there is a small room reserved at the venue, please contact Herbert Damker
- Specific agenda topics backlog:
- Kevin Smith Arazzo Specification discussion https://lists.camaraproject.org/g/tsc/topic/camara_tsc_arazzo_1_0/107766330
Action items
- Type your task here, using "@" to assign to a user and "//" to select a due date