...
- Pull requests
Open:
- #16 updated documentation to include User Story and API readiness checklist Mahesh has seen the comments and is working on them
- #19 Create Megalinter merged during call
Merged since last call: #7 , #8, #10, #11, 15
- Issues
Open:
- #17 Event subscription and notifications should be aligned with API Design Guidelines assigned to Kevin
- #18 Alignment with API design guidelines: add linter fixed by #19 (now merged)
- Discussions
Completed actions were confirmed:
IN PROGRESS Kevin to clarify if a need for consent (or a check for consent-needed) is determined by the sub-project or other body in CAMARA.
Guidance from commonalities is to include a security component but with an empty scope until this is clarified.
Issues: see discussion and resolution in 'Issues' section above.
Question: can megalinter be run outside Github (as a precheck)?
Labels added to issues and PRs: 0-2-0-wip and 0-3-0-wip. These indicate the target version for the issue/PR (i.e. 'this issue is intended to be fixed in 0-3-0-wip', 'this PR is to create the 0-3-0-wip version' )
- AOB
- none
Action items
- Kevin Smith to check if megalinter can be run outside Github as a pre-check
- Kevin Smith to align the Connectivity Insights API spec with commonalities guidelines, following results of local Spectral output