I am loathe, as a lowly list administrator (on cPanel hosts, at that) to participate in the clash of titans, but this _is_ the "mailman-users" discussion list. It is somewhat distressing to see so little participation by the Mailman2 users, who will be most affected by any changes in its support.
Speaking as _a_ user, my requirements are simple: 1. MM2 must continue to work, 2. support must continue to be provided.
Any proposal that jeopardizes those fundamentals must be rejected.
By "support", I mean everything except new functionality: bug fixes, installation/administration hand-holding, dumb questions not properly answered by the user community, the occasional "Why does Mailman do this?" query, and any number of issues that depend on the encyclopedic institutional knowledge residing in Mark's and Stephen's crania.
This includes structural changes to way email is handled (DMARC, encryption, etc.). This does not include additional language tables, or any of the issues on my personal laundry list of "I sure wish Mailman had a way to ...".
-Chip-
On 9/13/2020 1:06 PM, Mark Sapiro wrote:
On 9/13/20 9:29 AM, Jim Popovitch via Mailman-Users wrote:
Just what is the Cabal willing to accept in a proposal? Try us and see?
My own opinion is I would want a commitment to take over what I currently do including making releases on Launchpad, distributing them to sourceforge and gnu.org, updating version info on https://www.list.org/ (and mirrors) and announcing them. I would be willing to mentor someone through this process.
I would ask for all that because I am not willing to make releases of code I haven't audited, and if I were willing to audit all the changes, we wouldn't be having this conversation at all. And, I don't see what use there is of just updating the branch on Launchpad without making releases.
You may have ideas about how this can work without all that. That's why I think we want to see and discuss your proposal.