[Jenkins-infra] Mailing List Migration/Move idea/notes

Tim Jacomb timjacomb1 at gmail.com
Sun Jan 26 09:42:28 UTC 2020


This would be great to get done

Preference for google groups, as the rest of the lists are on it

On Sun, 26 Jan 2020 at 09:31, Arnaud Héritier <aheritier at gmail.com> wrote:

> No real preference
> I didn’t know groups.io
>
>
> Le dim. 26 janv. 2020 à 09:46, Oleg Nenashev <o.v.nenashev at gmail.com> a
> écrit :
>
>> Thanks to Gavin for starting this thread! I am +1 for moving out of
>> mailman, the Infra channel is the only non-deprecated list there after JAM
>> changes.
>>
>> Regarding the migration target, my preference would be to go with Google
>> Groups, just because it is consistent with the rest of the project. Access
>> from China is not a blocker, because folks from China cannot efficiently
>> operate in the community without VPN. Access to devlist is critical.
>>
>> No problem to try groups.io for something new, but IMHO Infra list is
>> too important to be used for testing
>>
>> BR, Oleg
>>
>>
>> On Sun, Jan 26, 2020, 06:20 Gavin <halkeye at gmail.com> wrote:
>>
>>>
>>> So the the idea of the migration of the infra mailing list got brought
>>> up a few times in the last couple weeks because my domain accidentally
>>> caused a bunch of people to get bounces, and I believe unsubscribed.
>>>
>>> The problem is due to the fact that mailman (current mailing list
>>> software) is a little dated, and tries to resend out emails on behalf of
>>> the user that sent them. This actually breaks SPF/DMARC which I have setup
>>> on my domain to prevent spam (I have it set that only a single server can
>>> send out emails with my domain).
>>>
>>> So, discussions were had about why infra was setup differently than all
>>> the other mailing lists. I've lost my irc logs by accident, so I'm going by
>>> memory. Please please give feedback, ideas, and point out what I assume is
>>> many mistakes.
>>>
>>> rtyler is in favor of getting off mailman. Slight preference for google
>>> since its known
>>> oleg is is in favor of getting off mailman
>>> gavin (halkeye) in favor of getting off mailman, slight preference for
>>> google
>>> olblack is in favor of getting off mailman, but doesn't want to use
>>> google groups
>>> alex (slide) is in favor of getting off mailman
>>>
>>> mailmain:
>>> * Has been around for a while
>>> * Can use custom domain (lists.jenkins-ci.org)
>>> * Breaks with spf/dmarc (though apparently there are configuration -
>>> https://wiki.list.org/DEV/DMARC)
>>> * Hosted through OSUOSL
>>>
>>> Google Groups:
>>> * Possibly/probably breaks in china
>>> * Consistency with all the other lists
>>> ** Well known how to manage due to so many jenkins lists using it.
>>> * Has all the right headers/signing/etc
>>> * "Free" (like all things google)
>>> * Some pages old UI, some pages new UI (like lots of google projects)
>>> * Google calendar support
>>> * https://support.google.com/groups/answer/46601?hl=en
>>>
>>> Groups.io:
>>> * Modern platform
>>> * Not consistent with other jenkins mailing lists
>>> * Can be paid for/provided by CDF
>>> * Enterprise plan can do custom domain/branding
>>> * Has its own calendar
>>> * Olblak approved
>>> * Feature lists - https://groups.io/static/pricing
>>> _______________________________________________
>>> Jenkins-infra mailing list
>>> Jenkins-infra at lists.jenkins-ci.org
>>> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
>>>
>> _______________________________________________
>> Jenkins-infra mailing list
>> Jenkins-infra at lists.jenkins-ci.org
>> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
>>
> --
> -----
> Arnaud Héritier
> http://aheritier.net
> Mail/GTalk: aheritier AT gmail DOT com
> Twitter/Skype : aheritier
> _______________________________________________
> Jenkins-infra mailing list
> Jenkins-infra at lists.jenkins-ci.org
> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20200126/99f83094/attachment.html>


More information about the Jenkins-infra mailing list