Brainstorm minutes

Hi all 

Here's the meeting minutes of our third brainstorm meeting where we
consolidated the findings of the first two meetings.

Meeting minutes Brainstorm Meeting 2003-2-13

1. Agenda
   * set priorities for TODO
   * assign TODOs

2. Priorities

   Last time we discussed the TODOs resulting from the brainstorm
   day. It turned out that we agreed on the following issues to be
   important:

   a) Deployment

      * we will tag the tree now (this allows us to branch later).

      * we will work towards a stable release.

      * we will separate the CMS and the publications. This allows us
        to stabilize on a stable CMS and still improve the
        publications separately.

      * we will establish stable (CVS) branches post 1.0. This means
        that development will be on HEAD (as it is now) whereas
        bug fixing will be on a stable branch.

   b) Testing

   We do not have time to write exhaustive unit test ATM. We'll write
   them as we do the refactoring, i.e. as we go.

   c) Refactoring

      * we agreed to do the easy things first on an existing
        publication.

      * if we do major changes (such as directory structure changes)
        we cannot afford to keep all publications in sync.

      * do the hard things with a new generic publication

      * do an overview of the existing classes. From that check which
        ones are the most critical.

      * do a road map	  | gregor

3. TODOs

   a) Hard

      We classified the following tasks as hard:
      
      * sitemap
      * disentangle CMS + pubs
      * reduce redundancies between authoring and live
      * URI scheme standard 
      * Page envelope
      * publish images from authoring (depends on URI scheme standard)
      * directory structure
      * menu (depends on URI scheme standard)

      As decided above the easy things are done first which means that
      the hard TODOs are deferred for now.
      
   b) Not that hard

      The following tasks can be done immediatele and help the "new"
      developers to get up to speed with wyona CMS before we tackle
      the hard issues.

				| who will do it
				|
      * content creator		| we will look at the class diagrams
      *	xlink include		| and decide which classes need
      *				| changes and assign  tasks then.
      * revision controller	| michi
      * dead code removal	| egli
      * coding standards	| egli
      * standardize dtml	| gregor
      * Bitflux URI		| michi
      * Cocoon integration	| andreas
      * log4j removal		| egli


-- 
Christian Egli
wyona: research & development
http://www.wyona.com