[KIEKER-1608] Resolve issues with current SourceForge-based mailing lists

rju commented 4 days ago

JIRA Issue: KIEKER-1608 Resolve issues with current SourceForge-based mailing lists Original Reporter: Andre van Hoorn

Currently we have four mailing lists hosted at SourceForge, namely kieker-users, kieker-developers, kieker-tickets, and an internal. (See http://kieker-monitoring.net/support/)

We should get rid of these SourceForge-hosted lists for the following reasons:

They recently sent (SPAM-like) e-mails to subscribers with the requests to confirm the subscription. Most subscribers missed this e-mail and are no longer on the list.
Even the administrator cannot see the list of subscribers
Often, there are major delays (many hours) until a mail is actually sent via the list.

We need to find an alternative.

rju commented 4 days ago

author André van Hoorn -- Wed, 27 Sep 2017 14:01:47 +0200

Some ideas (not saying that possible)

Hosted mailman (or other system)
Google groups could be an option
Nice to have: custum URL, e.g. ..lists.kieker-monitoring.net
Atlassian-based solution
Self-hosted
Docker-based, e.g., https://github.com/fauria/docker-mailman

rju commented 4 days ago

author André van Hoorn -- Wed, 8 Nov 2017 14:28:30 +0100

Use DFN-hosted lists: https://www.listserv.dfn.de/sympa

rju commented 4 days ago

author DaGeRe -- Wed, 6 Mar 2024 16:51:05 +0100

Andre van Hoorn evaluates how anonymous users can create tickets in Jira. If this is possible, we just remove the mailing lists.

kieker-monitoring / kieker

[KIEKER-1608] Resolve issues with current SourceForge-based mailing lists #2230