ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Laura Abbott <laura@labbott.name>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: ksummit-discuss@lists.linuxfoundation.org,
	tech-board-discuss@lists.linuxfoundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [Ksummit-discuss] Linux Foundation Technical Advisory Board Elections -- Change to charter
Date: Wed, 11 Mar 2020 22:20:15 -0400	[thread overview]
Message-ID: <750770eb-1fd4-73e1-da8a-f1247e31e7d8@labbott.name> (raw)
In-Reply-To: <20200312003436.GF1639@pendragon.ideasonboard.com>

(speaking only for myself)

On 3/11/20 8:34 PM, Laurent Pinchart wrote:
> Hi Laura,
> 
> On Wed, Mar 11, 2020 at 08:19:46PM -0400, Laura Abbott wrote:
>> On behalf of the Linux Foundation Technical Advisory Board (TAB), I
>> would like to announce the following changes to our charter, available
>> at https://wiki.linuxfoundation.org/tab/start
>>
>> - Line 2b that previously read "All members shall be elected by a vote
>> amongst all invitees of the Linux Kernel Summit." is changed to "All
>> members shall be elected by a vote amongst all attendees of the Linux
>> Kernel Summit."
>>
>> This clarifies that kernel summit is no longer invite only.
> 
> This is a good clarification, no issue with it.
> 
>> - Under meetings and membership, the following line is added
>> "The TAB, at its discretion, may set criteria to allow for absentee
>> voting for those who are unable to attend the Linux Kernel Summit."
> 
> This is however a bit more problematic. I understand the intent, which I
> believe is good, but it would make ballot stuffing very easy. At the
> same time I understood it will not be an easy task to set clear written
> rules that wouldn't be over complex and would still allow reaching the
> end goal of expanding the election to the whole community through
> electronic voting. I'm afraid I don't have a solution to propose to this
> problem at this time.
> 

Thanks for the feedback.

Yes, this is a lot of the discussion we've been having. This is
definitely something we are carefully considering and intend to work
through. I, personally, want to err on the side of letting more
people participate but it's very hard to figure out what's a realistic
threat model. The TAB has a charter but it only works because the
community trusts us. If we were to get vote flooded by 10000 sock
puppets and elect 5 people who the majority of the community doesn't
trust, what impact could they actually have?

The charter also has this line: "The TAB is being formed at the
discretion of the Board. The Board alone may decide to terminate the TAB
in its sole discretion; provided however, that the Board or its
authorized officer shall first consult the TAB Chair." So in theory,
the TAB could be abolished. Would this actually happen? I would
really hope not but it's worth pointing out that there is a possible
solution for election edge cases, even if it's a very destructive one.
On the other hand, maybe I've actually provided a stronger argument for
why we really need to be careful about avoiding ballot box stuffing
if the only option is to burn it all down.

Also in case anyone in the community is worried we're trying to rush
this through in case of conference cancellations, this (really) has
been in discussion for the past few months. The way this is change is
worded the TAB also has the option of not allowing absentee voting, so
if in the unlikely event we don't come up with acceptable terms we will
be going with the existing voting procedures and not allowing absentee
voting.

Thanks,
Laura

>> For those who like diff form, this looks like
>>
>> diff --git a/charter b/charter
>> index 45816d7..70b2e56 100644
>> --- a/charter
>> +++ b/charter
>> @@ -4,7 +4,8 @@
>>        - Promote and Support the programmes with which the TAB is charged
>> to the wider Linux and Open Source Communities.
>>      - Meetings and Membership.
>>        - The TAB consists of ten voting members.
>> -    - All members shall be elected by a vote amongst all invitees of
>> the Linux Kernel Summit.
>> +    - All members shall be elected by a vote amongst all attendees of
>> the Linux Kernel Summit.
>> +    - The TAB, at its discretion, may set criteria to allow for
>> absentee voting for those who are unable to attend the Linux Kernel Summit.
>>        - Self nominations for the election shall be accepted from any
>> person, via email to the TAB mailing list, up until the time of the
>> election.
>>        - Membership of the TAB shall be for a term of 2 years with
>> staggered 1-year elections.
>>        - The TAB shall elect a Chair and Vice-Chair of the TAB from
>> amongst their members to serve a renewable 1 year term.
>>
>>
>> This change is intended to be a follow on to last year's changes to vote
>> electronically instead of using paper ballots
>> (see
>> https://lists.linuxfoundation.org/pipermail/ksummit-discuss/2019-July/006582.html)
>> We will be announcing criteria for absentee voting at a later date.
>>
>> If you have any questions, feel free to speak up here or privately at
>> tab@lists.linuxfoundation.org.
> 
_______________________________________________
Ksummit-discuss mailing list
Ksummit-discuss@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss

  reply	other threads:[~2020-03-12  2:20 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-12  0:19 [Ksummit-discuss] Linux Foundation Technical Advisory Board Elections -- Change to charter Laura Abbott
2020-03-12  0:34 ` Laurent Pinchart
2020-03-12  2:20   ` Laura Abbott [this message]
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         ` [Ksummit-discuss] [Tech-board-discuss] " Greg KH
2020-03-13  9:41           ` 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                     ` Steven Rostedt
2020-03-13 14:10                       ` Jani Nikula
2020-03-13 14:52                         ` Theodore Y. Ts'o
2020-03-13 15:08                           ` Jani Nikula
2020-03-13 15:26                             ` James Bottomley
2020-03-13 17:14                               ` Bird, Tim
2020-03-13 17:36                                 ` Steven Rostedt
2020-03-13 15:18                         ` James Bottomley
2020-03-13 10:30           ` Jani Nikula
2020-03-13 13:05             ` Sasha Levin
2020-03-13 15:42               ` Steven Rostedt
2020-03-13 14:59             ` 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=750770eb-1fd4-73e1-da8a-f1247e31e7d8@labbott.name \
    --to=laura@labbott.name \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tech-board-discuss@lists.linuxfoundation.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 NNTP newsgroup(s).