mirror of
https://github.com/logos-messaging/pm.git
synced 2026-01-05 07:33:08 +00:00
adding last milestones
This commit is contained in:
parent
81963e64e8
commit
85fb465f63
@ -33,6 +33,7 @@
|
||||
| Logos Web apps | Decentralized Forum PoC, Qaku library, demonstration of Codex integration w/ Waku and more resilience to Web3 RPC outages for nwaku | 7/10 |
|
||||
| Explore Peer Discovery Gap | Partial Mixnet PoC, dogfooding store sync for network message consistency | 6/10 |
|
||||
| Debugging Tools | Local metrics dashboard to enable study of software behaviour and usage of Waku | 5/10 |
|
||||
| BD - Acquire first 10 Customers | 1 additional project has been secured (#5), 2 more are to come out of stealth | 5/10 |
|
||||
|
||||
## 🧩 Strategic Benefits Realised
|
||||
|
||||
@ -60,6 +61,7 @@
|
||||
| Nwaku in Status Mobile and Light Mode MVP | Underestimated work for desktop integration, reprioritized for H2 behind Chat SDK work | Yes |
|
||||
| Debugging tools, log parser | Handed over to Vac-DST who already have similar log tool and just need to extend its functionality | No |
|
||||
| Messaging API | Work was expected to only start in H1, which it did. Milestone was re-worked for H2 to better fit team resources | Yes |
|
||||
| BD - Acquire first 10 Customers | Engineering focus on Status over community needs, meaning known gaps (e.g. Rust SDK) creating friction for integration. | Yes |
|
||||
|
||||
## 🛠️ FURPS Execution Snapshot
|
||||
|
||||
@ -107,4 +109,5 @@ https://notes.status.im/E_bcw7cLR36QKI39k-PlMg#
|
||||
- It was a first round of planning with FURPS. Lessons have been learned and being applied for H2.
|
||||
- The Waku internal hackathon was a great experiment to identify use-case but also improvements to the Waku dev ex. With a focus on building (developer) tribes, its strategic value has increased.
|
||||
- Milestones that involved breaking changes were dragged across several Status release; need to review how this is planned to not postponed milestone completion dates by months.
|
||||
- Some research items took time to wrap-up, sort bindings, etc. Will discuss with the team on how we can be better are getting research PoC ready for dogfooding.
|
||||
- Some research items took time to wrap-up, sort bindings, etc. Will discuss with the team on how we can be better are getting research PoC ready for dogfooding.
|
||||
- With a refocus on community, need to improve tracking of BD results.
|
||||
@ -30,19 +30,19 @@ Strategy changes:
|
||||
|
||||
## 🚩 Proposed Milestones(s)
|
||||
|
||||
| Milestone Headline | Strategic Objective | Capacity | Business Val (0/10) | FURPS |
|
||||
|-------------------------------------------------------------------------------------------------------|---------------------------------------------------------|----------|---------------------|---------|
|
||||
| [Define Incentivisation for RLNaaS](draft-roadmap/define_incentivisation_for_rlnaas.md) | Logos Vision: Core Values Alignment | 0.25 | 7 | FURPS_ |
|
||||
| [Improve DevEx: API, TWN, Metrics, Docs](draft-roadmap/improve_devex_api_twn_metrics_docs.md) | Logos Movement Community Enabling via Dev-X + Telemetry | 1.5 | 10 | FURPS_ |
|
||||
| [Introduce mixnet for message sending](draft-roadmap/introduce_mixnet_for_message_sending.md) | Logos Vision: Core Values Alignment | 0.33 | 4 | F___S_ |
|
||||
| [Formalize and Expand Waku Web Apps](draft-roadmap/formalize_and_expand_waku_web_apps.md) | Logos Movement Community Enabling | 0.25 | 7 | FURPS_ |
|
||||
| [Create Chat SDK MVP](draft-roadmap/create_chat_sdk_mvp.md) | Logos Movement Module Build Out | 1.5 | 8 | FURPS+ |
|
||||
| [Integrate RLN with Waku API](draft-roadmap/integrate_rln_with_waku_api.md) | Logos Movement Module Build Out | 0.83 | 9 | FUR_S+ |
|
||||
| [Streamline DevEx: Mobile, Rust and Web dev](draft-roadmap/streamline_dev_ex_local_dev_rust.md) | Logos Movement Community Enabling via Dev-X | 0.5 | 7 | FU__S+ |
|
||||
| [Extend Chat SDK with Group Conversations](draft-roadmap/extend_chat_sdk_with_group_conversations.md) | Logos Movement Module Build Out | 1 | 8 | F_RPS+ |
|
||||
| Incentivisation follow-up (write outline) | Logos Vision: Core Values Alignment | TBD | 7 | FU_____ |
|
||||
| [Nim Usage Improvements](draft-roadmap/nim_usage_improvements.md) | Logos Movement Community Enabling: Dev Journey | 0.33 | 5 | TBD |
|
||||
| Acquire first 10 customers | Logos Movement Community Enabling: Growth | 1.5 | 6 | N/A |
|
||||
| Milestone Headline | Strategic Objective | Capacity | Business Val (0/10) | FURPS |
|
||||
|-------------------------------------------------------------------------------------------------------|---------------------------------------------------------|----------|---------------------|--------|
|
||||
| [Define Incentivisation for RLNaaS](draft-roadmap/define_incentivisation_for_rlnaas.md) | Logos Vision: Core Values Alignment | 0.25 | 7 | FURPS_ |
|
||||
| [Improve DevEx: API, TWN, Metrics, Docs](draft-roadmap/improve_devex_api_twn_metrics_docs.md) | Logos Movement Community Enabling via Dev-X + Telemetry | 1.5 | 10 | FURPS_ |
|
||||
| [Introduce mixnet for message sending](draft-roadmap/introduce_mixnet_for_message_sending.md) | Logos Vision: Core Values Alignment | 0.33 | 4 | F___S_ |
|
||||
| [Formalize and Expand Waku Web Apps](draft-roadmap/formalize_and_expand_waku_web_apps.md) | Logos Movement Community Enabling | 0.25 | 7 | FURPS_ |
|
||||
| [Create Chat SDK MVP](draft-roadmap/create_chat_sdk_mvp.md) | Logos Movement Module Build Out | 1.5 | 8 | FURPS+ |
|
||||
| [Integrate RLN with Waku API](draft-roadmap/integrate_rln_with_waku_api.md) | Logos Movement Module Build Out | 0.83 | 9 | FUR_S+ |
|
||||
| [Streamline DevEx: Mobile, Rust and Web dev](draft-roadmap/streamline_dev_ex_local_dev_rust.md) | Logos Movement Community Enabling via Dev-X | 0.5 | 7 | FU__S+ |
|
||||
| [Extend Chat SDK with Group Conversations](draft-roadmap/extend_chat_sdk_with_group_conversations.md) | Logos Movement Module Build Out | 1 | 8 | F_RPS+ |
|
||||
| [Incentivisation Follow-up Outline](draft-roadmap/incentivisation_follow_up.md) | Logos Vision: Core Values Alignment | 3 | 7 | TBD |
|
||||
| [Nim Usage Improvements](draft-roadmap/nim_usage_improvements.md) | Logos Movement Community Enabling: Dev Journey | 0.33 | 5 | FU____ |
|
||||
| [BD - Acquire first 10 customers](draft-roadmap/acquire_first_10_customers.md) | Logos Movement Community Enabling: Growth | 0.75 | 7 | N/A |
|
||||
|
||||
## 🧩 Strategic Benefits Realisable from coming Half-Year (Top 5)
|
||||
|
||||
|
||||
@ -100,8 +100,9 @@ In order of priority.
|
||||
| 6 | [Integrate RLN with Waku API](integrate_rln_with_waku_api.md) | 30 Sep | 1*1m | 1*2m | 1*2m | |
|
||||
| 7 | [Streamline DevEx: Mobile, Rust and Web dev](streamline_dev_ex_local_dev_rust.md) | 30 Nov | | 1*1m | 1*2m | |
|
||||
| 8 | [Extend Chat SDK with Group Conversations](extend_chat_sdk_with_group_conversations.md) | 19 Dec | | | | 2*3m |
|
||||
| 9 | Incentivisation follow-up | TBD | TBD | | | |
|
||||
| 10 | [Nim Usage Improvements](nim_usage_improvements.md) | 19 Dec | | | 1*2m | |
|
||||
| 9 | [Incentivisation follow-up Outline](incentivisation_follow_up.md) | TBD | 1.5*5m | | | |
|
||||
| 10 | [Nim Usage Improvements](nim_usage_improvements.md) | 19 Dec | | | 1*2m | |
|
||||
| 11 | [BD - Acquire 10 Customers](acquire_first_10_customers.md) | 19 Dec | | | | 0.5*6m |
|
||||
|
||||
Pushed to 2026
|
||||
- WebTransport: depending on nim-libp2p (delivery Q4)
|
||||
|
||||
@ -11,7 +11,7 @@
|
||||
|
||||
## Strategic Objective
|
||||
|
||||
TODO: Clarify with Leonard
|
||||
Logos xxx
|
||||
|
||||
## FURPS
|
||||
|
||||
|
||||
44
draft-roadmap/acquire_first_10_customers.md
Normal file
44
draft-roadmap/acquire_first_10_customers.md
Normal file
@ -0,0 +1,44 @@
|
||||
# Business Dev - Acquire First 10 Customers
|
||||
|
||||
**Estimated date of completion**: 2025H2 Period
|
||||
|
||||
**Resources Required for 2025H2**:
|
||||
- 1 Business Development Lead
|
||||
- 0.5 Solution Engineer
|
||||
- Comms Hubs Support
|
||||
|
||||
Onboard Waku first 10 customers. Customers are projects using Waku for their peer-to-peer communication stack, or conversation/chat.
|
||||
First 10 customers assume involvement from the engineering team to get things right and help co-design.
|
||||
|
||||
Status, Railgun, TheGraph, Portrait and Chrom.ar should count as the first five.
|
||||
|
||||
A couple of projects are in stealth mode and can be counted in once they go public.
|
||||
|
||||
## Strategic Objective
|
||||
|
||||
Logos Movement Community Enabling: Growth
|
||||
|
||||
## Risks
|
||||
|
||||
| Risk | (Accept, Own, Mitigation) |
|
||||
|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| No dedicated Dev Rel | Work closely with Logos Movement to funnel developers to Waku. Apply guerilla tacting to leverage current Waku team members. Use Solution Engineer for conference talk and presence. |
|
||||
| No dedicated Growth Lead | Rely on Comms Hubs for Social Media presence, event organization, content and other initiatives. Leverage keen Waku team members to roll out dev community growth initiatives. |
|
||||
|
||||
## KPIs for 2025H2
|
||||
|
||||
- [ ] Identify 15 Highly Qualified Leads
|
||||
- [ ] Discuss solution engineering with 10 leads
|
||||
- [ ] Bring 5 leads into Discord bridge (will to connect and discuss)
|
||||
- [ ] 3 new integrations started
|
||||
- [ ] Identify 3 ecosystem grants, and secure initial calls
|
||||
|
||||
## Deliverables
|
||||
|
||||
### Chat SDK MVP Definition
|
||||
|
||||
**Owner**: BD
|
||||
|
||||
Based on customer interviews and co-design sessions, identify the potential Waku Chat SDK USPs and outline an MVP.
|
||||
|
||||
Communicate with targeted customers on MVP.
|
||||
@ -3,7 +3,7 @@
|
||||
**Estimated date of completion**: 31 July 2025
|
||||
|
||||
**Resources Required for 2025H2**:
|
||||
- 1.5 core researchers for 1 month = 0.25
|
||||
- 1.5 core researchers for 1 month
|
||||
|
||||
By the end of this milestone, we will have defined a roadmap and implemented a working proof of concept to incentivise node operators running Waku infrastructure for shared shards.
|
||||
|
||||
|
||||
30
draft-roadmap/incentivisation_follow_up.md
Normal file
30
draft-roadmap/incentivisation_follow_up.md
Normal file
@ -0,0 +1,30 @@
|
||||
# Incentivisation Follow-Up Outline
|
||||
|
||||
**Estimated date of completion**: TBC
|
||||
|
||||
**Resources Required for 2025H2**:
|
||||
- 1.5 core research engineer for 5 months
|
||||
- {external services consumed (Vac/IFT)}
|
||||
- {infrastructure}
|
||||
|
||||
Proceed with follow-up step once the [incentivisation light push PoC](https://github.com/waku-org/pm/issues/245) is delivered.
|
||||
|
||||
The exact commitments and deliverables are to be defined as part of the [incentivisation roadmap output](https://github.com/waku-org/pm/issues/246)
|
||||
|
||||
## Strategic Objective
|
||||
|
||||
Logos Vision: Core Values Alignment
|
||||
|
||||
## FURPS
|
||||
|
||||
TBD
|
||||
|
||||
## Risks
|
||||
|
||||
| Risk | (Accept, Own, Mitigation) |
|
||||
|--------|-------------------------------|
|
||||
| [Risk] | [how to we address this risk] |
|
||||
|
||||
## Deliverables
|
||||
|
||||
TBD
|
||||
Loading…
x
Reference in New Issue
Block a user