Re: CPAN - consolidating PAUSE permissions on DateTime-Format-ISO8601 distribution
Hi Neil, Yes, I'm OK with making the change. Thanks for keeping me in the loop. -Josh -- On 8/17/20 9:39 AM, Neil Bowers wrote: > Hi Joshua, > > I’m one of the PAUSE admins. I’m tidying up distributions that have > shared first-come ownership, since PAUSE tries now to not let this > happen — it maintains the permissions profile on the lead module, > regardless of who releases (in the past the releaser would get > first-come on newly added modules). > > The DateTime-Format-ISO8601 distribution is one of these. You have the > first-come permission on the lead module, DateTime::Format::ISO8601, > but Dave Rolsky has been doing recent releases, and has first-come on > DateTime::Format::ISO8601::Types, which I’m guessing he added in one > of his releases. > > Given Dave seems to be maintaining this now, are you happy for me to > transfer your first-come permission to Dave, so he has full control > over the distribution? You would retain co-maint on both packages. > > Cheers, > Neil
Re: [lsst-sqre/jenkins-dm-jobs] add "clean" build jobs (#189)
Hi Nick, Clearly, I've dropped the ball on updating this module. I think it would be reasonable to add Dave Rolsky as an official co-maintainer, so I am not a single point of failure. However, what I'd really like to see happen is someone PR deployment to cpan via travis, upon push of a tag, from https://github.com/jhoblitt/DateTime-HiRes rather than ping-ponging around who can actually ship to cpan. I've just added Dave as a github collaborator as well. Are you interested in working on getting CD setup? -Josh -- On 8/15/19 3:56 PM, Nick Tonkin wrote: > Hi there Joshua, > > I'm contacting you again regarding the Perl module DateTime:HiRes > which is broken with newer Perls. I would be happy to become a > co-maintainer or take over the module, is that OK with you? > > Thanks, > > - nick > > On Wed, Oct 4, 2017 at 1:32 PM Joshua Hoblitt <mailto:j...@hoblitt.com>> wrote: > > Hi Nick, > > I'm just returning from leave. I'll be in touch shortly. > > -Josh > > -- > On 10/04/2017 09:29 AM, Nick Tonkin wrote: > > Hi Josh, > > > > I see that you saw and deleted the comment I left on a recent Github > > commit of yours regarding a failing DateTime::HiRes test, sorry > about > > that; I had tried a few times first to get you by email. > > > > I take that my attempts to contact you via email and via Github are > > not welcome, and also that you are no longer interested in > maintaining > > the CPAN module. Please correct me if I've wrongly interpreted your > > lack of reply. I know how things are and how things can get > busy. But > > if you're no longer interested in maintaining the module, please let > > me know and I'll be happy to help or take over. > > > > Thanks, > > > > Nick > > > > > > > > On Wed, Oct 4, 2017 at 12:11 PM, Joshua Hoblitt > > mailto:notificati...@github.com> > <mailto:notificati...@github.com > <mailto:notificati...@github.com>>> wrote: > > > > Merged #189 > <https://github.com/lsst-sqre/jenkins-dm-jobs/pull/189>. > > > > — > > You are receiving this because you commented. > > Reply to this email directly, view it on GitHub > > > <https://github.com/lsst-sqre/jenkins-dm-jobs/pull/189#event-1278299403>, > > or mute the thread > > > > <https://github.com/notifications/unsubscribe-auth/AMNsXfmJWKmvmEsnynL7rX9_aX1YpjGyks5so64cgaJpZM4PoDhM>. > > > > >
Re: [lsst-sqre/jenkins-dm-jobs] add "clean" build jobs (#189)
Hi Nick, I'm just returning from leave. I'll be in touch shortly. -Josh -- On 10/04/2017 09:29 AM, Nick Tonkin wrote: > Hi Josh, > > I see that you saw and deleted the comment I left on a recent Github > commit of yours regarding a failing DateTime::HiRes test, sorry about > that; I had tried a few times first to get you by email. > > I take that my attempts to contact you via email and via Github are > not welcome, and also that you are no longer interested in maintaining > the CPAN module. Please correct me if I've wrongly interpreted your > lack of reply. I know how things are and how things can get busy. But > if you're no longer interested in maintaining the module, please let > me know and I'll be happy to help or take over. > > Thanks, > > Nick > > > > On Wed, Oct 4, 2017 at 12:11 PM, Joshua Hoblitt > <notificati...@github.com <mailto:notificati...@github.com>> wrote: > > Merged #189 <https://github.com/lsst-sqre/jenkins-dm-jobs/pull/189>. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/lsst-sqre/jenkins-dm-jobs/pull/189#event-1278299403>, > or mute the thread > > <https://github.com/notifications/unsubscribe-auth/AMNsXfmJWKmvmEsnynL7rX9_aX1YpjGyks5so64cgaJpZM4PoDhM>. > >
Re: [RFC] new module proposal - Log::Colorize
How about: Text::Illustrate or Text::Exemplify -J --
namespaces, command and control (fwd)
Oh great gods of the namespace realm. We, your humble servants of the DateTime Asylum, seek your infinite wisdom and guidance. As simple serfs we only wish to plant our seeds of temporal knowledge into the fertile soil of the CPAN and have it flourish. Alas - the realm is awash with vagabonds that may trample upon our fields and ruin our orthogonal namespace rows. We bow before your mighty power and ask that you ordain our crops as holy and that you bestow upon us magical charms to protect us from the many evils that have been unpleased in these dark times of top level depravity. -J -- -- Forwarded message -- Date: Wed, 11 Jun 2003 12:50:30 -1000 (HST) From: Joshua Hoblitt [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: DateTime [EMAIL PROTECTED] Subject: namespaces, command and control While writing some documentation for the DateTime project ( http://datetime.perl.org ) I seem to have brought up the question of namespace control. This is the paragraph in question: -- =head2 Namespace Allocation CDateTime::* namespace is allocated by the C[EMAIL PROTECTED] mailing list. Do not create a new 2nd tier namespace without first seeking approval from the list. Unless specifically noted as Copen most 2nd tier namespaces are not available to 3rd party developers. -- Currently we have modules in the DateTime namespace and more then a dozen 2nd tier namespaces. Is it appropriate for us [the DateTime 'Asylum'] to be presuming some sort of control over the DateTime namespace? Further, is it possible to seek control over a top level namespace? I believe there is some president for this, for example DBI, but the issue does seem somewhat vague. At least nothing of this nature seems to be officially ordained. Any clarification would be appreciated. Cheers, -J --
Re: namespaces, command and control (fwd)
Oh great gods of the namespace realm. We, your humble servants of the DateTime Asylum, seek your infinite wisdom and guidance. As simple serfs we only wish to plant our seeds of temporal knowledge into the fertile soil of the CPAN and have it flourish. Alas - the realm is awash with vagabonds that may trample upon our fields and ruin our orthogonal namespace rows. We bow before your mighty power and ask that you ordain our crops as holy and that you bestow upon us magical charms to protect us from the many evils that have been unpleased in these dark times of top level depravity. Err, umm... s/unpleased/unleashed/ -J --
