head 1.2; access; symbols; locks http:1.2; strict; comment @# @; 1.2 date 2004.02.09.17.03.01; author MarkusDolensky; state Exp; branches; next 1.1; 1.1 date 2004.02.09.16.51.39; author MarkusDolensky; state Exp; branches; next ; desc @none @ 1.2 log @minutes of telecon, Feb. 5, 04 @ text @AVO Telecon: Feb. 05, 2004 participants: MA Mark Allen TB Thomas Boch SD Sebastien Derriere PR Piero Rosati GR Guy Rixon NW Nicholas Walton chair: PP Paolo Padovani minutes: MD Markus Dolensky, revised by PP excused: PH Paul Harrison TL Tony Linde KN Keith Noddle AR Anita Richards next telecon: Feb. 23, 3 pm GMT New Action Items: MD create .pdf version of extragal. tutorial; release software PP announce to SWG V1.001 together with other news/infos/action NW+MA provide written feedback from SWG tutorial session to PP MD initiate work on "how to use my own data" in the VO context PP continue to collect and sort out input received after the demo; prepare a draft document with prioritized list and submit it for discussion to the AVO team Important software demo events should be announced beforehand to twiki@@euro-vo.org in order to optimize the 'success rate'. Level of AVO prototype support: ESO forwards incoming requests to relevant parties. Users should receive notification within a working day and an indication whether there will be further communication in that matter or there isn't more to say than in the original response. If one party is unavaialble for several working days a notification needs to be sent to - or better - name a replacement. Agenda: - "after-the-demo" debriefing: * comments, impressions, rumours from SWG and others * comments, impressions from AVO team * report on CDS debriefing - various ways to collect SWG's feedback: * notes on the feedback session: done by Mark (I have circulated them last week: any comments?) * sub-group reports: we have the ppt files, I'll try to distill the common features and circulate those * tutors' feedback action items on us: - summary of feedback (to be circulated to the SWG ASAP), with our priorities, ranked also in terms of feasibility, on: * tools * short term goals + next demo * longer term (Science Reference Mission) - "How to publish my data in the VO" page; I promised this at the meeting, it would be good to have this ready on a short time scale as well @ 1.1 log @minutes of telecon, Feb. 5, 04 @ text @a35 1 MD clarify expected level of support for AVO prototype more explicit d43 8 @