Re: Requesting co-maintenance for TeX::Encode
Hello Neil, Hello Tim, thanks for the co-maintenance. I just pushed a new version with hopefully more to follow, as time allows. Regards, Ahmad On Mon, Oct 24, 2016 at 2:17 PM, Neil Bowers wrote: > Hi Ahmad, > >> I would like to ask for co-maintainenance rights to TeX::Encode. >> I posted my patch to the PAUSE bugtracker >> (https://rt.cpan.org/Ticket/Display.html?id=118001) on 2016-09-03. I have >> since tried contacting the author on his timbr...@cpan.org email (doesn't >> deliver), the email in the .pm file as well as the email on his Github >> profile, all without success. > > I got in touch with Tim, and he gave me permission to grant you co-maint on > TeX::Encode and the other two modules in the distribution. > > I’ve just given you co-maint. Thanks for stepping forward to update this > distribution, and fight the CPAN bitrot! > > And thanks to Tim for giving permission. > > Cheers, > Neil >
PAUSE permissions clash between Load and load modules [MPOURASG - Load]
Hi George, I’m emailing you wearing my PAUSE admin hat: I’m working on resolving conflicts caused by PAUSE now considering package names case insensitively. This has left us with some situations where two or more people are owners of namespaces previously considered distinct, and now considered the same. You own the Load namespace, which is used in your FastDB distribution. This now clashes with the “load” module, which is owned by PAUSE user ELIZABETH. To resolve this conflict, I’d like to propose that you rename the modules in your distribution to follow the usual convention of all being in the namespace of the distribution. So your modules would be renamed as follows: Delete => FastDB::Delete Load=> FastDB::Load Question=> FastDB::Question I could then drop your permissions on the Delete, Load, and Question namespaces. Are you happy to make this change please? PAUSE doesn’t let situations like this occur any more, so I’m working through the existing cases, trying to get them resolved. Cheers, Neil
