Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 5 Nov 2002 13:37:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 5 Nov 2002 13:37:28 -0500 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:7946 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Tue, 5 Nov 2002 13:37:27 -0500 Date: Tue, 5 Nov 2002 10:43:12 -0800 (PST) From: Linus Torvalds To: Alan Cox cc: linux-kernel@vger.kernel.org, Subject: Re: PATCH: Driver Maintainers In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1379 Lines: 31 On Tue, 5 Nov 2002, Alan Cox wrote: > > One thing the FSF do which is rather sensible is keep a list in the packages > of people who you can pay to fix stuff in them. I asked on Linux-kernel > and got a small initial set of company responses. hopefully more will appear > once its merged. I would really prefer for there to be some kind of explicit requirements for this. Even if we don't endorse the thing, I'd hate to have a bad egg or two (assuming this expands a lot, which I think it might) causing trouble. I'd also like for it to be explicitly only for individuals or small companies ( "less than x people" ), or some other way make sure that the thing is balanced and we set peoples expectations right (both users of the list as well as people who want to be on the list). Also, is the kernel source really the right place for this, considering that many people will have sources that are years old and there is no way to remove potential problematic entries from already-released kernels? In other words, wouldn't it be better to have some nice place on the web and a pointer to that in the kernel sources? Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/