On Wed, 2019-06-05 at 20:03 -0400, Ben Cotton wrote:
Voting is now open for the Fedora 30 election cycle. You can vote in the Elections app[1]. Interviews with candidates are available on the Fedora Community Blog[2], with links available in the Elections app. Voting ends at 23:59 UTC on 20 June.
[1] https://elections.fedoraproject.org [2] https://communityblog.fedoraproject.org/?p=7774
-- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis
I received the above via the Announce list on Friday June 21, after voting had closed. I don't know if others have had the same experience, but clearly something is amiss.
This is the complete message with all headers:
Delivered-To: pocallaghan@gmail.com Received: by 2002:ac0:8cd0:0:0:0:0:0 with SMTP id s16csp2585588ima; Fri, 21 Jun 2019 10:01:26 -0700 (PDT) X-Google-Smtp-Source: APXvYqyXaRDJs1s36qebRnXr7n+AgbCWp9X4gJmw7uUCIKNtrP2Ldxz0Z/529Ggt8P/J/4QzKVRA X-Received: by 2002:a05:620a:5a:: with SMTP id t26mr16362927qkt.201.1561136486917; Fri, 21 Jun 2019 10:01:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561136486; cv=none; d=google.com; s=arc-20160816; b=fgfyblN2zKmXjutzoRHj248Uew1MgDJ/ZhzIXnEBMi2dPaKSv0mruzM9cuPmcTtHTI LF1Uocvh/xde9ms++jAdZYQwn9vvPsPwTPT6toow5qUH44Fsi56FjemSD0GhQxOq2ZdZ P7uvFdRqkq7uGr0Z3u7uLFYZ7DqYQm2+a6Hi1jbaBr8B1ms7cwA3Be0VUgNV7ePkL1QD KkIYYRm7/XztRizSdZk1deJEWVOvHbgdKmPg+u3g86jeioLw2ylIrfH6ijFOAiBvpSVQ 4kXghxkDtzBtOENXHHErwMIXMEs7Fojn8K2R5Ls4O695qSU5Jt4NpiJEUg0ig8DFztZ+ xJOw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:list-unsubscribe:list-subscribe:list-post :list-help:list-archive:archived-at:list-id:reply-to:precedence :message-id-hash:to:subject:message-id:date:from:mime-version :dkim-filter; bh=CYSK3mGSoevqiSprAUsZQfGNDdvJ3YeVnEv6siklDFg=; b=0gVCkjVoKT4RfKkPko0Lz5KWkdqjLT8Eb0fWuNxV288lBs1oItgeDmx3cx8SJ7eX0H bCpsrgWgyiqMtrO/v3aUOwuDycW7tADRLn6tQkPmWEpiXMLHRgrYtKHzQUkuGtoe2yBm ls0uOiE2mcXt8+SrBkl00qRjqEK6JdjC6GJ1u7qt/MExgBtD28m/e/9JLiJB8J/kWvH1 dFn9jI1q74Z7X+AEuYbW/OKuTTvZdn38C0nfKbzyUZZK1WOi98iKslw7v3Jxcuhn9pXI ATM5nVNWQaZ0fZaUFQKeswB7pi2ipvp2WI6RIVlnY5mrqVjqV+IPPFHUjJ5kvhtK7MUI 8s/g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of announce-bounces@lists.fedoraproject.org designates 209.132.181.2 as permitted sender) smtp.mailfrom=announce-bounces@lists.fedoraproject.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: announce-bounces@lists.fedoraproject.org Received: from bastion.fedoraproject.org (bastion01.fedoraproject.org. [209.132.181.2]) by mx.google.com with ESMTPS id u54si2218798qte.102.2019.06.21.10.01.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Jun 2019 10:01:26 -0700 (PDT) Received-SPF: pass (google.com: domain of announce-bounces@lists.fedoraproject.org designates 209.132.181.2 as permitted sender) client-ip=209.132.181.2; Authentication-Results: mx.google.com; spf=pass (google.com: domain of announce-bounces@lists.fedoraproject.org designates 209.132.181.2 as permitted sender) smtp.mailfrom=announce-bounces@lists.fedoraproject.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: from mailman01.phx2.fedoraproject.org (mailman01.phx2.fedoraproject.org [10.5.126.36]) by bastion01.phx2.fedoraproject.org (Postfix) with ESMTP id 2C88E62D722B; Fri, 21 Jun 2019 16:14:06 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 bastion01.phx2.fedoraproject.org 2C88E62D722B Received: from mailman01.phx2.fedoraproject.org (localhost [IPv6:::1]) by mailman01.phx2.fedoraproject.org (Postfix) with ESMTP id 7BC375819A783; Fri, 21 Jun 2019 16:14:05 +0000 (UTC) Received: by mailman01.phx2.fedoraproject.org (Postfix, from userid 991) id B978A5806C9DD; Thu, 6 Jun 2019 00:03:46 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mailman01.phx2.fedoraproject.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE autolearn=disabled version=3.4.0 Received: from smtp-mm-cc-rdu01.fedoraproject.org (smtp-mm-cc-rdu01.vpn.fedoraproject.org [192.168.1.55]) by mailman01.phx2.fedoraproject.org (Postfix) with ESMTP id 615265806BF55 for announce@lists.fedoraproject.org; Thu, 6 Jun 2019 00:03:46 +0000 (UTC) Received: from mail-pf1-f179.google.com (mail-pf1-f179.google.com [209.85.210.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by smtp-mm-cc-rdu01.fedoraproject.org (Postfix) with ESMTPS id EBF0E306A3B7 for announce@lists.fedoraproject.org; Thu, 6 Jun 2019 00:03:45 +0000 (UTC) Received: by mail-pf1-f179.google.com with SMTP id q17so299974pfq.8 for announce@lists.fedoraproject.org; Wed, 05 Jun 2019 17:03:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=6TKGT+Izh1Rk1x/ON2ZcYFEcVorET5ga0GSs7WNDkZs=; b=PLH5vdjXWkEwwMgQl3jKTx3wIrh0+u+Ti/p6Bw8pM3BrRbH1RmGl3iBXvfYp6o4PAq zRTZnmGmxrwftmOqxJbLXTnjCo0qQ2gUiL3YRWQCxikZ9IC4Fj4AGoHwz+I9rc/cX5I1 8S2+H57JzQVyeqj371w2TxhJj700syOGVJMdLBm4+EvrI5TBWoMXFUMvnmlthMkbv+D7 cjhxYciNfwDhq7DTLCGLrVtr5L6c7s2A8S5iqgrUbsbg3sCWYlINR1zi2Y6OFwcOCVUk xXOgHEUkLrs1EoV7AjRPsuAqyeGEkhMnR1t7q1fu0f3x+lzHG8Yvpw7ie/zNP/OYt+KG NGIA== X-Gm-Message-State: APjAAAUJXIx5JIKKeXnlHLDL43ozIB5LH/9VWkvn/xht7E7Yp+/Rt/ZP PFJqCCXKtzRuOk4xjdyh4p0vkd5yKUdksa3fl819gA== X-Received: by 2002:a63:dc15:: with SMTP id s21mr493408pgg.215.1559779424972; Wed, 05 Jun 2019 17:03:44 -0700 (PDT) MIME-Version: 1.0 From: Ben Cotton bcotton@redhat.com Date: Wed, 5 Jun 2019 20:03:34 -0400 Message-ID: CA+voJeUM-nr+5u537NC+mFN=kpMW=FRrQLXE2LPPf4dVd62Eyw@mail.gmail.com Subject: Fedora 30 voting is now open To: devel-announce@lists.fedoraproject.org, announce@lists.fedoraproject.org, mindshare@lists.fedoraproject.org, Discussions with the Fedora Council and community council-discuss@lists.fedoraproject.org X-MailFrom: bcotton@redhat.com X-Mailman-Rule-Hits: member-moderation X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address Message-ID-Hash: YJDEZPW5LQEQG3OMI522GTJGRQMUALKI X-Message-ID-Hash: YJDEZPW5LQEQG3OMI522GTJGRQMUALKI X-Mailman-Approved-At: Fri, 21 Jun 2019 16:11:08 +0000 X-Mailman-Version: 3.1.1 Precedence: list Reply-To: users@lists.fedoraproject.org List-Id: Announcements related to the Fedora Project <announce.lists.fedoraproject.org> Archived-At: https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.org/message/YJDEZPW5LQEQG3OMI522GTJGRQMUALKI/ List-Archive: https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.org/ List-Help: mailto:announce-request@lists.fedoraproject.org?subject=help List-Post: mailto:announce@lists.fedoraproject.org List-Subscribe: mailto:announce-join@lists.fedoraproject.org List-Unsubscribe: mailto:announce-leave@lists.fedoraproject.org Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 X-Evolution-Source: 77495d48f741550f2e4e759f8306473bacb8ff59
Vm90aW5nIGlzIG5vdyBvcGVuIGZvciB0aGUgRmVkb3JhIDMwIGVsZWN0aW9uIGN5Y2xlLiBZb3Ug Y2FuIHZvdGUgaW4NCnRoZSBFbGVjdGlvbnMgYXBwWzFdLiBJbnRlcnZpZXdzIHdpdGggY2FuZGlk YXRlcyBhcmUgYXZhaWxhYmxlIG9uIHRoZQ0KRmVkb3JhIENvbW11bml0eSBCbG9nWzJdLCB3aXRo IGxpbmtzIGF2YWlsYWJsZSBpbiB0aGUgRWxlY3Rpb25zIGFwcC4NClZvdGluZyBlbmRzIGF0IDIz OjU5IFVUQyBvbiAyMCBKdW5lLg0KDQpbMV0gaHR0cHM6Ly9lbGVjdGlvbnMuZmVkb3JhcHJvamVj dC5vcmcNClsyXSBodHRwczovL2NvbW11bml0eWJsb2cuZmVkb3JhcHJvamVjdC5vcmcvP3A9Nzc3 NA0KDQotLQ0KQmVuIENvdHRvbg0KSGUgLyBIaW0gLyBIaXMNCkZlZG9yYSBQcm9ncmFtIE1hbmFn ZXINClJlZCBIYXQNClRaPUFtZXJpY2EvSW5kaWFuYS9JbmRpYW5hcG9saXMKX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KYW5ub3VuY2UgbWFpbGluZyBsaXN0 IC0tIGFubm91bmNlQGxpc3RzLmZlZG9yYXByb2plY3Qub3JnClRvIHVuc3Vic2NyaWJlIHNlbmQg YW4gZW1haWwgdG8gYW5ub3VuY2UtbGVhdmVAbGlzdHMuZmVkb3JhcHJvamVjdC5vcmcKRmVkb3Jh IENvZGUgb2YgQ29uZHVjdDogaHR0cHM6Ly9kb2NzLmZlZG9yYXByb2plY3Qub3JnL2VuLVVTL3By b2plY3QvY29kZS1vZi1jb25kdWN0LwpMaXN0IEd1aWRlbGluZXM6IGh0dHBzOi8vZmVkb3JhcHJv amVjdC5vcmcvd2lraS9NYWlsaW5nX2xpc3RfZ3VpZGVsaW5lcwpMaXN0IEFyY2hpdmVzOiBodHRw czovL2xpc3RzLmZlZG9yYXByb2plY3Qub3JnL2FyY2hpdmVzL2xpc3QvYW5ub3VuY2VAbGlzdHMu ZmVkb3JhcHJvamVjdC5vcmcK
On 6/22/19 3:11 AM, Patrick O'Callaghan wrote:
I received the above via the Announce list on Friday June 21, after voting had closed. I don't know if others have had the same experience, but clearly something is amiss.
No problems here. Actually got 3 message on announce. Time received is in GMT+8.
6/6/19, 8:03 AM Voting Open 6/12/19, 12:15 AM Re: Voting Open (body indicated 2 more days to vote) 6/20/19, 4:55 AM Re: Voting Open (body indicated final reminder)
All 3 were received moments after being sent.
In the case of the first message sent, this is the part that is OK for me but not for you.
Received: from mailman01.phx2.fedoraproject.org (localhost [IPv6:::1]) by mailman01.phx2.fedoraproject.org (Postfix) with ESMTP id E29605806BF63; Thu, 6 Jun 2019 00:03:56 +0000 (UTC) Received: by mailman01.phx2.fedoraproject.org (Postfix, from userid 991) id 10C2B5806BF7A; Thu, 6 Jun 2019 00:03:47 +0000 (UTC)
On 6/22/19 11:58 AM, Tim via users wrote:
??????
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
On 6/22/19 9:35 AM, Ed Greshko wrote:
No problems here.
Oh, just got an email from Tim ignored_mailbox@yahoo.com.au saying he had the same issues as POC.
But, of course, I can't respond as the email is "ignored". So, I'm putting it out here in case Tim doesn't notice the mistake.
Tim said:
"But I'd encountered the same thing as POC.?? A seriously delayed message about voting, and three followups by the original poster that were also delayed.?? My headers showed that was delayed by Fedora mailing system until the 21st. "
On 22/6/19 6:22 pm, Ed Greshko wrote:
But, of course, I can't respond as the email is "ignored".?? So, I'm putting it out here in case Tim doesn't notice the mistake.
Oops, sorry, didn't mean to send that privately.?? I'm used to mailing lists where hitting reply sends the reply back where it's expected to go, for some dumb reason the mail client ignored the reply-to header.?? They're supposed to obey that instruction absolutely unless YOU override it, which I didn't.?? Sodding nerks who want to redesign email in yet another broken way.
I'm not having the best run of luck with emails today.
On Sat, 2019-06-22 at 09:35 +0800, Ed Greshko wrote:
On 6/22/19 3:11 AM, Patrick O'Callaghan wrote:
I received the above via the Announce list on Friday June 21, after voting had closed. I don't know if others have had the same experience, but clearly something is amiss.
No problems here. Actually got 3 message on announce. Time received is in GMT+8.
I also got three messages, but only quoted the first one. All three were delivered on June 21 within seconds of each other. I'm assuming it's a problem with the mailing list software, but it should be looked at. I CC'ed the sender but haven't heard anything back from him as yet.
If this happened to a significant number of people it could potentially invalidate the election. Having worked on election systems in the past, I would consider this a serious bug.
poc
On 6/22/19 7:37 PM, Patrick O'Callaghan wrote:
On Sat, 2019-06-22 at 09:35 +0800, Ed Greshko wrote:
On 6/22/19 3:11 AM, Patrick O'Callaghan wrote:
I received the above via the Announce list on Friday June 21, after voting had closed. I don't know if others have had the same experience, but clearly something is amiss.
No problems here. Actually got 3 message on announce. Time received is in GMT+8.
I also got three messages, but only quoted the first one. All three were delivered on June 21 within seconds of each other. I'm assuming it's a problem with the mailing list software, but it should be looked at. I CC'ed the sender but haven't heard anything back from him as yet.
If this happened to a significant number of people it could potentially invalidate the election. Having worked on election systems in the past, I would consider this a serious bug.
Maybe contact someone on the Infrastructure Team and ask them to check the logs?
On 2019-06-22 at 12:37:38 Patrick O'Callaghan wrote:
On Sat, 2019-06-22 at 09:35 +0800, Ed Greshko wrote:
On 6/22/19 3:11 AM, Patrick O'Callaghan wrote:
I received the above via the Announce list on Friday June 21, after voting had closed. I don't know if others have had the same experience, but clearly something is amiss.
No problems here. Actually got 3 message on announce. Time received is in GMT+8.
I also got three messages, but only quoted the first one. All three were delivered on June 21 within seconds of each other. I'm assuming it's a problem with the mailing list software, but it should be looked at. I CC'ed the sender but haven't heard anything back from him as yet.
If this happened to a significant number of people it could potentially invalidate the election. Having worked on election systems in the past, I would consider this a serious bug.
poc _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Same happened to me.
-- Regards, Erik P. Olsen
What happened is unfortunate, but simple to explain:
The announce list is moderated for all posts, so every post needs to be approved before it is sent out.
The Fedora Program Manager (Ben Cotton) Sent those emails out at various times and they waited in the moderation queue for approval.
I usually approve those posts, but for some reason mailman did not send me the normal 'post waiting for moderation', or if it did, I didn't see it as I was on vacation, then traveling to meetings. Others who also approve those must not have seen them either as no one did.
So, when I noticed them I approved them all, but as you note they then showed up all in a bunch.
In order to prevent this from happening again, I've made Ben a list moderator so he can approve posts and we will be looking to see why the moderation emails didn't go out.
Sorry for the confusion.
kevin
On Sat, 2019-06-22 at 12:46 -0700, Kevin Fenzi wrote:
What happened is unfortunate, but simple to explain:
The announce list is moderated for all posts, so every post needs to be approved before it is sent out.
The Fedora Program Manager (Ben Cotton) Sent those emails out at various times and they waited in the moderation queue for approval.
I usually approve those posts, but for some reason mailman did not send me the normal 'post waiting for moderation', or if it did, I didn't see it as I was on vacation, then traveling to meetings. Others who also approve those must not have seen them either as no one did.
So, when I noticed them I approved them all, but as you note they then showed up all in a bunch.
In order to prevent this from happening again, I've made Ben a list moderator so he can approve posts and we will be looking to see why the moderation emails didn't go out.
Sorry for the confusion.
Thanks for the clarification. Do you have any sense of how this may have affected voting numbers compared to previous years?
poc
On Sun, Jun 23, 2019 at 4:56 AM Patrick O'Callaghan pocallaghan@gmail.com wrote:
Thanks for the clarification. Do you have any sense of how this may have affected voting numbers compared to previous years?
The impact seems to be fairly small, if it exists at all. The number of voters for F30 was down a little bit from F29, but there were also fewer candidates (the Council election, in particular, was uncontested). Regular announcements and reminders were sent on the council-discuss, devel/devel-announce, and mindshare mailing lists, and the Community Blog post was "sticky" for the duration of the voting period. I suspect — though I have no way of confirming — that the number of people who would vote and only subscribe to the announce list is relatively small. Of course, that doesn't mean they shouldn't have the opportunity to vote. As Kevin said, we've taken steps to prevent this from happening in future elections.
I encourage everyone who has in an interest in the internal workings of the community to follow the Community Blog[1]. In addition to announcements of elections, we also publish proposed changes to council policies, technical and process posts from teams and contributors, and a weekly summary of change proposals/schedule/etc. The Community Blog is a low traffic (generally 1 or fewer posts per day) way to keep up with Fedora. If you have feedback on the Community Blog, we'd be happy to hear from you on Discussion[2].
As a long-time Fedora contributor, I understand how important the elections are to making sure the community is well-represented. If you ever have questions or concerns, I'm happy to discuss them with you on- or off-list, or in the weekly FPgM office hours on IRC[3].
[1] https://communityblog.fedoraproject.org/ [2] https://discussion.fedoraproject.org/tags/c/project/commops/commblog [3] https://apps.fedoraproject.org/calendar/council/#m9527
On Mon, 2019-06-24 at 11:53 -0400, Ben Cotton wrote:
I suspect ??? though I have no way of confirming ??? that the number of people who would vote and only subscribe to the announce list is relatively small. Of course, that doesn't mean they shouldn't have the opportunity to vote.
Simple test: Use the announce list to ask people to respond if they missed out on voting because they didn't see an announcement list email.
On Mon, 2019-06-24 at 11:53 -0400, Ben Cotton wrote:
Regular announcements and reminders were sent on the council-discuss, devel/devel-announce, and mindshare mailing lists, and the Community Blog post was "sticky" for the duration of the voting period. I suspect — though I have no way of confirming — that the number of people who would vote and only subscribe to the announce list is relatively small.
The only one of those lists I subscribe to is Announce and I don't generally read blogs. I do subscribe to the Fedora Users list, which I would guess probably has more traffic than all of those combined. I don't know if posting election announcements on the Users list is against list policy, though I'd suspect it isn't, but you may want to consider doing so in future, even if to a limited extent.
poc
On Tue, 2019-06-25 at 06:58 +0930, Tim via users wrote:
On Mon, 2019-06-24 at 11:53 -0400, Ben Cotton wrote:
I suspect ??? though I have no way of confirming ??? that the number of people who would vote and only subscribe to the announce list is relatively small. Of course, that doesn't mean they shouldn't have the opportunity to vote.
Simple test: Use the announce list to ask people to respond if they missed out on voting because they didn't see an announcement list email.
+1
(assuming the Announce list is now working correctly of course :-)
poc