1. 5g. Repository For GSICS Work Use of github for codes etc
Hyunjong Oh KMA
CMA, CNES, EUMETSAT, ISRO, IMD, JMA, KMA, NASA, NIST, NOAA, ROSHYDROMET, USGS, WMO

2. Overview and Purpose
Overview (From Peter’s presentation, 2015 GSICS meeting)
As a result of successful collaboration amongst its GSICS members, several tools have been developed to support its activities.
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
To share the codes for these tools efficiently with the GPRCs, the usage of version control software was proposed in last GSICS meeting
Purpose of the Presentation
To discuss and define the “How”, “By Whom” and “Until When” of implementing the version controlling system such as github for supporting GPRCs activities.

3. Proposed solution for Implementation of version controlling SW
From Peter’s presentation (2015, Repository for GSICS work)
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. Action Items raised in last meeting on SW for version controlling
<Related Action Items raised in last meeting(2015)>
(GDWG_2015.4h1) all GPRC to report what version controlling software is used and propose possible software to be used in the GSICS activities. (completed in Apr by Jaegwan Kim)
(GCC_15.3) GCC to check the availability to provide administration role on github. (Due date : 29th Feb. 2016)

5. Possible SW for version controlling
Most GPRC said that github is possible and good for us.
Now, shall we go with github ?
Organization
Remarks on github usage
EUMETSAT
Investigate the use of github
NOAA
github can give Better performance
CMA
Possible
JMA
Good for us
KMA
IMD
No Answer

6. Short review on SVN vs. Git
Category
SVN
Git
Type
Centralized
(central repository)
Distributed
(local repository)
Speed
(push/pull)
Slow
Fast
Meaning of Branch
Directories including
Pointer to a certain version
Commit
Only possible on-line
Instantly to the central repository
Ascending version number
Possible even if off-line
Recorded in local repository
Hashed string is used
Sharing works
Automatically shared by commit
Nothing uploaded automatically

7. git vs. github
git : Git is a piece of software that you install locally on your computer which handles 'version control' for you
github : literally a hub for Git repositories. github gives you a bunch more features, like a nice website to allow you to compare changes and administrate user accounts

8. How to & Who will implement it?
Option 1 : use web-based service provided by company
(e.g.
- Pros : well-configured environment
- Cons : for private service, it costs
for public service, it doesn’t cost (within 1 GB storage)
* Codes are to be open
An alternative for github : bitbucket
This service gives you free private repos (unlike github) for up to 5 users, in case you aren't ready to share your work with the world.
However github is the most widely used Git hosting service, and has a broad community of users sharing code and interacting.
To view Comparison of github vs. gitlab vs. bitbucket
Goto

9. How to & Who will implement it?
Option 2 : Construct GDWG’s own github system based on git (open source)
- Pros : private, flexible &expandable storage
- Cons : A lot of efforts, resources for construction & management Needed

10. Example of github service

11. Example of github service : price

12. Issues (1/2) : Implementation
If GDWG goes with github, who will administrate the implementation of it?
What would be the timeline of its implementation?

13. Issues (2/2) : Code licensing
I wanted to point out that code licensing may be a point to discuss when sharing code as it is really becoming an issue at EUM level.
( from Sebastien, 24th Feb. 2016)
=> How to solve it? (open discussion)

14. Estimate the time taken for implementation. Deliverables
[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
From Peter’s presentation (2015, Repository for GSICS work)

15. Recommendation to GSICS Executive Panel
[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 ]

16. End of Presentation: Thank you for your attention
WMO GSICS Portal
GSICS Coordination Centre -
GSICS Product Catalog -
EUMETSAT’s Data and Management Server

17. Appendix SVN vs. Git

18. Appendix : Git Data Transport Commands