mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rick A. Hohensee" <rickh@Capaccess.org>
To: linux-kernel@vger.kernel.org
Subject: www.kernel.org/hierarchy
Date: Fri, 01 Feb 2002 04:47:30 -0500	[thread overview]
Message-ID: <fc.00858412002c684900858412002c6849.2c684d@Capaccess.org> (raw)

Welcome to www.kernel.org/hierarchy

www.kernel.org/hierarchy/index.html is by Linus. It looks like this...



Send Linux kernel patches to the best fit you can find for what you patch
is about in the web pages starting here...


area                    contact
.......                 ...............         ....................
ext2                    Ted T'so

VFS                     Al the Virile

linux/kernel/           Linus Torvalds
                        Ingo Molnar

not 2.5                 Alan Cox
.                       David Wienhall
.
.
.



        or whatever the map in the mind of the Unit Penguin looks like.
Each area links to another page. Linus sets up the permissions to edit
that page to the people he affiliates with that area. He emails them thier
passwords. All 10-20 of them. This causes them to have analagous authority
over the people and subpages they assign/create. <Submit> buttons are
LAAETTR (left as an excercise...). Down that road lies CVS. The perms
aspect is recursive root on a webserver, also LAAETTR. (that's actually
where a human patch penguin comes in, probably.) Another handy thing would
be for the page to deadman-ping "maintainers" roughly monthly, and trim
the dead ones.

It is also, in contradiction to what the Unit Penguin says, strictly
militaristically hierarchical, as far as perms. It probably won't stay a
true tree, but... But it's just about where to send patches if you're not
a Single-Digit Penguin. The US military is a 5-branch tree. The Romans
used a 10-branch tree. The wonders of the Internet and his manifest genius
seem to enable Torvalds to better the Romans by about 1.5. Caesar gone
hexadecimal. Oh well, politics are unavoidable.

The page itself can be dynamic. It can also become a MAINTAINERS directory
in the sources, at about the same size as MAINTAINERS, with a lynx -dump
or a wget or something in Linus's pack-it-all-up script.

Torvalds talks about his cliq^H^H^H^H main advisors in terms of trust. Who
trusts the trunk of the tree might benefit from better documentation. The
Internet won't eliminate hierarchies. Just documenting them is plenty.

Rick Hohensee


             reply	other threads:[~2002-02-01  9:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-01  9:47 Rick A. Hohensee [this message]
2002-02-06 12:45 ` www.kernel.org/hierarchy David Weinehall
2002-02-06 13:38   ` www.kernel.org/hierarc Rick A. Hohensee

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=fc.00858412002c684900858412002c6849.2c684d@Capaccess.org \
    --to=rickh@capaccess.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®