[Epic] chat-sdk tracking

[chair28980]

Summary

Objective

This issue serves as the primary tracking and coordination point for the chat-sdk team. Currently the focus is on addressing and managing tasks primarily within the https://github.com/status-im/status-go/ repository, which is external to the waku-org organization.

Guidelines

• Post weekly updates in the comments section of this issue. https://github.com/waku-org/pm#reporting
• Relevant issues and tasks should be listed and regularly updated in this issue's description.

Project board

All chat-sdk issues should be tracked via the project board:

https://github.com/orgs/waku-org/projects/4/views/1

[chair28980]

This central tracking issue is a temporary measure for immediate project management needs. We're developing a more detailed PM process for the Chat-SDK team, in line with discussions on the VAC forum https://forum.vac.dev/t/reviewing-milestone-planning/238.

[kaichaosun]

Weekly Update

• achieved: implement local DNS resolver for testing.
• next: update PeerExchange test to use local resolver.
• blocker: no

[plopezlpz]

Weekly Update

• achieved: Running custom built desktop with status-go, working on community store node
• next: continue working on community store node
• blocker: no so far

[plopezlpz]

Weekly Update

• achieved: Working on next steps of #4366: community store node
• next: continue working on community store node
• blocker: no so far

[kaichaosun]

Weekly Update

• achieved: Analysis and resolve max message length bug in status go.
• next: Move filter tests in waku v1 to v2.
• blocker: no

[kaichaosun]

Weekly Update

achieved: Fix hash algorithm in go-waku, remove store config in status-desktop.
next: Work on filter delay issue.
blocker: Move filter tests in waku v1 to v2 (pending for review and low priority).

[kaichaosun]

Weekly Update

• achieved: close connections for filter light client, draft a doc about messages on the relay
• next: work on user cannot join the community bug
• blocker: no

[plopezlpz]

Weekly Update

• achieved: owner can setup a storenode for his community
• next: document full process of setting up storenode for community and test
• blocker: no