TransferringToGitLab


 * STEP 1**: Create an account on GitLab using this link: https://gitlab.com/users/sign_in
 * STEP 2**: Get a colleague with access rights to the EAVISE GitLab to add you as user once your account has been created: https://gitlab.com/groups/EAVISE
 * STEP 3**: Let the fun begin

__//**How to make a new repository?**//__
 * 1) Log into Gitlab
 * 2) Click on groups --> Click on EAVISE
 * 3) Select the projects page --> New Project
 * 4) Give a small meaningfull description and select if you want a public or private repo

Once this is done, all the necessary git commands are there for you to make your local clone and then push the changes online.

This has to be your own choice. Public means that anyone can browse the project through a link that will be placed at the EAVISE webpage, while internal means every logged in gitlab user (including members outside of the EAVISE group) can access your code and use it whenever they prefer it. Private means that only members of the EAVISE group can access your code.
 * __//Private, internal or public?//__**


 * __//Rules of EAVISE online Gitlab//__**
 * 1) If you have a new piece of software make a new repository. This makes it easy to clone that project in the future and continue working on it for any other colleagues.
 * 2) Please add documentation. If you do not plan to add them, then you better not bother create a repository. A good way to start is a README with installation instructions and comments on top of each function discussing the content.
 * 3) Do not remove repositories of colleagues unless they asked you to do so.

To ensure there is some structure in naming repositories/projects, do follow these rules
 * 1) TETRA projects start with IWT_TETRA_{name}
 * 2) Paper projects start with YEAR_{conference_name}_{author_name}
 * 3) Consultancy projects can start with CONSULTANCY_{name_project}
 * 4) Frameworks start with FRAMEWORK_{name_framework}

__//**NEED HELP?**//__ Ask Steven or Wiebe for help or pointers on how to do something!