public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@sunsite.dk>
To: Robert Love <rml@tech9.net>
Cc: Rik van Riel <riel@conectiva.com.br>,
	"Holzrichter," Bruce <bruce.holzrichter@monster.com>,
	linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: Maintainers master list?
Date: 27 Jun 2001 17:12:18 +0200	[thread overview]
Message-ID: <d3bsnac5yl.fsf@lxplus015.cern.ch> (raw)
In-Reply-To: <Pine.LNX.4.33L.0106261602380.23373-100000@duckman.distro.conectiva> <993588379.763.0.camel@phantasy>
In-Reply-To: Robert Love's message of "26 Jun 2001 16:46:05 -0400"

>>>>> "Robert" == Robert Love <rml@tech9.net> 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

  parent reply	other threads:[~2001-06-27 15:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-26 17:53 Maintainers master list? Holzrichter, Bruce
2001-06-26 19:03 ` Rik van Riel
2001-06-26 20:46   ` Robert Love
2001-06-26 23:10     ` Marc Brekoo
2001-06-27 15:12     ` Jes Sorensen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-27 15:15 Holzrichter, Bruce
2001-06-22 20:48 Holzrichter, Bruce
2001-06-22 14:47 Missing help entries in 2.4.6pre5 Holzrichter, Bruce
2001-06-22 20:00 ` Maintainers master list? Eric S. Raymond
2001-06-22 20:54   ` Rik van Riel
2001-06-22 21:09     ` Eric S. Raymond
2001-06-22 21:19     ` Timur Tabi
2001-06-23 17:39       ` Rob Landley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d3bsnac5yl.fsf@lxplus015.cern.ch \
    --to=jes@sunsite.dk \
    --cc=bruce.holzrichter@monster.com \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    --cc=rml@tech9.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox