#3028: Migrate mailing lists to Mailman3
------------------------------+-----------------------
Reporter: strk | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Mailman | Keywords:
------------------------------+-----------------------
See Upgrading Mailman 3 — Mailman Suite 3.3 documentation
Current debian stable (12) has Mailman3 by default
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3028>
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3028: Migrate mailing lists to Mailman3
------------------------------+------------------------
Reporter: strk | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Mailman | Resolution:
Keywords: |
------------------------------+------------------------
Comment (by neteler):
The mailman3 looks very good indeed:
e.g., News & Announcements - Fedora Discussion
--
Ticket URL: <#3028 (Migrate mailing lists to Mailman3) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3028: Migrate mailing lists to Mailman3
------------------------------+------------------------
Reporter: strk | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Mailman | Resolution:
Keywords: |
------------------------------+------------------------
Comment (by robe):
Replying to [comment:1 neteler]:
> The mailman3 looks very good indeed:
>
> e.g., News & Announcements - Fedora Discussion
That does not look like mailman3. That looks more like discourse they are
using. You can tell by the url and the formatting of the page.
Discourse using /c for category compare the above to one of ours -
General - OSGeo Discourse
--
Ticket URL: <#3028 (Migrate mailing lists to Mailman3) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3028: Migrate mailing lists to Mailman3
------------------------------+------------------------
Reporter: strk | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Mailman | Resolution:
Keywords: |
------------------------------+------------------------
Comment (by neteler):
Sorry, it was the wrong link. Now:
Redis will no longer be OSS... now what? - devel - Fedora Mailing-Lists
--
Ticket URL: <#3028 (Migrate mailing lists to Mailman3) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3028: Migrate mailing lists to Mailman3
------------------------------+------------------------
Reporter: strk | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Mailman | Resolution:
Keywords: |
------------------------------+------------------------
Comment (by robe):
Interesting so they support both discourse and mailman3. I'm assuming
because some people prefer mailman over discourse.
Though it looks like this HyperKitty thing is in addition to mailman3, to
interface with mailman3 and not part of mailman3 because mailman3
pipermail was not sufficient for their needs.
So question in my mind, is how much trouble is that to maintain in
addition to maintaining mailman3. It's possible they are using HyperKitty
I suppose because when they switched to mailman3 it didn't have all the
features they needed.
--
Ticket URL: <#3028 (Migrate mailing lists to Mailman3) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3028: Migrate mailing lists to Mailman3
------------------------------+------------------------
Reporter: strk | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Mailman | Resolution:
Keywords: |
------------------------------+------------------------
Comment (by jjimenezshaw):
Replying to [comment:4 robe]:
>
> Though it looks like this HyperKitty thing is in addition to mailman3,
to interface with mailman3 and not part of mailman3 because mailman3
pipermail was not sufficient for their needs.
> So question in my mind, is how much trouble is that to maintain in
addition to maintaining mailman3. It's possible they are using HyperKitty
I suppose because when they switched to mailman3 it didn't have all the
features they needed.
In Migrating from Mailman 2.1 to Mailman 3 — Mailman Suite 3.3 documentation they mention
HyperKitty, so I assume it is very related.
--
Ticket URL: <#3028 (Migrate mailing lists to Mailman3) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.