...
- Defining the outputs of the fly-in
- Top-level architectural diagrams
- Component diagrams
- Inputs/Outputs for each component
- Draft HTTP API
- Draft requirements
- Performance considerations
- Data flow considerations
- Convergence of diagrams
- How to improve VIVO to more seamlessly consume Rialto-Combine-esque data?
- How to improve VIVO to more seamlessly produce Product-Evolution-esque data?
- How to modularize core VIVO to be more accessible and maintainable for developers?
- How to distribute CPU-intensive processes across multiple machines?
- "Required reading" materials before fly-in
- Architecture
- ?product evolution
- ?Rialto (VIVO/Vitro assessment)
- ?JavaScript frameworks
- Thoughts on the fly-in agenda
...