Bug#1117692: ITS: libwiki-toolkit-plugin-ping-perl

[Andreas Tille]

Hi Dominic,

I understood you do not want this package be maintained in the Perl
team.  Should I close this ITS or should it remain open as some
remainder that you can cherry-pick from

   https://salsa.debian.org/perl-team/modules/packages/libwiki-toolkit-plugin-ping-perl

Please let me know when I should remove this repository once you
uploaded to avoid any confusion.

Kind regards
    Andreas.

Am Fri, Oct 10, 2025 at 05:19:13PM +0200 schrieb Andreas Tille:
> Hi Dominic,
> 
> Thanks for getting back to me and explaining your reasoning. I
> understand your concern about not wanting to burden the pkg-perl team
> with niche packages.
> 
> Am Thu, Oct 09, 2025 at 11:32:24PM +0100 schrieb Dominic Hargreaves:
> > 
> > Hi, I'm a member of pkg-perl
> 
> I know this and naively assumed you had some time constraints I could
> help out.
> 
> > but I specifically didn't add these
> > (libwiki-toolkit-* and a few others, rdepends only of openguides AFAIK)
> > to the perl team as they are very niche and only of interest to a tiny
> > number of users. So I don't think they are worth bothering pkg-perl with.
> 
> However, I'd like to suggest that handling "niche" Perl modules is
> precisely what the pkg-perl team is designed for. The automated team
> workflows actually make maintaining such packages less burdensome, as
> they help ensure consistent standards and catch issues (like outdated
> Vcs fields) across all packages, regardless of their user base.
>  
> > I will of course address substantive issues with the package but so far
> > I see only one minor severity issue that failed to get any consensus on
> > relevance after two years, so I don't think that's a clear signal.
> 
> For instance, I noticed that libwiki-toolkit's Vcs fields still point to
> Alioth. Keeping these fields accurate is one of the things the team
> automation helps with. Moving it to the team would resolve this and
> similar issues automatically in the future, ensuring the package stays
> clean with less manual effort from any single maintainer.
> 
> The merge request I prepared is ready to go and would handle this
> transition seamlessly. I am happy to upload it on the team's behalf or
> adapt it for your personal repository if you prefer. This would be a
> one-time action for a long-term maintenance benefit.
> 
> Would you be willing to give this a try with the libwiki-toolkit
> package?
> 
> Kind regards
>    Andreas.
> 
> -- 
> https://fam-tille.de

-- 
https://fam-tille.de