Waku Gantt

2024-04-19 12:38:06 +01:00 · 2024-04-19 12:38:06 +01:00 · aa4ece3056
parent 03ce7838cb
commit aa4ece3056
1 changed files with 94 additions and 0 deletions
--- a/content/waku/2024-gantt.md
+++ b/content/waku/2024-gantt.md
@ -0,0 +1,94 @@
+# Waku Roadmap 2024 Gantt Charts
+
+Status short term work only:
+
+- reliability for 1:1 chat and communities
+- up to 100 communities
+
+Colour legend:
+
+- **Red**: engineering work to deliver the feature.
+- Other: test and telemetry work to ensure quality
+
+```mermaid
+gantt
+    dateFormat YYYY-MM-DD
+    axisFormat %d-%b
+    
+%% Milestones overview with deliverables
+    section Store Service Upgrade
+        Store v3-beta (msg hash): crit, milestone, after storev3-br, 0
+        Store v3 (sync): crit, milestone, after storev3-r storev3-g storev3-n, 0
+        DoS protection for req-res protocols: crit, milestone, after dosreqresn dosreqresj dosreqresg, 0
+        PostgreSQL maintenance: crit, milestone, after pgsql, 0
+        (metric) Count store messages: milestone, after count-store-msg, 0
+    section Direct Message Reliability
+        (testing) direct messages: milestone, after test-direct-msg, 0
+        Review connection management: crit, milestone, after review-conn-mgmt-1 review-conn-mgmt-2, 0
+        (telemetry) Fleet logging: milestone, after telem-fleet-logging, 0
+        (telemetry) direct message reliability: milestone, after telem-d-msg-rel, 0
+        Reliability Protocol for Relay: crit, milestone, after rel-relay-g rel-relay-n, 0
+        Reliability Protocol for Resource-Restricted Clients: crit, milestone, after rel-reqres-g rel-reqres-j, 0
+        Review MVDS usage and fail path: crit, milestone, after mvds, 0
+    section Static Sharding - dedicated shards
+        (telemetry) Measure Bandwidth: milestone, after telem-bandwidth, 0
+        Sharding peer mgmt and discovery hardening: crit, milestone, after sh-peer-mgmt-j sh-peer-mgmt-n sh-peer-mgmt-g, 0
+        (testing) Custom shard impl of Communities: milestone, after test-custom-shard, 0
+    
+    section golang eng
+        %% Estimation TBC
+        Review connection management: crit, review-conn-mgmt-1, 2024-05-13, 8w
+        %% Estimate TBC
+        Review MVDS usage and fail path: crit, mvds, after review-conn-mgmt-1, 6w
+        %% Estimate/start TBC
+        (testing) direct messages: test-direct-msg, after mvds, 4w
+        %% Estimate TBC
+        (testing) Custom shard impl of Communities: test-custom-shard, after test-direct-msg, 4w 
+    section golang eng
+        %% Estimation TBC
+        Reliability Protocol for Relay (status-go): crit, rel-relay-g, 2024-05-13, 20w
+    section golang eng
+        Store v3 (go-waku client only): crit, storev3-g, 2024-02-26, 2024-05-24
+        %% Estimate TBD
+        DoS protection for req-res protocols (go-waku client only): crit, dosreqresg, after storev3-g, 4w
+        %% Estimate TBC - assuming parallel work possible
+        Review connection management: crit, review-conn-mgmt-2, 2024-05-13, 8w
+        (metric) Count store messages: count-store-msg, after review-conn-mgmt-2, 2w
+    section golang eng
+        %% Review if actually needed
+        Store v3 (sync): crit, 2024-02-08, 2024-04-26
+        %% Estimate TBC assuming no RFC here
+        Reliability Protocol for Resource-Restricted Clients (status-go): crit, rel-reqres-g, 2024-05-13, 10w
+        %% TBC Estimate
+        Sharding peer mgmt and discovery hardening (go-waku): crit, sh-peer-mgmt-g, after rel-resreq-g, 8w
+    section golang eng
+        %% TBC estimate and start
+        (telemetry) direct message reliability: telem-d-msg-rel, 2024-06-17, 6w
+        %% TBC estimate and start
+        (telemetry) Measure Bandwidth: telem-bandwidth, after telem-d-msg-rel, 8w
+    section research eng
+        %% TBC estimation done?
+        Store v3-beta (msg hash): crit, storev3-br, 2024-01-01, 12w
+        %% TBC estimation
+        Store v3 (sync): crit, storev3-r, after storev3-br, 20w
+    section test eng
+        %% TODO: start small scale simulations of DST such store perf
+    section nim eng
+        PostgreSQL Maintenance: crit, pgsql, 2024-01-01, 2024-05-24
+        %% TBC estimate, this is assuming PoC is done, ie,  how much hardening would be needed?
+        Store v3-beta + v3 (nwaku): crit, storev3-n, after storev3-br, 3w
+        %% TBC estimate
+        Reliability Protocol for Relay (nwaku): crit, rel-relay-n, 2024-05-01, 40w
+    section nim eng
+        %% TBC estimate/end
+        DoS Protection for Req-Res Protocols: crit, dosreqresn, 2024-01-01, 90d
+        (telemetry) Fleet logging: telem-fleet-logging, 2024-05-15, 4w %% TBC estimate/end/start
+    section nim eng
+        %% TBC estimate/end
+        Sharding peer mgmt and discovery hardening (nwaku): crit, sh-peer-mgmt-n, 2024-05-13, 12w
+    section js eng
+        Reliability for Req-Res Protocols: crit, rel-reqres-j, 2024-01-01, 90d
+    section js eng
+        %% TBC scope
+        Sharding peer mgmt and discovery hardening: crit, sh-peer-mgmt-j, 2024-06-01, 4w
+```