In our last meeting, @jstac suggested that we could release the myst-parser and myst-nb projects in a "public beta" fashion, relatively soon. I think it could be a good idea to get some of these tools out there sooner than later. What do people think about:
- In the next few days, start telling twitter, open-source colleagues, etc about the MyST-parser for Sphinx
- After @AakashGfude's PR lands in MyST-NB and we have a week-or-so to test it out, do the same thing for MyST-NB
What do folks think about that?
And on the second point, we should also reach out to the nbsphinx project and see if they have any ideas for how we could dovetail our stacks into one another.
The one question I have here, is whether @chrisjsewell thinks that recent conversations about markdown-it-py should delay the "announcement" of MyST and the MyST parser. Chris, what do you think?
In our last meeting, @jstac suggested that we could release the myst-parser and myst-nb projects in a "public beta" fashion, relatively soon. I think it could be a good idea to get some of these tools out there sooner than later. What do people think about:
What do folks think about that?
And on the second point, we should also reach out to the
nbsphinxproject and see if they have any ideas for how we could dovetail our stacks into one another.The one question I have here, is whether @chrisjsewell thinks that recent conversations about
markdown-it-pyshould delay the "announcement" of MyST and the MyST parser. Chris, what do you think?