Bacalhau Roadmap

[aronchick]

NOTE: This is a root issue. All children should be mapped here. Do not remove items, only add to here.

children:

• Engineering - M1 - End Users #1220
• Engineering - M1 - Compute Providers #1221
• Partners - M1 - Market Analysis #1261
• DevRel - M1 #1265
• Engineering - 1.0 Launch - Projects #2179
• Partners - M2 - Product+Market Validation #1262
• DevRel - M2 #1263
• Engineering - M3 - End Users #1234
• Engineering - M3 - Compute Providers #1248
• Partners - M3 - Scaling Workload and Partner Growth #1311
• DevRel - M3 #1318
• Engineering - M4 - End Users #1242
• Engineering - M4 - Compute Providers #1249
• Partners - M4 - Scaling Workload and Partner Growth #1356
• DevRel - M4 #1317

[momack2]

hey @aronchick - can I have a TLDR version of your roadmap that includes 5 milestones or less in the same form as the FVM roadmap? I'm thinking "GA Launch", "Ship onboarding for XYZ SDKs / onboarding flows", etc - each milestone should be worth writing a "shipped" blog post about. I'd really like to link to these milestones from the EngRes and Filecoin roadmaps - but right now there are way too many things here to figure out what to point to.

[aronchick]

Happy to do whatever! The issue is the FVM roadmap is way smaller in scope - e.g. it only talks about a very specific deliverable (developer tooling) relevant for a specific audience (filecoin developers).

Would you like us to scope down to this level? Or would you like one deliverable by segment/audience? Just lemme know!

[wesfloyd]

Woops - sorry 🤦‍♂️

[momack2]

I disagree that the FVM roadmap is smaller in scope. There is a lot of partnership, DX, engineering, security, and collab work embedded in each of these milestones - but they've done the hard work of boiling down the capabilities into a single "big rock" that marks a large xfunc upgrade in capabilities and value creation. I'd like to see you find these "big rocks" for bacalhau across threads and user groups - really judging by when someone outside the project would care and get to make use of an important step function upgrade in utility. Those "outside" folks could be end users or developer integrations (ex via FVM contracts to call compute over data), but milestones that are only about internal bookkeeping / incremental progress should be kept on more work-oriented trackers (instead of this "stakeholder" level roadmap).

[momack2]

@aronchick can you please come to my office hours and we can try to work through some better milestones for Cod? I think this would really help the project to align on these!

[lukemarsden]

Hey @momack2, I've updated our starmap:

With a new top-level Engineering - 1.0 Launch - Projects issue issue:

This hopefully captures the "big rocks" for Bacalhau across threads and user groups which we are targeting before our 1.0 launch on May 9. I've added a description to each of the issues in #2179 which hopefully articulates the user-facing value. Happy to receive any feedback on how to make these better. Thanks!

• Insulated Jobs: new paradigm where compute is securely moved to data, audited & approved #2182
• On-prem with Streaming: local data sources generate a stream of CIDs, for edge #2183
• Stable API: ecosystem can confidently build on our APIs knowing they won't break in future #2184
• Resilience & Scale: performance & stabilty, retry jobs in case of node and network failures #2185
• Amplify: connect to data, run data through computational graph, and record the derivative result in IPFS #2186
• Octostore: track and surface (input, job, output) metadata and construct lineage graph automatically #2187
• Business Dashboard: surface key project metrics - public network stats, website, downloads, stars #2188
• Excellent Documentation: ensure excellent DX through accurate & compelling docs and examples #2189
• Streaming Logs: attach to live stream for a job to observe/debug ongoing long-running job progress #2190
• Station Integration: enable Bacalhau compute nodes in Station to expand public network #2191
• Spot Instances (stretch goal): enable network to auto-burst into spot instances from cloud #2192