https://github.com/cncf/toc/blob/master/process/graduation_c...
which includes complying with the Core Infrastructure Initiative requirements:
https://bestpractices.coreinfrastructure.org/en/criteria/0
It does have a marketing aspect, as all Linux Foundation projects do, but it's not pure fluff.
CNCF projects have a maturity level of sandbox, incubating, or graduated, which corresponds to the Innovators, Early Adopters, and Early Majority tiers of the Crossing the Chasm diagram. The maturity level is a signal by CNCF as to what sorts of enterprises should be adopting different projects.
> Are there any foundations that don't operate like this?
Presumably. My main experiences are with the Apache Software Foundation, though, which in terms of "incubation" operates similarly to CNCF.
> Are foundations good at all for anything?
The answer is foundation-specific. But in general, foundations allow for pooling of resources and wisdom such as legal services, and allow for consumers to know a lot about a project's governance and status at a glance in a way which is difficult to ascertain for a standalone project on the web or Github or wherever.
Although, as you say, the specifics vary by foundation and range quite a bit in how heavyweight they are, foundations also provide something of a neutral home for projects. A company may still be somewhat dominant in a given project but it can't just take its ball and go home to the degree possible if it kept control of domains, trademarks, and so forth on its own.
I don't think it makes sense to assume that just because a project is at a foundation that it is independent by any useful definition. It's possible for dominant players to set things up such that they maintain effective control over the governance of a project which resides at a foundation. It's possible to generalize when you know the foundation, but it's not possible to generalize across all foundations.
In any case, if most of a project's committers are with a single company, that company is going to have a lot of control even if the project is nominally under generally neutral governance.
Here are ones I specifically know are important:
Graduated: kubernetes,prometheous,rook, helm, containerd, coredns
Incubating: CNI (Container Networking Interface), CRI-O, etcd, gRPC
Which is both a good and a bad thing. On one hand, without marketing, getting a system adopted on a large scale is hard. (as evident by many RFC's which are not used a lot in the wild). On the other hand, the CNCF seems to have a zillion products which all solve roughly the same problem in the same problem space, which seems to make it unnecessary and complex.
Maybe I'm being pedantic but what bugs me is the 'C' in CNCF. The CNCF is mostly/all 'K'ubernetes specific which is a subset of the software that targets 'C'loud Infrastrture-as-a-Service. The term cloud-native has lost some meaning, at least in search results.
The warts of CNCF are the same warts of GCP
The entire 'ecosystem' is filled with worthless crap like this with stupid marketing like "incubating" and "graduation" to infer on it some level of acceptance.
Are there any foundations that don't operate like this? Are foundations good at all for anything?