From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 5 Jul 2001 19:07:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 5 Jul 2001 19:07:22 -0400 Received: from [199.29.68.121] ([199.29.68.121]:21256 "EHLO MailAndNews.com") by vger.kernel.org with ESMTP id ; Thu, 5 Jul 2001 19:07:08 -0400 X-WM-Posted-At: MailAndNews.com; Thu, 5 Jul 01 19:04:45 -0400 Message-ID: <01e901c105a5$a0205220$0100a8c0@chello.nl> From: "Marc Brekoo" To: Subject: [OT] Maintainers master list: new idea Date: Fri, 6 Jul 2001 00:52:07 +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 Hi there, Sorry to bother you with this, but I have some new ideas to keep the MAINTAINERS-file up-to-date. Currently, data in the file aren't up-to-date. I had the following idea: What if we create a website, where maintainers can verify and update their records. Records could also be added, in case a new driver appears, or removed if the code was obsoleted. The nice thing about this is that we can send a mail to the maintainer when he hasn't updated his record for say, 6 months (as suggested in previous mails). This way, patches to the original file could be sent to Linus on a regular basis. MAINTAINERS would be UP TO DATE!! Please give me some suggestions, or mail me for more details. Regards, Marc Brekoo.