[seek] instructions for weekly status reports

[Matt Jones]

Hello,

At the last SEEK meeting in Edinburgh we agreed that we need more 
communication about the current status of work by SEEK participants. 
Consequently, we agreed that all developers, postdocs, and graduate 
students would send a status report on Monday of each week detailing 
major issues.  This is not intended to be a bean-counting exercise, but 
rather a real assessment of progress to help intra-project communication 
and decide priorities.  Some weeks will have no completed tasks, which 
is fine.

This email outlines the details of how to send that brief report.  I 
will summarize the salient parts of the reports on Tuesday of each week 
and send it to the whole SEEK project and post it on the web (or I will 
designate an alternate if I will be gone). (Eventually these reports may 
be submitted through the website, but for now email will suffice).

Reports should be emailed every Monday to:
   seek-reports at ecoinformatics.org

The report email should contain three sections:
   1) Completed tasks/bugs fixed
      -- a list of bugs and tasks completed, with brief summaries
         if that helps clarifies really important points
      -- as this is a weekly report, "None" is a perfectly valid response
         for this section.  Certainly some weeks will have no fully
         completed tasks.
   2) Current Work and Bugs
      -- Brief summary of what you are working on or intend to work
         on this week -- reference bug numbers if at all possible
   3) Significant issues
      -- summary of issues that need wider attention by other
         participants. highlight issues that are important across groups.

This assumes that all participants have provided detailed descriptions 
of their tasks in Bugzilla, which minimizes the amount that they have to 
type -- a really brief summary is adequate if referring to a bugzilla 
bug.  I have included a fictitious example that was derived from stuff 
that Rod sent to me. Please let me know if you have any questions.

Thanks,
Matt
--------------------------------------------------------------------------

Status report
Rod Spears
June 7, 2004

Completed Tasks/ Bugs Fixed:
----------------------------
* Attended the Kepler UI design meeting in Santa Barbara

Current Work and Bugs:
----------------------
* Bug 1594 - Implemented revised Resultset XSD for all 3 platforms
   * The XSD has been changed and the resultset java classes
     have been generated
   * DiGIR Resultset parser has been tested
   * Currently working on the generic transform from the
     Resultset to HTML for display purposes. At this time it
     doesn't look like the an XSLT transform will work due to the
     complexity of the new resultset set definition. I am sure it
     can be done, for now I think a simple DOM parser will be
     easier to maintain considering this will more than likely
     not be used in the final production mode.
* Will start on Bug 1595 - Create Advance Query Builder UI

Significant Issues
------------------
* Globus has moved on to version 3.2, this means it will be
   difficult to get support for 3.0.2
   * They have deprecated the PersisentGridServiceImpl class and
     replaced it with GridServiceImpl
   * The have included a "simple CA" which I was able to generate
     a local certificate and get it working
* When we move to the next version of the Resultset we should
   consider moving to 3.2
-------------------------------------------------------------------


-- 
-------------------------------------------------------------------
Matt Jones                                     jones at nceas.ucsb.edu
http://www.nceas.ucsb.edu/    Fax: 425-920-2439    Ph: 907-789-0496
National Center for Ecological Analysis and Synthesis (NCEAS)
University of California Santa Barbara
Interested in ecological informatics? http://www.ecoinformatics.org
-------------------------------------------------------------------