Re: List managers [Was: Link usability]

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-1596476994-1679695605=:87440
Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT

On Fri, 24 Mar 2023, Odhiambo Washington wrote:

> On Fri, Mar 24, 2023 at 5:10?PM doug <doug@safeport.com> wrote:
>       On Tue, 21 Mar 2023, Pete Wright wrote:
>
>       >
>       >
>       > On 3/21/23 12:22, possessor.assizer305@aceecat.org wrote:
>       >> On Tue, Mar 21, 2023 at 07:49:11PM +1100, Ian Smith wrote:
>       >>
>       >>> Ah, right.  Yet another consequence of the regressive move from
>       >>> mailman plus pipermail to mlmmj is loss of clickable links in the
>       >>> archived messages.  Duh!
>       >> Out of curiosity, what was the rationale for the move?
>       >>
>       >> My opinion:
>       >> Mailman has its warts but it's ubiquitous and well suited for
>       >> a world where almost everything has to be done in the browser
>       >> for $REASONS.
>       >>
>       > my understanding is that mailman was tied to python2, and the next version of
>       > mailman (v3 iirc) that supports python3 is incompatible with the previous
>       > version.  i think it also had a bunch of other shortcomings/issues.  so i
>       > suspect the lift to use mlmmj was easier than moving to mailman v3.
>       >
>       > i agree its an unfortunate situation, but its i think it would be
>       > irresponsible to rely on python2 for such critical infrastructure.
>       >
>       Boo on the mailman project. There is a conversion utility that takes care
>       of the syntax changes. The only maajor changes I hit were the MySQL, and a
>       couple of DNS modules. In something as complex as mailman I am sure there
>       was more but relative to just maintaining something that complex well
>       within there Python knowledge I would assume.
> 
> 
> I have run Mailman2 since 2005. I am currently running Mailman3.Mailman2 
> relied on Python2.7. Mailman3 relies on Python3. There is a migration 
> script for Mailman2 to Mailman3. The installation for Mailman3 is better 
> done in a Python Virtual Environment. Being a FressBSD SysAddmin since I 
> encountered FreeBSD in 1997, I can authoritatively say that it is very 
> easy to migrate. And IF anyone needs assistance to migrate their Mailman2 
> lists to Mailman3, I am willing to hold their hands. Perhaps I should 
> document the whole process. It is quite easy. The only challenge I have 
> faced is the startup script for controlling Mailman3, but I have a 
> rudimentary one that works. I am running Mailman3 on FreeBSD 13- RELEASE, 
> if it matters. I tried Sympa, but waah. Never again. If anyone has 
> questions, I am willing to respond to them. All of them. If you have been 
> running Mailman2, the move to Mailman3 is the most painless!!
>
Thanks for the information. So I change my boo to boo on the list 
maintainers if the fallout is as described. As I use pine following links 
is somewhat problemactic for me anyway. Nice to know the mailman folks were 
not remiss/lazy.

_____
Douglas Denault
http://www.safeport.com
doug@safeport.com
Voice: 301-217-9220
   Fax: 301-217-9277
--0-1596476994-1679695605=:87440--