We will have our regular TOSCA Community meeting on Wednesday July 1 at 5:00pm CET, at 4:00pm in the UK, at 8:00am US Pacific Time, and10:00am US Central Time. Please join at https://us02web.zoom.us/j/83059314783?pwd=QZ0ria97PMZsFMDrQb1uXAwaLassq9.1
This week, we will focus on the following:
Action-item review
- Abstract-profile PR (Chris, N8) - platform-specific connection properties (management address, credential file, config/access file) on the abstract platform types. Status / review.
- in_range PR (Roberto, D8) - re-add in_range to community.tosca.core with the TOSCA v1.3 2-arg (value, range) signature. Status / review.
- Governance docs - confirm the folder move to the repository top level (P5); collect review feedback (I19: add test info).
Release process
Last week's meeting adopted a simple release process (GitHub workflow packaging CSAR artifacts, a 0.1 release, flat directory structure). Chris has since built exactly this for the Ubicity profile repos and can share what worked, as a reference for the community 0.1:
- Draft-first flow - the workflow builds + signs and opens a draft release; notes are added and it is published deliberately (keeps asset ids stable through to publication).
- Sigstore keyless signing + verification - CSARs signed via the GitHub Actions OIDC identity (cosign), with verify_release.sh / verify_all.sh helper scripts consumers run. Recommend adopting for the community 0.1.
- CSAR naming from the profile: keyword - derive the CSAR filename from the advertised profile name, not the directory path, so a version bump is a one-place edit and flat directories work cleanly.
- Decide: target date for the 0.1; workflow owner; adopt Sigstore signing?
Thanks,
Chris