Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chris S reduced maintainership #961

Open
chrisjsewell opened this issue Mar 3, 2023 · 1 comment
Open

Chris S reduced maintainership #961

chrisjsewell opened this issue Mar 3, 2023 · 1 comment

Comments

@chrisjsewell
Copy link
Member

chrisjsewell commented Mar 3, 2023

Hey @executablebooks/steering-council and @executablebooks/core-team,
I just wanted to let you know, so you can plan accordingly,
I will be primarily restricting work in the organization to markdown-it-py, mdit-py-plugins, myst-parser and the spec/enhancement proposals,
mainly just because I have less time these days
(although it is also non-negligible that recent changes in governance have lead to me being stripped of administrative accesses, that increases the difficulty to effectively maintain existing repositories)

There is great work progressing with the spec, that I'm excited to be a part of 🎉.
But obviously the new focus on mystjs does bring into question the long term support of the "Python stack"

I think markdown-it-py/mdit-py-plugins already have a thriving user base outside of EBP (nearing 1 million downloads per/day 🤩 , plus I've been working with Ubuntu/Google on improving security), and indeed I have already suggested that they might be better served in a separate organisation: #841

Similarly, with myst-parser I feel it has a decent user base that is different/complimentary to that of mystjs and they can exist together.
I'm really happy about the recent release/documentation, and also how it is feeding into the spec improvements.

With things like jupyterbook though, it just feels like it would be, let's say, an unrewarding experience; there is a lot of complexity there, balancing dealing with sphinx/docutils, notebook execution, caching, text based formats, user needs, developer needs, thinking about deprecation pathways, etc, and now having to comply with myst-spec, mystjs, myst-jupyterlab. If its just going to be to move everyone to mystjs, then well 🤷
I'm interested to see if anyone takes on the challenge 😬

On a personal note, I'm very interested in Rust, LSPs, nextjs and djot these days, so maybe they'll be a MyST related side project there in the future.
Also, I've got all the sphinx extensions I've been messing around with lol: https://github.com/sphinx-extensions2

Cheers,
Chris

@saulshanabrook
Copy link

Thank you for your work on these tools.

I can totally sympathize with it being a bit of an unrewarding space and squeezed between a lot of different constraints.

I hope you have fun in your next endeavors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants