Infrastructure/arc
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

docs: update index for mailman3

Browse source
This commit is contained in:
Mark O Brien 2021-09-10 15:36:50 +01:00
parent 5d08a8060e
commit d404e4ad6f
2 changed files with 22 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

2
ansible/inventory
View file

@ -12,3 +12,5 @@ pdc ansible_host=100.27.3.145
mailman ansible_host=18.209.248.21 mailman ansible_host=18.209.248.21
[mailman_fedora] [mailman_fedora]
mailman_fedora ansible_host=44.193.222.216 mailman_fedora ansible_host=44.193.222.216
[mailman_docker]
mailman_docker ansible_host=184.73.148.17

25
docs/mailman3/index.rst
View file

@ -4,8 +4,8 @@ Mailman3
Purpose Purpose
------- -------
Purpose of this investigation is to find a possible ways to migrate CentOS mailing lists to Purpose of this investigation is to find potential ways to migrate the CentOS mailing lists to
mailman3 from the current solution and look at them more closely. The output of the investigation mailman3 from the current solution and allow for a frontend. The output of the investigation
is this document. is this document.
Resources Resources
@ -17,17 +17,32 @@ Resources
Investigation Investigation
------------- -------------
Here is the list of ideas/things we looked at: Here is the list of ideas/things we discussed/looked at:
.. toctree:: .. toctree::
:maxdepth: 1 :maxdepth: 1
building_rpm_centos_stream building_rpm_centos_stream
install_using_pip_and_venv
install_using_podman
add_centos_to_fedora_server
Conclusions 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.
Proposed roadmap 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