Sign up here if you plan to attend!
Git involved in organising this and other HUBs!
What and how? Collaborations: Using Git to stay in control. - Fun games with version control.
When? Thu, 23rd January, 18:30
Who? A team of people working at several different life-science organisations within Heidelberg are organising HUB, with your help (just get in touch or add your comments to this page).
|18:30||Help setting up software for those who need it|
|18:45||Welcome, ice-breaker & introduction|
|19:00||Brief practical introduction to version control using git|
|19:20||Little fun game(s) using git|
|20:45||To the pub (Marstall).|
What is git?
Git is a version control system, initially designed to handle source code, but is no longer used only by software developers but also writers and others, to be used to handle almost any type of documents.
"For individual researchers, Git provides a powerful way to track and compare versions, retrace errors, explore new approaches in a structured manner, while maintaining a full audit trail." (Ram,K)
- Git for Scientists: A Tutorial
- A Visual Git Reference
- A visual guide to version control
- Version control for scientific research
- Try Git
Scientific Articles about using git for science
- Git can facilitate greater reproducibility and increased transparency in science
- Improving the reuse of computational models through version control
Please add yourself to the list of participants by editing the list below. You need an account on this wiki to be able to edit the page - if you don't have one, start by signing up for one. Once your account has been confirmed by one of the organisers, you can log in and edit this page by clicking on the 'edit' link at the top of the page.
Also bring your laptop, if you want to participate and indicate which Operating System you're running on your laptop (Windows, Mac, Linux). This will help us to gauge interest and to contact you with more details of the meeting.
If you want to participate in the practical part (which you should), please install git on your laptop; you'll find download links below. In case you have any problems in installing any of the software, just come 30minutes earlier, and we will help you set it up.
- git for Windows: http://www.git-scm.com/download/win
- git for Mac: http://www.git-scm.com/download/mac
SourceTree (a graphical user interface for git):
- Windows/Mac: http://www.sourcetreeapp.com/download/
DiffMerge (a graphical merge tool):
- Windows/Mac: http://www.sourcegear.com/diffmerge/
alternatively: Kdiff3 (another graphical merge tool):
- Windows/Mac: http://kdiff3.sourceforge.net/
List of participants:
- Holger Dinkel, EMBL, (Mac OSX)
- Jon Fuller, HITS, (Mac OS X)
- Matthew Betts, CellNetworks / BioQuant, (Mac OSX)
- Toby Mathieson, Cellzome GSK, (Windows)
- Aidan Budd, EMBL, (Mac OSX)
- Nati Ha,BZH/Uni Heidelberg (Ubuntu 12.10)
- Paul Cross, Avedas AG, (Windows)
- Erich Bornberg, Uni Muenster
- Janos Binder, EMBL, (Mac OSX)
- Emiliano Izquierdo, Bioquant/Uni Heidelberg , (Linux/Ubuntu)
- Ruben Drews, Uni Heidelberg / DKFZ , (Windows or OpenSUSE)
- Jean-Karim Heriche, EMBL, (Mac OSX)
- Agnes Hotz-Wagenblatt, DKFZ, (Windows)
- Juan Mateo, COS Uni Heidelberg, (Mac OSX)
- Jan Kosinski, EMBL
- Chen Chen, DKFZ (Mac OSX 10.9.1)
- Bogdan Costescu, HITS, (Linux/Fedora)
- Laura Rubinat, EMBL (Windows)
- Pierre Khoueiry, EMBL (Mac OSX)
- Christine Gemünd, Cellzome
- Holger Franken, Cellzome (Windows)
- Alvaro Mateos Gil, DKFZ
- Th. Soldatos, MH
- Charles Girardot, EMBL (Mac OSX)
- Bronagh Carey, EMBO (Mac OSX)
- Holger Dinkel
- Jon Fuller
- And you?... get in touch, come to one of the planning meetings, or just get involved!
A list of tasks that need to be done on or before the meeting day. Just sign your name to say that you'll do a task, and the same again when the task is done.
|To arrange before evening||Person responsible||Done|
|List of registered people||Bronagh|
|Short presentation slides||Holger, Jon||Done|
|Drinking Water and Cups?||Matt|
|Print & bring HUB poster||Matt|
|A4 signs in plastic envelopes to help people find the room|
|Create the poster||Bronagh||Done|
|Print and display poster where relevant||
|Advertise on linkedin||Agnes||Done|
|Send reminder email||Holger||Done|
|To do on the evening||Person responsible||Done|
|Open the room||Jon|
|Arrange tables/chairs (in pairs)|
|Hang up signs to the room|
|Setup and welcome attendees|
|Bring extension cables (for all the laptops)|
|Bring tape to fix cables|
|Setup Network/Connectivity||Holger, Jon|
|Help people with setup of their laptops||Holger, Jon, Matt|
|MC/Chair the meeting||Holger, Jon|
|Chair the Standing-on-a-line warmup|
|Tidy and close room||Laura|
Wednesday Jan 08, 2014
Adam, Bronagh, Holger, Katja, Matt
git experts to help at the event: Holger, Jon, Aidan? Grischa? Qianhao?
how many groups / people per group?
I think "having fun using git part two", and then the subtitle - wasn't it something like describe your research in 1000 words, using the most common english words?
If you want to play with git, there is a very good free online tutorial at http://try.github.io/levels/
- having fun
- getting people competent in working together using git
- make people less scared of conflicts and more confident in solving conflicts
Schedule for the evening
- Doing stuff collaboratively:
- upgoer 5 (HUBgoer 5):
- Writing a short paragraph describing one's work or HUB or something else? (using 'git add', 'git commit' and 'git push')
- one group validates the other group's writings (using 'git pull')
- correcting mistakes in text (using 'git merge', solving conflicts)
- Writing some text together
- eg. improving HUB wiki page
- HUB article
- in the end show final article highlighting all contributions?
- upgoer 5 (HUBgoer 5):
Thursday Dec 12, 2013
- Time 14:00, at EMBL
- Informal meeting between Jon & Holger
- Brief outline of things to do:
- Try to repeat/followup on HUB7: using git for collaborative work
- This time, it might be better to run through a "scripted workflow" using 3-6 Participants (really Organizers) to show different features of git/workflow
- using the GUI as well as commandline?
- Use one or more RaspberryPi(s) to create connectivity
- possibly use multiple individual shares for individual groups to avoid problems?
- Use USB sticks as fallback
- Test the setup/script in January (doodle?)
- Provide git cheatsheet