> Michael, is this correct for your entry?
The state of Configure/Menuconfig/Xconfig is no longer "Maintained".
"Orphan" is more accurate.
Also you can list http://kbuild.sourceforge.net as our web site.
It has links to the mailing list archives.
The old torque.net address can definitely be retired, but I want to have
a discussion first. Should we have a separate "kbuild-user" list for
kbuild users, or should we have one unified list?
The argument for separate lists:
. It separates out frequently asked questions. This is the way that
gcc and gdb operate their mailing lists, and this strategy works for
them.
. The separate lists could have separate policies for message acceptance.
Right now, kbuild-devel accepts messages from subscribers + a known
set of non-subscribers; other posts are held for review by an admin
(I discard spam and approve everything that's not spam).
. The separate lists woud have separate archives, which is more convenient
for people who want to fix their own problems by reading the archives.
The argument for unified list:
. It forces developers to pay more attention to users. This is the way
that linux-kernel works: it's a list for developer discussion, and it's
also the public list for bug submissions.
I'm in favor of a single unified list. If the developers get so many
bug reports that they can't work on the next version, then they should
improve the software or improve the documentation that goes with it.
In particular, if lots of people experience usablility problems, then
the docs usually need more work.
But I'm interested in other people's opinions before making a decision.
Michael
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/kbuild-devel
