logos-co
/
roadmap
mirror of https://github.com/logos-co/roadmap.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Few clarifications (#7)

This commit is contained in:
fryorcraken 2023-10-10 09:26:11 +11:00 committed by GitHub
parent 7003266724
commit fd50a05037
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 24 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

35
content/waku/monthly-reports/2023-sept.md
View File

@ -9,7 +9,8 @@ tags:
## Executive Summary
The month of September saw an agreement and solidification of the Waku roadmap which defines the process of launching the Waku Network as an independent piece of infrastructure the broader ecosystem can rely upon. Along with this, a revamp of the process in which work is labeled and tracked was performed which has an automated part and is generally more in line with the requests from the Insights team.
Work continues in the scaling and productionization efforts across the clients. A substantial amount of work was done on the integration of PostgreSQL for `WAKU-STORE` and it is expected to be finalized next month. A Waku static sharding strategy is being integrated into Status to accommodate the first growth milestones of the re-release and adaptive sharding research and implementation is close behind.
Work continues in the scaling and productionization efforts across the clients. Work previously done to enables PostgreSQL engine for `WAKU-STORE` in nwaku is being locally stress tested, further stress test using dev fleet is expected to be finalized next month. A Waku static sharding strategy is being integrated into Status to accommodate the first growth milestones of the re-release and adaptive sharding research and implementation is close behind.
Local simulation of `RLN-RELAY` has enabled the discovery of minor bugs which are fixed in the latest release of zerokit and nwaku and the study of the affect of RLN on performance.
Kurtosis as a platform was found to be insufficient for modeling a Waku network at the scale we wish, and the Vac team is pursuing an alternative strategy and writing up learnings from the boundaries were able to push.
@ -19,16 +20,22 @@ The process to add native integration APIs to `nwaku` is underway such that the
## Key Updates
### Personnel
- addition of Aaron as Project Manager
- Opened two Job Descriptions around the following roles:
-
- addition of
- Aaron as Project Manager
- Sergei as Researcher
- Gabriel as nwaku Engineer
- Several Jobs Descriptions have been reviewed this month to be opened shortly:
- Growth Lead/Marketing strategist to drive Waku's growth and liaise with Comms Hubs
- Business Development Lead, to further develop partnership with ecosystem projects
- Solution Engineer, to provide technical support to projects integrating Waku
- A core contributor to lead the Waku Chat SDK team has been secured, with start date in November.
### Milestones
A lot of work has been put into coalescing and finalizing the development tracking process that is in line with the Insight Reporting requirements, and Aaron's addition to the team this month as pushed it over the edge to completion. Much of this has gone into automating the weekly reporting process via Github labels and comments on issues.
A lot of work has been put into coalescing and finalizing the development tracking process that is in line with the Insight Reporting requirements, and Aaron's addition to the team this month as pushed it over the edge to completion. Much of this has gone into automating the weekly reporting process via GitHub labels and comments on issues.
For tracking Waku maintains these Milestones in the `waku-org/pm` repo. Within each milestone description, you'll find the corresponding Epics. Every Epic is distinctly labeled, and this label is affixed to each issue associated with that particular Epic. The labels are managed by the `labels.yaml` file located in the `waku-org/pm` repo.
Given the expansive nature of Waku and its various repositories working towards the milestones, the labels established in the `labels.yaml` file are replicated across each respective `waku-org/pm` repo. This structure allows for seamless navigation, starting from top-level milestones down to the most granular issues.
Given the expansive nature of Waku and its various repositories working towards the milestones, the labels established in the `labels.yaml` file are replicated across each respective `waku-org` repo. This structure allows for seamless navigation, starting from top-level milestones down to the most granular issues.
Waku is broken out into the following four Milestones, with Epics associated with them:
- `Waku Network Gen0`
@ -41,7 +48,7 @@ More details on the structure and progress of all Waku work can be tracked in th
#### [Waku Network Gen0](https://github.com/waku-org/pm/issues/50)
The Waku Network RFC was created and [published on Vac](https://rfc.vac.dev/spec/64/) as RAW which details the ideas and architecture of the Waku Network. The next version of RLN was also [published on Vac](https://rfc.vac.dev/spec/58/) as RAW.
A benchmark of RLN was conducted and [the results](https://github.com/waku-org/research/issues/23) were discussed in a [Logos Research Call presentation](https://minutes.logos.co/logos/logos-research-call-notes#september-27) (TODO: DETAILS NEEDED IN THIS MINUTES LINK). The tl;dr is copied here for convenience:
A benchmark of RLN was conducted and [the results](https://github.com/waku-org/research/issues/23) were discussed in a [Logos Research Call presentation](https://minutes.logos.co/logos/logos-research-call-notes#september-27) (See [waku-org/research#23](https://github.com/waku-org/research/issues/23) for details). The tl;dr is copied here for convenience:
> [!QUOTE] TLDR:
>
@ -53,27 +60,33 @@ A benchmark of RLN was conducted and [the results](https://github.com/waku-org/r
Based on these two specification publications and other associated work, efforts have begun to launch the first dev-testnet in time for the DevConnect event in November 2023.
#### [Waku Network Can Support 1MM Users](https://github.com/waku-org/pm/issues/83)
A review of 2023 Q3 Waku usage and metrics was started. A poll was created to query what language priority we should have was gone, go see the [results here](). They'll be published on socials next month to boost engagement and feedback.
All launch critical work for autosharding has been done in terms of RFC and nwaku.
#### [Waku Network Can Support 1MM Users](https://github.com/waku-org/pm/issues/83)
Significant work was completed on the PostgreSQL integration and setup within `nwaku`, which supports the data retention and retrieval of Waku archival nodes. The implementation is currently being stress-tested to ensure production performance metrics are met.
The efforts in simulating a Waku Network of 10k users within a single shard continues and is tracked within [[vac/dst/index|Vac DST Roadmap]]. The performance of Wakurtosis (Kurtosis backend) was found to be insufficient for our requirements for scaling simulations. The creation of a Kubernetes orchestration tool, written in Python, has begun construction. This tool is heavily architected to mimic what Codex has created. It was chosen to reproduce this tooling in Python in order to increase usability and ease of maintenance/contribution as C# is a less known language within the org. The reasoning for this development can be tracked in [[vac/dst/wakurtosis/vac/retrospective-rlog|retrospective-rlog]].
The effort to understand a "professional Waku node operator" has begun and initial notes can be tracked within this [minutes doc](https://notes.status.im/node-operators-meeting).
A "static sharding" fleet was setup to test Status integration and Communities scale.
A "static sharding" fleet was setup to test sharding and PostgreSQL by Waku team.
Setup of a similar fleet dedicated to Status Communities is in progress (the first fleet may be used in the interim).
#### [Quality Assurance Processes in Place](https://github.com/waku-org/pm/issues/73)
This milestone was created to ensure preparedness for the upcoming production client needs (specifically Waku Network Gen0 and Status Communities). A list of required processes in place was constructed and tasked out so that all implementations of Waku go through a standardized production release cycle.
This work is coordinating with the new [[vac/dst/index|Vac DST]] additions focused on testing rubrics for Logos Projects. This milestone is expected to be completed by Q1 2024.
This work is coordinating with the new [[vac/dst/index|Vac DST]] additions focused on testing rubrics for Logos Projects. This milestone is expected to be completed by Q1 2024.
Work has started to use the js-waku CI as an integration test suite for nwaku and go-waku. This test suite can now easily be run for either client as part of their release process.
#### [Support Many Platforms](https://github.com/waku-org/pm/issues/42)
This is a large milestone created last month that tracks Waku's "integration landscape" and attempting to ensure any developer seamlessly is able to integrate Waku.
It has started to list the work required for completion but more detail is needed to be fleshed out on prioritization and estimated resource needs. Currently, it is slotted for completion by April 2024.
Much of the work this month was fleshing out the available REST APIs of `nwaku`.
A [poll](https://discord.com/channels/1110799176264056863/1111568123007606855/1149298157306531890) was created to query what language priority we should have was gone. They'll be published on socials next month to boost engagement and feedback. This poll will assist with priorities for this milestone.
## Perceived Changes in Project Risk
- Waku doing most integration of Waku into `status-go` consumes a lot of Go-related developer resources.