Hi Joshua

No, I do not believe that Travis or some other CI/CD is appropriate or
needed or worth the effort here. If Dave set something up for the whole
ecosystem then of course DT::HR should be in it. But like Dave I find the
release and prerelease testing and management provided by dzil to be
perfect for my CPAN needs. (Although I have been wondering about making a
PAUSE API now that  the innards are all new and shiny ;-) )

Please keep in mind that the change needed to DT::HR is trivial and has
been reported for over three years IIUC, and it's well over a year since I
contacted you. That statement is *only* about my ability and willingness to
help; not about your own time commitments/priorities/interests. We all get
busy. I was quite distant from Perl for some time (when my kids were small)
and I undrstand it and you may be back as strong or stronger than before.
But in the meantime please reconsider handing the module over or at least
co-maint.

Thanks!

- nick

On Fri, Aug 16, 2019 at 8:08 AM Dave Rolsky <auta...@urth.org> wrote:

> The problem with deploying from Travis is going to be that PAUSE doesn't
> really have an API, so you would have to store some sort of PAUSE
> username/pw in a way Travis can access. That means the releases are still
> tied to an account. Of course, you can make a "Foo group" account and share
> the credentials, but it's a pretty gross solution. FWIW I've found that
> using Dist::Zilla has made releases easy enough to not want even think
> about automating it further.
>
>
> Cheers,
>
> Dave Rolsky
> http://blog.urth.org
> https://github.com/autarch
>
>
> On Fri, Aug 16, 2019 at 6:22 PM Joshua Hoblitt <j...@hoblitt.com> wrote:
>
>> 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 <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
>>> > <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
>>> >.
>>> >
>>> >
>>>
>>>
>>

Reply via email to