Replies: 2 comments 12 replies
|
We're not having any more conversation in all-male online spaces. Not happening. |
|
Heya... we can support a safer approach than plugins. For use cases such as including docstrings in markdown it'd be neater & more careful to support templating-in-markdown, plus guiding users towards CI for any additional tooling. We don't want to be locked into a Python-specific approach, and we shouldn't be gearing up for a docs system that relies on unbounded execution. |
|
I get your point, but it's very important to my projects that I do not create duplicate duplicate documentation. Being able to automatically generate parts of my documentation such that they always remain in-sync with the state of my codebase is very important to me, and so having plugins to support that is very important to me. I'm always very busy, so try my best to avoid creating duplicate work for myself. |
|
If github / github discussions are not the place to have this conversation, is there a place where this should rather take place? Genuine question. I am not very closely following the mkdocs community, please forgive me if I'm missing something obvious, here. |
|
Personally I haven't really had many issues with GitHub being a "boys club". I've had a few negative experiences with certain repositories, certainly, but it is far from common: I just block problematic users and avoid contributing to and using projects where maintainers are awful. |
|
I do not doubt that Github skews male HEAVILY. My point really is: what is the more inclusive, more diverse alternative where this discussion would be welcome? The readme specifically mentions Github for discussions and Matrix for "small questions". @lovelydinosaur sounds like there is something else, maybe the readme is just not up to date. |
|
It is not for me to say who should maintain it. I am neither qualified to answer that, nor do I think I'm entitled to anyone's free work. I wish to thank the authors and any contributors for mkdocs 1.x, which was a good basis for things I wanted to publish. So questions 1-3 are basically answered. For the 4th one, the notes, I wish to leave this: I trust that they will not actively f*ck this up on purpose. At the same time, I am not sure if switching from 1.x to 2.x is worth it for me. I might as well switch to something else because it is ultimately a similar amount of work. I have not fully decided, yet, but the missing plugin system and overall maintenance activity is certainly a consideration for me. Priorities, visions and needs differ. That is fine with me. There are literally hundreds of site generators out there, there's something near-perfect for everyone. I'm not naming alternatives. I'm sure whoever looks for alternatives does not need my advice here. |
Uh oh!
There was an error while loading. Please reload this page.
Important
Nothing in this post is official. It's a simple Request for Comment to see what the communities overall opinion is about MkDocs current maintainership, and if there should be a change.
It is in no way endorsed, nor supported by the actual current MkDocs team.
It is also NOT for trying to harass or attack any mentioned people. Please do not do this. State your dislike if you want, but don't insult individuals. Thank you.
It now has been a veeeeery long while since MkDocs has received a signigicant update, including just ones for updating dependencies.
And while v2 was announced is it not really something I would call an improvement on MkDocs itself. More a downgrade, as significant parts such as the plugin API have been removed for no good reason, with no clear mention on when or even IF it will be re-added.
This, alongside other parts I will not get into details with, made me wonder: How happy are people with the current maintainers of this project, and who they think would fit the best to fill this role?
I genuinly want to know:
Speaking personally, I would go with oprypin as the maintainer, as he did suggest to come back as a maintainer. Yes, he did some arguably bad stuff (The kick of Squidfunk from the team) but the general reactions to that were overblown and I haven't really seen much negative stuff from him either.
If anything may he be less bad than I was and am in certain situations. But no matter his attitude, he did maintain the project and his leave caused the end pretty much.
lovelydinosaur simply doesn't seem to care to at the very least update dependencies of MkDocs to improve security with a proper release, nor has shown any activity until his v2 announcement, which is anything but what I would call an improvement to MkDocs. I do not see him as qualified to keep this project maintainership and if I had the choice, would I remove him.
Anyways, with all of that said would I like to see your responses. I want to have some discussion to see the communities views on this!
All reactions