From: Luc Verhaegen <libv-AgBVmzD5pcezQB+pC5nmwQ@public.gmane.org>
To: Harry Wentland <hwentlan-5C7GfCeVMHo@public.gmane.org>
Cc: xorg-devel <xorg-devel-go0+a7rfsptAfugRpC6u6w@public.gmane.org>,
dri-devel
<dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
wayland
<wayland-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
"xorg-go0+a7rfsptAfugRpC6u6w@public.gmane.org"
<xorg-go0+a7rfsptAfugRpC6u6w@public.gmane.org>,
"members@x.org" <members@x.org>,
"mesa-dev-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<mesa-dev-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: 2019 Xorg Election Results
Date: Wed, 8 May 2019 17:01:48 +0200 [thread overview]
Message-ID: <20190508150148.GH15876@skynet.be> (raw)
In-Reply-To: <a473bcae-113f-a347-9afd-d69d7176c264-5C7GfCeVMHo@public.gmane.org>
On Wed, May 08, 2019 at 02:06:37PM +0000, Harry Wentland wrote:
>
> It should also be noted that even though our election process as
> outlined at https://www.x.org/wiki/BoardOfDirectors/Elections/ allows
> denying candidates any points our website didn't take this into account
> and forced voters to rank every candidate. Due to the lack of
> controversy about the candidates we don't expect this to have had any
> impact on the final results.
Does this change not massively skew results?
Lack of controversy has absolutely nothing to do with it.
Luc Verhaegen.
_______________________________________________
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel
next prev parent reply other threads:[~2019-05-08 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 14:06 2019 Xorg Election Results Harry Wentland
[not found] ` <a473bcae-113f-a347-9afd-d69d7176c264-5C7GfCeVMHo@public.gmane.org>
2019-05-08 14:37 ` Trevor Woerner
2019-05-08 15:01 ` Luc Verhaegen [this message]
2019-05-08 15:10 ` Luc Verhaegen
2019-05-13 14:47 ` Navare, Manasi D
2019-05-08 15:06 ` Luc Verhaegen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190508150148.GH15876@skynet.be \
--to=libv-agbvmzd5pcezqb+pc5nmwq@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=hwentlan-5C7GfCeVMHo@public.gmane.org \
--cc=members@x.org \
--cc=mesa-dev-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=wayland-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=xorg-devel-go0+a7rfsptAfugRpC6u6w@public.gmane.org \
--cc=xorg-go0+a7rfsptAfugRpC6u6w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox