Wikinaut writes: > I suggest to modify the code so that all member preferences can be > set via the command line.
They already can be set via "mailman shell", and common settings can be automated using a withlist script. > What do you think? User preferences are extremely complicated because they can be set at several levels. If you know what you're doing Mailman-wise, it requires very little Python to script it (and most of the folks here can help those who don't have that much yet, it doesn't take a core developer). If you don't, the web UI is much better because it is already contains documentation and is more suitable for maintaining that documentation. If you want to provide a patch and commit to documenting it and maintaining it for say 5 years (I do *not* recommend this for the same reasons I really really don't want to do it myself ;-), I promise to review it. It might be interesting to provide a batch API in REST where you could provide an arbitrary sequence of changes in JSON format to address the efficiency problem, but that would be a big project. I haven't thought carefully about it so no promises there. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan _______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-le...@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/237O2OTNOCDANYGJC3ND7EFXSMEJBF3X/ This message sent to arch...@mail-archive.com
