Our Continuation of MkDocs
github.com
Our Continuation of MkDocs
1–10 of 17 posts
Re: Our Continuation of MkDocs
#2Re: Our Continuation of MkDocs
#3Re: Our Continuation of MkDocs
#4> I do not see him as qualified to keep this project maintainership and if I had the choice, would I remove him.
…where “him” is Tom Christie, aka lovelydinosaur, the original author from what I can tell, and the copyright holder from the license file.
I don’t know what’s going on, but if someone contributing to one of my projects, that I wrote, started a public conversation about how to remove me, my public response might appear as that person disappearing from the project.
Sure, feel free to follow the license and fork the project. Make it clear that it’s a fork, though. It feels misleading to describe it as a continuation of the existing project.
Re: Our Continuation of MkDocs
#5Also, this MkDocs maintainer sounds crazy. Nobody is discouraging women from contributing.
Re: Our Continuation of MkDocs
#6See recent discussion in [0] [0]: https://news.ycombinator.com/item?id=47482185
Re: Our Continuation of MkDocs
#7Re: Our Continuation of MkDocs
#8I hope they are able to monetize in a way the keeps the core project open while making it a sustainable venture going forward.
Re: Our Continuation of MkDocs
#9Earlier quoted context omitted.
Yeah that’s a better link for the overall situation. Personally I’m betting on Zensical.
Good to point out -- Zensical is the project by MkDocs author to supersedes the latter.
Re: Our Continuation of MkDocs
#10Zensical has been a solid replacement for us so far. In general everything "just works" out of the box and is way quicker to build/reload. It is still in fairly early stages, but is actively being worked on https://zensical.org/spark/proposals/zap-005-navigation-auth... I hope they are able to monetize in a way the keeps the core project open while making it a sustainable venture going forward.