5 ms·
Am I missing something, or is Jekyll still receiving fairly active contributions[1]? Even by that (misleading) metric, it doesn't seem to be dead. Expecting ma
by woodruffw 5y ago
Am I missing something, or is Jekyll still receiving fairly active contributions[1]?
Even by that (misleading) metric, it doesn't seem to be dead. Expecting maintainers to tilt at the newest windmill instead of actually maintain is a critical part of why so many in the open source community burn out.
[1]: https://github.com/jekyll/jekyll/commits/master https://github.com/jekyll/jekyll/commits/master
- jspaetzel 5y agoMaybe this is just clickbait? Jekyll is in a fine state for an extremely mature project. It would be extremely souring to me if Jekyll decided to add webpack and other javascript dependencies with a newer version. One of the things I like about Jekyll is that it's a STATIC site generator that doesn't try to do everything. Some sites I want to be dead simple, and that's what you get with Jekyll. If I want more complexity I'd go with a more complex generator like Hugo or Gatsby.
- woodruffw 5y ago> Jekyll is in a fine state for an extremely mature project. That's my impression as well, as an outsider. A recurring nightmare of mine as a maintainer is that I'll wake up one day and read someone's blog proclaiming the death of one of my projects, when all I've done is stopped adding new features to it. Especially so when it's someone who's made a living for themselves as a downstream user. And I'm in the same boat as you: I've had a Jekyll-based blog, without incident, for a little bit under a decade now. It's only gotten faster and easier to use over time, which is more than I even asked for.
- jaredcwhite 5y agoI never declared the death of the project. Frank, the remaining release maintainer of Jekyll after Parker Moore left, declared it. Read the article. :)
- Lammy 5y agoRight, you're just taking private words from someone who "refrain[ed] from making any public statement", publicizing them, and trying to capitalize on it four entire days after his obituary was published now that he's not around to speak for himself. Toootally different.
- donatj 5y agoAgreed! I personally maintain a couple projects I consider feature complete. Changes are very rare other than occasional bug fixes or breaking ecosystem changes, but that doesn't mean the code is bad. The code is a hammer, you don't need the newest shiniest hammer. You just need the hammer that hits nails.
- jaredcwhite 5y agoIs Hugo built with Ruby? Is Gatsby? Why are we saying that someone can only use the biggest Ruby-based SSG if they want something incredibly simple that will never change, otherwise they need to look somewhere else. Rails has never had that limited value prop for example.
- DocTomoe 5y agoIsn't that asking the wrong question? If I want an SSG, I want an engine that takes a relatively simplistic text markup format, like Markdown or Org, and create a series of HTML documents from it. Why would the technology that does the gruntwork matter to me as an user? Also, with Jekyll's plugin structure, what is an example of a functionality that cannot be achieved in Jekyll, but can in another non-Ruby SSG?
- gwern 5y agoI dunno, if you look at the releases instead (https://github.com/jekyll/jekyll/releases https://github.com/jekyll/jekyll/releases), they were doing monthly releases for a long time, and now it's been 6 months without a release. The last was April 2021, and OP quotes the "release maintainer" of Jekyll as declaring Jekyll dead in "May 2021"... Sounds like a "Hotel California" repo now, if you follow me. Which is unacceptable for a lot of distributors/users (are they just going to package random git HEAD snapshots whenever they feel like it, now that releases are apparently de facto banned?).
- woodruffw 5y agoThis is where my outsider's perspective falls short: assuming that the old release maintainer isn't actively preventing the project from appointing a new release maintainer, what stops them from just keeping on? Deviations from their previous release schedule are certainly noteworthy, but release schedules also naturally length as projects mature. And then there's the Theseus-type questions: if Jekyll changes its name because the current maintainers have lost access to the RubyGems credentials, is it really not Jekyll anymore? It occurs to me that OSS is replete with `${project}-ng` namings, the `ng` suffix typically indicating that the project serves the same purpose as its original form but has been moved to a different namespace for whatever reason. If Jekyll's current maintainers were to publish `jekyll-ng` on RubyGems, I'd be inclined to call that a continuation of the original Jekyll for all extents and purposes.
- gwern 5y agoI'm not familiar with Github release permissions because it's not a process I've ever used, but I assume it's a different capability from being able to push patches. A "release maintainer" & repo owner who won't release or isn't adding release capabilities isn't "actively preventing" anything; they are simply not doing anything. At this rate, if the release maintainer continues to ghost the project (including by refusing to make any clear public announcement), Jekyll users are going to have to fork. You can't wait forever. > but release schedules also naturally length as projects mature. That's why I pointed out they had been maintaining a very steady monthly release schedule for years beforehand (and just look at the total release count!). Plus, "maybe they don't need to do a release" is rather contradictory with "this project is in rude health, look at how many patches they're receiving piled up in the (unreleased) HEAD!"...
- JeremyNT 5y agoYeah, I'd like some corroboration for this blog post's rather alarmist rhetoric about Jekyll's project health. I get that the blog author is maintaining a fork so it's possible he has some other motive to make things sound this bad. It's kind of interesting to me that the author opted not to use the Github "fork" feature to start Bridgetown, and there's no reference to Jekyll in the README (and hardly any in the git history either). This strikes me as an odd way to respond if the concerns are for the health of the upstream project; it would make sense to reach out and try to work with upstream if they aren't doing what needs to be done, then explain why a fork is needed in the README. Jekyll itself is a project that still receives active commits and continues to do everything I ask of it (and indeed, it seemed essentially feature complete for my uses years ago).
- jaredcwhite 5y ago> I'd like some corroboration for this blog post's rather alarmist rhetoric about Jekyll's project health. It's literally at the top of the article.