I think there’s a terminology gap that the article doesn’t do a great job with. Open source in 2021 does not require anything on the list. But to be a widely de

I think there’s a terminology gap that the article doesn’t do a great job with. Open source in 2021 does not require anything on the list. But to be a widely deployed open source project does generally require those kinds of things. As the parallel commenter noted, it doesn’t need to specifically be Discord or GitHub or Twitter or whatever, but to have mass adoption, the project needs to have directionality and momentum. Even if that’s “we feel we’re feature complete, if you find bugs, report them here”. Without that, plenty of things are still “open source”, but users can’t really pick them up for their projects because they can’t rely on them. That’s fine: there’s plenty of really fascinating and meaningful projects out there that can’t be relied on for the long term. But for something like Jekyll, if I’m looking for a platform for my blog, I’d be remiss to pick something that’s stuck in the state it’s in. That’s the issue that the author seems to be pushing at: he forked Jekyll because Jekyll is a widely adopted codebase that’s no longer able to support its niche, and he’s hoping that Bridgetown can fill that niche for users.