|
1 | 1 | # 2022 |
2 | 2 |
|
| 3 | +## April |
| 4 | + |
| 5 | +### Atending |
| 6 | + |
| 7 | +- Matthew McKay / ANU / mmcky |
| 8 | +- Rowan Cockett / Curvenote / rowanc1 |
| 9 | +- Chris Sewell / EPFL / chrisjsewell |
| 10 | +- Chris Holdgraf / 2i2c / choldgraf |
| 11 | +- Damián Avila / 2i2c / damianavila |
| 12 | +- Aakash Gupta / ANU / aakashgc |
| 13 | + |
| 14 | +### Notes |
| 15 | + |
| 16 | +- `myst-spec` - @fwkoch, @rowanc1, @chrisjsewell |
| 17 | + - over the past month, we've put together a language-agnostic repo of JSON schema types for the MyST AST nodes, building on existing `mdast` types. |
| 18 | + - github: https://github.com/executablebooks/myst-spec |
| 19 | + - dist: https://unpkg.com/browse/myst-spec/dist/ |
| 20 | + - This also includes test cases, similar to the commonmark spec, which may be used to validate implementations of the spec |
| 21 | + - `mystjs`, the markdown-it javascript implementation, already consumes myst spec |
| 22 | + - [`unified-myst`](https://github.com/executablebooks/unified-myst), the new unified ecosystem implementation, will also be "spec compliant"! |
| 23 | + - python side hasn't been adressed quite yet. |
| 24 | +- [Unified MyST](https://github.com/executablebooks/unified-myst) |
| 25 | + - There are some drawbacks of markdown-it |
| 26 | + - It doesn't have a well specified AST |
| 27 | + - myst-spec uses `mdast`, but that's a "unified ecosystem" thing, not a markdown-it thing |
| 28 | + - Unified ecosystem has their own parser called [micromark](https://github.com/micromark/micromark) (and that is bundled in [remark](https://remarkjs.com/)) |
| 29 | + - The [unified-myst](https://github.com/executablebooks/unified-myst) parser uses this framework instead of markdown-it |
| 30 | + - Q: **What's the relationship between all of these parsers?** |
| 31 | + - MyST-js would use the unified parser |
| 32 | + - VSCode uses markdown-it-docutils (not even mystjs) |
| 33 | + - Unified ecosystem is well-maintained with many extensions |
| 34 | + - Q: **how do all of these pieces fit together for the end-user experience?** |
| 35 | + - We should have a strategy meeting about the direction of these pieces so that we can align on a path forward. |
| 36 | + - There is not currently a "product" at the end that is driving all of this forward (from an end-user's perspective). |
| 37 | + - Q: **This seems like a lot of stuff to maintain. How can we sustain our efforts?** |
| 38 | + - We have a bunch of stuff we've added to grow our maintenance burden. |
| 39 | + - Can we tie the JS myst stuff to end-users in a way that we can fund? |
| 40 | + - General agreement that we need a better story around the strategy and maintainability of this stack. |
| 41 | + - Product strategy meeting? |
| 42 | + - Bring in multiple stakeholders around a "product vision / strategy" for where the ecosystem could move going forward. |
| 43 | + - Could we bring the learnings from the JS world back into the Python world to improve Jupyter Book. |
| 44 | +- Curvenote renderer for multiple composable "JupyterBooks" |
| 45 | + - Hosting a conference at end of April! |
| 46 | + - https://transform.softwareunderground.org/ |
| 47 | +- CH: New book theme is out, will update Jupyter Book to use it soon! |
| 48 | + |
| 49 | +**Note: we did not get to the following topics, but there are some notes** |
| 50 | + |
| 51 | +- [Gated Directives (sphinx-exercise)](https://ebp-sphinx-exercise.readthedocs.io/en/latest/syntax.html#alternative-gated-syntax). There has been some comments and interest in making this syntax more general so it could be used for other directives. |
| 52 | + - Best Strategy? As an extension? |
| 53 | + - Mention this with work being done on `myst-spec` |
| 54 | +- First Developer Interview: "Deep Dive into Parsing" (with Chris Sewell) |
| 55 | + - https://github.com/executablebooks/meta/issues/672#issue-1147568262 |
| 56 | + - cover myst-parser, markdown-it-py |
| 57 | + - Any questions? Please add it to the issue. |
| 58 | + - Will post a recording to share more widely. |
| 59 | +- JupyterLab Myst Extension as you go |
| 60 | + - Editing experience in jupyter is very critical! |
| 61 | +- MyST Docs |
| 62 | + - New repository? Migrate and refurbish content? |
| 63 | + |
3 | 64 | ## March |
4 | 65 |
|
5 | 66 | ### Attending |
|
0 commit comments