First, I'd like to move away from having separate "milestone tracks" like "Design 1" vs "Implementation 1". Instead let's just have "Milestone N" and define the goals for N, and N increments.
Any "concurrency" we want between distinct "tracks" of work can just be woven into these monolithic milestones (especially while we're a small team).
Split up "Design and Implementation Phase 2" into "Milestone 2" and "Milestone 3"
I want to split up Design and Implementation Phase 2, which currently looks like this:
Milestone 2 - Integrate Crosslink
The new milestone 2 will be capstoned by #85 and maybe some of the "nice-to-have" items capstoned by #99.
I actually think that will be enough work for a milestone, even though it's largely formatting / infrastructure work, because I assume we'll have to do edits to translate hackmd to mdbook, tweak the automation, include new dependencies, etc…
Then it will also include some amount of editorial work to make sure the terminology and scoping and chapter layouts all jive well.
Milestone 3 - Security Analysis
This will include a lot of security analysis, such as the rest of the current #84 capstone, and a lot of those transitive dependencies such as https://github.com/zcash/simtfl/issues/14 capstone.
Suggested Improvement
Monotonic Milestones
First, I'd like to move away from having separate "milestone tracks" like "Design 1" vs "Implementation 1". Instead let's just have "Milestone N" and define the goals for N, and N increments.
Any "concurrency" we want between distinct "tracks" of work can just be woven into these monolithic milestones (especially while we're a small team).
Split up "Design and Implementation Phase 2" into "Milestone 2" and "Milestone 3"
I want to split up Design and Implementation Phase 2, which currently looks like this:
Milestone 2 - Integrate Crosslink
The new milestone 2 will be capstoned by #85 and maybe some of the "nice-to-have" items capstoned by #99.
I actually think that will be enough work for a milestone, even though it's largely formatting / infrastructure work, because I assume we'll have to do edits to translate hackmd to mdbook, tweak the automation, include new dependencies, etc…
Then it will also include some amount of editorial work to make sure the terminology and scoping and chapter layouts all jive well.
Milestone 3 - Security Analysis
This will include a lot of security analysis, such as the rest of the current #84 capstone, and a lot of those transitive dependencies such as https://github.com/zcash/simtfl/issues/14 capstone.