public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miles Lane <miles@megapathdsl.net>
To: Matti Aarnio <matti.aarnio@zmailer.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.5 module development mailing list needed?  [Fwd: Linux Security Module Interface]
Date: Wed, 11 Apr 2001 10:07:27 -0700	[thread overview]
Message-ID: <3AD48F4F.1000800@megapathdsl.net> (raw)
In-Reply-To: <3AD3C1CC.D6167000@megapathdsl.net> <20010411122000.H805@mea-ext.zmailer.org>

Matti Aarnio wrote:

> On Tue, Apr 10, 2001 at 07:30:36PM -0700, Miles Lane wrote:
> 
>> Hi,
>> 
>> 	acpi@phobos.fs.tum.de
>> 	linux-hotplug-devel@lists.sourceforge.net
>> 	linux-power@phobos.fs.tum.de
>> 	linux-security-module@wirex.com
>> 	LKML
>> 
>> Comments?
> 
> 
> 	Proper place to do this discussion is linux-kernel@vger.kernel.org

It sounds good in theory.  In practice, though, almost all of the
design discussions have been occuring in private e-mail.
For example, I have seen none of the messages discussing
the changes planned for the power management stuff in 2.5,
even though these changes will apparantly touch every single
modular driver.  I know for a fact that the changes planned
to enable better implementation of PCMCIA support have
gone on between only a few developers.  Also, from the
announcement from the Security Module folks, I gather that
there discussions haven't been held on LKML and aren't
planned to migrate here.

So, if you really think that all these module-related design
discussions should happen on LKML, we're going to have
to convince a bunch of people to move their discussions
here.  This will not necessarily be easy.  I know that the
reason that many of these discussions occur between only
a few people is that these folks want a decent signal to
noise ratio.  That's why I proposed a "2.5-module-devel"
list.  It would allow people who really care about this stuff
to coordinate their work.


> 	The amount of traffic won't probably be very high in comparison
> 	to the average flow (150-250 emails per day at peak) of L-K.

Well, I'd say it's more like 250-750/day.  :-)


> 	The more you split things around, the less the people who really
> 	need to follow it up can follow it.

Well, there are probably two sets of audiences.  The initial design
teams, who need to collaborate and the modular driver developers.
The driver developers could come into the loop later, if they please.
Although there would be value in their contribution earlier on.


> 	As this is free world, nothing prevents you from going ahead and
> 	creating some linux-25@xyz list somewhere.     Just don't expect
> 	everybody to rush into it.

Well, I'll do that, if a few people say they'll move their design
discussions there and out of private e-mail and other lists.

>> 	Miles
> 
> 
> /Matti Aarnio



  reply	other threads:[~2001-04-11 17:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-11  2:30 2.5 module development mailing list needed? [Fwd: Linux Security Module Interface] Miles Lane
2001-04-11  9:20 ` Matti Aarnio
2001-04-11 17:07   ` Miles Lane [this message]
2001-04-11 20:06     ` Rik van Riel

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=3AD48F4F.1000800@megapathdsl.net \
    --to=miles@megapathdsl.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matti.aarnio@zmailer.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