mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean <seanlkml@sympatico.ca>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Greg KH <greg@kroah.com>, Adrian Bunk <bunk@stusta.de>,
	Josh Boyer <jwboyer@gmail.com>,
	linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: Adrian Bunk is now taking over the 2.6.16-stable branch
Date: Sun, 20 Aug 2006 18:51:23 -0400	[thread overview]
Message-ID: <BAYC1-PASMTP04048965AE8E3CB2A134C1AE400@CEZ.ICE> (raw)
Message-ID: <20060820185123.e84fafaf.seanlkml@sympatico.ca> (raw)
In-Reply-To: <20060820223046.GB10011@opteron.random>

On Mon, 21 Aug 2006 00:30:46 +0200
Andrea Arcangeli <andrea@suse.de> wrote:

> I think it would be great to have the users choosing their preferred
> maintainer to end the era of maintainers being decided by other
> maintainers like you actually did. A simple website on kernel.org can
> achieve it, where users can registers for voting and the maintainers
> willing to maintain 2.6-stable can registers themself too. That's at
> least less random than the current status if what you said above is
> true and if 2.6.16-stable is meant to reach any critical mass.

There's no need for a vote.  Users already vote for a maintainer when
they decide to use a paticular kernel tree.

No user is forced to follow a particular maintainer.  And anyone can step
up and declare that they are also offering a maintained tree.

And this situation is already self correcting; if no users follow, it's
unlikely that a maintainer will continue doing the required work.  And
if a maintainer doesn't do a satisfactory job, it's very unlikely many
people will choose to use that tree.

Sean

  reply	other threads:[~2006-08-20 22:51 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-03 20:49 Greg KH
2006-08-04  2:43 ` Josh Boyer
2006-08-04  6:26   ` Jan Engelhardt
2006-08-04 23:00   ` Adrian Bunk
2006-08-06  0:46     ` Andrea Arcangeli
2006-08-06  4:52       ` Greg KH
2006-08-20 22:30         ` Andrea Arcangeli
     [not found]           ` <20060820185123.e84fafaf.seanlkml@sympatico.ca>
2006-08-20 22:51             ` Sean [this message]
2006-08-20 23:15             ` Andrea Arcangeli
2006-08-20 23:38               ` Adrian Bunk
2006-08-21  0:05               ` Willy Tarreau
2006-08-21 13:33                 ` Andrea Arcangeli
2006-08-20 23:05           ` Alan Cox
2006-08-20 23:17             ` Andrea Arcangeli
2006-08-21  6:21             ` David Miller
2006-08-21  9:35               ` Andrea Arcangeli
2006-08-22  7:27                 ` Matthias Andree
2006-08-24 13:00                 ` Pavel Machek
2006-08-06  6:17     ` Willy Tarreau
2006-08-07 12:40     ` Pavel Machek
2006-08-07 16:53       ` [stable] " Greg KH
2006-08-07 17:59       ` Adrian Bunk
2006-08-07 23:30         ` Pavel Machek
2006-08-08 19:55           ` Adrian Bunk
2006-08-09 21:45 Chuck Ebbert
2006-08-09 22:00 ` Adrian Bunk
2006-08-09 22:18   ` Greg KH
2006-08-09 22:45     ` Adrian Bunk
2006-08-09 22:53       ` Greg KH
2006-08-09 23:05         ` Chris Wright
2006-08-09 23:20     ` Rene Scharfe
2006-08-10 11:57   ` Stefan Richter
2006-08-12 16:24     ` Adrian Bunk

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=BAYC1-PASMTP04048965AE8E3CB2A134C1AE400@CEZ.ICE \
    --to=seanlkml@sympatico.ca \
    --cc=andrea@suse.de \
    --cc=bunk@stusta.de \
    --cc=greg@kroah.com \
    --cc=jwboyer@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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®