From: "Eric S. Raymond" <esr@thyrsus.com>
To: "Holzrichter, Bruce" <bruce.holzrichter@monster.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Russell King <rmk@arm.linux.org.uk>,
linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Maintainers master list?
Date: Fri, 22 Jun 2001 16:00:02 -0400 [thread overview]
Message-ID: <20010622160002.B16285@thyrsus.com> (raw)
In-Reply-To: <3AB544CBBBE7BF428DA7DBEA1B85C79C9B6BEA@nocmail.ma.tmpw.net>
In-Reply-To: <3AB544CBBBE7BF428DA7DBEA1B85C79C9B6BEA@nocmail.ma.tmpw.net>; from bruce.holzrichter@monster.com on Fri, Jun 22, 2001 at 10:47:03AM -0400
Holzrichter, Bruce <bruce.holzrichter@monster.com>:
> 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?
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
"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.
next prev parent reply other threads:[~2001-06-22 19:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-22 14:47 Missing help entries in 2.4.6pre5 Holzrichter, Bruce
2001-06-22 20:00 ` Eric S. Raymond [this message]
2001-06-22 20:54 ` Maintainers master list? 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
-- strict thread matches above, loose matches on Subject: below --
2001-06-22 20:48 Holzrichter, Bruce
2001-06-26 17:53 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
2001-06-27 15:15 Holzrichter, Bruce
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=20010622160002.B16285@thyrsus.com \
--to=esr@thyrsus.com \
--cc=bruce.holzrichter@monster.com \
--cc=dwmw2@infradead.org \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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