A while ago CNCF has created the CNCF landscape project: GitHub - cncf/landscape: 🌄The Cloud Native Interactive Landscape filters and sorts hundreds of projects and products, and shows details including GitHub stars, funding or market cap, first and last commits, contributor counts, headquarters location, and recent tweets.. This landscape was later adopted by other orgs including the CDF: GitHub - cdfoundation/cdf-landscape: 🌄CDF Landscape: a living document that developers, investors, vendors, researchers and others can use as a resource on the landscape of continuous delivery.
I wonder whether we could create our own Jenkins Landscape focused on users.
Proposed structure
The latest version of CNCF landscape supports multiple tabs. We can leverage that.
General tab
- Jenkins installer and public cloud distributions, similar to what jenkins.io/download offers
- Key plugins and integrations
- Sub projects: JCasC, Remoting, Jenkins Operator for Kubernetes, Jenkinsfile Runner, Stapler, etc.
- Downstream OSS projects using Jenkins, e.g. Spinnaker, Jenkins X, Kubesphere, Gitlab (via Gitlab Jenkins Wrapper)
- Jenkins training providers/platforms: The Linux Foundation, Udemy, Simplilearn, CloudBees, etc.
Community tab
- Project entities: Board, teams, etc.
- Special interest groups
- Key people (elected roles, team leads). Might be a matter for the community landscape
- Communication channels
- Social media
- Key company contributors
- TBD: Key donors
Commercial tab
Somewhat replaces https://wiki.jenkins.io/display/JENKINS/Commercial+Support
- Jenkins vendors and support providers, including CloudBees, VirtusLab, Red Hat
- Paid support/consulting providers, e.g. TechMatrix, Eficode, etc.
- Training providers
- Certification providers, e.g. Linux Foundation or CloudBees
- Contract development/outsourcing