hmm, Links of archived discussions in private mailing lists are not as
important as the ones in public lists, we definitely should migrate public
mailing lists first and after that we can migrate any private mailing list
that is okay with their links being broken (and then we remove those old
archives to make it unaccessible to public). It probably means we need to
keep mailman2 around for a while.
On Sun, Aug 9, 2020 at 9:38 PM AntiCompositeNumber <
anticompositenumber(a)gmail.com> wrote:
I would agree that it would be a good solution,
except for the next
bullet in the same document:
"The above mechanism won’t work for private archives since the
archives are gated with password and without a Mailman 2 list, there
is no password. You can however import them to Mailman 3."
Since keeping private lists private is also a requirement, that pretty
much means rolling our own auth system on top of Mailman 3 or creating
a bunch of HTTP redirect rules.
On Sun, Aug 9, 2020 at 3:31 PM Amir Sarabadani <ladsgroup(a)gmail.com>
wrote:
):
"If you need your URLs for Mailman 2
archives to work, you can keep the
HTML files generated for the archives around and your web server
configuration for the archives intact (possibly with a notice to viewers
that it is now a read-only archive, see this list
<https://mail.python.org/pipermail/security-sig/> for example)."
Here's an example:
https://mail.python.org/pipermail/security-sig/ (with a
notice).
It means, the old archives will stay the same (and accessible/searchable
with the new interface as well) but new mails won't get added there to
the
old archives. I think that's a good
compromise.
On Sun, Aug 9, 2020 at 9:19 PM David Gerard <dgerard(a)gmail.com> wrote:
yes - those links are thrown around as if
they're archival. How will
the change affect links to past messages? Will someone need to
construct a redirect farm?
- d.
On Sun, 9 Aug 2020 at 19:54, AntiCompositeNumber
<anticompositenumber(a)gmail.com> wrote:
>
> Glad to hear this is moving forward!
>
> Keeping archive links working, for both public and private lists,
> should be a requirement. There's a lot of institutional knowledge
> stored in the mailing list archives, and it's very important to keep
> that around.
>
> ACN
>
> On Sun, Aug 9, 2020 at 1:05 PM Zoran Dori <zorandori4444(a)gmail.com>
wrote:
> >
> > Hello,
> > this looks great. Especially because of "mobile friendly" function.
> >
> > Best regards,
> > Zoran Dori
> > Volunteer on Wikimedia Foundation's projects
> > E: zorandori4444(a)gmail.com
> > W: kizule.tk
> > I: iamkizule <https://instagram.com/iamkizule>
> > _______________________________________________
> > Wikitech-l mailing list
> > Wikitech-l(a)lists.wikimedia.org
> >
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
>
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
--
Amir (he/him)
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
--
Amir (he/him)
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org