Keyrus Gitlab

Keyrus Gitlab Sign-up

To use the Keyrus Gitlab create one account with your Keyrus email address. Once this is done please contact one of the gitlab administrators so he/she can validate your account. Do not forget to follow the naming conventions for projects given in the platform guidelines.

Keyrus Gitlab Coorporate Platform Guidelines

Please use the following guidelines when creating a new project.

• Projects should have a project code name:

  • Client projects: PROJ-COUNTRY-CLIENT-nameOfTheProject
  • Internal projects: INTERNAL-nameOfTheProject
  • R&D projects: RD-nameOfTheProject
  • Trainings: TRAIN-nameOfTheProject
  • Generic Deployment scripts: DEPLOY-nameOfProject
  • External data and data recuperation scripts: DATA-nameOfProject
  • For any other scripts: SCRIPT-nameOfProject
  • Reusable Libraries and frameworks: LIB-nameOfProject

• In case any project can enter several categories please use the most obvious one (consult with collegues in case of doubt)

• Personal/private projects(not shared with the rest of the comunity) do not have to follow this code names.

• Please add as much tags as possible in the description of the project to facilitate searching a project. Tags can be technologies used, languages, clients, libraries, etc. All tags should be lower case. In case you use multiword tags please use a "-" simbol betweeb the words. Example:

TAGS = #spark #python #r #pyspark #elasticsearch #data-science 

• Add authors and collaborators to the documentation
• All code pushed in to the master branch should work. Non working modifications and code should be done in other branches to keep the master branch working. Any deprecated code should be marked with the tag #deprecated.
• For completely outdated projects that need to be archived please change the name of the project and used the following code name: DEPREC oldProjectCode-nameOftheProject
• Any code pushed to the platform should be documented and should follow the language defined guidelines. If there are not any guidelines for that specific language user must specify in the documentation the guidelines he used.
• Please check the project INTERNAL-CodingConventions for language coding conventions