On Fri, Apr 27, 2007 at 11:15:30AM -0700, John Plocher wrote: > Is it worth spending a few lines on the other end of a project's lifecycle, > that is, how it can morph into something else or disband and die? > > Even placeholders pending future discussion might be worthwhile here, so > that > this document can become the whole project procedure and not just one part > of > an incomplete whole.
I don't object to adding another entry in the dependencies section, but I'd really like to keep our efforts centered on simple, small pieces that we can implement quickly to provide immediate benefit. Attempting to be comprehensive is nice, but at this point I think it's more important to start fixing the most serious problems and building a record of success. The major challenge for the OGB will be avoiding paralysis in the face of overwhelming complexity. -- Keith M Wesolowski "Sir, we're surrounded!" FishWorks "Excellent; we can attack in any direction!"
