Gitlab Social Sciences
 | |||||||||
| Development status | Active | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Operating system | any | ||||||||
| Platform | Microsoft Windows, MacOSX, Linux | ||||||||
| License | MIT License | ||||||||
| Website | gitlab.socsci.ru.nl | ||||||||
| |||||||||
The Social Sciences GitLab server offers Git repository management, code reviews, issue tracking, activity feeds and wikis.
Features
With GitLab you can easily manage your projects, synchronize your code between computers, or create wiki-pages for documentation. Whether you write code or a paper, you can review, deploy, or document your project together with others. You can create at least 50 projects, and you can make them private, or share them with your lab members, or even the entire Internet.
Think of GitLab as a "Facebook" around your projects. Similar services include e.g. GitHub.com or GitLab.com (which also runs the GitLab software on their servers). In contrast to these services, GitLab Social Sciences is self-hosted on a server on the Radboud campus. That means we determine our own terms of use; for example, here you can private projects for free - on GitHub, you would have to pay.
Note that there's another self-hosted GitLab service running at the Faculty of Science. Anyone who has a "science login" can also use this service; it's running the same software (just the login page looks different).
Requirements
1. A GitLab account to log in at https://gitlab.socsci.ru.nl:
- Everyone from Radboud University can login (with their U-, S-, E- or F-number).
- External users can ask for an account and then login with their username (switch to the "Standard" tab in the Sign-In page).
2. For more than the most basic tasks, you'll also need to install Git on your computer.
External Users
If you want to allow people without Radboud University account to access and contribute to your GitLab project, you can request a standard user account by sending an email to gitlab@socsci.ru.nl. Please provide the full name of the user, a requested username, and a valid email address, preferably from the university the person is working in.
Note that with an external account, the user has to switch to the "Standard" tab on the Sign-In page. From GitLab's point of view, all accounts have the same rights and restrictions. Once logged in, there are no further differences.
Setup, Configuration and Usage of Git clients
For more advanced tasks, you will need a Git installed on your computer. There is excellent documentation for this available throughout the Internet, for example https://git-scm.com/documentation or https://docs.gitlab.com/ce/gitlab-basics/README.html. It would make little sense to repeat these here. There are many graphical user interfaces available for every major operating system. In addition, many development software packages (including Matlab) are aware of Git repositories and you can set them up to work with GitLab. Note that for most daily tasks, only about 5 Git operations are necessary to know about.
Troubleshooting
For technical issues you can contact gitlab@socsci.ru.nl.
Frequently asked questions
Who has access to gitlab.socsci.ru.nl?
Short answer: Anyone from Radboud University, and some people from other universities.
Longer answer: All employees and students of Radboud University have access (with their U-, S-, E- or F-number). If you log in the first time, a corresponding account will be created. In addition, you can request accounts for people from other universities, for example to collaborate with them on confidential projects. See External Users above.
Who can see my project(s) within GitLab?
Short answer: You decide for each project (if you're the project owner).
Longer answer: GitLab distinguishes read-access within 3 layers, and you can choose for each project individually. Each project can be either
- private: only you and your hand-picked users (and groups) can read it,
- or internal: anyone with a GitLab account can read it,
- or public: anyone on the Internet can read it.
For more information, see https://gitlab.socsci.ru.nl/help/public_access/public_access#visibility-of-projects.
What can/should be stored on GitLab?
Short answer: Scripts, documentation, theses, figures etc. No data please! For data, use https://data.donders.ru.nl/.
Longer answer: Git and GitLab are meant primarily for smaller amounts of data (think Megabytes, not Gigabytes). Most features, like comparing versions, only really make sense with text-based files. Git keeps track of every change you make in its history, and never really forgets. That means Git repositories only grow larger, and even if you "delete" files, you can go back and un-delete them. That's a main feature, you get an "unlimited undo" for all kinds of files (and across different editors and computers).
Keeping an unchangeable history makes it impractical for data - you can't really delete them, comparing versions of them makes little sense. And potentially you later want to make the project available to more people - but maybe without sharing all data. Finally, our server also has limited capacity. For all these reasons, please use https://data.donders.ru.nl/ for your data.