PTL 2018-11-19 Meeting Agenda

Release Management Status

Including:

1. ONAP deployment: While doing the deployment of your Docker image, do you have to run  a “git clone” cmd or in other word is there “git clone” call in the Dockerfile?
2. Sync up from Helm chart to Docker Manifest files

Questions on CLM jobs going forward, PTL responsibilities.

(20181111 add oparent clm daily build - not weekly to keep CLM count at 0,0 for the root oparent pom) - https://lists.onap.org/g/onap-discuss/topic/oparent_spring_5_0_9_versions/28087317?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,28087317

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
2) to not disclose out vulnerabilities beyond vetted committers

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