GSICS 2015 GDWG Breakout Session 1 Repository For GSICS Work Code Peter Miu EUMETSAT CMA, CNES, EUMETSAT, ISRO, IMD, JMA, KMA, NASA, NIST, NOAA, ROSHYDROMET, USGS, WMO

GSICS 2015 GDWG Breakout Session Overview and Purpose  Overview As a result of successful collaboration amongst its GSICS members, several tools have been developed to support its activities. Currently the code for these tools resided with the GPRC leading its development. The disadvantage of this is only the GPRC can support future agreed enhancements thus can hamper the progress of GSICS activities.  Purpose of the Presentation The purpose of the presentation is to list these tools and identify a mechanism whereby the enhancement of these tools can be shared amongst the GSICS members. Current GSICS tools are:  GSICS Plotting Tool – written in Java and GWT  NetCDF Checker Tool – written in ?  CF conventions Checker - ?  GSICS Product Generation Framework – written in Java 2

GSICS 2015 GDWG Breakout Session Requirements for a Mechanism for code storage for collaboration  Collaboration Requirements  Code shall be accessible by all GPRC.  A configuration control process is required to: Review updates to ensure updates meet new requirements Track changes and assign versions Package new code into a release for deployment  Note: the implementation of the proposed solution shall be validated by a test plan tracked to these requirements. 3

GSICS 2015 GDWG Breakout Session GDWG Proposed Solution for the Storage of GSICS developed code for Collaboration  Group discussion to proposed the following solution  GPRC to provide a code to members for development.  GCC to be the central repository for GSICS developed Code.  Investigate a “free” tool for code configuration accessible via the Internet by all GSICS members. An example of such a tool is GitHub. 4

GSICS 2015 GDWG Breakout Session GDWG discussion on the Pros and Cons of the presented solutions  S1: GPRC to provide a code to members for development.  Pros: simple,  Cons: Code owner still need to do the work to validate and keep code up to date. Inconsistencies in what versions are provided can be introduced due to manual process. Not practical for large developments due to size of release package provide to developers.  S2: GCC to be the central repository for GSICS developed Code.  Pros: Central Repository.  Cons: Major resources are required in the GCC to support this activity.  S3: Investigate a “free” tool for code configuration.  Pros: this is similar to existing code configuration management using in- house tools like subversioning, CVS (Current Versioning System), etc.  Cons: may not be accessible by all GPRCs (TBC when investigating). May not be supported or available because its free.  Members recommend to invest resources to implementing S3. 5

GSICS 2015 GDWG Breakout Session [ToDo: Task details for the proposed solution to support the lead to implement it]  Resources Needed:  Man Days Effort  HW & SW Procurements  Proposed Time Scale:  Estimate the time taken for implementation.  Deliverables  Priority of the Task [High, Medium, Low]  High – A date is specified  Medium – Before the next Joint Meeting  Low – When a lead is found 6

GSICS 2015 GDWG Breakout Session [ToDo: Summarise the result(s) ; define actions, Working Group member taking lead and/or EP recommendations ]  Actions List:  Recommendation to GSICS Executive Panel  Working Group Member Taking the Lead:  [ CMA | EUMETSAT | IMD | JMA | KMA | NOAA |... | No Lead Identified ] 7

GSICS 2015 GDWG Breakout Session 8 End of Presentation: Thank you for your attention WMO GSICS Portal GSICS Coordination Centre GSICS Product Catalog EUMETSAT’s Data and Management Server