AWOB Meeting 2011-04-20

MPDL,GAVO

Agenda
Continued from the last meeting. Also go over a few use scenarios.


 * Use Scenarios (Main Discussion)
 * User Stories


 * State of the art analysis
 * *Candidate tools and platforms
 * *Candidate functionalities
 * *Relevant projects and collaboration

 Platform clarification 
 * SVN repositories, Maven, development and building environment (Vlad 15 min)
 * JIRA as issue tracker (Natasa, 5-10 mins)

 Next steps discussion, first todo lists for participants 
 * Kick-off meeting in May
 * Agenda

Minutes
Participants  Platform clarification  [[Media:2011-04-20_mpdl_build_and_dev_environment.ppt|Presentation]]
 * Natasa, Vlad, Sveto, Gerard, Jaiwon[minutes]
 * SVN repositories, Maven, development and building environment (Vlad 1hr)
 * Internal project development
 * Overview
 * All the source code are in java  in subversion (like cvs)
 * Maven: development core (like ant)
 * Nexus: store all the build artifacts,eg jar
 * Continuum: check whether the project successfully get built before deploying.
 * repository layout
 * common : reusable modules of MPDL
 * solutions: a repository for each mpdl project.
 * [VLAD/natasa/gerard] please add the discussion here about how to organize codes for AWOB.
 * any code developed for awob -> in MPDL subversion repository
 *  any external libraries -> xxxx
 * Nexus
 * add external libraries not available to maven.
 * JIRA(Natasa, 40mins)
 * To see issues: click 'eye' at upper right hand corner.
 * 'watch': if interested in the issue, send an email whenever there is update in the issue.
 * an issue is 'resolved'(not tested) vs 'closed'(the solution is approved and tested and finished)
 * 'card','feature' are synonyms for 'issue'.
 * Issue Types: (general:Task, software:bug, new feature, improvement.)
 * Notify AWOB mailing list if a new issue is created at JIRA.
 * Do you really want to notify everyone via the AWOM mailinglist when a new Jira ticket is created? Based on my experience with other projects, e.g. during testing times it could happen that one person creates more than 20 tickets a day. That would create a lot of traffic. Therefore I think it would be enough when the person to whom the ticket is assigned, will get a notification. And that is already a standard Jira functionality. --Kristina 10:39, 21 April 2011 (CEST)
 * Yes, we would like to notify upon ticket creation. Already discussed. All other changes accordingly to the asignee and the reporter (according standard workflow for reporters)--Natasa 11:36, 27 April 2011 (CEST)

Use Scenarios (50 mins)
 * Issue is assigned to a single person.
 * Who can close an issue? mainly testers? or issue raiser? still need to discuss.
 * On other MPDL projects, normally only the testers should close the issues, as at the end the testers have the responsibility to decide whether a software version is stable enough to be official released or if there are still some bug fixes needed. --Kristina 10:42, 21 April 2011 (CEST)
 * Discuss user stories on project management File:UsageStories.ppt

Next meeting
 * Apr 29 Friday, 10am. at MPDL
 * continue on user stories
 * Natasa, Vlad, Sveto, Gerard, Jaiwon and whoever interested in