Re: mailing list migration

This is a reminder that openmcl-devel will be retired soon.

Many people have subscribed to the replacement ccl-devel list, and the =
new list has seen a few messages.

If you want to subscribe to the new list, send mail to =
[email protected] and reply to the message that it sends =
you to confirm your subscription.

If you tried to subscribe, and haven=E2=80=99t seen a reply asking you =
to confirm your subscription, please send a new subscription request (or =
mail me directly and I can add you by hand).


> On Aug 28, 2024, at 12:05=E2=80=AFPM, R. Matthew Emerson =
<[email protected]> wrote:
>=20
> [email protected] <mailto:[email protected]> will be =
retired soon.  Its replacement is a new list, [email protected] =
<mailto:[email protected]>.  Your subscription will not be =
automatically moved over. If you wish to subscribe to the new list, you =
can do so by sending mail to [email protected] =
<mailto:[email protected]>.
>=20
> For more details, read on.
>=20
> This mailing list, [email protected] =
<mailto:[email protected]>, has been managed by the Mailman =
program for many years.
>=20
> Mailman 2, which is what we=E2=80=99ve been running, requires Python =
2.  The Python developers quit working on Python 2 in back in January =
2020.  Instead of porting Mailman 2 to Python 3, the Mailman developers =
decided to create Mailman 3, which is quite different from Mailman 2.
>=20
> At the moment, Python 2 is still available for easy installation on =
FreeBSD and probably some other systems, but they are warning that it is =
deprecated, and at some point, they will stop providing it.
>=20
> So, I=E2=80=99ve decided to try using new mailing list management =
software, namely mlmmj (http://mlmmj.org <http://mlmmj.org/>).
>=20
> Here is the plan.
>=20
> I have created a new mailing list [email protected] =
<mailto:[email protected]>, managed by mlmmj.  You have to subscribe =
to it anew by sending mail to [email protected] =
<mailto:[email protected]>. [1]
>=20
> List archives for the new list will not be immediately available, but =
will be in the near future.  I will also make the old Mailman list =
archives conveniently accessible somewhere.
>=20
> For the moment, the way to subscribe and unsubscribe to the new list =
is by sending it email.  There is a simple web-based front end for =
subscribing and unsubscribing that I will make available when the list =
archives become available.
>=20
> I hate to have to do this, because it takes up time I=E2=80=99d rather =
spend on something else.  Renaming the list is probably going to be =
disruptive as well.  But I feel that I have to do something to get off =
Python 2.
>=20
>=20
>=20
> 1. There is no technical reason I couldn=E2=80=99t automatically add =
all current subscribers, but I don=E2=80=99t feel like that=E2=80=99s =
appropriate.  I would rather have people take explicit action.
>=20