It would make sense, though I am not sure how another email domain would make a difference there. Sending emails to Google addresses is not blocked in China from what I know. CDF might be able to set up an email for us, but I am not sure about timing. If we want to start the sign-up process on Sep 24 as planned, it would be quite a challenge to get the email in time.
Any thoughts from others? On Tue, Sep 22, 2020 at 8:12 PM 'Gavin Mogan' via Jenkins Developers < [email protected]> wrote: > > jenkins-2020-elections@googlegroup > > It will definitely help contributors in areas where Google services are > blocked > > Wouldn't it make sense for the fallback email to be something other than > google then? > > cd.foundation is using mailgun (according to MX records), so maybe they > could setup [email protected] that forwards to > google/the board, so there's no issues. > > Gavin > > On Tue, Sep 22, 2020 at 11:01 AM Oleg Nenashev <[email protected]> > wrote: > >> As an additional mitigation, we can also add a "send a sign-up email to >> jenkins-2020-elections@googlegroups" fallback process to the >> announcement. It will definitely help contributors in areas where Google >> services are blocked >> >> On Tue, Sep 22, 2020, 19:00 Mark Waite <[email protected]> wrote: >> >>> >>> >>> On Tue, Sep 22, 2020 at 4:28 AM Oleg Nenashev <[email protected]> >>> wrote: >>> >>>> > it requires users to login to a Google account when using the >>>> Google Forms mechanism. It does allow us to reduce the possibility of >>>> duplicate voting. >>>> >>>> Apart from duplicate voting, it also prevents from submitting voting >>>> sign-up forms for other individuals. If we do not use a Google account or >>>> any other authentication service, anyone will be able to submit a form for >>>> anyone else, including doing submissions for participants who may not want >>>> their emails to be stored and who do not want to receive communications >>>> from the Jenkins project. It increases the risk of abuse for the voting >>>> sign-up system. >>>> >>>> We do not want to rely solely on Jenkins LDAP, but I think we need some >>>> kind of identity management. Google Auth could bridge the gap, as one of >>>> the options we can rollout quickly. We de-facto require it for many other >>>> contribution areas. >>>> >>>> >>> I think we should use Google Auth to bridge the gap as you've suggested. >>> >>> >>>> Best regards, >>>> Oleg >>>> >>>> >>>> >>>> On Monday, September 21, 2020 at 10:15:23 PM UTC+2 Richard Bywater >>>> wrote: >>>> >>>>> Personally I don't think we should be forcing people to sign up for >>>>> third-party services just to be able to vote on Jenkins related matters. >>>>> There may be good reasons that people have for not wanting to create a >>>>> Google account. >>>>> >>>>> Richard. >>>>> >>>>> On Tue, 22 Sep 2020, 3:15 AM Slide, <[email protected]> wrote: >>>>> >>>>>> Hi Everyone, >>>>>> >>>>>> The Jenkins Governance Board Elections Committee is currently >>>>>> implementing the process which has been defined for Governance Board and >>>>>> Officer Elections. As part of this, we are creating the form that will be >>>>>> used for signing up to participate in the elections. We need to collect >>>>>> email addresses as part of the process. We are using a Google Form for >>>>>> the >>>>>> sign-up and it provides a mechanism to collect email addresses, but it >>>>>> requires users to login to a Google account when using the Google Forms >>>>>> mechanism. It does allow us to reduce the possibility of duplicate >>>>>> voting. >>>>>> We will not keep the data after the voting. Another option would be to >>>>>> just >>>>>> have a short text input that accepts an email address and we would >>>>>> collect >>>>>> it that way. We would like the opinions of those on this list to >>>>>> determine >>>>>> whether this is acceptable or not. We need the email addresses in order >>>>>> to >>>>>> communicate if there are issues in the contribution information as well >>>>>> as >>>>>> to add the folks to the Condorcet vote. >>>>>> >>>>>> Please let us know ASAP your thoughts on this. >>>>>> >>>>>> Regards, >>>>>> >>>>>> Alex Earl >>>>>> >>>>>> >>>>>> -- >>>>>> Website: http://earl-of-code.com >>>>>> >>>>>> -- >>>>>> >>>>> You received this message because you are subscribed to the Google >>>>>> Groups "Jenkins Developers" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to [email protected]. >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVer2x2iug%2BCFNoJkyQDmPoQt_BZyTukijGTnSjezJp2eA%40mail.gmail.com >>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVer2x2iug%2BCFNoJkyQDmPoQt_BZyTukijGTnSjezJp2eA%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> >>>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Jenkins Developers" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-dev/cef9e1d2-f7a0-4e1e-bc04-00756c164eecn%40googlegroups.com >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/cef9e1d2-f7a0-4e1e-bc04-00756c164eecn%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "Jenkins Developers" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/jenkinsci-dev/pzDc62So6xM/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFVHGcagjz9ejMMwP027_30bjfQ_XUV6UZVXY-ASriamg%40mail.gmail.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFVHGcagjz9ejMMwP027_30bjfQ_XUV6UZVXY-ASriamg%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLD-ixcHAtFaU6%3DtfdVPPY1SdFqeS%2B62gKhdUNs%2BBNfS_A%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLD-ixcHAtFaU6%3DtfdVPPY1SdFqeS%2B62gKhdUNs%2BBNfS_A%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/pzDc62So6xM/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DusUC3CgtGmvg69Cv%2B9Ojh8dEu1e3Ra%3DqXLZYJ8DoW-BLw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DusUC3CgtGmvg69Cv%2B9Ojh8dEu1e3Ra%3DqXLZYJ8DoW-BLw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDRNGYQrmDsioBcuHUrthaC%2BLgGU_5SBbgEsuEiU35zWg%40mail.gmail.com.
