kubernetes / kubernetes/steering
Revision of third-party content in documentation
- Dominant language
- No language data
- Stars
- 100
- Forks
- 70
- PR merge metrics
- No merged PRs in 30d
Description
### Problem Statement
This issue serves as a follow-up to [kubernetes/website#51014](https://github.com/kubernetes/website/pull/51014).
To summarize: [kubernetes/enhancements#1327](https://github.com/kubernetes/enhancements/pull/1327) introduced a new policy regarding third-party content. However, this change went largely unnoticed until it surfaced during the review of [PR #51014](https://github.com/kubernetes/website/pull/51014).
Several maintainers and contributors shared their concerns about the policy, and it was suggested that the conversation be continued here to more effectively address feedback from the community.
### Proposed Solution
Initiate a formal discussion with the Kubernetes Steering Committee to better understand the rationale behind the policy introduced in [kubernetes/enhancements#1327](https://github.com/kubernetes/enhancements/pull/1327). This will help clarify the intent, scope, and long-term vision for third-party content guidelines.
Contributor guide
Research direction
Start by reviewing kubernetes/website#51014 and kubernetes/enhancements#1327, then read the discussion in this issue for the concerns about third-party content policy. Done means holding the proposed formal discussion with the Kubernetes Steering Committee and clarifying the policy's rationale, scope, and long-term guidance.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100