Wookey writes:
> http://www.armlinux.org and fill in the form. When you have
> finished go on-line and submit it. Alternatively you can fill
> in the form directly on-line.
Yet more splitting, that even I wasn't aware of. ;(
> <[79][EMAIL PROTECTED]> is for
> kernel-related discussions, generally of a technical nature.
> This normally covers the kernel, compilers, related tools and
> new hardware.
Not compilers I'm afraid.
> I agree with Russell's fundamental point that too much splitting is not
> good, but equally I think that linux-arm and linux-arm-kernel are both
> quite busy.
Please define "busy". From the linux-arm* lists combined, the maximum that
I've had (not including my postings) from them in one month (April 2000) is
331 messages in 30 days. Of those, there were 161 messages on the linux-arm
list. That's an total average of 11 messages a day, or 5 per day for
linux-arm. Note that it normally averages 2 to 3 messages per day. This
is "silent" compared with other lists such as "linux-kernel" who have 140+
messages a day, and the "mgetty" list which has about 4 per day. I just
get very amused with people saying that the linux-arm* lists are busy.
I'm not sure that the correct answer is to create parallel lists with the
same subject area, but to have a clearly defined separation between the
lists (eg, linux-arm and linux-arm-kernel). In general, the "right"
splits are on subject matter, not machine type since many problems span
most linux-arm machine types (eg, "how do I build a cross compiler" "does
xxx work on ARM Linux" "building cross libraries" "angel boot loader"
etc) and to fragment the community over these issues can only lead to
poorer information.
For instance, I believe that we have at least a third person announcing
that they will create a site where an x86 ARM cross toolchain will be
available from. However, because it is distributed across a wide number
of hosts, it gets lost, and then someone else comes along and announces
the same thing. Eventually we end up with some people going to one site,
and someone else creating another toolchain.
I have always offered to provide FTP space on the main site - in fact
there has always been a set of cron scripts running which automagically
mail me when stuff gets uploaded into /pub/linux/arm/incoming so that
it can be moved into the appropriate area, but I've yet to see anyone
take up on this.
As it stands, the "community" is becoming very fragmented with little or
even no communication between the parties, especially the 'armlinux.org'
group who appear to keep themselves completely to themselves. This is
BAD, since it will lead to decay of quality, not improvement.
Oh, while we're on the subject of mailing lists, I'd like to table a
motion to close down [EMAIL PROTECTED] and move to
[EMAIL PROTECTED] The reasons for this is:
1. vger.rutgers.edu is rather overloaded now, to the point where
the admins are refusing to setup new mailing lists.
2. Since Southampton Uni has finally closed my mail accounts (yay),
I no longer get the administrivia mail from vger.
3. lists.arm.linux.org.uk is easier to administer, and is seen (I hope)
as the central point for ARM Linux.
4. lists.arm.linux.org.uk has a faster response time than vger.
That's my 2p's worth tonight.
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King [EMAIL PROTECTED] --- ---
| | | | http://www.arm.linux.org.uk/ / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
++ Please use [EMAIL PROTECTED] for ++
++ kernel-related discussions. ++
