CAMARA Population Density Data API - Follow-up meeting #12 - 2024-07-31
July 31th, 2024
Attendees
Name | Company |
---|---|
Gregory Lindner | Ericsson |
Rafal Artych | DT |
Jorge Garcia | Telefonica |
Population Density Data API minutes: https://wikilf-camaraproject.camaraprojectatlassian.orgnet/wiki/display/CAM/Population+Density+Data+API+Minutes
Agenda
- Approval of previous meeting minutes #9 and meeting agenda
- Open issues and PRs
- Issues: #12 #35 #37 #38 #39 #40
- PR #25 #41 #42
- Initial algorithm proposal review
- Timeline and next steps
- AoB
Open Issues & PRs
Issue#12 | Telefonica | Discussion on API algorithm - Initial proposal |
Issue#35 | Telefonica | Readiness checklist |
Issue#37 | Telefonica | Basic API Test Cases |
Issue#38 | Telefonica | API Code commonalities validation |
Issue#39 | Telefonica | API documentation |
Issue#40 | Ericsson | Area Data-type |
PR#25 | Telefonica | Documentation of API Algorithm |
PR#41 | Telefonica | Create API readiness checklist |
PR#42 | Ericsson | Documentation Update |
Approval of previous meeting minutes & documentation (1)
→ Approved
API proposal review (2)
Include the checklist for meta-release Fall24, including documentation, ATPs and alignment with commonalities (0.4.0)
...
AP: Rafal to validate the compliance of current code with the commonalities and I&CM v0.4.0
Status: Rafal to propose initial set of changes, to be reviewed during meta-release process, check Issue is opened
- API versioning convention applied → done
- API documentation → validate current documentation and (optionally) finalize the review of the algorithm description
...
AP: provide direct feedback on the commonalities issue Issue #242. Groups is ok to create a homogeneous definition of the area types, as long as each API can later select granularly which types apply (and not getting obligation to support all the types, or getting involved in a complex data model).
Status: Delayed until september, following commonalities track
Including the RC1 proposal for the API to be part of Meta-release process, updated also in wiki tracker
Review documentation changes and merge when ready.
Provide feedback to be merged before meta M4
Initial algorithm proposal (3)
K-anonimization to be clarified (in which step it is implemented)
...
Telefonica to provide feedback on these two topics to move on.
Status:
AoB (4)
Next steps:
- Group Break → To cancel meeting on 14th August, coming back on 28th of August.
Discussion Summary
Issue#12 | Discussion on API algorithm - Initial proposal | To continue offline, Telefonica to provide feedback |
Issue#35 | Readiness checklist | To include proper scope for meta-release |
Issue#37 | Basic API Test Cases | Telefonica to provide first proposal |
Issue#38 | API Code commonalities validation | Rafal (DT) to validate the compliance of current code with the commonalities and I&CM v0.4.0 |
Issue#39 | API documentation | Gregory (E//) to review and validate current documentation. |
Issue#40 | Area Data-type | ALL to provide feedback into commonalities issue |
PR#41 | RC proposal | To validate with meta-release admins |
PR#42 | Documentation (solving Issue39) | To be reviewed |
Next steps
- Feedback on algorithm proposal→ Follow-up meeting #13
- Align Meta-release items → #13
...