Duration 60 minutes
| Duration | Agenda Item | Requested by | Notes / Links |
|---|---|---|---|
| START RECORDING | |||
| Integration Testing Status | |||
| Release Management Status | Gildas Lanilis Gmail | ||
| Kubernetes Version Governance | TSC-46 - Getting issue details... STATUS | ||
| Questions on CLM jobs going forward, PTL responsibilities. | |||
Grant nexus-iq access to non-committer contributors seeking to fix CLM issues While I understand the dual reasons why we protect clm content from non-committers - we are loosing the active contributors that fall out of the access scope. The access is currently binary - because anyone can get a non-vetted LF account - it needs to be 3 part - in order to work and accelerate clm work Committers, contributors, the rest of LF users. 1) to abide our license agreement Proposal: allow for vetted contributors that can access nexus-iq and the security space. This could be done by providing a way for all contributors to be a committer on at least one project - or create a sandbox project we can vet committers to. Gildas raised a good point - verify we are not overriding any oparent versions that already fix the dependencies | TSC-49 - Getting issue details... STATUS | ||
| Status on nexus-iq replacement - github now has a fully functional microsoft contributed vulnerability scan - the owner of github.com/onap should see them | TSC-32 - Getting issue details... STATUS | ||