PhUSE Semantic Technologies LT 12 Jul 2013

looneyvillebiologistInternet and Web Development

Oct 21, 2013 (3 years and 9 months ago)

52 views

PhUSE Semantic Technologies LT

12 Jul 2013

Status of the Working Groups

Source Control Systems

07 Jun 2013

PhUSE Emerging Technologies

Semantic Technologies WG

Source Control (briefly)

SOURCE CONTROL


Source control analogy


updating a document


Each time you make an update (locally)


Put the current version into a file


Copy the current version


Make the changes


Write your name, the date and time at the top


Remotely


Send the current document to offsite storage


Want to try something out?


Copy the current version into another folder


Update,
etc

SOURCE CONTROL


High level concepts/terms


Repository


a source controlled location (eg folder)


Commit


writing version of a file/s to the local repository


Tag


collect versions of all files under a symbolic name


Branch


Split of repository for development in parallel


Merge


coercing the versions of one branch into another


Clone


copy the repository (including branches)


Checkout


select a particular branch


Pull


get a copy of all the commits in the remote in your local


Push


send all your local commits to the remote

THIS IS FOR DISCUSSION, NO
DECISION HAS BEEN MADE

Repository Design


How do we want this to be laid out?


Currently a folder with files


We have a slightly higher organisational requirement


Dimensions


Standard (SDTM, ADaM, SEND, CDASH, PRM, etc)


Subset (Model, IG)


Version (SDTM Model 1
-
2, SDTM Model 1
-
3)


Mocks what is done in
CDISC2RDF repository
already


The
ontologies

folder will
mapped to a
url

(
eg

http://rdf.cdisc.org/sdtm/
) and
the individual files can be
served from the folder.


Each project has it’s own
folder



Problem: MMS....


sdtm

import
-
files

ontologies

docs

Repository Layout

Source Control Systems

Source Control Systems


We talked about local vs remote


what is remote?


Source control is good, source sharing is even better


having the
code in a central location with multiple contributors is even better


Suppliers have arisen to fill this need


Currently using Google Code (cdisc2rdf)


is this what we want to
continue with?


PhUSE uses Google Code also (for standard programs)


Carried out an evaluation (documented on the wiki)


Considered the following systems:


GitHub


Google Code


BitBucket


Gitorius


Codeplex

Source Control Systems..


Matrix on the wiki.



What is important to us?


Cost


Ability to serve files


Range of authentication options


Ability to download repository


Teams/Team management


‘Nice’ representation of changes


Client ease of use



GitHub

Google Code

Discussion?