Group Presentation
Rich Lewis
20/03/14
Group Website
- Most of the content has now been added.
- The template unfortunately hasn't yet been updated to that of the new website.
Members Page
- We will either have the group photo here, or a list of names with pictures next to them - opinions?
- I've tried to add everyone to the list, but if anyone is missing .
New members
- Welcome!
- Log into the website with your new Raven account
- Email me so I can add permissions to your account to edit your page
All members
- Keep filling in your details!
- Once they are done, I'll quickly check through, putting in links
- If you want any help to get everything formatted,
- Add a picture, and make sure you call it your crs_id name (e.g. rl403)
- Any extra suggestions for things that should be added?
Research Pages
- Currently, we only have a single page explaining the high level area the group is involved in.
- Should we allocate people to write up a quick description of the research areas?
News Section
- If anyone has any news, we can put it up on the news section of the website
- e.g. papers published, winning awards, any personal news
- Hopefully, we can have a live update of the news on the front page
Wiki
- The wiki is now live!
- It is behind a Raven wall, so only those with approved Raven accounts can view it.
- Therefore it should be safe for more sensitive group information, for example datasets.
- Anyone that can access it can contribute, so please edit at will to add information on any tools you are using.
- Demonstation
GitHub
The problem
- As a group, we are very multi-disciplined. As such, collaboration within the group should be at the core of what we do.
- Also, as a computational research group, we are very code focused.
- Naturally, we should have a central place where we keep group related code and files, and leave them open for people to correct and improve as well as possible.
- At the moment, there are the shared drives, which work well for large datasets, however keeping track of code is more difficult
- For this, I propose we use GitHub
What is GitHub?
- GitHub is built around Git, a version control tool designed by the same team that created Linux.
What is Git?
- A version control tool: this keeps track of changes made to source code, allowing tracking of a projects progress.
- This allows for quickly tracking where bugs are introduced in the code.
- It also permits multiple people to work on a project without too much hassle.
How does it work?
- The code is stored on a central server as a master copy in what git calls a repository.
- A copy of this can be downloaded (pulled) by somebody to a remote repository on their local machine, edited by them in a helpful way, have these changes added to their local machine's repository (commited) and finally uploaded (pushed) into the master copy.
How is it related to GitHub?
- GitHub is built on top of this system, and provides an much easier to use, online system.
- The git server is hosted remotely on the GitHub servers, so everything is managed from the cloud.
- There is a GUI that integrates the command line tools, and lets you easily track the changes in the files, along with anything anyone else has used.
GitHub.com
- Seach for repositories
- Clone them into your local machine's git
- See what others have commented on your project
- Readmes and wikis
- Show statistics for your coding life!
Demo
Benefits of GitHub
- Helps you work: Keep better track of the development of your code
- Collaboration: Let people easily locate, download and look at your code, and suggest improvements
- Open Source Techniques: Provides an inside look into the development of many of the open-source project we use everyday, and open the doors for helping
- Professional Development: Provides access to another professional 'social' network - a potential employer can look at your GitHub history and be assured that you can code well.