From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753168AbYE1RU1 (ORCPT ); Wed, 28 May 2008 13:20:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751794AbYE1RUS (ORCPT ); Wed, 28 May 2008 13:20:18 -0400 Received: from accolon.hansenpartnership.com ([76.243.235.52]:45784 "EHLO accolon.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751737AbYE1RUQ (ORCPT ); Wed, 28 May 2008 13:20:16 -0400 Subject: [Ksummit-2008-discuss] Fixing the Kernel Janitors project From: James Bottomley To: ksummit-2008-discuss@lists.linux-foundation.org Cc: linux-kernel Content-Type: text/plain Date: Wed, 28 May 2008 12:20:12 -0500 Message-Id: <1211995212.3445.52.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.22.1 (2.22.1-2.fc9) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org In the spirit of having a more process than technical based kernel summit, I'd like to put the topic of the kernel Janitors project up for discussion. In the early days, the project was conceived as a way of getting fresh blood into kernel development by giving them fairly simple but generally useful tasks and hoping they'd move more into the mainstream. If we wind forwards to 2008, there's considerable and rising friction being generated by janitorial patches. This is only an example: http://marc.info/?l=linux-kernel&m=121135889328760 but there are many more. The greatest problem, as I see it is that by pouring vitriol like this on newbies, we're really damaging our reputation as a community that welcomes newcomers and strangling our necessary supply of willing volunteers. On the other hand, as a maintainer, when there's people yelling me at about patches not being included plus a persistent regressions list and about ten bug reports to track down, the last thing I want to see within a million miles of my inbox is a white space fixing patch. The more of these patches we get, the worse the problem becomes and the shorter and more inflammatory the responses get. We can't go on like this. The most obvious solution might be to shut the Janitors project down, or at least more tightly manage its TODO list (although a lot of what gets seen as janitorial patches, like whitespace fixes, isn't on the TODO list in the first place). However, since the purpose is to get new people involved with kernel development, perhaps we should repurpose the project so it actually does this. My suggestion is that we replace it with the kernel bugs project. Kudos for finding bugs, more for finding better ways of finding bugs, and the most for finding and actually fixing a bug. Perhaps we should simply start the discussion with the premise that we want to encourage new people to do useful work and draw them into the development community and see where it leads. James