From fbc153b15fe8b0120644fb277d7d010ba30b3608 Mon Sep 17 00:00:00 2001 From: Dustin Black Date: Wed, 3 Jul 2024 10:47:10 +0200 Subject: [PATCH] Adopt an Arcaflow roadmap (#48) initial draft to adopt an Arcaflow roadmap --- .../proposals/2024-06-07-arcaflow-roadmap.md | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 art-decisions/proposals/2024-06-07-arcaflow-roadmap.md diff --git a/art-decisions/proposals/2024-06-07-arcaflow-roadmap.md b/art-decisions/proposals/2024-06-07-arcaflow-roadmap.md new file mode 100644 index 0000000..014b9b2 --- /dev/null +++ b/art-decisions/proposals/2024-06-07-arcaflow-roadmap.md @@ -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.