Yeah totally fine by me. Do I need to do anything in pause?

> On Jul 24, 2020, at 5:57 PM, Chris Prather <ch...@prather.org> wrote:
> 
> 
> I talked to Matt via Facebook about handing over his XML modules 
> (Specifically XML::Parser) which is why I have first come I suspect now. I 
> wanted to make sure that they had people who were still interested in XML and 
> Perl shepherding them and I was happy to be that person.
> 
> I'm entirely ok with Yanick taking it if he's happy with that or with  
> Dominique taking it if they prefer. Otherwise I'm happy to shepherd it as 
> well. Basically whatever everyone else wants to do as long as they don't fall 
> into ADOPTME I'm good with :)
> 
> -Chris
> 
>> On Fri, Jul 24, 2020 at 3:53 PM Dominique Quatravaux 
>> <domini...@quatravaux.org> wrote:
>> I am DOMQ and I approve of this plan.
>> 
>> -- 
>> Dominique Quatravaux
>> domini...@quatravaux.org
>> 
>>> Le ven. 24 juil. 2020 à 21:34, Neil Bowers <neil.bow...@cogendo.com> a 
>>> écrit :
>>> Hi,
>>> 
>>> I’m one of the PAUSE admins, and I’m emailing you wearing that hat.
>>> 
>>> The XML-XPathScript distribution was originally created by Matt; Dominique 
>>> then did 5 releases; since 2005 Yanick has done 24 releases. Chris 
>>> (PERIGRIN) doesn’t seem to have done any releases, but he has the 
>>> first-come indexing permission on the lead module (XML::XPathScript), and 
>>> YANICK has first-come on the others. The rest of you have co-maint on the 
>>> (other) modules.
>>> 
>>> The fractured ownership means that no single person could grant co-maint to 
>>> someone else, or transfer ownership to a new maintainer. PAUSE tries hard 
>>> now to not this happen[1], so I’m tidying up the historical cases.
>>> 
>>> The default rule is that whoever has first-come on the lead module should 
>>> get it on the rest, but I suspect here that it would make more sense for 
>>> YANICK to get first-come on XML::XPathScript — is that ok?
>>> 
>>> Cheers,
>>> Neil
>>> 
>>> [1] http://neilb.org/2020/07/24/inconsistent-permissions.html

Reply via email to