From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id EC10363A for ; Sat, 19 Aug 2023 06:45:41 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id DE8ABC433C8; Sat, 19 Aug 2023 06:45:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1692427541; bh=Tla+qVhYEd5rxxQeMFVvoBTEaHNjHghDVHL/vm1BJPo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=eBwIMSOPg/shuGSLtLH9I53u+Z/vGyw7Xb1Z50EoRCvOi3cDN/4xOOyDUjspEH6pY OXcwlbrhHW/hGIMPXcIUiTpfEIhkERFJ67TjmAVFIGurK2sbMhhjziLuTkIOoQiatg f2vT8lmP0hI5Wb79+4TmYwJJo5wVxm10sOUOnjwAla5nq3wtboF+nwRTkkVWHBbijZ CaeTDAOKkQDVxG08DNnPGZJfVurhHs3qz9t9lMKINY5FSOuwRqgqEeAokiuPP2u6M5 Y9/tbQeB9RYA7F5dGZtSjG2bGKIafHnsW6hOzaUHlRd39XYjV3nC+ZUVJAGblpo1yn Q4iFre4afihiw== Date: Sat, 19 Aug 2023 09:45:37 +0300 From: Leon Romanovsky To: Linus Torvalds Cc: Jakub Kicinski , Linus Walleij , Alexei Starovoitov , Andrew Lunn , Laurent Pinchart , Luis Chamberlain , Josef Bacik , ksummit@lists.linux.dev, Jeff Layton , Song Liu Subject: Re: [MAINTAINERS SUMMIT] Maintainer burnout Message-ID: <20230819064537.GM22185@unreal> References: <20230816180808.GB2919664@perftesting> <20230817093914.GE21668@pendragon.ideasonboard.com> <44814ed5-7bab-4e56-9ca6-189870f97f41@lunn.ch> <20230817081957.1287b966@kernel.org> <20230818080949.7b17b0d5@kernel.org> Precedence: bulk X-Mailing-List: ksummit@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Fri, Aug 18, 2023 at 07:07:24PM +0200, Linus Torvalds wrote: > On Fri, 18 Aug 2023 at 17:10, Jakub Kicinski wrote: > > > > I was wondering last time if we can do a run of short sessions > > where a few volunteers talk about their subsystems? Let's say > > 10min talking about > > - current process subsystem uses > > - "realities" / day to day challenges / problems > > - how the subsystem is evolving the process > > I feel like we did exactly that a few years in a row, but it was > probably back before covid times, and probably when it was still > called the "kernel summit" rather than "maintainer summit". <...> > I do think the whole "how to spread the pain of being a maintainer" is > very much the point of the maintainer summit, though, so I do think we > should revisit. It is worth to try to get honest feedback from active developers/contributors/vendors what is their "real" excuse for not doing code review. I saw in this thread about "have no time to do code review" answers and we all can relate to it, but IMHO it is just an excuse and not the real reason. Especially for a people who are employed by big corporations to do their upstream work. >From what I personally saw, the reasons can be different from truly no time upto toxic subsystem behavior with huge variety and gray areas in between. It is not clear to me how to get honest answers without fear of loosing an ability to work with that subsystems later. Thanks > > Linus >