Mailman3
========

Purpose
-------

Purpose of this investigation is to find potential ways to migrate the CentOS mailing lists to
mailman3 from the current solution and allow for a frontend. The output of the investigation
is this document.

Resources
---------

* Mailman3 upstream: https://wiki.list.org/Mailman3
* Mailman3 Fedora dist-git: https://src.fedoraproject.org/rpms/mailman3

Investigation
-------------

Here is the list of ideas/things we discussed/looked at:

.. toctree::
    :maxdepth: 1

    building_rpm_centos_stream
    install_using_pip_and_venv
    install_using_podman
    add_centos_to_fedora_server


Conclusions
-----------

Based on the investigations carried out the most beneficial but probably most difficult
solution would be to build the rpms for mailman3 hyperkitty and postorius for epel. This
would make this available for Centos but could also be used by fedora which could help
with some longstanding issues such as https://pagure.io/fedora-infrastructure/issue/5478.

The installation using containers would address the issues of compatibility and push
them upstream but it also brings the problems of relying on an upstream maintainer who 
is not a part of our community.

When installing with pip and venv similar problems are encountered as with rpm where 
dependencies are not available or up to date in the fedora or stream environment.

Adding Centos mailing list to the fedora server would be a quick fix but doubles down
on using the fedora setup which itself in not in perfect health. It would also involve
some issues with naming as the centos mail list uses centos.org rather than lists.centos.org