Before this degenerates into talking about how dotLRN is
"unavailable," let me attempt to clarify things. The issue is not
that community input would slow down the development of
dotLRN. The issue is that someone needs to set a direction for
dotLRN before it can take off. That's what we've been doing.
Finding that direction. Defining the initial high-level goals of
dotLRN and taking a first pass at implementation of this. We are
almost there. These decisions cannot be made by committee. Is
dotLRN a course management system? A learning
management system? An extension to OpenACS that everyone
will want to use? *Those* discussions would have slowed
things down.
And don't downplay the role of CVS and bug tracking. One of the
biggest killers of open-source projects is the inability to provide
feedback. Putting source out there isn't enough. Successful
open-source projects have strong leadership, a well-defined
direction, and a solid process for feedback.
