github.com/GoogleContainerTools/skaffold/v2@v2.13.2/docs-v2/design_proposals/README.md (about)

     1  # Design Proposal Process
     2  
     3  Hello Contributors!
     4  
     5  This document describes the process for proposing a new feature or making any
     6  large code changes to `skaffold`. By large we mean,  large in impact or large in
     7  size.
     8  
     9  Examples for large impact changes would be:
    10  
    11  1. Introduce templating, or
    12  2. Arbitrary command execution in certain places
    13  
    14  These could be small code changes but large in impact.
    15  
    16  Submitting a proposal before a pull request will likely reduce the back and
    17  forth between the contributor and the core team. A proposal also ensures that
    18  each new feature or a large change has a design review.
    19  
    20  For any new feature, config or large change, please add a design proposal document
    21  as described in [Design Proposal Template](./design-proposal-template.md).
    22  
    23  Once you create a PR with the proposal, one of the maintainers will be
    24  assigned as a design shepherd. The role of the design shepherd will be to make
    25  sure:
    26  
    27  1. The feature/change is aligned with the Skaffold roadmap and the team's general
    28     philosophy for the tool and not a one off solution for a specific use case.
    29  2. The feature/change scope is well defined.
    30  3. When changing any existing feature, the implementation plan adheres to
    31     [Skaffold Deprecation Policy](http://skaffold.dev/docs/references/deprecation/).
    32  
    33  Once the proposal has been approved, we can move discussions to our bi-weekly
    34  meetings to address any open concerns,and to reach a final decision on whether
    35  or not to accept the feature or change.