Date: Mon, 13 Jan 2003 01:19:23 +0100
From: Arador <diegocg@teleline.es>
To: Andrew Walrond <andrew@walrond.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Moderated forum for linux-kernel
Message-Id: <20030113011923.11a7b127.diegocg@teleline.es>
In-Reply-To: <3E21ECC2.1040404@walrond.org>
References: <3E21ECC2.1040404@walrond.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2556
Lines: 55

On Sun, 12 Jan 2003 22:31:30 +0000
Andrew Walrond <andrew@walrond.org> wrote:

<Just my opinion; because as the Hell.surfers troll treads, it's free>

> I can think of advantages;
> 
> Better Thread organisation and seperate topic areas for drivers, 
> patches, ide, ...
> Being able to cheery pick threads of interest, and completely ignore others
> Not having to dump your inbox after a week away just to catch up
> Moderated forums (Off-topic threads policed and deleted)

Not posible. You can't firewall all the mail ; and you can't delete
it after (There's always someone reading a post sec after it's sent to people)

> Read only forums (write for registered/invited members)
marc.theaimsgroup.com

Better thread organization is indeed something good. Linux has like
?&$%=%)=& differents mailing lists. It'd be much nicer to have
kernel-sound@domain.com, kernel-smp@domain.com...
A project could ask a mailing list (even space for web and patches;
if someone plans to support it). Just because one can imagine a
kernel-sound@domain.com list. But whatever the alsa mailing list is;
it's harder to remember. You can forward kernel-sound@domain.com to 
the true malinign list if you want.

Mixing always 2.4 and 2.5 stuff it isn't a good idea either

The everything-in-linux-kernel@vger.kernel.org just doesn't work as well as
one would want. Yes, you've [RFC], [PATCHES], [BENCHMARK] to filter.
But what the hell is the [RFC] mail about? net? vm?

*nobody* reads all the mails (well, there's Alan Cox, but he isn't human)
Some good posts indeed are lost between the noise. We have marc.theaimsgroup.com.
But do you really think it's enought? BK has given us some degree of
organization (you can search who and when touched something, what files were 
touched in the patch, etc). The bugzilla database tries to give us
some degree of organization in the bugs field, just because the 
all-in-linux-kernel@vger.kernel.org approach is a *true hell* in that sense.

What we need to address that? Resources. No, that's not the first thing. We need
that people think that we need it, and we need that people *wants* it. 

After that we need resources: Which is a difficult point. But it's more
important that some of the nice features that have been merged in 2.5 IMHO
(as it's a long-term benefit)

Diego Calleja.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/