Feature #86016

Feature #83085: Replace mailinglists, newsgroups and forum with Discourse

Replace typo3-announce mailing list

Added by Michael Stucki 8 months ago. Updated 10 days ago.

Status:
Accepted
Priority:
Should have
Target version:
-
Start date:
2018-08-28
Due date:
% Done:

0%


Description

We plan to shut down the outdated Mailman mailing list solution. The procedure to replace public mailing lists has been discussed over at Discourse:
- https://decisions.typo3.org/t/replace-mailinglists-newsgroups-and-forum-with-discourse/190/11
- https://talk.typo3.org/t/welcome-to-talk-typo3-org/8

What is currently missing is:

  1. a replacement for the typo3-announce mailing list
  2. a replacement for the private Security Team mailing list

The following suggestions need to be discussed:

  • Replace typo3-announce with a Discourse forum
  • Use Google Groups / Mailchimp / <any other external service>
  • Move security team mailing list to the Association mailing list server (at least temporarily?)
  • ...

Considerations:

  • GPG signing of outgoing mails should still be possible.

History

#1 Updated by Michael Stucki 8 months ago

  • Description updated (diff)

#2 Updated by Michael Stucki 8 months ago

  • Parent task set to #83085

#3 Updated by Michael Stucki 8 months ago

  • Tracker changed from Task to Feature
  • Status changed from New to Accepted
  • Assignee set to Michael Stucki

#4 Updated by Michael Stucki 7 months ago

  • Description updated (diff)

Update 2018-09-19: Wrote mail to Benni, Helmut, Olly +

#5 Updated by Michael Stucki 14 days ago

Update 2019-04-08: Olly says that the nntp group "typo3.projects.security" can be deleted. For now, I have removed access for everyone, but the group still exists.

#6 Updated by Michael Stucki 14 days ago

Another possible tool (feature seems to arrive shortly): https://gitlab.com/gitlab-org/gitlab-ce/issues/4272

#7 Updated by Oliver Hader 14 days ago

2019-04-08: Short update call (Michael, Oliver)

General

  • splitting up into
    • newsletter/announcements (outbound only)
    • discussion (community communication)
  • currently about 7.700 recipients in typo3-announce mailing list

Community Communication

  • can most probably be handled by talk.typo3.org with keeping old Mailman archives (HTTP dump)
  • actually removing those lists from NNTP/Mailman

Announcements

  • possible alternatives
  • or keeping Mailman only for the typo3-announce list
  • any future system should have some API interface (SMTP counts as “API” as well)
  • maintenance efforts should be kept to a reasonable amount
  • message integrity (cryptographic signing) should be possible

Conclusion (for the time being)

  • homework: find good replacement for Mailman
  • for the time being: enable opt-in functionality in Mailman (in order to reduce manual actions for new subscriptions)

#8 Updated by Andri Steiner 13 days ago

From my point of view, this lists are no mailinglists but newsletters technically.

Instead of looking at Sympa & Co, we should consider something like Mailchim (Cloud) or Mautic (OS) or whatever other newsletter based tool.

#9 Updated by Oliver Hader 10 days ago

Andri Steiner wrote:

From my point of view, this lists are no mailinglists but newsletters technically.

Instead of looking at Sympa & Co, we should consider something like Mailchim (Cloud) or Mautic (OS) or whatever other newsletter based tool.

Personally I'd be fine with that in case those tools (or any other tool) would allow to

  • be used by an API - I don't need another tool I have to login to in order to manually add information - it should be working with our automated release process
  • maintain information integrity - especially for security announcements and providing cryptographic hash sums (PGP) signatures are essential

Also available in: Atom PDF