chair
chair
@shrpne thank you for your submission we'll take a look and get back to you shortly! cc @kittyslasher
Item removed from Epic 1.2: https://github.com/waku-org/pm/issues/65
Notes from js-waku pm 2023-11-07 - Danish - https://github.com/orgs/waku-org/projects/2/views/1?pane=issue&itemId=42532971 - Will be a significant change. Currently we store callbacks in the class implementation - We want to switch to an...
Blocked by https://github.com/waku-org/js-rln/issues/91
@weboko do you think this work can be included in one of the Milestones defined on the 2024 roadmap? Perhaps `Composing Waku Protocols to Improve Reliability` https://github.com/waku-org/pm/blob/fffa450b0d20c3aac2479106e8b2217706f68ae1/ROADMAP.md https://github.com/waku-org/pm/issues/114
Related to #1814
@danisharora099 to inspect the issue and update with findings.
Closing issue, based on feedback in conversation with hackathon participants, they have signaled that examples of implementations are more useful than comments in the code.
Blocked by https://github.com/waku-org/nwaku/issues/2502
https://github.com/waku-org/research/issues/3 @danisharora099 @weboko Per the research issue, can y'all verify if this is required for JSWaku and assign ownership as necessary. Thank you!