MPDL Developer Meeting 2008-05-29

MPDL  Restricted Access to MPDL

Planning and estimates

 * As on planning meeting was not clear to every member of dev team about whether estimates and dependencies are clearly taken into consideration while defining plans, the plan for R3 was presented to show that this is taken into consideration.
 * Agreed with all to try to make printout / or inform on changes in the plan, moving dates as the plan is updated. If possible, plan will be communicated in read-friendly form via dev list.
 * Planning/estimates will be maintained as before by Natasa

Re-schedule of developer meetings

 * There will be two developer meetings during the week, made on weekly bases:


 * Tuesdays:
 * Dev Status report 13.00-13.30 (Participants: Development Team)
 * Dev meeting: 13.30-14.15 (Participants: Development Team)
 * Video Conference with FIZ 14.30-16.00 (Participants: Wilhelm Frank, Natasa Bulatovic and some team members, depending on agenda if needed)


 * Thursdays:
 * Progress report 14.00 (max 15-20 mins. Participants: Natasa and some development team members if necessary, Service management and other interested people) (to be checked with Ulla if bi-weekly is fine)
 * AB meeting 15.00-16.00 (60 mins) (Participants: Development Team)--Natasa 12:23, 28 August 2008 (UTC)

Status reports contents

 * Status reports will be short info on current tasks (max 2-3 mins per person in DevTeam)
 * Short info if somebody has problem and can ask for support or other experience
 * More detailed information on problems in tasks should be in JIRA task comments

Dev meetings contents

 * Colab page for Dev meetings agenda discussion will be created (even if single topic)
 * During the current week agenda is updated for the next week meeting
 * All outcomes are to be on the agenda
 * Preparation for topics will be done in a manner that topics are not discussed heavily on the meetings, but in advance. Meetings will serve to inform and fix decisions (if there are any)

LTA working group

 * Natasa asked for people willing to make a small LTA working group to be able to identify requirements and define how it should be implemented.
 * Vlad is interested to work on this issue as well
 * For Vlad and other team members that may raise interest links will be posted to Dev list.