DRAFT
...
MINUTES
Attendees & Representation
...
- Minutes of previous TSC meeting: 2024-07-04 TSC Minutes
- Herbert has to change the date of the open action (done)
Action Item Review
- See home page Technical Steering Committee
...
- Open Source Summit (Sept 16-18, Vienna) : - no updates from Markus yet:
- CAMARA applied for 2 Call for Papers (2 presentations) but still no feedback
- Current plan is to have a little booth and some swag. Also here still waiting on feedback
...
- API Proposal for approval, see https://lists.camaraproject.org/g/tsc/message/206:
- Number Recycling - https://github.com/camaraproject/APIBacklog/issues/54
- Ricardo provided a sum-up to the API objective.
- Discussion in KnowYourCustomer: Do Tenure API, NumberRecycling API and Shutdown Service Status API fit in KYC Family /KYC SP meeting?
- Eric Murray raised a point about the complexity to manage KYC (managed by Toshiyasu Wakayama ) as we have now a lot of APIAPIs. We can have probably some 'subteam' meeting. Toshi has raised an issue to discuss this in the KYC WG.
- Herbert Damker asked that these 3 APIs scope have to be clarified to avoid redundancy (example: if Number recycling provide the length of the contract for this number what is the difference with Tenure?)
- We create the repo for NumberRecycling pointing to KYC but this attachment could be challenged.
- Number Recycling - https://github.com/camaraproject/APIBacklog/issues/54
- Herbert Damker There are still some PRs open within the former WorkingGroups repository. Would it be possible to decide about these (stale?) PRs?
- Action Point Ricardo Serrano Gutierrez
...
- Release 0.4.0-rc.1
- Aggregated list of bugfixes: https://github.com/camaraproject/Commonalities/issues/253
- New topics:
Add rules in design guideline about multi-endpoint API design & implementation requirement #246
- Do we decide that an API must be fully implemented (all endpoints have to be able to provide 2xx response) in order to be "certified"* ?
- Tendency to yes and split to have distinct yaml if independent resource
- We need an option for an optional endpoint when they are on the same resource (we cannot split-up)
- We can add only 501 when, for a multi-endpoint working on a same resource, we have optional endpoint
- Mandatory endpoints must not have 501 defined as a valid response
- We have a discussion on SimSwap API and in particular the challenge to provide the date for some implementation. Diego provided his perspective; this is covered with the current API where we can sent back null information if date is not available. To be discussed in the simswap group but this proposal could avoid splitting.
- Do we decide that an API must be fully implemented (all endpoints have to be able to provide 2xx response) in order to be "certified"* ?
Add an “Area” data-type into CAMARA_common.yaml #242
- Sub projects using geographical area definitions asked for their feedback
- This is a topic for next meta-release
- None of the API concerned by this PR will be in 'stable' maturity level.
- Jose Luis Urien also raised the point about enhancing common artifact to easily re-use structure definition from one API to another (and avoid manually copy).
How to inform API consumer about unprocessable subscription request in Async mode #243
Request body is required but all properties are optional #247
...
- Next TSC Meeting will be on August 1st at 10:00 CEST / 08:00 UTC / 01:00 PST
- No summer break !!
- Specific agenda topics backlog:
- ...
Action items
- Create repository for NumberRecycling Herbert Damker
- Migrate remaining open PRs out of https://github.com/camaraproject/WorkingGroups/ Ricardo Serrano Gutierrez
- Tanja de Groot will send a email indicating that the PR release (changelog, readme, yaml, checklist) & target (list of issue) must be provided by
- Casey Cain Will check if SSO with LFID will continue to work after a migration of the wiki into the Atlassian Cloud