jurra
commented
6 years ago For those who are not aware, or behind with the migration to gitlab, we would like to give some context: After starting to collaborate with Open Source Ecology partners, the legitimate question about working with open source tools whenever possible came.
- A first reason to move to gitlab is that is open source, and you can even have your own gitlab server whenever you think is necessary. It has the essential basic tools and services that github provides.
- For future integrations, and development with APIs, as well as custom feature developments, it can be more convenient in the long term to work on an open source technology platform.
- We can still have mirror repositories in github, while having issues, and project management taking place in gitlab.
Migration steps overview
1. Contributors/ Community Migration (This will be done by GO!Commons)
1.1. Recreate groups and teams in gitlab 1.2. Invite team members to the new organization
2. Necessary actions by contributors and community members
2.1. Make gitlab account. 2.2. (for those having local repositories) Update local git repo origin from github to gitlab. Here is a video showing how to make this with the command line. This is another video for those using gitkraken 2.2.1. Alternatively you can clone the repo from gitlab, via git command line, or gitkraken (this might be easier for beginners). 2.3. Update issues, comments, whatever development and project management activity in gitlab
3. Website update
3.1. Change url to gitlab 3.2. State in the website that we are migrating to gitlab
4. Mirror gitlab repo in github
We can have redundant repositories in github and gitlab.
But for community management and discussions we, we chose to have them in gitlab.