Re: Crypt-SSLeay release & maintenance

--0000000000005fb54c05d9e190d8
Content-Type: text/plain; charset="UTF-8"

Thanks Sinan, for your return.
I clearly understand your statement and recommendations. This looks like a
sane direction to me.

Note that multiple Perl distro depends on this package, view
https://metacpan.org/module/Crypt::SSLeay/requires
Crypt-SSLeay is pretty high in the CPAN River, and will be until we replace
it from all these main distributions listed in the above link.

At minimum we should clearly advertise this on the default POD page.

Would you mind giving me co-maint on Cryp-SSLeay to move in that direction?
or do you prefer taking care of this on your end?

IMO the "Don't declare a dependency on Crypt::SSLeay" statement should not
only live on a blog post.
We should add the statement to the main POD with probably a link to the
blog.
And also consider removing it from distro using it in a non backup way.

my 2cnts

thanks for your considering my take over offer
nicolas


On Thu, Mar 10, 2022 at 11:12 AM A. Sinan Unur <[email protected]> wrote:

> I had not seen the earlier message.
>
> Quite frankly, with IO::Socket::SSL & Net::SSLeay, I don't see the need
> for further development on this module.
>
> See also
> https://www.nu42.com/2014/08/dont-declare-dependency-on-cryptssleay.html
> and previous linked post.
>
> I humbly think further development efforts should focus on those two
> modules.
>
> --Sinan
>
> On Thu, Mar 10, 2022, 1:04 PM Nicolas R. <[email protected]> wrote:
>
>> Dear PAUSE admins, I'm contacting you to request a module takeover for
>> Crypt::SSLeay.
>>
>> As you could see I tried to contact Sinan without success.
>> That module had no release since 2014 but a few trial releases
>> occurred since.
>>
>> Also note that the GitHub repo for the project has some pending Pull
>> Requests.
>>
>> Would it be possible to add me as co-maint so I can provide support and
>> maintenance releases for this distro.
>> Waiting for your reply
>>
>> Sincerely
>> nicolas
>>
>> ---------- Forwarded message ---------
>> From: Nicolas R. <[email protected]>
>> Date: Tue, Mar 1, 2022 at 10:37 AM
>> Subject: Crypt-SSLeay release & maintenance
>> To: <[email protected]>
>> Cc: <[email protected]>
>>
>>
>> Hi Sinan, I am contacting you regarding the Crypt-SSLeay Perl distro you
>> maintain.
>>
>> The last available version on CPAN is 0.72 from 2014.
>> Since then, I can see that you released two development versions in 2017
>> 0.73_06 is the most recent one and includes several fixes (the fix for
>> '.' in INC...).
>>
>> I wondered if there is a reason to block the release of 0.74?
>>
>> Also, note that the GitHub repo has some pending Pull Requests:
>> https://github.com/nanis/Crypt-SSLeay/pulls
>>
>> If you need help, I would gladly provide support and perform a release of
>> the distro.
>> If you are interested, could you add me as a CO-MAINT on pause for the
>> Cryp-SSLeay distro? Additionally, giving me some perms on the GitHub repo
>> would allow me to handle the pending pull requests.
>>
>> Both my Github and CPAN nicknames are atoomic
>>
>> Thanks in advance for your consideration & reply
>> nicolas
>>
>>

--0000000000005fb54c05d9e190d8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks Sinan, for your return.<br><div>I clearly understan=
d your statement and recommendations. This looks like a sane=C2=A0direction=
 to me.</div><div><br></div><div>Note that multiple Perl distro depends on =
this package, view=C2=A0 <a href=3D"https://metacpan.org/module/Crypt::SSLe=
ay/requires">https://metacpan.org/module/Crypt::SSLeay/requires</a></div><d=
iv>Crypt-SSLeay is pretty high in the CPAN River, and will be until we repl=
ace it from all these main distributions listed in the above link.</div><di=
v><br></div><div>At minimum we should clearly advertise this on the default=
 POD page.<br></div><div><br></div><div>Would you mind giving me co-maint o=
