Present: Jacek (1st half only), BillC, K-T, Douglas, AndyH, Serge, Fabrice

Discussion on code/design documentation
  * We should use MathJax for documenting math in doxygen comments
  * Could try Sphinx, but it's only good for code doc, ala doxygen or 
javadoc, and not for design doc
  * Trac is going away sometime this FY14 (before construction)

Restructuring of Qserv Trac
  * multiple pages on installation need to be made 
consistent/orthoganal/up-to-date. Fabrice and Douglas will work on this 
in conjunction with pushing out a new qserv release.


Modules (see whiteboard diagram sent by K-T)
  * Bill presented module organization for qserv using MVC concepts 
(model = domain-specific logic; controller = program flow)
  * Diagram shows high-level blocks for master + worker
  * Added metadata, metadata API to original diagram, connects to many 
points
  * overall, all agreed it looks good at the high level
  * Homework for Tuesday 9:30am meeting (all):
    * Think about lower levels not discussed during meeting. See 
"Redesign (MVC-based version)" on 
https://dev.lsstcorp.org/trac/wiki/db/Qserv/Components
    * Consider code you have written or will write for Qserv. Where does 
it fit?
    * Do future features/code fit?
    * What's missing? Are there items which will disappear?
    * If your code does not fit in those modules, please add the 
appropriate modules
    * Are there code blocks that spans multiple modules?

Other homework: wishlist, brokenness on Trac

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1