Launch the MyST -> Jupyter Book parity project

[choldgraf]

To begin, we'd like to communicate our intent to use MyST as a Jupyter Book build engine, and define the basic framework for organizing and prioritizing our work internally.

Progress towards goal

This is the first step towards the following goal:

• Bring MyST document engine up to feature parity with Jupyter Book, with the intent of offering MyST as a backend to Jupyter Book #1000

This will give us a foundation to begin iterating, with the goal of getting new functionality in front of users as quickly as we can so that we can learn and improve with them.

Outputs

• Blog post about Jupyter Book 2
  • Blog draft
  • BLOG: MyST-md plans for Jupyter Book executablebooks/meta#1177
• JEP
  • pre-proposal: Pre-proposal: Incorporate jupyter-book as a Jupyter sub-project jupyter/enhancement-proposals#122
  • JEP: Add Jupyter Book as subproject jupyter/enhancement-proposals#123
• Guiding principles for MyST section
• Next initiative: Minimum Viable Product of Jupyter Book functionality with MyST #1106

Strategy and coordination

• Principles to guide the Jupyter Book transition from Sphinx to MyST #1113
• Add enough information to get started: Minimum Viable Product of Jupyter Book functionality with MyST #1106
• Define goals and principles for the MyST document engine #1146
• Write blog post
• Create JEP for incorporating as Jupyter sub-project: JEP: Add Jupyter Book as subproject jupyter/enhancement-proposals#123

[stevejpurves]

We can still identify and start talking to one or two communities now, or stakeholders in those communities, it doesn't need to be blocked by the blog post but the blog post will be helpful for enabling the message to be better communicated across those communities.

[agoose77]

I've removed #618 from this list, as we've discussed that it should be the responsibility of JB2 to convert Sphinx-style glossaries.

[choldgraf]

Spoke a bit with @agoose77 about this today. We've got the two "guiding principles" issues finished up, one of them is merged and the other we'll leave open and use it as a reference for our development-focused initiative:

• Minimum Viable Product of Jupyter Book functionality with MyST #1106

The only remaining thing for this one is to get the blog post out. @agoose77 is going to finish up a draft and get feedback from one or two communities and then I think we can post it soon

[choldgraf]

Current status

• We've got a draft blog post ready to go
• We've got a JEP pre-proposal ready to go: Pre-proposal: Incorporate jupyter-book as a Jupyter sub-project jupyter/enhancement-proposals#122

The pre-proposal has gotten positive feedback as well, and one person asked if we'd be willing to speak with the software steering council on Monday to answer any questions people may have.

Current plan

• Attend the SSC meeting on Monday (8am California time)
• If that goes positively, then convert the JEP into markdown and make it a PR
• Link the PR from the blog post, and then post the blog post as well

[choldgraf]

OK all - I think the final two outputs of this one are done:

• Blog post announcing jupyter book using mystmd: BLOG: MyST-md plans for Jupyter Book executablebooks/meta#1177
• JEP for incorporating as Jupyter sub-project: JEP: Add Jupyter Book as subproject jupyter/enhancement-proposals#123

I suggest we close this one and focus on the development-oriented initiative here w/ @agoose77 :

• Minimum Viable Product of Jupyter Book functionality with MyST #1106