From Code to Docs to Marketing: How to Contribute
summary
Overview of concrete contribution paths: weekly SIG meetings and a public Argo project calendar, labelled good-first-issue GitHub tags, and membership steps in the umbrella repo. Examples: a production Argo CD perf bug gets fixed in two days; one newcomer lands a single PR that upgrades a cluster UI feature. Dev tips: use the developer guide, run controllers locally, run make pre-commit to catch CI checks, expect flaky end-to-end tests. Built items to reuse: the Argo CD extension system (Rollouts as an extension), a reverse-proxy extension PR, and an AdaLogics security audit with CVEs already fixed.
AI-written summary · about
chapters (7)
- 0:00Argo projects contribution intro
- 1:05Why contributing isn’t just about coding
- 15:49Argo Workflows codebase
- 29:24Marketing for open source
- 33:52Argo UI and extensions
- 44:09Security contributions
- 50:34Q&A
related talks
04mPull Requests Welcome! - How to Contribute to the Argo Community
11mLightning Talk: 10 Ways To Get Involved in Argo Project
38mTAG Workshop
34mHow to get them to Commit?
07mSponsored Keynote: Argo Project: The Cloud Native Key Ingredient
26mContributing to Open Source with the example of Icinga
32mYour Guide To How CNCF Projects Actually Do Documentation
46mBuilding Developer Community One Pull Request at a Time
