I consider to package YaCy for the official Debian archive so that users can install YaCy without even adding a third-party archive as was the case with the now defunct YaCy provided deb packages.
I’m still early in my evaluation of YaCy but please be so kind to help me with some answers already:
- Is there actually interest in the first place from the YaCy project in having YaCy packaged for the Debian archive?
- From this forum and other places I get the impression that YaCy is mainly developed and maintained by one person. It is somewhat old but still active software and there is no plan to deprecate it any time soon. There is a related project YaCy grid but this is not intended as a replacement to YaCy. Is this correct?
- I’ll need to pick some commit or tarball to package and give it a version number. Could the project commit on a versioning scheme and provide updates in this versioning scheme on a regular basis, e.g. every half a year?
- I might discover hurdles with YaCy in relation to Debian packaging guidelines and provide patches to solve these. Is there capacity to review a few hopefully small patches and merge them?
- When I learn a new code base I like to write down my learnings as README files in the code itself. Would you merge such code documentation?
I’ve experience in Java, Search, Web development, kubernetes, distributed systems and linux administration. I’d be happy to talk about areas where I could contribute to the project once I’ve familiarized myself more.
Next I want to set up a dedicated machine that I’ve laying around with 1 TB of hard discs to take YaCy for a more serious test drive.