TEP19: migrate to gitlab.com

[cpascual]

Title: Migrate to gitlab.com
TEP: 19
State: DRAFT
Date: 2021-03-08
Drivers: Carlos Pascual-Izarra [email protected]
URL: https://github.com/cpascual/taurus/blob/tep19/doc/source/tep/TEP19.md
License: http://www.jclark.com/xml/copying.txt
Abstract:
Move the project hosting from github.com to gitlab.com

[cpascual]

Hi @taurus-org/integrators , can you please give your opinion about this?

I've already been working on the migration of the CI, and it is ready now, so I propose to migrate taurus to gitlab on next week.

[cpascual]

User action required for mapping gitlab and github accounts

In preparation for the migration of taurus-org to gitlab.com: to properly attribute comments, issues, statistics, etc to the right account in gitlab.com, we need to map the github accounts to gitlab accounts. This requires that the participants of all taurus-org repositories (via commits, comments, issues or pull requests) do one of the two following actions before the 15th of March:

1. log-in at least once on gitlab.com using the Github authentication. Or...
2. ensure that they have an account on gitlab.com that uses the same e-mail address as the Github primary address which must be public in this case.

Notes

• login on gitlab.com using the "log with github" button does not give your Github password to Gitlab.
• If you your Github e-mail address is private, any commits done with the web interface are assigned a dummy email (something like [email protected]) and won't be recognized as coming from your associated gitlab account. So your contribution stats might not be as good as before for your past contributions.
• If a participant account is not mapped at the time of migration, the comment / issue / commit will appear as created by the migrator bot account. In this case a line will be added in the comment, specifying that this comment was "Created by: <>".

Important:

In order to keep track of users who already have mapped their gitlab and github accounts (and avoid spamming them when migrating other tango / taurus / sardana projects) we are using this list of already-mapped accounts (from the tango community). Please add your name to it when your gitlab-github accounts are already mapped.

The following users have participated in taurus-org projects and are not yet in the "already-mapped" list:

@Alexandre31415, @ByRellex, @CorF4, @KrystianKedron, @LJBD, @NexeyaSGara, @SergiiChernov, @Shaid3r, @TNoga0, @TacHuynh, @almarass, @amilan, @askalski85, @avagin, @bilderbuchi, @birkenfeld, @cpt-majkel, @danyan90, @droldan, @dvucko, @evaki1, @felocru, @fscholz-desy, @ghost, @gjover, @hayg25, @jkrueger1, @jordiandreu, @kklmn, @lorcat, @lucabar, @malvarezcells, @mariocaptain, @marouanebj, @mbroseta, @mrosanes, @napppoli, @nfalcoz, @pierreH23, @piertoni, @pinam, @praveenbvarrier, @rhomspuron, @rile993, @sf-migrator-bot, @shysky, @srgblnch, @stanislaw47, @stanislaw55, @tcsgmrt, @teresanunez, @thorstenkracht, @vallsv, @xoffey, @yacremann, @RomainDl, @dscran

[cpascual]

It seems that there is a maximum number of 50 mentions allowed in a comment. I am adding the missing mentions in this comment. Please see #1179 (comment)

@teresanunez, @thorstenkracht, @vallsv, @xoffey, @yacremann, @RomainDl, @dscran

[teresanunez]

Hi Carlos, i agree with the migration, nothing against it.

[cpascual]

Regarding the preparation for gitlab CI, I am using the following repos:

• For taurus: https://gitlab.com/c-p/taurus-tmp-gitlab/-/pipelines
• For taurus_pyqtgraph: https://gitlab.com/c-p/tpg-tmp-gitlab/-/pipelines

[cpascual]

Starting migration now.
Freezing https://github.com/taurus-org/taurus