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