Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adopt an Arcaflow roadmap #48

Merged
merged 1 commit into from
Jul 3, 2024
Merged

Adopt an Arcaflow roadmap #48

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions art-decisions/proposals/2024-06-07-arcaflow-roadmap.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
# Implement Arcaflow Roadmap

Arcaflow should have a high-level roadmap used to guide the project's strategic
direction. The roadmap should be kept as a ROADMAP.md file in the
[.github](https://github.com/arcalot/.github) with other community documents. The
roadmap should be be time- and dependency-based, defining the major ambitions we have
for the Arcaflow project as a community. The roadmap should not duplicate or restate
efforts that are already tracked in Issues or Pull Requests, but it may reference them
as sub-efforts or dependencies. The roadmap should be reviewed and updated routinely
as part of regular community meetings.

## Voting Period

The voting period for this proposal will be open for 10 working days from its submission.

## Benefits

The roadmap will help us focus as a community on our major strategic priorities for
Arcaflow. It is also required to have a defined roadmap as part of a CNCF submission.

## Drawbacks

The roadmap becomes another planning tool to maintain and could become stale if we do
not ensure it is part of our regular processes to review and update.