[saga-rg] sessions at GGF17...

[Andre Merzky]

Hi Folx, 

the sessions scheduled for GGF17 are:

  Wednesday, May 10  1:45 pm -  3:15 pm, room G-408
  Wednesday, May 10  3:45 pm -  5:15 pm, room G-408
  Thursday,  May 11  3:45 pm -  5:15 pm, room G-408
  Friday,    May 12 11:00 am - 12:30 pm, room G-408

The agendas we originally proposed are somewhat out of sync
with the status of the group work, so we would like to
propose the following agendas.  Feedback is appreciated.  We
intent to publish the agenda on the GGF web pages on Sunday
morning.

It is recommended to read both the SAGA Requirement Document
and the SAGA API specification prior to the sessions.  That
is not to scare people away if they don't read the docs, but
efficiency of the meetings will certainly improve with
familarity with the work done in the group so far.

The agendas below also imply that reading of other GGF specs
and drafts (JSDL, BES, DRMAA) would be very beneficial.

Cheers, Andre.


Session 1 (RG):
---------------

  The new SAGA-RG incarnation will discuss administrativa,
  and plan collaboration with other GGF groups (RPC, CPR,
  SAGA-CORE, ...). A short overview presentation of the
  current SAGA API is included for bypassers.

  Agenda:
  - administrativa
  - SAGA overview for the crowd (3 slides), announce 
    other sessions etc
  - evaluate the SAGA REQ document, and derive RG scope out
    of that
  - sync with RPC and CPR, finalize on design teams


Session 2 (RG):
---------------

  The SAGA-RG will flesh out the work of the RPC and CPR
  design teams, and work on synchronization with other GGF
  groups in general.  

  Agenda:
  - plan for real req. document for these design teams
  - work on SAGA-RPC draft
  - work on SAGA-CPR draft (if available)
  - synchronize with (and plan for future)
    new specs in GGF (GFS, BES, JSDL, ...)
    (we should READ them before GGF)
  - considerations about a SAGA look-&-feel spec
    (based on the look-&-feel parts of the core spec)



Session 3 (WG):
---------------

  - discuss parts of API which should be
    moved into the RG look-&-feel document
    (object, task, ...)
  - update on issue list, try to close remaining items
  - define timeline/responsibilities for finalization
    (editing, proof reading, consistency checks)
  - define timeline/editors for cook-book


Session 4 (WG):
---------------

  - continue on open issues if needed
  - define editors and format for language bindings
  - update on implementations
  - discuss bulk optimizations


-- 
"So much time, so little to do..."  -- Garfield