LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jani Nikula <jani.nikula@intel.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "tech-board-discuss@lists.linuxfoundation.org" 
	<tech-board-discuss@lists.linuxfoundation.org>,
	"ksummit-discuss@lists.linuxfoundation.org" 
	<ksummit-discuss@lists.linuxfoundation.org>,
	Vlastimil Babka <vbabka@suse.cz>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Ksummit-discuss] [Tech-board-discuss] Linux Foundation Technical Advisory Board Elections -- Change to charter
Date: Fri, 13 Mar 2020 08:18:30 -0700	[thread overview]
Message-ID: <1584112710.3391.12.camel@HansenPartnership.com> (raw)
In-Reply-To: <874kusl50q.fsf@intel.com>

On Fri, 2020-03-13 at 16:10 +0200, Jani Nikula wrote:
> On Fri, 13 Mar 2020, Steven Rostedt <rostedt@goodmis.org> wrote:
> > On Fri, 13 Mar 2020 11:50:45 +0100
> > Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > 
> > > > > > Given that before now, there has not be any way to vote for
> > > > > > the TAB remotely, it's less restrictive :)  
> > > > > 
> > > > > But people without kernel.org accounts could still vote in
> > > > > person before, right?  
> > > > 
> > > > Yes, and they still can today, this is expanding the pool, not
> > > > restricting it.  
> > > 
> > > Oh right, assumed we'll still have a conference in person, and
> > > unrestricted travel.
> > 
> > Correct. But if we don't change the voting requirements, and the
> > conference is canceled, or people are restricted from traveling,
> > then those people will not be able to vote with the current
> > charter.
> > 
> > We are trying to extend who can vote beyond those that the charter
> > allows.  We are not preventing those that can vote under the
> > current rules from voting.  IIUC, we are trying to create absentee
> > voting which we never had before. Thus, you can either vote the
> > current way by getting travel to wherever Kernel Summit is and
> > attending the conference, or we can extend the charter so that if
> > you can not come for whatever reason, you have an option to vote
> > remotely, if you satisfy the new requirements. Remember, not
> > attending means you do not satisfy the current requirements.
> > 
> > The TAB has bikeshed this a bit internally, and came up with the
> > conclusion that kernel.org accounts is a very good "first step". If
> > this proves to be a problem, we can look at something else. This is
> > why we are being a bit vague in the changes so that if something
> > better comes along we can switch to that. After some experience in
> > various methods (if we try various methods), we could always make
> > whatever method works best as an official method at a later time.
> > 
> > But for now, we need to come up with something that makes it hard
> > for ballot stuffing, and a kernel.org account (plus activity in the
> > kernel) appears to be the best solution we know of.
> 
> Thanks for writing this. I, for one, would welcome more open and
> proactive communication from the TAB.
> 
> Have you considered whether the eligibility for running and voting
> should be made the same? As it is, absolutely anyone can self-
> nominate and run.

When the TAB charter was written (in 2006), the original reason was to
prevent manipulation (real or imagined) by the committee who would then
become the arbiters of nominations and thus able to influence who might
run for the TAB.  There are a couple of reasons for the electorate
clause: when the TAB was formed, it was done by the kernel developers
unhappy at the way OSDL (precursor organization to the LF) was behaving
with regard to the kernel, who forced their way onto its board and
formed the TAB to gain input and control on behalf of kernel
developers, so the TAB was formed by kernel developer for kernel
developers and, since most other non-kernel open source groups had
their own foundation like entities, keeping it kernel only wasn't seen
as a problem.  The other reason was that OSDL was a bit unhappy to be
reformed in this way and we foresaw that one way to dilute the
reforming influence of the TAB would be to dilute kernel developer
representation since they were the main community interested in that
reform.  When the OSDL became the LF, some of the initial antagonism
and need for reform went away and the elections were opened to the co-
located conferences as a sign of improved trust.

James


  parent reply	other threads:[~2020-03-13 15:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-12  0:19 Laura Abbott
2020-03-12  0:34 ` [Ksummit-discuss] " Laurent Pinchart
2020-03-12  2:20   ` Laura Abbott
2020-03-12 21:28   ` Bird, Tim
2020-03-12 22:58     ` Laura Abbott
2020-03-13  3:19     ` Theodore Y. Ts'o
2020-03-13  8:58       ` Jani Nikula
2020-03-13  9:35         ` [Tech-board-discuss] " Greg KH
2020-03-13  9:41           ` [Ksummit-discuss] [Tech-board-discuss] " Vlastimil Babka
2020-03-13 10:07             ` Greg KH
2020-03-13 10:16               ` Geert Uytterhoeven
2020-03-13 10:37                 ` Greg KH
2020-03-13 10:50                   ` Geert Uytterhoeven
2020-03-13 12:12                     ` [Tech-board-discuss] [Ksummit-discuss] " Steven Rostedt
2020-03-13 14:10                       ` [Ksummit-discuss] [Tech-board-discuss] " Jani Nikula
2020-03-13 14:52                         ` [Tech-board-discuss] [Ksummit-discuss] " Theodore Y. Ts'o
2020-03-13 15:08                           ` Jani Nikula
2020-03-13 15:26                             ` [Ksummit-discuss] [Tech-board-discuss] " James Bottomley
2020-03-13 17:14                               ` Bird, Tim
2020-03-13 17:36                                 ` [Tech-board-discuss] [Ksummit-discuss] " Steven Rostedt
2020-03-13 15:18                         ` James Bottomley [this message]
2020-03-13 10:30           ` Jani Nikula
2020-03-13 13:05             ` [Ksummit-discuss] [Tech-board-discuss] " Sasha Levin
2020-03-13 15:42               ` [Tech-board-discuss] [Ksummit-discuss] " Steven Rostedt
2020-03-13 14:59             ` [Ksummit-discuss] [Tech-board-discuss] " Konstantin Ryabitsev
2020-03-13 15:07               ` Jani Nikula

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=1584112710.3391.12.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=geert@linux-m68k.org \
    --cc=jani.nikula@intel.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tech-board-discuss@lists.linuxfoundation.org \
    --cc=vbabka@suse.cz \
    --subject='Re: [Ksummit-discuss] [Tech-board-discuss] Linux Foundation Technical Advisory Board Elections -- Change to charter' \
    /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

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 NNTP newsgroup(s).