Document Requirements for spending CNCF money on sigs about k8s.io

[dims]

"Various projects in the kubernetes and kubernetes-sigs github organizations produce artifacts including release binaries, container images etc. The wg-k8s-infra will help figure out choices/options for supporting the creation and dissemination of these artifacts."

Is this enough? where do we add this language?

[spiffxp]

I think we should add this to the wg-k8s-infra charter.

We also discussed:

• escalation: checking with a CNCF representative first, then going to steering
• priority: spend money to migrate Google-owned infra to CNCF-owned infra, understand our burn rate, and then consider additional spend on new/other infra
• (discussed in steering) if it's less than $X, use service desk tickets directly with CNCF

[spiffxp]

/kind documentation

[idvoretskyi]

/cc

[dims]

/assign @spiffxp
/unassign

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.