cncf / cncf/landscape

Question: Should "Projects and products" show all CNCF projects?

Open
#4,522 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
10k
Forks
2.2k
Avg merge
2d 1h
Merged PRs (30d)
71

Description

Currently, not all CNCF projects are available by selecting the "Projects and products" group, and the Status -> CNCF Projects filter, which is misleading.

Is this intentional, or do projects that aren't currently listed need to update their category or second_path in the cncf/landscape landscape.yml?

For example, k3s, CozyStack, Flatcar, and Kubeclipper are not available under the "Project and products", and are rather only available under "Certified partners and providers", the name of which is also misleading.

k0s on the other hand, is available in both locations, because it's first path is `Orchestration & Management -> Scheduling & Orchestration` and it's second_path is `Platform / Certified Kubernetes - Distribution`. Arguably, those categories should be flipped. But regardless, should k3s, CozyStack, Flatcar, and Kubeclipper have `Orchestration & Management / Scheduling & Orchestration` added as a second path? And should other projects be advised to also add additional paths? Or perhaps is "Projects and products" missing some categories?

Contributor guide

No contributing guide indexed for this repository

Research direction

Review the project entries and path fields in cncf/landscape's landscape.yml, comparing k3s, CozyStack, Flatcar, Kubeclipper, and k0s. Clarify the intended relationship between the displayed groups and category paths before changing anything. Done means the categorization policy is decided and the affected project entries or labels consistently reflect it.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.