Re: Are Email::* modules unmaintained?

--3MwIy2ne0vdjdPXF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* [email protected] [2018-06-25T05:08:32]
> So what is status of Email::* modules? Does silence now mean that
> modules are abandoned / unmaintained? I guess so.

You are mistaken.

The answer is the same as every other time you have asked:  I am here, I am
alive, I am interested, and I am extremely busy, so these don't often make =
it
to the top of my list.

We don't have any sort of sense of community here or a practice of shared c=
ode
review, so everything comes down to "when does Rik have the time to consider
each change."  That is "not all that often."

If we had three or four people who committed to create a better sense of gr=
oup
responsibility, maybe we'd see more progress.

The last thing you wrung your hands about "we have no maintainer!" was
something for which we didn't even have a clear and isolated fix, so the ta=
sk
here wasn't "nobody will review and apply this commit," but "nobody is will=
ing
to write a fix."  So, in that sense, yes, nobody is doing active maintenanc=
e on
Email::Address much of the time, but somebody is alive.

With Email::MIME, keep in mind that part of maintenance is not just applying
any old patch, because people rely on this software to not change too
radically.  So, there has to be not only patches, but also review and
consideration, so "we aren't adding new features" isn't always a sign of
disrepair, but can also indicate "we don't have the time to predict the imp=
act
of these changes on existing users."

So:  you can wait for me to have more time, or people with some vested
interest can agree to step up to do more in general.

I'm not going to be shamed into doing a release that might break things and
cause me ten times as much work as leaving things be.

--=20
rjbs

--3MwIy2ne0vdjdPXF
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJbMOCMAAoJEOYby6cMccU5CFYIAKIGF1Y9pbCDjJ8qriiQU7aH
qnB530Lz16o+pKrOpPPxok15cp9z6qhRsrTEnFVn2hAf2w8B0ZCKuNoYKeQ3wio3
a1OU864oXroLVX8hZ5ZVv8THKCoHM9ZVzWpvmSTSCtG0zMYgpGRG5ukYdgUh7U8+
vCsZMaDDd0oJtfchVKNIKFyZinpB0Ttn5ibXd7S5th9tFekTgagfbFXR5iUu0nm/
bJkm1AI0k+qjCCyfKG1gwOwJn5iuE995IncYoRCPcxSPpI6pZ/mvH1yPcH2oQ2kJ
t/paI0pn1VIuSPoLgZgGN5TtpQV5COsQFP+m3/0hig9P+S4aVC9Zm8WMrasP8vM=
=BlDp
-----END PGP SIGNATURE-----

--3MwIy2ne0vdjdPXF--