SQO-OSS meeting 2007-04-18

Some random notes I 've kept and also some things that I 've though of while writing:

• We should work in 2 week iterations, after which we are going to integrate and sync our work
• We will use UMLGraph for classes and possibly for activity/sequence diagrams
• Metrics that do not output a single value but things such as diagrams or plots are going to be stored on the hard disk and a the file path will be stored in their value field.
• We will need a lightweight job submission/work queue implementation, ie an asynchronous work model will be used
• The presentation layer will use web services as a mechanism to retrieve results.
  • What about job submission? Should we only use local (ie cmd-line) job submission?
  • What about security and authentication?
• What are the requirements for data sources such as mailing lists and bug management databases?

Work on D5

The work on D5 will be carried out in a distributed manner. Each person that has been assigned a piece of D5 is responsible for all phases of designing, from implementing prototypes to asking and managing partners' contribution. Panos will have the final word in all cases.

• Sections in D5 and work assignments
  • Plugin description and infrastructure, sync with equinox (bkarak)
  • Database access and DB schema (panos)
  • Presentation layer (gousiosg)
  • Access to version control systems (and possibly other data sources) (circular)

• dmitro will work on finding references and information on OSGi and giving a presentation to all of us