From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 00472C10DCE for ; Fri, 13 Mar 2020 08:57:43 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id ADF69206FA for ; Fri, 13 Mar 2020 08:57:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726437AbgCMI5m (ORCPT ); Fri, 13 Mar 2020 04:57:42 -0400 Received: from mga09.intel.com ([134.134.136.24]:39797 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726055AbgCMI5m (ORCPT ); Fri, 13 Mar 2020 04:57:42 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Mar 2020 01:57:41 -0700 X-IronPort-AV: E=Sophos;i="5.70,548,1574150400"; d="scan'208";a="237153595" Received: from unknown (HELO localhost) ([10.252.52.87]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Mar 2020 01:57:39 -0700 From: Jani Nikula To: "Theodore Y. Ts'o" , "Bird\, Tim" Cc: "tech-board-discuss\@lists.linuxfoundation.org" , "ksummit-discuss\@lists.linuxfoundation.org" , "linux-kernel\@vger.kernel.org" Subject: Re: [Ksummit-discuss] Linux Foundation Technical Advisory Board Elections -- Change to charter In-Reply-To: <20200313031947.GC225435@mit.edu> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <6d6dd6fa-880f-01fe-6177-281572aed703@labbott.name> <20200312003436.GF1639@pendragon.ideasonboard.com> <20200313031947.GC225435@mit.edu> Date: Fri, 13 Mar 2020 10:58:00 +0200 Message-ID: <87d09gljhj.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 12 Mar 2020, "Theodore Y. Ts'o" wrote: > So that means we need to be smart about how we pick the criteria. > Using a kernel.org account might be a good approach, since it would be > a lot harder for a huge number of sock puppet accounts to meet that > criteria. Per [1] and [2], kernel.org accounts "are usually reserved for subsystem maintainers or high-profile developers", but apparently it's at the kernel.org admins discretion to decide whether one is ultimately eligible or not. Do we want the kernel.org admin to have the final say on who gets to vote? Do we want to encourage people to have kernel.org accounts for no other reason than to vote? Furthermore, having a kernel.org account imposes the additional requirement that you're part of the kernel developers web of trust, i.e. that you've met other kernel developers in person. Which is a kind of awkward requirement for enabling electronic voting to be inclusive to people who can't attend in person. Seems like having a kernel.org account is just a proxy for the criteria, and one that also lacks transparency, and has problems of its own. Not that I'm saying there's an easy solution, but obviously kernel.org account is not as problem free as you might think. BR, Jani. [1] https://www.kernel.org/faq.html [2] https://korg.wiki.kernel.org/userdoc/accounts -- Jani Nikula, Intel Open Source Graphics Center