From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 22 Jun 2001 15:57:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 22 Jun 2001 15:56:56 -0400 Received: from snark.tuxedo.org ([207.106.50.26]:57866 "EHLO snark.thyrsus.com") by vger.kernel.org with ESMTP id ; Fri, 22 Jun 2001 15:56:47 -0400 Date: Fri, 22 Jun 2001 16:00:02 -0400 From: "Eric S. Raymond" To: "Holzrichter, Bruce" Cc: David Woodhouse , Russell King , linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net Subject: Maintainers master list? Message-ID: <20010622160002.B16285@thyrsus.com> Reply-To: esr@thyrsus.com Mail-Followup-To: "Eric S. Raymond" , "Holzrichter, Bruce" , David Woodhouse , Russell King , linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net In-Reply-To: <3AB544CBBBE7BF428DA7DBEA1B85C79C9B6BEA@nocmail.ma.tmpw.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AB544CBBBE7BF428DA7DBEA1B85C79C9B6BEA@nocmail.ma.tmpw.net>; from bruce.holzrichter@monster.com on Fri, Jun 22, 2001 at 10:47:03AM -0400 Organization: Eric Conspiracy Secret Labs X-Eric-Conspiracy: There is no conspiracy Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Holzrichter, Bruce : > Now that sounds like a credible idea. Would it be possible to set up a LK > maintainers master list, and host from www.kernel.org or somewhere (Not > knowing anyone at kernel.org, I can't speak for them.) that could be linked > from sites, and have one person or maintainer in charge of keeping track of > who is in charge of maintaining what. This could be a point of contact for > issues like this, and where they can be addressed. It would be a large > administrative project, but could be a point of help for some of us who are > not quite capable of real kernel level hacking yet :o) I think maintaining such a list separately from the kernel sources themselves will just be asking for extra work and for the database to drift out of sync with reality. I have proposed that the MAINTAINERS file should be replaced by metadata markup in the kernel sources themselves, distributed so that it will naturally be kept up to date by the people named in it and mechanically gathered into a generated MAINTAINERS at make dep time. I still think this is the right thing, and was planning to revisit the issue after the 2.5 cutover. But it certainly doesn't have to be me that does it, and between CML2 and the Configure.help file and countering Microsoft's anti-open-source propaganda war I have plenty of other things to worry about. So if you want to take this on, I encourage you to go to it. Want a copy of the metadata schema I wrote up? -- Eric S. Raymond "The power to tax involves the power to destroy;...the power to destroy may defeat and render useless the power to create...." -- Chief Justice John Marshall, 1819. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 22 Jun 2001 16:50:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 22 Jun 2001 16:50:04 -0400 Received: from mailsorter.ma.tmpw.net ([63.112.169.25]:42274 "EHLO mailsorter1.ma.tmpw.net") by vger.kernel.org with ESMTP id ; Fri, 22 Jun 2001 16:49:56 -0400 Message-ID: <3AB544CBBBE7BF428DA7DBEA1B85C79C9B6C02@nocmail.ma.tmpw.net> From: "Holzrichter, Bruce" To: "'esr@thyrsus.com'" Cc: David Woodhouse , Russell King , linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net Subject: RE: Maintainers master list? Date: Fri, 22 Jun 2001 16:48:53 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org >I have proposed that the MAINTAINERS file should be replaced by >metadata markup in the kernel sources themselves, distributed so that >it will naturally be kept up to date by the people named in it and >mechanically gathered into a generated MAINTAINERS at make dep time. >I still think this is the right thing, and was planning to revisit the >issue after the 2.5 cutover. But it certainly doesn't have to be me that >does it, and between CML2 and the Configure.help file and countering >Microsoft's anti-open-source propaganda war I have plenty of other things >to worry about. >So if you want to take this on, I encourage you to go to it. Want a >copy of the metadata schema I wrote up? I would be happy to look at any work that you have already done on this, so feel free to send it along to me. Let's take a look at what you have and where we might be able to take this. B. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 22 Jun 2001 16:55:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 22 Jun 2001 16:55:04 -0400 Received: from perninha.conectiva.com.br ([200.250.58.156]:34057 "HELO perninha.conectiva.com.br") by vger.kernel.org with SMTP id ; Fri, 22 Jun 2001 16:54:50 -0400 Date: Fri, 22 Jun 2001 17:54:20 -0300 (BRST) From: Rik van Riel X-X-Sender: To: "Eric S. Raymond" Cc: "Holzrichter, Bruce" , David Woodhouse , Russell King , , Subject: Re: Maintainers master list? In-Reply-To: <20010622160002.B16285@thyrsus.com> 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 On Fri, 22 Jun 2001, Eric S. Raymond wrote: > I have proposed that the MAINTAINERS file should be replaced by > metadata markup in the kernel sources themselves, distributed so that > it will naturally be kept up to date by the people named in it and > mechanically gathered into a generated MAINTAINERS at make dep time. Look, when somebody stops maintaining something, they'll stop sending patches. When this happens it's only natural that the information you want to use to generate the MAINTAINERS file is also out of date. I fail to see how your idea would solve anything. regards, Rik -- Executive summary of a recent Microsoft press release: "we are concerned about the GNU General Public License (GPL)" http://www.surriel.com/ http://www.conectiva.com/ http://distro.conectiva.com/ From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 22 Jun 2001 17:07:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 22 Jun 2001 17:06:48 -0400 Received: from snark.tuxedo.org ([207.106.50.26]:20235 "EHLO snark.thyrsus.com") by vger.kernel.org with ESMTP id ; Fri, 22 Jun 2001 17:06:38 -0400 Date: Fri, 22 Jun 2001 17:09:45 -0400 From: "Eric S. Raymond" To: Rik van Riel Cc: "Holzrichter, Bruce" , David Woodhouse , Russell King , linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net Subject: Re: Maintainers master list? Message-ID: <20010622170945.A16757@thyrsus.com> Reply-To: esr@thyrsus.com Mail-Followup-To: "Eric S. Raymond" , Rik van Riel , "Holzrichter, Bruce" , David Woodhouse , Russell King , linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net In-Reply-To: <20010622160002.B16285@thyrsus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from riel@conectiva.com.br on Fri, Jun 22, 2001 at 05:54:20PM -0300 Organization: Eric Conspiracy Secret Labs X-Eric-Conspiracy: There is no conspiracy Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Rik van Riel : > Look, when somebody stops maintaining something, they'll > stop sending patches. When this happens it's only natural > that the information you want to use to generate the > MAINTAINERS file is also out of date. True. Distributed metadata won't solve this problem. It won't make the problem any worse, either, so it's a wash on this issue. > I fail to see how your idea would solve anything. What happens now when somebody takes over responsibility for a file or subsystem and the MAINTAINERS file doesn't get patched, either because that person forgets to send a MAINTAINERS update or Linus doesn't happen to take the MAINTAINERS patch for a while? What happens when I look at a file and it's not obvious which subsystem it belongs to? Sure, I can grovel through MAINTAINERS. But how do I know which verbal description matches the function of the cryptically-commented or uncommented code I have in front of me? Distributed-information problems need distributed-information solutions. Locality is your friend. This crowd should know that if anybody should. -- Eric S. Raymond A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. -- Robert A. Heinlein, "Time Enough for Love" From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 22 Jun 2001 17:20:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 22 Jun 2001 17:20:27 -0400 Received: from isimail.interactivesi.com ([207.8.4.3]:7951 "HELO dinero.interactivesi.com") by vger.kernel.org with SMTP id ; Fri, 22 Jun 2001 17:20:07 -0400 Date: Fri, 22 Jun 2001 16:19:57 -0500 From: Timur Tabi To: linux-kernel@vger.kernel.org In-Reply-To: <20010622170945.A16757@thyrsus.com> In-Reply-To: <20010622160002.B16285@thyrsus.com> ; from riel@conectiva.com.br on Fri, Jun 22, 2001 at 05:54:20PM -0300 Subject: Re: Maintainers master list? X-Mailer: The Polarbar Mailer; version=1.19a; build=73 Message-ID: X-AntiVirus: scanned for viruses by AMaViS 0.2.1 (http://amavis.org/) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org ** Reply to message from "Eric S. Raymond" on Fri, 22 Jun 2001 17:09:45 -0400 > What happens now when somebody takes over responsibility for a file > or subsystem and the MAINTAINERS file doesn't get patched, either because > that person forgets to send a MAINTAINERS update or Linus doesn't > happen to take the MAINTAINERS patch for a while? Wouldn't this whole problem go away if the kernel source were stored in a master CVS repository? Maintainers would have write access to their respective code, but only Linus and Alan would have delete access. Everyone else would have read-only access. -- Timur Tabi - ttabi@interactivesi.com Interactive Silicon - http://www.interactivesi.com From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 23 Jun 2001 19:33:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 23 Jun 2001 19:33:38 -0400 Received: from 216-60-128-137.ati.utexas.edu ([216.60.128.137]:50835 "HELO tsunami.webofficenow.com") by vger.kernel.org with SMTP id ; Sat, 23 Jun 2001 19:33:24 -0400 Content-Type: text/plain; charset=US-ASCII From: Rob Landley Reply-To: landley@webofficenow.com To: Timur Tabi , linux-kernel@vger.kernel.org Subject: Re: Maintainers master list? Date: Sat, 23 Jun 2001 13:39:27 -0400 X-Mailer: KMail [version 1.2] In-Reply-To: <20010622160002.B16285@thyrsus.com> In-Reply-To: MIME-Version: 1.0 Message-Id: <01062313392708.00696@localhost.localdomain> Content-Transfer-Encoding: 7BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Friday 22 June 2001 17:19, Timur Tabi wrote: > ** Reply to message from "Eric S. Raymond" on Fri, 22 Jun > 2001 17:09:45 -0400 > > > What happens now when somebody takes over responsibility for a file > > or subsystem and the MAINTAINERS file doesn't get patched, either because > > that person forgets to send a MAINTAINERS update or Linus doesn't > > happen to take the MAINTAINERS patch for a while? > > Wouldn't this whole problem go away if the kernel source were stored in a > master CVS repository? Maintainers would have write access to their > respective code, but only Linus and Alan would have delete access. > Everyone else would have read-only access. This has been suggested about eight thousand times so far, and the answer is "no". I'm fairly certain there's a FAQ entry on this. The reason Linus won't do it is it conflicts with the way he works. He approves patches by reading through them in his mail reader (Pine, I think) and appending the ones he likes to a file. Then when he's done reading mail he pipes the whole file to patch and it goes into his tree. (I'm pondering an idea of sending Linus a perl script that he can use to pipe that file to patch which will split out the individual emails and forward them to an otherwise read-only "patches-linus-has-applied" mailing list. The important part of this idea is it doesn't change the way he works or make him do any extra work at all. And we get the documentation in the emails and a record of what patches got applied when. And this WOULD allow a fairly granular CVS tree to be kept up-to-date by a third party who simply subscribes to the list and automatically feeds the patches into CVS.) But Linus will NOT allow a line of code into his tree which he hasn't personally approved. He may apply patches forwarded to him by maintainers without thoroughly reading them first, but he still approves them and knows when they go in, and makes sure they don't conflict with anything else he's applying or already applied. So in a "Linux-kernel CVS tree", only Linus would have the ability to check stuff in, so he considers it a waste of time and just sends us tarballs instead. The fact Linus does this is a bottleneck, sure. But the fact we've got one guy in charge making decisions and vetoing anything that shouldn't go in is also the main reason we've got a coherent source base. Look at the ongoing fight between Rik and Andrea: even smart people who are generally right can disagree about architectural direction, and if they both make changes without somebody steering Bad Things will result. Rob From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 26 Jun 2001 13:55:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 26 Jun 2001 13:55:45 -0400 Received: from mailsorter.ma.tmpw.net ([63.112.169.25]:49696 "EHLO mailsorter1.ma.tmpw.net") by vger.kernel.org with ESMTP id ; Tue, 26 Jun 2001 13:55:27 -0400 Message-ID: <3AB544CBBBE7BF428DA7DBEA1B85C79C9B6C43@nocmail.ma.tmpw.net> From: "Holzrichter, Bruce" To: "'esr@thyrsus.com'" , Rik van Riel Cc: David Woodhouse , Russell King , linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net Subject: RE: Maintainers master list? Date: Tue, 26 Jun 2001 13:53:50 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org >What happens now when somebody takes over responsibility for a file >or subsystem and the MAINTAINERS file doesn't get patched, either because >that person forgets to send a MAINTAINERS update or Linus doesn't >happen to take the MAINTAINERS patch for a while? >What happens when I look at a file and it's not obvious which >subsystem it belongs to? Sure, I can grovel through MAINTAINERS. But >how do I know which verbal description matches the function of the >cryptically-commented or uncommented code I have in front of me? >Distributed-information problems need distributed-information >solutions. Locality is your friend. This crowd should know that >if anybody should. I'll throw this back out again, and if you all are not interested, drop it if you want. I am looking for places and points to help out where I see issues come up several times, and this is one I have seen occasionally. I am not advocating Eric's proposal for sweeping maintainer's changes, though I respect Eric, and all the developers work. How about starting with a simple MAINTAINERS file maintainer? Someone to actively follow project developers and contact info? Not a small or simple project, I understand, but maybe a central point to send patches to Linus for the Maintainers file? Just my two cents, on a Tuesday :o) B. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 26 Jun 2001 15:03:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 26 Jun 2001 15:03:44 -0400 Received: from perninha.conectiva.com.br ([200.250.58.156]:39429 "HELO perninha.conectiva.com.br") by vger.kernel.org with SMTP id ; Tue, 26 Jun 2001 15:03:29 -0400 Date: Tue, 26 Jun 2001 16:03:05 -0300 (BRST) From: Rik van Riel X-X-Sender: To: "Holzrichter, Bruce" Cc: "'esr@thyrsus.com'" , David Woodhouse , Russell King , , Subject: RE: Maintainers master list? In-Reply-To: <3AB544CBBBE7BF428DA7DBEA1B85C79C9B6C43@nocmail.ma.tmpw.net> 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 On Tue, 26 Jun 2001, Holzrichter, Bruce wrote: > respect Eric, and all the developers work. How about starting > with a simple MAINTAINERS file maintainer? Someone to actively > follow project developers and contact info? That's the best idea I've read so far. Any takers? regards, Rik -- Executive summary of a recent Microsoft press release: "we are concerned about the GNU General Public License (GPL)" http://www.surriel.com/ http://www.conectiva.com/ http://distro.conectiva.com/ From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 26 Jun 2001 16:47:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 26 Jun 2001 16:47:18 -0400 Received: from zero.tech9.net ([209.61.188.187]:36868 "EHLO zero.tech9.net") by vger.kernel.org with ESMTP id ; Tue, 26 Jun 2001 16:47:09 -0400 Subject: RE: Maintainers master list? From: Robert Love To: Rik van Riel Cc: "Holzrichter," Bruce , "'esr@thyrsus.com'" , David Woodhouse , Russell King , linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net In-Reply-To: In-Reply-To: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 26 Jun 2001 16:46:05 -0400 Message-Id: <993588379.763.0.camel@phantasy> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On 26 Jun 2001 16:03:05 -0300, Rik van Riel wrote: > On Tue, 26 Jun 2001, Holzrichter, Bruce wrote: > > > respect Eric, and all the developers work. How about starting > > with a simple MAINTAINERS file maintainer? Someone to actively > > follow project developers and contact info? > > That's the best idea I've read so far. > > Any takers? me. I took issue with the MAINTAINERS file when Eric brought it up originally. However, I don't think drastic measures need to be taken. I have seen a lot of ideas, including Meta-data in the kernel source. What I think we need is the simple solution: find a maintainer for the file, cleanup the current cruft and misinformation, and then actively work to keep the file current. I am willing to be this maintainer. I am not a major "maintainer" in the kernel, but I have and do contribute. Thus I think this is a good task for me. I am willing and wanting to do this. Comments? -- Robert M. Love rml at ufl.edu rml at tech9.net From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 26 Jun 2001 19:33:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 26 Jun 2001 19:33:08 -0400 Received: from MailAndNews.com ([199.29.68.123]:6162 "EHLO MailAndNews.com") by vger.kernel.org with ESMTP id ; Tue, 26 Jun 2001 19:33:03 -0400 X-WM-Posted-At: MailAndNews.com; Tue, 26 Jun 01 19:32:55 -0400 Message-ID: <019701c0fe98$382c8620$c405a33e@Brekoo> Reply-To: "Marc Brekoo" From: "Marc Brekoo" To: "Robert Love" Cc: In-Reply-To: <993588379.763.0.camel@phantasy> Subject: Re: Maintainers master list? Date: Wed, 27 Jun 2001 01:10:59 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 26 Jun 2001, Robert Love wrote: > me. I took issue with the MAINTAINERS file when Eric brought it up > originally. However, I don't think drastic measures need to be taken. > I have seen a lot of ideas, including Meta-data in the kernel source. > > What I think we need is the simple solution: find a maintainer for the > file, cleanup the current cruft and misinformation, and then actively > work to keep the file current. I am willing to be this maintainer. > > I am not a major "maintainer" in the kernel, but I have and do > contribute. Thus I think this is a good task for me. I am willing and > wanting to do this. Comments? I've been waiting for an opportunity like this to join in, so I'd be very happy to help you with this. (This would be my first contribution to linux, please be gentle :-) Regards, Marc Brekoo From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 27 Jun 2001 11:13:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 27 Jun 2001 11:12:55 -0400 Received: from smtp1.cern.ch ([137.138.128.38]:20997 "EHLO smtp1.cern.ch") by vger.kernel.org with ESMTP id ; Wed, 27 Jun 2001 11:12:35 -0400 To: Robert Love Cc: Rik van Riel , "Holzrichter," Bruce , linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net Subject: Re: Maintainers master list? In-Reply-To: <993588379.763.0.camel@phantasy> From: Jes Sorensen Date: 27 Jun 2001 17:12:18 +0200 In-Reply-To: Robert Love's message of "26 Jun 2001 16:46:05 -0400" Message-ID: User-Agent: Gnus/5.070096 (Pterodactyl Gnus v0.96) Emacs/20.4 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 >>>>> "Robert" == Robert Love writes: Robert> me. I took issue with the MAINTAINERS file when Eric brought Robert> it up originally. However, I don't think drastic measures Robert> need to be taken. I have seen a lot of ideas, including Robert> Meta-data in the kernel source. Robert> What I think we need is the simple solution: find a maintainer Robert> for the file, cleanup the current cruft and misinformation, Robert> and then actively work to keep the file current. I am willing Robert> to be this maintainer. A good place to start would be to write a script that checks the email addresses listed in there for bounces say every 6 months (not too often or people will get grumphy). Oh and maybe include the data about the person so he/she can verify it's ok, maybe this way we can get forget this meta-data sillyness. Robert> I am not a major "maintainer" in the kernel, but I have and do Robert> contribute. Thus I think this is a good task for me. I am Robert> willing and wanting to do this. Comments? Well, you'd become the maintainer maintainer. Thats worth a slot in the MAINTAINERS file ;-) Jes From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 27 Jun 2001 11:16:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 27 Jun 2001 11:16:35 -0400 Received: from mailsorter.ma.tmpw.net ([63.112.169.25]:23073 "EHLO mailsorter1.ma.tmpw.net") by vger.kernel.org with ESMTP id ; Wed, 27 Jun 2001 11:16:18 -0400 Message-ID: <3AB544CBBBE7BF428DA7DBEA1B85C79C9B6C50@nocmail.ma.tmpw.net> From: "Holzrichter, Bruce" To: "'Rik van Riel'" , "Holzrichter, Bruce" Cc: "'esr@thyrsus.com'" , David Woodhouse , Russell King , linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net Subject: RE: Maintainers master list? Date: Wed, 27 Jun 2001 11:15:17 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org >On Tue, 26 Jun 2001, Holzrichter, Bruce wrote: >> respect Eric, and all the developers work. How about starting >> with a simple MAINTAINERS file maintainer? Someone to actively >> follow project developers and contact info? >That's the best idea I've read so far. >Any takers? Along with some other people that have replied, I would be happy to help out any way I can. Bruce H.