Present at the Argo Workflows community meeting
Open
- Dominant language
- Go
- Stars
- 112
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
You should come tell our users more about this.
Contributor guide
Research direction
Start by reviewing the repository description and the Argo Workflows community meeting context to determine what Orkestra should present. Confirm the meeting’s submission or scheduling requirements and define completion as delivering or arranging the requested presentation; no implementation files or tests are identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- content
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100