Maintainer decisions that gate the remaining book-theme parity phases. These are choices, not tasks — resolving them unblocks the phase issues in the book-theme parity milestone.
Source: PLAN.md → Open questions for maintainers
- Upstream-first? Git-metadata rendering, the language switcher, and RTL could be contributed to
jupyter-book/myst-theme rather than kept QuantEcon-only. Which are worth upstreaming vs forking?
- Plugin home. Should the build-time git-metadata plugin (Phase 1) live in a shared
quantecon-myst-plugins repo consumed by every lecture repo, or per-repo? (Currently interim in plugins/ here.)
- Compute model. How much of the launch story moves to in-page Thebe vs external Colab / private hub, given infra cost and the existing
.notebooks convention? (Drives Phase 2.)
- First-migration scope. Which lectures migrate to JB≥2 first, and which subset of phases must land before that cutover? (Phase 1 git-history is likely a must-have.)
Discuss inline; record the resolution in PLAN.md and close when all four are decided.
Maintainer decisions that gate the remaining book-theme parity phases. These are choices, not tasks — resolving them unblocks the phase issues in the book-theme parity milestone.
Source: PLAN.md → Open questions for maintainers
jupyter-book/myst-themerather than kept QuantEcon-only. Which are worth upstreaming vs forking?quantecon-myst-pluginsrepo consumed by every lecture repo, or per-repo? (Currently interim inplugins/here.).notebooksconvention? (Drives Phase 2.)