Save your Bugtracker/Mantis login => Reminder: Moving to GitLab

[winni]

Stonage IT

[wp]

This is an arrogant attitude towards the people who do all the work for the move to git.

[Fred vS]

Maybe Stonage is exaggerated , Paleolithic is more realistic.

For example, I want to transfer a unassigned bug created by somebody who left us, how to do?

[Martin_fr]

Ok, I do not know for the original Post what exactly is supposed to be stonage....

But for the "unassigned", there is no problem.
All issues are transferred.  All issues will state who created them on mantis.
Example: https://gitlab.com/freepascal.org/lazarus/sandbox/lazarus-test-4/-/issues/39200

If people are still active, and want to have their gitlab account mentioned, then we offer that option. That is all.

[Fred vS]

Ok, I do not know for the original Post what exactly is supposed to be stonage....

I think Winni was talking about this:
https://forum.lazarus.freepascal.org/index.php/topic,55167.0.html

But for the "unassigned", there is no problem.
All issues are transferred.  All issues will state who created them on mantis.

OK, then you confirm that this unassigned bug will be transferred too?

If yes, perfect (and dont forget to fast assign it, fix it and commit it).

 

[Fred vS]

If people are still active, and want to have their gitlab account mentioned, then we offer that option. That is all.

Ha, ok, understood now.

But, why not simply create a GitLab issue asking to gitlab members to give their Mantis login?
For each answer, you will now the gitlab account.

Forget Mantis, do all via gitlab now.

[Fred vS]

If people are still active, and want to have their gitlab account mentioned, then we offer that option. That is all.

Ha, ok, understood now.

But, why not simply create a GitLab issue asking to gitlab members to give their Mantis login?
For each answer, you will now the gitlab account.

Forget Mantis, do all via gitlab now.

OK, OK, you want to do it via Mantis to be sure that Gitlab users dot usurp a Mantis account.
Yes, indeed, safer and more logical.

Sorry for the noise.

[EDIT] Hum, but Mantis users can also usrp Gilab account, so not so evident.
[EDIT2] So you need to create 2 issues, one in Mantis that ask the Gitlab account and one in GitLab that ask the Mantis account.
And after compare if both are the same.


Fre;D

[Fred vS]

@Winni

I agree with you that using issues (from Mantis or GitLab) is archaic.
And it will need lot of boring work for the maintainer to do manually the transfer for each answer.

Are you thinking to a special program to do the job, via internet and using database?

Fre;D 

[Martin_fr]

@Winni

I agree with you that using issues (from Mantis or GitLab) is archaic.
And it will need lot of boring work for the maintainer to do manually the transfer for each answer.

Are you thinking to a special program to do the job, via internet and using database?

Mantis is a database frontend.

https://gitlab.com/freepascal.org/mantis_to_gitlab

[Fred vS]

Mantis is a database frontend.
https://gitlab.com/freepascal.org/mantis_to_gitlab

Ooops, ok, you are already deep inside.

So, if I understand ok, one of the last problem is to assign Mantis user-name to their possible gitlab acount-name?

Indeed, not evident.
How will you do for the Mantis user-name that do not have a GitLab account?
Will you create new one or centralize to only one?

[valdir.marcos]

@Winni

I agree with you that using issues (from Mantis or GitLab) is archaic.
And it will need lot of boring work for the maintainer to do manually the transfer for each answer.

Are you thinking to a special program to do the job, via internet and using database?

Mantis is a database frontend.

https://gitlab.com/freepascal.org/mantis_to_gitlab

Just curiosity.
Let's suppose you want to move this data to any other solution in the future.
Gitlab allows that as Mantis?

[Fred vS]

@Winni

I agree with you that using issues (from Mantis or GitLab) is archaic.
And it will need lot of boring work for the maintainer to do manually the transfer for each answer.

Are you thinking to a special program to do the job, via internet and using database?

Mantis is a database frontend.

https://gitlab.com/freepascal.org/mantis_to_gitlab

Just curiosity.
Let's suppose you want to move this data to any other solution in the future.
Gitlab allows that as Mantis?

Of course!

For example I have one account in GitLab and one in GitHub.
All my GitHub repositories are mirrored and updated in (nearly) real time in the GitLab repositories.

And vice-versa, you may do the same from GitLab to GitHub.

Also I may login in GitLab with a GitHub account!

[EDIT] In "Settings-General" you have even a option to easy export the project (see picture):

[Martin_fr]

To clarify:

We can't create an gitlab issue in someone else's name. All issues will be reported by the same "fpc" account. All notes will be added by that account.

But, we can add a bit of text that says "this ... was created by mantis-user martin_f @martin_frb
Then if someone adds a new note, and want to refer to a previous, they know who wrote it, and can do "@martin_frb" if they need.

If we do not have the gitlab name, then we just use the mantis name, and there is no @martin_frb

As for assigning: the gitlab issues can be assigned to gitlab accounts during conversion. But here we only need the accounts of those few who have developer status in mantis.

[Martin_fr]

Let's suppose you want to move this data to any other solution in the future.
Gitlab allows that as Mantis?

gitlab has an API, so like we can import now, we can export.

The git data itself, is not gitlab dependent anyway. It's git.
Anyone can clone a git repro and push it elsewhere.

But gitlab has mirroring functions too.

And gitlab is open source. If they ever close, we could also self-host again.
(so by not self hosting, we get access to some of the paid features for free. Gitlab offers this to open source projects)

[avra]

I followed the instructions today, but it seams that deadline was yesterday. Did I really miss the chance?
https://bugs.freepascal.org/view.php?id=39246