mailing list migration
"R. Matthew Emerson" <[email protected]> Wed, 28 Aug 2024 12:05:19 -0700
| Newsgroups | gmane.lisp.openmcl.devel |
|---|---|
| Message-ID | <[email protected]> |
[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]>. For more details, read on. This mailing list, [email protected] = <mailto:[email protected]>, has been managed by the Mailman = program for many years. 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. 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. So, I=E2=80=99ve decided to try using new mailing list management = software, namely mlmmj (http://mlmmj.org <http://mlmmj.org/>). Here is the plan. 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] 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. 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. 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. 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.