n Cryp-SSLeay to move in that direction?</div><div>or do you prefer taking =
care of this on your=C2=A0end?</div><div><br></div><div>IMO the &quot;Don&#=
39;t declare a dependency on Crypt::SSLeay&quot; statement should not only =
live on a blog post.</div><div>We should add the statement to the main POD =
with probably a link to the blog.</div><div>And also consider removing it f=
rom distro using it in a non backup way.</div><div><br></div><div>my 2cnts<=
/div><div><br></div><div>thanks for your considering my take over offer</di=
v><div>nicolas</div><div><br></div></div><br><div class=3D"gmail_quote"><di=
v dir=3D"ltr" class=3D"gmail_attr">On Thu, Mar 10, 2022 at 11:12 AM A. Sina=
n Unur &lt;<a href=3D"mailto:[email protected]">[email protected]</a>&gt; wrote:<=
br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto=
">I had not seen the earlier message.<div dir=3D"auto"><br></div><div dir=
=3D"auto">Quite frankly, with IO::Socket::SSL &amp; Net::SSLeay, I don&#39;=
t see the need for further development on this module.</div><div dir=3D"aut=
o"><br></div><div dir=3D"auto">See also=C2=A0<a href=3D"https://www.nu42.co=
m/2014/08/dont-declare-dependency-on-cryptssleay.html" target=3D"_blank">ht=
tps://www.nu42.com/2014/08/dont-declare-dependency-on-cryptssleay.html</a> =
and previous linked post.</div><div dir=3D"auto"><br></div><div dir=3D"auto=
">I humbly think further development efforts should focus on those two modu=
les.</div><div dir=3D"auto"><br></div><div dir=3D"auto">--Sinan</div></div>=
<br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu=
, Mar 10, 2022, 1:04 PM Nicolas R. &lt;<a href=3D"mailto:[email protected]=
g" target=3D"_blank">[email protected]</a>&gt; wrote:<br></div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Dear PAUSE admins,=
 I&#39;m contacting you to request a module takeover for Crypt::SSLeay.<div=
><br></div><div>As you could see I tried=C2=A0to contact Sinan without=C2=
=A0success.</div><div>That module had no release since 2014 but a few trial=
 releases occurred=C2=A0since.</div><div><br></div><div>Also note that the =
GitHub repo for the project has some pending Pull Requests.</div><div><br><=
/div><div>Would it be possible to add me as co-maint so I can provide suppo=
rt and maintenance releases=C2=A0for this distro.</div><div>Waiting=C2=A0fo=
r your reply</div><div><br></div><div>Sincerely</div><div>nicolas<br><br><d=
iv class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">---------- F=
orwarded message ---------<br>From: <strong class=3D"gmail_sendername" dir=
=3D"auto">Nicolas R.</strong> <span dir=3D"auto">&lt;<a href=3D"mailto:nico=
[email protected]" rel=3D"noreferrer" target=3D"_blank">[email protected]</=
a>&gt;</span><br>Date: Tue, Mar 1, 2022 at 10:37 AM<br>Subject: Crypt-SSLea=
y release &amp; maintenance<br>To:  &lt;<a href=3D"mailto:[email protected]" r=
el=3D"noreferrer" target=3D"_blank">[email protected]</a>&gt;<br>Cc:  &lt;<a h=
ref=3D"mailto:[email protected]" rel=3D"noreferrer" target=3D"_blank">nanis@cp=
an.org</a>&gt;<br></div><br><br><div dir=3D"ltr">Hi Sinan, I am contacting =
you regarding the Crypt-SSLeay Perl distro you maintain.<br><br>The last av=
ailable version on CPAN is 0.72 from 2014.<br>Since then, I can see that yo=
u released two development versions in 2017<br>0.73_06 is the most recent o=
ne and includes several fixes (the fix for &#39;.&#39; in INC...).<br><br>I=
 wondered if there is a reason to block the release of 0.74?<br><br>Also, n=
ote that the GitHub repo has some pending Pull Requests:<br><a href=3D"http=
s://github.com/nanis/Crypt-SSLeay/pulls" rel=3D"noreferrer" target=3D"_blan=
k">https://github.com/nanis/Crypt-SSLeay/pulls</a><br><br>If you need help,=
 I would gladly provide support and perform a release of the distro.<br>If =
you are interested, could you add me as a CO-MAINT on pause for the Cryp-SS=
Leay distro? Additionally, giving me some perms on the GitHub repo would al=
low me to handle the pending pull requests.<br><br>Both my Github and CPAN =
nicknames are atoomic<br><br>Thanks in advance for your consideration &amp;=
 reply<br>nicolas<br><br></div>
</div></div></div>
</blockquote></div>
</blockquote></div>

--0000000000005fb54c05d9e190d8--