-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Milestone] Support Many Platforms #42
Comments
fryorcraken
changed the title
[Epic] Support Various Platforms
[Epic] Support Many Platforms
Aug 6, 2023
fryorcraken
changed the title
[Epic] Support Many Platforms
[Milestone] Support Many Platforms
Aug 24, 2023
fryorcraken
added
Deliverable
Tracks a Deliverable
and removed
Epic
Tracks a sub-team Epic.
labels
Aug 24, 2023
fryorcraken
changed the title
[Milestone] Support Many Platforms
[Epic] Support Many Platforms
Aug 24, 2023
fryorcraken
added
Epic
Tracks a sub-team Epic.
Deliverable
Tracks a Deliverable
and removed
Deliverable
Tracks a Deliverable
Epic
Tracks a sub-team Epic.
labels
Aug 24, 2023
fryorcraken
changed the title
[Epic] Support Many Platforms
[Milestone] Support Many Platforms
Aug 25, 2023
monthly update Several learnings on wrapping nim in another GC languages such as NodeJS. New recommended strategies are being implemented before we can release NodeJS and Python packages. |
Tentative due date set to 2024Q1 but will need to be revise once the scope is set. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2023 Milestones: https://notes.status.im/s/iylE6wdli#
This is a new milestone that was not initially identified
Milestone: https://github.com/waku-org/pm/milestone/2
Priority Tracks: Growth
Due date: TBD
Summary
To grow the Waku ecosystem, we need to ensure that the integration of Waku in any software of library is possible and friction-less.
Justification
As an infrastructure project, Waku needs to be available in various languages and platform so that projects can integrate it easily, without having to deal with building or integration issues.
We are pushing js-waku first to project external to Logos/Status, so that web app developers, hackers and any one wanted to build a quick PoC can.
However, most serious/production adoption of Waku out there also use native system library: XMTP, TheGraph, Status.
To achieve this goal, we need to provide SDK and examples that demonstrate how Waku can be used with several languages and on several platforms.
Finally, community developers out there with limited dev resources will prioritize building single business logic libraries on top of Waku to use on all environment (mobile, node, desktop, web). We need to enable them to do so with Waku SDKs.
Scope
Scope is yet to be defined.
The first step would be to define a number of languages and platforms. A community poll is tracked in waku-org/docs.waku.org#107.
Once defined, for each platforms we should produce:
Producing all 3 artefact above for the selected languages is the acceptance criteria for this milestone.
In addition to this, an exhaustive c-bindings and REST APIs enables willing developers to integrate Waku in any other non-supported languages.
As of Oct 2023:
Epics
The text was updated successfully, but these errors were encountered: