Update foo2zjs driver suite metadata: Migrate from dead rkkda upstream

[SinghCod3r]

Changes:

• Updated the <url> tags in all foo2*.xml driver files (foo2zjs, foo2hp, foo2lava, etc.).
• Replaced the dead upstream link (http://foo2zjs.rkkda.com/) with the active OpenPrinting GitHub repository (https://github.com/OpenPrinting/foo2zjs).

Reason:
The original upstream website (rkkda.com) is no longer available. OpenPrinting has adopted this driver suite, and the GitHub repository is now the correct canonical source for these drivers.

[SinghCod3r]

@tillkamppeter , Please Review this as it will fix big problem of missing link.

[tillkamppeter]

https://github.com/OpenPrinting/foo2zjs is already there on OpenPrinting and looks like that this one was derived from Debian's packaging repository. Its default branch "main-fixes" seems to contain the upstream source code.

As we have this foo2zjs repo on OpenPrinting already, I suggest to make it the upstream repo as it is very easy to find on OpenPrinting.

But we need to check whether it is really unmaintained at the location which is given as upstream location according to the Debian package. If there is active upstream maintainership we could look into inviting the maintainer(s) to maintain foo2jzs on OpenPrinting.

We also need to find a solution for the color profiles which we cannot host on OpenPrinting.

Also, our repo should be in sync with the newest developmnent of foo2zjs, wherever it is hosted.

For your URL updates, there are more that the 4 driver entries which need updating. All drivers with "foo2..." names should be checked.

[SinghCod3r]

@tillkamppeter ,
Thank you for the guidance, Till!

1. Upstream Verification: I double-checked the Debian package metadata (apt show foo2zjs), and it lists the upstream URL as http://foo2zjs.rkkda.com/. Since that site is definitely down (and has been for some time), it confirms that there is no active upstream maintainer at the original location. Adopting the OpenPrinting repo as the new canonical upstream seems to be the correct move.
2. Driver Coverage: Regarding the number of files: My PR currently updates 9 files (everything matching foo2*.xml in the drivers directory). I believe this covers the entire suite, but I will double-check if any non-foo2 named files belong to this package and update them if I missed any.
3. Color Profiles: I noted the concern about color profiles. I assume we can address the hosting/licensing of those specific binaries in a separate discussion or PR once the metadata link is fixed.
   I am ready to proceed with these changes pointing to the OpenPrinting GitHub if you agree!

[tillkamppeter]

Please check:
/usr/share/doc/printer-driver-foo2zjs/NEWS.Debian.gz

There I have summarized all my knowledge (but already some time ago, things can have changed).

[SinghCod3r]

@tillkamppeter ,
I have checked /usr/share/doc/printer-driver-foo2zjs/NEWS.Debian.gz as suggested.

The logs from August 2021 confirm that the original upstream rkkda.com ceased operations back then. The logs mention that patches were added to redirect the getweb script to mirrors like linkevich.net and quirinux.org to keep firmware downloads working.

Since those are scattered mirrors and the koenkooi repo was noted as 'stone-old' in the logs, I agree that establishing OpenPrinting/foo2zjs as the canonical upstream is the best path forward to unify development.

I have verified that my PR updates the URL for the entire suite (4 files) to point to the OpenPrinting GitHub.

[SinghCod3r]

@tillkamppeter , any updates for this pr ?

[tillkamppeter]

First, there are more than just the foo2zjs*.xml files to be updated, but also foo2lava.xml, foo2hp.xml, ... as you mention in the initial posting.

Also the getweb file needs to be updated as the one which comes in the Ubuntu package. You can use the patch for that.

In addition, you need to update the doumentation which comes with foo2zjs, based on this NEWS.Debian.gz which I had written for the Ubuntu package.