alt Hacker NewsInstead of providing a mirrored repository, they decided to intentionally not fixing the correctly identified problem while simultaneously still living 30 years in the past.
Setting up a git mirror that auto syncs takes less than 2mins of effort. And way less time than writing up this README that's just there to lecture people. If it's about disagreement with github, there's also better alternatives.
You can still setup the mirror and be done with it, and put the original repo links at the top in the README.
Replies
> You can still setup the mirror and be done with it, and put the original repo links at the top in the README
There is no original repo to link to. That's why the README says that there isn't one.
> Setting up a git mirror that auto syncs takes less than 2mins
Prove it.
It's obvious that the author wants to make a statement, and has their own reason to not expose their work on GitHub. Setting up a mirror would probably contradict these reasons.
Using a public source code hosting product is a choice.
Also centralising everything in one place is a seriously bad idea.
> they decided to intentionally not fixing the correctly identified problem
Which problem?
> Maybe someone should fork xscreensaver as xscreensaver-ng as a community project?
Feel free.
Or they could not. It’s their project they can do what they want you are not entitled to their labour.
The upstream has no public repository, neither on GitHub nor anywhere else.
JWZ might not even use git in the first place, the source might be in a local SVN repo, or just a series of tarballs and patches, assuming it is version controlled at all.