KEP-1326: update KEP and mark implemented

[lmktfy]

• One-line PR description: Update KEP and mark as implemented

• Issue link: Doc policies for third party content #1326

Other comments:

• This is a policy KEP and does not have any release-related graduation criteria.
• Replacement for PR KEP-1326: update KEP and mark implemented #5216

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: lmktfy
Once this PR has been reviewed and has the lgtm label, please assign jeremyrickard for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• keps/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Welcome @lmktfy!

It looks like this is your first PR to kubernetes/enhancements 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/enhancements has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @lmktfy. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[sftim]

/ok-to-test
(if I do say so myself)

[lmktfy]

These are from Steering, and the policy itself has already been approved (and implemented).

[kikisdeliveryservice]

@lmktfy could you add the appropriate reviewers/approvers for this?

[divya-mohan0209]

A nit.

We should consider explicitly stating that the scope of the policies mentioned in this point and the standards in the point below are specific to SIG Docs and the content it is responsible for. It might be implied, but I'd like to leave no room for misinterpretation later on.

[natalisucks]

agreed

[lmktfy]

Eesh. I don't want one policy that applies to content SIG Docs manages and a different policy for other documentation that is also from the Kubernetes project.

I want Kubernetes, the project, to follow one policy about third party content. Is that harmful if we do that? I am happy to get steering to endorse a project-wide policy.

[lmktfy]

To settle this, we should find people willing to reach out to other SIGs and let them know about this policy, and that we are planning to formally say that this applies across the Kubernetes project.

My reading of the KEP is that it already does, but we didn't staff a big effort to communicate the policy change. It may surprise people if we don't communicate it.

[divya-mohan0209]

A minor nit, but otherwise LGTM.

[lmktfy]

Actually, this is just a cleanup.

/assign @johnbelamaric

Wrong KEP

[lmktfy]

/unassign @johnbelamaric