Untitled - HackMD

Chris Holdgraf
·
Last edited by Chris Holdgraf on Oct 10, 2022
Linked with GitHub
Contributed by

Edit

2022/10/08 15:49:04

My feedback is that I would find it helpful to actually have a simplified PEP process in addition to this. The documents, over issues, are helpful to reason through changes, and also document the final narrative rather than the threaded discussion. I think this will be helpful moving forward, and designed in a light-weight way can be helpful now! (Edited)

Rowan Cockett

2022/10/08 15:55:56

I also think this assumes a bit more maturity to that repo than is actually there. It currently is only the AST definition, not the actual markup syntax, which needs some more work probably to even document what is there today. (Edited)

Chris Holdgraf

2022/10/08 18:54:08

So then you're suggesting something like: - Open an issue for informal alignment - Open a pull request in myst-eps that follows a more formal structure - Merging causes the decision to be made, and it is then implemented via a change to `meta/` or `myst-spec/`? (Edited)

Chris Holdgraf

2022/10/08 18:56:12

What do you recommend? That we use a different place to define MyST? Or that we make the changes to that repository to allow it to serve as a Source of Truth? If so, what minimal changes are needed? (Edited)

Moved to: https://github.com/executablebooks/meta/pull/843

Last changed by

Chris Holdgraf

112

Published on HackMD