Problem Validation: Guidelines for CI/CD template submissions from Technology Partners
Problem Statement
From #323727 (closed)
I believe we need to establish guidelines for every step of this process. Including:
- Guidelines for creating the template itself, with standards that can be used across all templates. This includes:
- Where to put the template, and naming standards?
- What syntax is recommended, and what syntax to avoid?
- Required style?
- Required comments? For example, explain if it's intended to be added with
include
or used standalone. Explanation of variables, prerequisites, etc.
- MR review process:
- Who to ping first?
- How to demonstrate the template in action?
- Template maintenance:
- Who is responsible for maintenance?
- How is the template maintained? If there are issues, who should the public contact, and how should they do it?
- What happens to the template if the partnership expires?
Reach
3.0 = Significant reach (~25% to ~50%)
Impact
2.0 = High impact
Confidence
80% = Medium confidence
Effort
Unknown