Is there at all a plan to cleanly fork calibre-web?

[halkeye]

Poking around I see the origins of it being a mod of the original calibre-web docker images. New skin added on top. Patches here and there. Some extra utils. Etc

I know in the past I've tried to submit patches to calibre-web, to have them shut down (and they are totally entitled to, its their project).

Are y'all still planning on trying to build ontop of upstream calibre-web, or is there an intention of forking and going in a different direction? It seems like the current method of just keeping files you want to change isn't exactly sustainable as it would be hard down the road to figure out why things were changed (like admin.py, if upstream got changed, you'd have to do a diff, then figure out if the difference was intentional. Or try to re-apply things commit by commit).

I just want to know the plan before i decide if i want to switch over, and maybe contribute new things

Btw, love the new theme, its so clean

[crocodilestick]

It's still undecided. CWA currently benefits a lot from the work of CW's team and community providing updates, bugfixes ect. to the core components, meaning we can mostly focus on refining and adding new functionality ect. But who knows, CW has essentially been in maintenance mode for a while now and updates are definitely becoming less and less frequent so at some point we may fully fork.

[halkeye]

Oh, I meant fork as in git, not project. So fork the repo, add your changes ontop of the repo as seperate commits, then if upstream changes happen, you can pull in their changes. Instead of right now where if something upstream happens, you need to check if the copied files were changed, and add those changes back in, losing history and credit.

[crocodilestick]

You're right, it was time and this was completed today. Apart from the calibre & kepubify binaries, the CWA repo now contains all the files it requires to function, standalone