Ksummit-Discuss Archive mirror
 help / color / mirror / Atom feed
From: Roland Dreier <roland@kernel.org>
To: clm@fb.com
Cc: tech-board-discuss@lists.linux-foundation.org,
	ksummit-discuss@lists.linux-foundation.org, dave.taht@gmail.com
Subject: Re: [Ksummit-discuss] [Tech-board-discuss] Results: Linux Foundation Technical Board Election 2018
Date: Wed, 14 Nov 2018 09:39:59 -0800	[thread overview]
Message-ID: <CAG4TOxOjh_RELGgdwwOqLN9b_iYKr88=nOg662H=MgwQvfFing@mail.gmail.com> (raw)
In-Reply-To: <CB581CD6-5D1C-4C20-9653-055829656444@fb.com>

On Wed, Nov 14, 2018 at 9:28 AM Chris Mason <clm@fb.com> wrote:
> On 14 Nov 2018, at 2:32, Jani Nikula wrote:
> > To play the devil's advocate, the TAB election process is democratic
> > and
> > open to anyone travelling to the conference and handing out a few
> > hundred dollars to the Linux Foundation. It's only some approximation
> > of
> > democratic and open, and we should not be complacent about that.
>
> I do understand your larger point, but it's important to remember the
> Linux Foundation maintains a travel fund to help bring community members
> to the conferences.

That is of course a positive thing but requiring travel to a
conference to vote still imposes a substantial barrier.  There are
many reasons that someone may not be able to or simply not want to
undertake a multi-day trip to cast a vote, beyond financial barriers.

One might argue that requiring travel limits voting to those with
sufficient "skin in the game", but the burden of travel does not fall
evenly - for example the journey to Edinburgh is much easier for a
Scot than someone from New Zealand.  I don't think anyone would argue
that we prefer to have more Scots and fewer Kiwis voting on the TAB.

 - R.

      reply	other threads:[~2018-11-14 17:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-14  2:26 [Ksummit-discuss] Results: Linux Foundation Technical Board Election 2018 H. Peter Anvin
2018-11-14  3:51 ` [Ksummit-discuss] [Tech-board-discuss] " Dave Taht
2018-11-14 10:32   ` Jani Nikula
2018-11-14 17:27     ` Chris Mason
2018-11-14 17:39       ` Roland Dreier [this message]

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='CAG4TOxOjh_RELGgdwwOqLN9b_iYKr88=nOg662H=MgwQvfFing@mail.gmail.com' \
    --to=roland@kernel.org \
    --cc=clm@fb.com \
    --cc=dave.taht@gmail.com \
    --cc=ksummit-discuss@lists.linux-foundation.org \
    --cc=tech-board-discuss@lists.linux-foundation.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).