Should we fork the project?

[piranna]

With 94 open issues, 77 pull-requests asking for updates, and the original author with no activity in two years, I think it would make sense if someone decides to take the ownership of the repo and continues improving the project... Does anyone about how to do it, or if already another "main" fork of it?

[angrymrtom]

skimming through the PR, looks like a lot of them are just changes people made to their own site, and are trying to merge here, for reasons that are beyond me.

[piranna]

for reasons that are beyond me

Maybe because they are useful? Other thing is they don't understand how a pull-request works and they continue to do their own changes on the same branch...

[angrymrtom]

that's what I mean, most of the files/code changed are values being filled in to the _config.yml. Those are changes that do not need to be pushed to the main repo.

[amitmerchant1990]

Shameless plug:

You can check https://github.com/amitmerchant1990/reverie if you like.

It's a better and more improved version of jekyll-now. It's actively maintained as well with new features coming in on a regular basis. 😃