On Mon, 15 Oct 2007, Poul-Henning Kamp wrote:
In message <[EMAIL PROTECTED]>, Robert Watson writes:
Wait please. It was on the ides list before the soc and during the soc.
There where links to an overview and to source files.
This is precisely why I've been concerned about the way things get randomly
put in the ideas list--something I've e-mailed you about many times.
People take it to represent a list of things we want, and frequently, items
on the list are not things that we want. Sometimes they are things that
should be looked at, and perhaps used or perhaps not, but often they are
things apparently hoovered up off a mailing list without thinking about
whether they are actually a good idea, and without talking to developers
who have expertise in the area they relate to.
This is exactly why I stopped maintaining the JKH list long time ago.
I don't object to the idea of an ideas list -- just to one in which we put
things on it that we don't want, and to one that we use to justify committing
something even though we don't want it. The benefits for our SoC students and
other potential new committers are significant if we do it right, but this it
not the first time someone has been burned by virtue of picking up a task on
the ideas list, doing it, and then discovering that the "idea" was not a
simply a "todo" item. "It was on the ideas list" should never be a
justification to commit something, and we need to make sure people looking at
such a list understand that. Vis the recent comment on the OpenBSD BIO
framework idea -- if our key RAID developers don't think it's the right way to
solve a problem, then why is it on the list? We only hurt ourselves, getting
into precisely the current sort of situation, by doing this.
Robert N M Watson
Computer Laboratory
University of Cambridge
_______________________________________________
cvs-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
