From owner-freebsd-ports@freebsd.org Tue Apr 28 15:33:47 2020 Return-Path: Delivered-To: freebsd-ports@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D52872BCCF5 for ; Tue, 28 Apr 2020 15:33:47 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49BQfL6pmQz3NP3; Tue, 28 Apr 2020 15:33:46 +0000 (UTC) (envelope-from matthias.andree@gmx.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1588088022; bh=uUeSB+2AupehuomBS/Oyaw+V5DoQszn9Wzo/mWZ4+bg=; h=X-UI-Sender-Class:From:Subject:To:Cc:References:Date:In-Reply-To; b=By01ocTDtDsYWqw64YegJmc20G5IDAOFgERoRjlHAhM1KcBgm4Y02t5a/DBC5yxpz lSdXuTae4ik06yU5YnZK3aJR4ZMk568MbGTT9GF9021xs/fZalRrd58sBvQ64lYf77 QNuyoU27IiZJb3uerVpSmgK6ikwd9fGCIQbPKfl4= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from mandree.no-ip.org ([217.224.112.40]) by mail.gmx.com (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MiJVG-1j0STT3iKc-00fVLx; Tue, 28 Apr 2020 17:33:41 +0200 Received: from ryzen.an3e.de (localhost [IPv6:::1]) by ryzen.an3e.de (Postfix) with ESMTP id 629F4122D9F; Tue, 28 Apr 2020 17:33:41 +0200 (CEST) From: Matthias Andree Subject: Re: mail/mailman v3? To: Kurt Jaeger , Dan Langille Cc: FreeBSD Ports References: <20200424130424.GJ39563@home.opsec.eu> Message-ID: <8684b670-d968-7457-231e-720ab8449190@gmx.de> Date: Tue, 28 Apr 2020 17:33:41 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <20200424130424.GJ39563@home.opsec.eu> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:cTNytDu9YznWSY0ShjtqHkVxZbjJEBt3RXO2vTrZM43vJ4qhgnt rVc+ngU6g4803Uoj2TCRSRb4iV8Fe2GjC4xJz/qF+W2g3D2gmkH6TGNysZq0CEjlQOYK5P+ SN3z6DLjPN/oQcJvODEjAjmIQVPYLW6mobVEBFdh+uDPSzFlHsNntPM2VbCrC06FY2p/oi0 j5RWT0ZSuXn3OYHQkaHow== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:PQCX9Zyk3uA=:6zOydQcKwtvBiPTJsqX0Oy BjDIaKXIVNLfqXYYHnACDtgLThEqjkCTgRiC789kVXvLEe2SCaL/z95hKakqw3A8J34oUN6m4 EM8r7DhHo/Qt+fsIlIWfh7MR1vwlA9Vu/Ysc+F9dP4sziwLWHeJ0oNPib21taRaEQnXye8/6R sSaYmscNDcLFOEfhaCW/1dpOB/3qizO/el7z2sLsejx4Ev+vbEG/ymJ51zKoaOSiQMF50yp1j +pNsWg8xrAzFMyCtfTwr4PfTvjZrRQDRLewm2esP6VDO/1KNxCvZXg62p4abvJ15luEN3Z8em RwGvTVnHKzaq60qzAj6Tn+RNtJFjM45/fgvXolSvLoJCfMN1KPmvSrmqwh7GnU2B6oQ/Jnygt ebxtAQAATQ8ccLwuT2GV2rtkBPTq/D2nXit7hscdHBV3PPaeHuiscqBOAfDHtNmGbzIeQcPHq gqr9gnkpQlf8G6VH3uwRTN0XteecNOhLyQbTto0ywYVVXaGm1w/7x0iWOKrhh/eO0Wy28ZLkj KONSsaX1waSGEfWguLTFNqxTrpYM9ct6oYd4gqBitoYjs7ApMs2m58GeqQURlPWlRa2JJxGCQ 0PxBy1CgPd/fBniJLsmKSMAWAL3U2nQpgPvNKTJM9skV3G6lTMYw4EXd9hTGt25626rSDYWNl 0SN2gSC4+VOaovZVHXQ5U6ssvhVcAKdax3G3HVHPnVf9TDjByLOAajVWZTRkNg8HKwTJYCq3Z 0GBBqlCUbYsQt2Qo0bErLgMT3A9H9pVkMimg6rqguoyzy4hsnozV9yfwLnhQWCNdCt3Wjooj2 I2K5wmu3R1I8tARYHkTmrajhDHUMzpaAiX2wjvde1f9DgkiOWEK9BYhQTcJ2riJGW8PHELM0J ewZ6aRCTwwvPeqppwkhqN6L0a2hhgKGqigLx4/WyEh1eNe8tl0mBdaGVQo1EJfDaoGJbfFMk9 zeiGvDERN0mksVHZV6xxK0xCjtyrB57mfbYDUSTfOIqO9cATUZw2dXCx6lm4F8EpJlwwXi9WV eYgljGE+tEd+TNk+cXGtKP2p+jff6pOJtmgqZ4A1bK2KRn4OEwuElIQmG/ohZ4ax01S94zKIa uFD6yIXfl37a2HyjO40bPrh4DASx7hl5YLiHpFXSlBsTuNhUg2grSpXpO8NE8WelsmJ/nM8I0 rG/BkFQvZPQbyV5VzEZm++JXzkBcMEd0p8UpvUXJD+Um+99gXjEqscKIefrfoDuc37cxajhh+ 8kTy2R1oAovapCjjH X-Rspamd-Queue-Id: 49BQfL6pmQz3NP3 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmx.net header.s=badeba3b8450 header.b=By01ocTD; dmarc=none; spf=pass (mx1.freebsd.org: domain of matthias.andree@gmx.de designates 212.227.17.20 as permitted sender) smtp.mailfrom=matthias.andree@gmx.de X-Spamd-Result: default: False [-0.09 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(0.00)[+ip4:212.227.17.0/27:c]; FREEMAIL_FROM(0.00)[gmx.de]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmx.net:+]; RBL_MAILSPIKE_BAD(1.00)[20.17.227.212.rep.mailspike.net : 127.0.0.12]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmx.de]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[20.17.227.212.list.dnswl.org : 127.0.3.1]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; R_DKIM_ALLOW(0.00)[gmx.net:s=badeba3b8450]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-0.99)[-0.995,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(0.00)[ip: (-6.41), ipnet: 212.227.0.0/16(-1.22), asn: 8560(2.05), country: DE(-0.02)]; DMARC_NA(0.00)[gmx.de]; IP_SCORE_FREEMAIL(0.00)[]; BAD_REP_POLICIES(0.10)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Apr 2020 15:33:47 -0000 [Dan, Kurt, this is a re-send of my message written 2020-04-24 with a different sender address.] Am 24.04.20 um 15:04 schrieb Kurt Jaeger: > Hi! > >> With mail/mailman being Python 2.7 (which is end-of-life), and mailman = 3 being Python 3 compatible: >> >> Do you know of any plans to port Mailman 3? > > There's already a PR about that: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225543 > > The patch itself is fine, but we need run-tests. > > This means: If you want to help, > - use that patch, > - build mailman3, > - and install it somewhere and > - test all the use-cases that you can think of > - then write some docs on how to move an existing mailman2 site > to mailman3 > - and give ideas how to handle list archives > *especially* keeping the URLs identical (!) > > And, speaking as one of the postmaster@ team: > As lists.freebsd.org uses mailman2, we need this! > > postmaster@ has not yet decided if we really want to move to mailman3, > so we are open to other options. The mail archive is the biggest hurdle = 8-( > Thanks Dan for the question, and Kurt for answering that question. As the mailman2 maintainer frequently being asked about mailman3, here are my thoughts on it. TL;DR: mailman3 documentation is an untidy inconsistent mess, is in my perception not honestly and outright advertising the mailman 2.x features that have not yet been reimplemented. The minimum version to be ported should be the latest release as they are still re-adding lost features, for instance, 3.3.1 is current has brought bounce processing. I am not driving mailman3 efforts, don't want be in the first line or maintain a mailman 3.x port, but may help here or there if I am being asked on advice. Long version: I have looked at Mailman 3 again and again, and the more often I look, the more I balk at it. Mailman 3 will be five years old coming Tuesday (3.0.0 released 2015-04-28), and the first-hand documentation is scattered across web sites and inconsistent, not frequently updated for the new releases. Mailman 3 is also a new product, "Mailman 3 is a fully rewritten code base." . It could bear a new name in honesty, and more importantly that means all the workarounds and experience from 2.x are lost, and have to be re-written, too. And some have not been, and they admit it on the hind pages. - FEATURE ADVERTISING COMPLETENESS: In quality and features 3.x appears to boast new "features" over 2.x but does not in the same prominent place list what's missing. Most of the "features" are implementation details that I don't deem critical for day-to-day operation. Others were just added less than a week ago, f.i. bounce processing only arrived in 3.3.1 - and the web sites above advertising feature advances over 2.x are at 3.3.0 or older status and DO NOT MENTION bounce processing missing, so the only conclusion is that there are more 2.x features missing in 3.x without being prominently marked as such. Quoting NEWS.rst > Features > -------- > * Add support for processing of email bounce events. Thanks to Aaryan Bh= agat for > working on this as a part of his GSoC project and Thanks to Google for > sponsoring the project as a part of GSoC.(See !584) Look right ABOVE the 3.3.0 section. (gitlab cannot render it with decoration, this is a download link instead, some 80 kB) - MIGRATION: http://docs.list.org/en/latest/migration.html mentions breaking archive URLs, and also "Some configuration and settings aren=E2=80=99t available i= n Mailman 3=E2=80=99s UI yet, so even though those settings will be migrated= to Mailman 3, you may not be able to change them from the Web UI today. All of those settings should be exposed in the UI very soon. Mailman 3 doesn=E2=80=99t have support for bounce processing yet, but it i= s on the roadmap." - so obviously the migration guide is outdated, too. - DOCUMENTATION TIDINESS: Mailman 3 documentation and everything is scattered across what feels half a dozen places, all inconsistent WRT what is the current version, features and all that, and obviously not kept up to date with releases. - https://mailman.readthedocs.io/ - https://docs.mailman3.org/en/latest/ (not sure how that relates to readthedocs, may be an alias or a copy) - https://wiki.list.org/Mailman3 - http://www.list.org/ - https://gitlab.com/mailman - https://pypi.org/project/mailman/ which seems to be the most up to date download - DEVELOPMENT AND COMPONENT CONCISENESS The Gitlab site show many side projects with unclear relation to the "mailman suite", no easily accessible roadmap besides a five-or-six-item list of what makes up the suite. Given the shape of the documents, and even assuming that documentation is the first thing that falls short in commercial time-pressed development, I find that messy. There is certainly a LOT of work to do, work out processes to get documentation consistent with the code releases, then actually do that. - PERSONAL CONCLUSION AND OUTLOOK This is a subjective and personal note of someone who has not read a single line of Mailman 3 implementation, but only its documentation that's accessible from web sites and several one-or-two clicks deep hyperlink chains, but is asked again and again (as mailman 2 maintainer) about mailman 3. I have shown how I feel that the documentation is untidy, inconsistent, and partially unmaintained on sites that are linked from list.org. I have shown how I personally do not trust that mailman 3 is feature-complete when looking at the mailman 2.x feature set. So assuming we've had a port, what calms a potential porter's or maintainer's mind that he's not going to be drowned in user support? Personlly I fear that a port would bring with it lots of people getting tripped up by the inconsistent web sites, and it would probably add more support work than the sum of all other ports I am currently listed MAINTAINER for. So I don't want to play a *major* role in the porting, feel free to ask me here or there, and I will not become maintainer now. If Python 3.x were not a rather important argument, I would have written a polite form of "leave me alone with that immature stuff and would have moved on. - FINAL QUESTIONS Leaving Python 3.x compatibility aside, what good arguments can anyone weigh in for Mailman 3.x who is using it in practice (f.i. on Linux)? How is it better? Is it mature? Would it be plausible to port Tauthon 2.8.2 (I am not doing that) and continue using mailman2 on it (I might help with this part)?