Alexis, thank you for the insights. > "Netdata is a fine project, but we struggled (as a TOC) to see it as cloud native." > "The decision was unanimous, in that no TOC member wished to sponsor

I was thinking of this comment: https://github.com/cncf/toc/pull/163#issuecomment-437167354 Harbor incubation proposal by clouderati · Pull Request #163 · cncf/toc · GitHub +1 non-binding. Our

Perhaps you’re thinking further kubernetes integrations which was in the slide deck for the TOC presentation. That preso was on 2018-06-19 while the links I provided for an early tagged release

Wasn't Harbor originally delivered ONLY as a virtual appliance, with the containers coming later? The discussion of whether to accept it as a CNCF project received pushback at the time based

Costa The decision was unanimous, in that no TOC member wished to sponsor Netdata. Had a sponsor stepped forward, Netdata would have been invited to initiate the DD process for incubation, with

+1, the TOC felt the same way when the voting happened. <markpeek=vmware.com@...> wrote:

Matt, Yes, indeed, we do have the Definition. The TOC worked on this along with the layered stack (architecture) and landscape (which fits into the stack). You are 100% right that there should be

Roger, I get your point but disagree with your example. Harbor is delivered as a set of containers and I would consider it cloud native. For convenience it is also delivered as a virtual

No, my point is that what makes something sufficiently cloud-native to be on the landscape may not be totally obvious. Roger B.A. Klorese Senior Product Manager SUSE 705 5th Ave S, Suite 1000 Seattle

Roger are you saying this applies to Netdata too? Because Netdata is not a virtual appliance...

If I recall correctly, for instance, when Harbor was added, it was a valuable component for cloud-native deployment - but it was not itself cloud-native, since it was delivered as a virtual

Alexis, thank you for the information. So, you say that TOC members discussed about Netdata and decided it is not cloud native and should not be invited to CNCF. Are there any meeting minutes about

Alexis, Maybe you can help me with this. The CNCF has a Cloud Native definition. A lot of things fit this bill in one way, shape, or form. Far more than are in the landscape. What is missing that the

Josh, please see my reply to Matt which expresses why it is so diminished. <josh.michielsen@...> wrote:

I'm well aware you did. Certainly that makes your opinion a valuable one! But again I have to stress being it's founder doesn't mean you can speak for everyone else that finds it valuable. The

Matt OK, but: We are doing a disservice to new users by publishing a "cloud native" landscape, that contains non-cloud-native projects. If we don't have an opinion about what is cloud native and

Josh I created the landscape, so I feel I have a dog in this race. a <josh.michielsen@...> wrote:

This comes across as "I don't find it valuable therefore it has no value", which isn't exactly a nuanced opinion. You certainly don't represent my feelings on the topic. Much like how you found

I have to respectfully disagree that it’s meaningless. Consider the case where someone is new to the space or a category in it. Where does one start to find the options in the space? Search engines

When we first made the landscape, it (1) had a particular structure and (2) attempted to show what projects are cloud native and where they live in that structure. Now, it has everything in it. So