Thanks - comments inline. On 20-Jun-17 23:48, Barry Warsaw wrote:
On Jun 20, 2017, at 11:18 AM, tlhackque via Mailman-users wrote:
I'd like to deploy a new project on Mailman 3, which I prototyped on 2.1). Unfortunately, it's organized as one mailing list with ~ 120 topics. (The project follows another source, and it's much easier to spin up (or down) a new topic than to instantiate & manage a new list.) I see that the latest Mailman 3 release (Congrats!) doesn't support topics yet.
Where is that on your todo list? It's not. We've discussed topics quite a bit and unfortunately, I don't think it's something we've seen enough traction on to want to support in Mailman 3. We think something along the lines of "dlists" (dynamic sublists, as originally implemented for Mailman 2 by Systers) as a better overall feature for supporting sub-conversations in parent lists.
That said, I think topics could be a good candidate for a plugin, and the work being done for GSoC this year will greatly improve the plugin architecture. So while topics may not be a built-in feature, it could be an interesting third party add-on. That's disappointing; I was expecting feature parity. Topics are a good fit for my use case - which is a bunch of announce-only lists on related topics. E.g. Project foo news, meeting agendas, meeting minutes, x several dozen projects.
I suppose I can map these to virtual e-mail addresses for Mailman's benefit (I have a process between the MTA and Mailman), but I'm not sure how that will play out with list creation via the API & the user interface. Perhaps creating a list isn't as heavyweight in V3 as it is in V2...
In V2, all I have to do to spin up a topic is use config_list to extract the the configuration, add the topic name, regexp & description, and then push it back, which is easy to do on the discovery path. Creating a list requires updating the MTA (aliases) & establishing the list's admin controls, templates, separate directories, user registrations, etc...
Creating a new list also doesn't provide the 'unless you do something, you get everything' default of V2's topics.... But I'll keep an open mind. Many of the other changes you've made seem, at first blush, to be helpful.
Once I get V3 to where I can experiment, I guess I have more work to do... Hoping for maybe a 3rd party plugin to appear doesn't constitute a plan on my end :-) And I don't want to switch UIs on my users soon after initial deployment.
I don't mean to sound negative - I'm excited about trying to make this work. Just trying to share a perspective from outside your usual suspects :-)
I seem to be about 1/3 of the way to getting MM3 up -- I finally got the core running in developer mode on Fedora. I'll post my "new user" notes on the process... they're not refined, but you only do something for the first time once :-)
Hopefully they'll be helpful.
First bug: Looking at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/.
If I set "results per page" to a large number & switch months, results per page reverts to the default (10).
It should stick with whatever I select...
It also would be nice to have an account preference for this, so it doesn't have to be set on each visit. The best place to capture this is on the HyperKitty tracker:
https://gitlab.com/mailman/hyperkitty/issues Done, Issue #138
Thanks again for all the good work.
Cheers, -Barry
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/