Present: Fred, Chiara, Gregory, Mireille, Emmanuel.

It is noted that all the participants will be available at least 2/3 of the time until September 1st. In the current development calendar 3 important deadlines have been (pre-) defined:
 July 1st for the pipeline model
 September 1st for the first useable proto-prototype
 December 1st for the start of T05 processing.

Tasks that were decided for the month of June:

Job handling

 Installation, basic configuration , right managements, and evaluation of the data transfer performance of Condor will be done by Fred. Deadline: July 1st. Once the installation has proven to work efficiently, Fred will begin migrating a subset of the cluster to a more recent version of Gentoo (not before July).

Database Management

 Although MySQL might exhibit some weaknesses with respect to other databases (like PostgreSQL), we go ahead with MySQL. If some serious problem arises we may switch to another DBMS later.
 The priority is set for defining

• a list of entities that should appear in the database (images, catalogs,...)
• a list of mandatory and useful generic fields which should be stored in the database for the different entities. Mireille and Chiara, plus Emmanuel, Fred and Gregory will write down a list, with for each field a tagname, a format (string, double, etc.), a unit, and some explanatory comment. Emmanuel will add a UCD to each field. Deadline: June 20th.
   Fred and Gregory will investigate what would be the most appropriate tool for building the Data Model. Suggestions: DIA, DBDesigner. Deadline: June 20th. Fred, Gregory and Emmanuel will also investigate what would be the best language and framework for interfacing Condor, the database, the metadata and the user interface. Suggestions: Python, Django. Deadline: July 1st. A first simple inheritance scheme shall be more or less in shape for July 1st (this concerns everyone).

Ingestion diagnostic tools

 Those will be discussed / built in July.

Development policy

 A subversion repository shall be set up for July 1st. It will be important to keep all pipeline code in small modules to facilitate maintenance and readability.

Next meeting: June 20th, afternoon