From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 8C174BC8 for ; Sun, 9 Sep 2018 20:06:03 +0000 (UTC) Received: from mx1.suse.de (mx2.suse.de [195.135.220.15]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 2A419102 for ; Sun, 9 Sep 2018 20:06:03 +0000 (UTC) Date: Sun, 9 Sep 2018 22:05:59 +0200 (CEST) From: Jiri Kosina To: Mauro Carvalho Chehab In-Reply-To: <20180908074708.249571f4@coco.lan> Message-ID: References: <1536263073.6012.3.camel@HansenPartnership.com> <1536263475.6012.5.camel@HansenPartnership.com> <20180908074708.249571f4@coco.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Cc: James Bottomley , ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] [MAINTAINER TOPIC] Succession Planning: Is It time to Throw Linus Under a Bus? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sat, 8 Sep 2018, Mauro Carvalho Chehab wrote: > Q: How many Kernel developers does it take to replace Linus? Somebody please remind me, what problem exactly are we trying to solve here, again? :) I honestly believe this all started as a joke from James (the mixed up conferences etc. of course providing excellent grounds for such a joke :) ), but now that this keeps going on, I think the problem that is actually being solved (and what would be the properties of expected outcome/solution) should be formulated again :) Linus explicitly stated that he's willing to go on merging, and we don't have any "bus factor" plans for other critical people either anyway. So if this "how do we generally deal with all the buses out there?", so be it, but it really should be clearly stated I think :) Thanks, -- Jiri Kosina SUSE Labs