[LWN Logo]
From: Peter Samuelson <peter@cadcamlab.org>
Date: Mon, 22 Jan 2001 05:59:33 -0600 (CST)
To: Michael Elizabeth Chastain <chastain@cygnus.com>
Subject: Re: [KBUILD] Request for discussion: move to kbuild@sourceforge.net

> I propose moving the list to a SourceForge project, so that it would
> become kbuild.sourceforge.net.

I don't have any concrete reasons to object, but I confess I have
become a trifle apprehensive over the past year or so with just how
dependent the free software world has become on SourceForge.  There are
just an awful lot of eggs in that basket.  Yes, I know, it's a
developer resource offered with no strings attached, VA just pouring
money into encouraging development of free-- erm, open-source software
so they can sell more hardware, all hail Larry and Eric and friends (oh
hi there Eric), yada yada yada.

Maybe I'm just being inflexible in the face of a new world order.  (I
went through the same thing when Yahoo replaced Archie.)  But it just
concerns me when a single company has the ability to (temporarily)
freeze the development of half the world's open-source software just by
unplugging a roomful of servers, either voluntarily or not (think
"court order").

> (1) Spam.  The current linux-kbuild list is a majordomo list, and
>     it's hard to prevent spam on majordomo.  SourceForge uses Gnu
>     Mailman, which has a better spam filter.

As may be, but the best tactic imho is to maintain a whitelist.  I've
done this with majordomo before, years ago.  Anyone not on the
whitelist gets moderated, and the moderator will add legitimate people
to it.  A light task, but if the current listmaster doesn't want it I
will take it.

> (2) Additional features.  SourceForge gives us a web site and an ftp
>     site in addition to a mailing list.

We've got that at kernel.org already.

> (3) Well-known interface.  People know what SourceForge is and what to
>     expect from it.

Which buys us...?


--  To unsubscribe, send mail to: linux-kbuild-request@torque.net --
--  with the single word "unsubscribe" in the body of the message. --