I’ve created the Antidote v1.0 plan. It is mostly a lynchpin for all of the MPs - as a few of you have asked for a high-level doc that contains links to stuff. So that’s what this is - a description of the v1.0 effort, a layout of the top-level work that needs done, and links to all of the other docs/PRs where the specifics are being discussed. Please bookmark this, as there will be no higher document when it comes to v1.0:
This file has been truncated.
# Antidote v1.0 Roadmap
We created NRE Labs in a very short amount of time, with the express intention of generating buzz early. This timeframe meant we had to take many shortcuts with how the platform scales and functions. This tradeoff has largely been worthwhile, as the buzz is now quite substantial.
However, what got us here, won’t get us there. To compare to the MCU - we’re nearing the end of Phase 1. We’re about to have our “Avengers” moment. And Ed Norton was a great hulk, he really was - but we need Mark Ruffalo if we’re going to pull this thing off long-term.
This document is meant to summarize all of the work underneath the v1.0 umbrella and provide a one-stop shop for all information or relevant links per the progress towards that goal. It is my hope that this document creates space for others to join the “platform team”, and generally provides insight throughout the community and the rest of the organization into what’s going on with the platform in the next few months.
# Antidote v1.0 Work Breakdown: Mini-Projects
We've logically separated the areas of focus for moving Antidote to v1.0 into what we call "mini-projects", code-named MP1, MP2, and so forth. Each of these mini-projects should be handled separately, and there will be links below to find external documents that focus on specific design proposals and implementation milestones relevant to each mini-project.
This section will intentionally omit any discussions of timing - but in general, these mini-projects should be done in sequence. There will be some natural overlap, but they are ordered in terms of not only priority, but also complexity, and there are some hard dependencies between them, which we'll try to call out within each design document.
Each mini-project definition below contains:
- A brief explanation of the purpose of the MP
- A link to the proposed design and implementation plan (many of these are currently links to Pull Requests, and feedback on these during this stage is **crucial**)
- A link to the community forum category where broader discussions relevant to that MP can be held