Design Process Suggestion

This idea has been rolling around in my head for a while... well, 2 weeks anyway.

The Chandler Mailing Lists provide a great avenue for entering ideas into the project.  
However, it can quickly become an information overload situation.  I think something must 
be done to assist everyone.  Here is my suggestion: 

  1) Create a top level list of topics in each list.  The major entries in this top level 
in the DESIGN list would correspond to 

    1a) the major functional areas of Chandler- communications/email, contact manager, 
calendar, todo/project, notepad/outliner, mini-database, document repository
(see my posting at http://lists.osafoundation.org/pipermail/design/2002-
November/001047.html

    1b) Other major dimensions of the application which relate across all or most 
functional areas- like UI, filtering, dates, archiving, etc.

  2) Develop some process and/or timeframe for making working decisions about each topic.

  3) Assign an individual to "moderate" the discussions in each topic area- not that they 
would have to respond to everything that was posted- but instead to create sub-topics to 
pull together multiple threads which relate to the same issue, AND to document decisions 
which have been made, and to facilitate some sort of polling about issues which could 
benefit from that type of feedback.

  4) Look for other opportunities to bring the discussion back into focus when 
necessary... kind of like an eb and flow- expanding ideas, then focussing once issues are 
critical and/or already decided.

  5) Hopefully the wiki will help in managing this.. once it is up and running

I look forward to your feedback, either here or on the list... :)

Dennis Lynch
Lynch Business Advisors

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Process" mailing list
http://lists.osafoundation.org/mailman/listinfo/process