Welcome to the Argo Community!
Argo is an open, community driven project to make it easy to use Kubernetes for getting useful work done. This document describes the organizational structure of the Argo Community including the roles, responsibilities and processes that govern Argo projects and community.
The Argo community has two regular community meetings:
-
Argo Workflows and Argo Events
- Meets monthly, 3rd Wednesday of every month 10:00 AM Pacific Time
- Agenda & Meeting Notes
-
Argo CD and Argo Rollouts
- Meets monthly, 1st Wednesday of every month 10:00 AM Pacific Time
- Agenda & Meeting Notes
Most of the community discussions happen in the Argo related CNCF Slack channels. You can join here.
Argo is organized into a set of projects. Each project has at least one lead. The leads are responsible for driving the project, publishing a roadmap, organizing community meetings, publishing meeting notes, and reporting on the current status of the project.
The projects are:
- Argo CD - Declarative GitOps Continuous Delivery
- Argo Events - Event-based Dependency Manager
- Argo Workflows - Container-native Workflow Engine
- Argo Rollouts - Progressive Delivery with support for Canary and Blue Green deployment strategies
Approvers and leads for each project are responsible for organizing regular community meetings to provide status updates and solicit feedback.
- Meeting agendas should be published at least one week prior to the meeting.
- Community members should be able to attend the meetings remotely.
- Meeting notes summarizing the meeting and any decisions made should be published within 24 hours of the meeting.
- Meeting recordings should be published within one week of the meeting.
Contributing doc here
Governance doc here