|
|
|
|
|
|
by Arnavion
2262 days ago
|
|
|
>It is tough to get contributors and maintainers of projects like this, [...] It has had a PR since day one, from the same person that opened the issue. >[...] and this issue in particular has been bombed by folks who don't even use Rust and are acting like the sky is falling. It has been "bombed" by people who use mdBook, or rather who no longer use mdBook because they were affected by the issue in question. The issue is on rust-lang/mdBook, not rust-lang/rust, and I don't see anywhere in its README.md that says you need to be a Rust user to use mdBook. |
|
|
Absolutely, and I'm appreciative of that. As you can see from that PR, it is unclear what the procedure is to get said PR merged; there's assertions that this is breaking, and assertions that it is not. This conversation was continued in the issue, and the PR author did not respond. It's effectively in a holding pattern where nobody has responded to the maintainer's feedback about the PR, either by updating the original PR or opening a new one.
Part of why this has taken a while is that mdbook has not had particularly strong leadership over its existence, due to what I said. The original author wrote enough for his purposes, I tweaked stuff for my purposes, but it's never been anyone's specific focus. There have been periods with effectively no maintenance. That's how open source goes.
> It has been "bombed" by people who use mdBook, ... I don't see anywhere in its README.md that says you need to be a Rust user to use mdBook.
To be clear, I do not think everyone in this issue is from some sort of "outside." But there's at least one person in that thread who started on it immediately after publicly trashing Rust. He then continues to be abrasive on the issue.
This contributes to a lack of bandwidth, at least for me. I'm not gonna bother touching this PR when there is so much other work to do, and I don't have to deal with this kind of thing. (I am also not the primary maintainer of mdbook so I don't know how the actual maintainers feel about it, maybe they aren't affected by it in the same way.)
I expect that someday, this will get sorted out, if the folks who care so much actually put in the effort to make the changes happen. Or maybe they'll use another tool. I think that's also totally fine. This was part of a broader move to remove google fonts across Rust properties, most of them were taken care of, because folks pushed and got the work done. I think this might be the last bit?