Yes Platonides, your comment (and bd808's at Space) makes me realize that I hadn’t stressed this point, which is completely assumed in this topic.
This proposal is about testing, and a private mailing list with sensitive information wouldn’t be a good candidate for these first tests even if Space would be in production and not in Cloud VPS.
We can still test private mailing list mirroring, for instance taking any public mailing list and mirroring privately to test access control without compromising anything.
We can also test private mailing list emulation by having non-confidential chit chat in a private setting to test access control, again without compromising anything.
_______________________________________________Hello QuimGiven that this is currently implemented on WMCS, I would think that their terms would prevail and certain private mailing lists NOT allowed be copied at all there (for instance a list where checkusers disccussed about vandal ranges), since it's on an "untrusted" network/servers that shall not contain such private data. Other private mailing lists may qualify, depending on what is actually discussed there (e.g. I would see no issue with a signpost editorial comments mailing list). And obviously, the content of public lists is simply... public.Best regards
Listadmins mailing list
Listadmins@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/listadmins
By sending a message to this list, you email all admins of all lists. To request technical changes for a specific list, instead create a task in Phabricator. See https://meta.wikimedia.org/wiki/Mailing_lists