[arch-dev-public] mailman3/hyperkitty/postorius in the repos now
Hey all! I'm just on my way home from FOSDEM - train time, mail time ;-) I've spent the last weeks bringing the mailman3 ecosystem(!) to [community] and [community-testing] (~56 packages). Today I've added wiki pages for mailman3 [1] (it will replace the current mailman page once it's done by moving that to be 'mailman2' and eventually deleting it), hyperkitty [2] and postorius [3]. I've done initial integration tests with mailman3, hyperkitty and postorius and they "should just work"(TM). Before moving all the stuff to [community] and replacing the wiki page, it would be great to get some further integration testing with actual mail servers (note the expansion macro [4] in the mailman article) and importing of mailman2 data [5] [6] going. Any help is very much appreciated, as the switch requires quite the data migration and configuration changes for e.g. our own lists (the archives of some of them are pretty large). Additionally, the hosting aspects of both Hyperkitty and Postorius need some expansion as well (e.g. for Apache setups and for proper subdomain setups). Everyone, feel invited to install and test the applications and propose fixes and expansions to the documentation (or packages) as needed. Best, David [1] https://wiki.archlinux.org/index.php/User:Davezerave/Mailman [2] https://wiki.archlinux.org/index.php/Hyperkitty [3] https://wiki.archlinux.org/index.php/Postorius [4] https://wiki.archlinux.org/index.php/User:Davezerave/Mailman#Integrate_with_... [5] https://wiki.archlinux.org/index.php/User:Davezerave/Mailman#Migrate_from_ma... [6] https://wiki.archlinux.org/index.php/Hyperkitty#Importing_mailman2_archives -- https://sleepmap.de
On Sun, 2020-02-02 at 17:48 +0100, David Runge wrote:
Everyone, feel invited to install and test the applications and propose fixes and expansions to the documentation (or packages) as needed.
Hello, Great! So happy you moved forward. I'll test your work with my building co-owner mailing list. For the record, the new mailman (3.x) ecosystem is split into several components (with different git and version), while the current version (2.x) has all in one scm. I remember you planned to name the package against the components names. Why did you named mailman-core to mailman3? As soon as we don't require mailman 2.x on our infra, I plan to move mailman to AUR. Cheers,
On 2020-02-02 19:24:15 (+0100), Sébastien Luttringer via arch-dev-public wrote:
Great! So happy you moved forward. I'll test your work with my building co-owner mailing list.
Please be aware, that you might still hit bugs and such! Integration is probably not really there yet. But also: \o/ I'm able to test the import of (small) archives and mailing lists on my own infrastructure when I'm home. Really interesting would be the proper rollout of a test list on some infrastructure and the gathering of insights from that.
For the record, the new mailman (3.x) ecosystem is split into several components (with different git and version), while the current version (2.x) has all in one scm.
Yes. The three most basic components are mailman(3), hyperkitty and postorius. As hyperkitty and postorius are optional, they can be run on a different or the same host, or not be used at all (no archiving and no clicky web-frontend for managing accounts then respectively).
I remember you planned to name the package against the components names. Why did you named mailman-core to mailman3?
In reality mailman-core is really mailman (both the repository and the python module are called mailman). My plan is to rename/replace mailman3 with mailman eventually (when mailman(2) has been gone from the repos for some time).
As soon as we don't require mailman 2.x on our infra, I plan to move mailman to AUR.
That's great! Would be awesome to introduce it as mailman2 then and make it conflict with the mailman(3) in the repos (they both share the same state dir and user). Best, David -- https://sleepmap.de
On Sun, Feb 2, 2020, 17:48 David Runge
Hey all!
I'm just on my way home from FOSDEM - train time, mail time ;-)
I've spent the last weeks bringing the mailman3 ecosystem(!) to [community] and [community-testing] (~56 packages). Today I've added wiki pages for mailman3 [1] (it will replace the current mailman page once it's done by moving that to be 'mailman2' and eventually deleting it), hyperkitty [2] and postorius [3].
I've done initial integration tests with mailman3, hyperkitty and postorius and they "should just work"(TM).
Before moving all the stuff to [community] and replacing the wiki page, it would be great to get some further integration testing with actual mail servers (note the expansion macro [4] in the mailman article) and importing of mailman2 data [5] [6] going.
Any help is very much appreciated, as the switch requires quite the data migration and configuration changes for e.g. our own lists (the archives of some of them are pretty large).
Additionally, the hosting aspects of both Hyperkitty and Postorius need some expansion as well (e.g. for Apache setups and for proper subdomain setups).
Everyone, feel invited to install and test the applications and propose fixes and expansions to the documentation (or packages) as needed.
Best, David
[1] https://wiki.archlinux.org/index.php/User:Davezerave/Mailman [2] https://wiki.archlinux.org/index.php/Hyperkitty [3] https://wiki.archlinux.org/index.php/Postorius [4] https://wiki.archlinux.org/index.php/User:Davezerave/Mailman#Integrate_with_... [5] https://wiki.archlinux.org/index.php/User:Davezerave/Mailman#Migrate_from_ma... [6] https://wiki.archlinux.org/index.php/Hyperkitty#Importing_mailman2_archives
Thanks for all of the hard work, David! :)
participants (3)
-
David Runge
-
Sven-Hendrik Haase
-
Sébastien Luttringer