...
- Add a process/policy around the cut-off dates in the release cycle for addressing vulnerabilities within the required 60 day window
- implement a " three strikes rule " to remove a PTL from a project if they fail to attend X number of TSC and PTL meetings w/o a designated proxy..
Requires a modification to Section 3.1.3 of the Community document
Kenny Paul - On-boarding new projects or usecases
- Improved documentation of who to talk to (which subcommittees) and when to do so. Seems to be more tribal knowledge based versus a clear process.
Gildas Lanilis Gmail - Make description Field mandatory in JIRA (for all type of issues)
- There are too many cases where people neglect to describe the issue they encounter, the expected behavior, the environment they are working one.
Gildas Lanilis Gmail - Obtain formal engagement from committer prior to M1
- By M1 Release Planning, PTLs should obtain formal written commitment from "committers" list on their engagement for Dublin Release. (no response from committer must be interpreted as a disengagement)
Eric Debeau - Provide a better control code chain for Python based code (PEP8, Pylint, Bandit, Coverage) cf
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Eric Debeau - Include documentation (RST file) control using doc8 and additional controls (cf Rich Bennett set of tools used to check bad links...)
Eric Debeau - Swagger API description validation to be included in Gating project (M3) cf
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Eric Debeau - Enhance Helm chart validation (each project will be responsible to define Helm charts, as a result, we need some control tools to validate the rules defined by OOM team)
Eric Debeau - Verify Dockerfile. CIA initiative has defined a set of rules to produce Docker images. We should implement some basic tests to verify what is possible (eg list of base images, number of layers...) cf
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|