EBP Team Meeting - October 2022

[rowanc1]

Hello @executablebooks/ebpteam! This is an issue to track the next Executable Books team meeting! Here's some relevant information:

• Date: Sydney time at 7:00AM on Oct 6 or 2pm MT Oct 5th (Wednesday)
• Google Calendar Link.
• Agenda+Video Links

If you'd like to discuss something at the meeting, please add an item to the agenda!

Before the meeting

• Update dates and make sure HackMD information is correct.
• Team members add agenda items.

After the meeting

• Turn any follow-ups into issues/comments/etc.
• Copy the meeting notes to the docs.
• Remove notes and clean up HackMD.

[rowanc1]

On twitter here if folks want to invite people:
https://twitter.com/rowancockett/status/1576798479284080641

Looking forward to seeing everyone!

[rowanc1]

We had a good meeting on Wednesday, the notes are here, thanks especially to @firasm and @echarles for dropping by!

New templates

We shared some updates on LaTeX and template improvements for mystjs:
- https://js.myst.tools/jtex
- https://github.com/myst-templates
- https://api.myst.tools/templates/tex
- Yesterday @stevejpurves and I also put together a video walkthrough of using the jtex templating CLI 📺

MyST Enhancement Proposals

As a follow on to our improvements to our community, we have been been moving towards implementing a enhancement process for MyST -- especially the myst-spec. @chrisjsewell has put together a first draft based on the Python PEP process, and created a website to host them: https://myst-eps.readthedocs.io.

In the meeting we decided to continue working on the current draft, to encourage more input from the community, and bring the MEP proposals to a more collaborative writing space (we will use HackMD for this!) so there can be some more authors and input, especially on these first few MEPs.

Specifically we wanted to work over the next month on three MEPs simultaneously: (1) defining the MEP process that we believe will help, but not be overly bureaucratic/onerous; (2) design a specific, scoped feature; and (3) write some high-level, informational design goals.

These are the three types of MEPs that we might envision for the project, and are based on the PEP process (standards, informational and process).

The drafts for the three MEPs are here:

1. Process: https://hackmd.io/8JnI4N82QKO84oo4rT6YMg
2. Cross Reference Simplifications using Markdown Links: https://hackmd.io/us8ZmFHrTjaHBGkkdoz0CQ
3. Some high level design goals: https://hackmd.io/LOdkezLAS-6Wrq4HoHJ5zQ

In the meeting we thought it would be possible to make progress as a team on these three documents to bootstrap the process, write down some design goals, and actually test out the process and those goals with a specific, scoped feature.

cc @choldgraf who is interested in this, but couldn't attend the meeting!

Looking forward to contributions and authorship here!