Skip to contentSkip to conversation

Create a message board?

DISCUSSION raymond jennings 6 participants 6 messages Feb 4, 2004 – Feb 5, 2004

lore
Share & tools
lore
#0 lore raw

Would a message board based forum help to alleviate some of the mailing list traffic by keeping information exchanges thread local (no pun intended)? This way the developers specializing in a certain portion of the kernel aren't swamped with information about something totally irrelevant, thus they can focus on what they know. Example: File system programmers getting messages relating to sound cards.

I am interested in any feedback on this idea.

_________________________________________________________________
Scope out the new MSN Plus Internet Software � optimizes dial-up to the max!
http://join.msn.com/?pgmarket=en-us&page=byoa/plus&ST=1

#1 lore raw
Quoted 8 lines · raymond jennings

Would a message board based forum help to alleviate some of the mailing list traffic by keeping information exchanges thread local (no pun intended)? This way the developers specializing in a certain portion of the kernel aren't swamped with information about something totally irrelevant, thus they can focus on what they know. Example: File system programmers getting messages relating to sound cards.

I am interested in any feedback on this idea.

That's what the bugzilla (http://bugzilla.kernel.org) is supposed to be really.

#2 lore raw
In reply to raymond jennings

On Tue, 03 Feb 2004 17:08:20 -0800 "raymond jennings" <[email protected]> wrote:

| Would a message board based forum help to alleviate some of the mailing list 
| traffic by keeping information exchanges thread local (no pun intended)?  
| This way the developers specializing in a certain portion of the kernel 
| aren't swamped with information about something totally irrelevant, thus 
| they can focus on what they know.  Example:  File system programmers getting 
| messages relating to sound cards.
| 
| I am interested in any feedback on this idea.

Actually I'd prefer fewer places to look instead of more places.

BTW, there is a linux-fsdevel mailing list for filesystem development.

--
~Randy

#3 lore raw
In reply to raymond jennings
Quoted 3 lines · raymond jennings

Would a message board based forum help to alleviate some of the mailing list traffic by keeping information exchanges thread local (no pun intended)? This way the developers specializing in a certain portion of the kernel aren't swamped with information about something totally irrelevant, thus they can focus on what they know. Example: File system programmers getting messages relating to sound cards.

I am interested in any feedback on this idea.

There are other mailing lists for subtopics.

Signature · 3 lines
bill davidsen <[email protected]>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979
#4 lore raw
In reply to raymond jennings
Quoted 2 lines · raymond jennings

Would a message board based forum help to alleviate some of the mailing list traffic

There are lists for other subtopics, btw

Forums are a pita, if you ask me. It's hard to navigate, it's messy to archive and it takes very long time to move around. However there is some code that makes forums and mailinglists transparent.

Forums are bandwidth waste.

Signature · 1 line
b0ef
#5 lore raw
In reply to raymond jennings
Quoted 9 lines · raymond jennings

Would a message board based forum help to alleviate some of the mailing list traffic by keeping information exchanges thread local (no pun intended)? This way the developers specializing in a certain portion of the kernel aren't swamped with information about something totally irrelevant, thus they can focus on what they know. Example: File system programmers getting messages relating to sound cards.

I am interested in any feedback on this idea.

I'd say that's covered pretty much by the FAQ, section 3, point 23.:

23. Why don't you split the list, such as having one each for the development and stable series?

(REG, by "hacksaw") It's true that the lkml is a high traffic list and can be a lot to handle. However, splitting the list wouldn't help, since most developers would just subscribe to both lists. In fact, there would then be extra traffic, because of the number of issues that hit both the development and stable kernels, or even farther back!