Change Details

With the porting of the repo from using KIO::SlaveBase to KIO::WorkerBase and thus following the new nomenclatura, the name of the repo no longer matches. And it is also not following the pattern seen with other repos of that kind, like "kio-gopher", "kio-gdrive", "kio-fuse", "kio-stash". Therefore I propose to rename the repo officially to kio-zeroconf in time for the upcoming KDE Gear 22.08 release. Inside the repo the only thing that needs adaption is the appstream metainfo.xml file, no changes needed in catalog names, documentation or installed files, if I saw correctly. Opinions?

With the porting of the repo from using KIO::SlaveBase to KIO::WorkerBase and thus following the new nomenclatura, the name of the repo no longer matches. (see https://invent.kde.org/network/zeroconf-ioslave/-/merge_requests/2 for the related MR). And it is also not following the pattern seen with other repos of that kind, like "kio-gopher", "kio-gdrive", "kio-fuse", "kio-stash". Therefore I propose to rename the repo officially to kio-zeroconf in time for the upcoming KDE Gear 22.08 release. Inside the repo the only thing that needs adaption is the appstream metainfo.xml file, no changes needed in catalog names, documentation or installed files, if I saw correctly. Opinions?

With the porting of the repo from using KIO::SlaveBase to KIO::WorkerBase and thus following the new nomenclatura, the name of the repo no longer matches. (see https://invent.kde.org/network/zeroconf-ioslave/-/merge_requests/2 for the related MR). And it is also not following the pattern seen with other repos of that kind, like "kio-gopher", "kio-gdrive", "kio-fuse", "kio-stash". Therefore I propose to rename the repo officially to kio-zeroconf in time for the upcoming KDE Gear 22.08 release. Inside the repo the only thing that needs adaption is the appstream metainfo.xml file, no changes needed in catalog names, documentation or installed files, if I saw correctly. Opinions?