Argo is not a single project

[kostis-codefresh]

Argo is actually 4 independent and self-contained projects

1. Argo Workflows should be placed in "pipeline orchestration"
2. Argo Rollouts should have a new category "Progressive delivery". See also Progressive Delivery Category #177
3. Argo CD should have a new category GitOps. See also GitOps Category #178
4. I am not sure where to place Argo Events. To be defined in the future..

[e-backmark-ericsson]

I would say that Argo Events should fit well in "Protocols and Messaging"

[tracymiranda]

A number of other projects are also umbrella projects in this way e.g. Tekton (Tekton triggers, chains, cd, etc) as well as Jenkins (Jenkins template engine, file runner, etc). We should consider how to find the right balance with showing the distinct projects under the same brand umbrella and not cluttering the landscape and making it overwhelming.

[MarckK]

#175

[sbtaylor15]

The CNCF pattern restricts projects/companies to one category. The projects/companies should pick the best overall core competency category. Additional, language should be added to the bottom of the landscape highlighting this pattern.

[kostis-codefresh]

I look at the CNCF landscape and I see

• Hashicorp (vault, terraform and nomad are different entries)
• Suse (rancher and portus are different entries)
• Redhat (openshift, quay, ansible are different entries)

[kostis-codefresh]

@sbtaylor15 Even at the Continuous Delivery Landscape itself I now see separate entries for Flux and Flagger.
So why not have different entries for Argo CD and Rollouts?