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.
If people are still active, and want to have their gitlab account mentioned, then we offer that option. That is all.
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.
@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.@WinniMantis is a database frontend.
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?
https://gitlab.com/freepascal.org/mantis_to_gitlab
Just curiosity.@WinniMantis is a database frontend.
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?
https://gitlab.com/freepascal.org/mantis_to_gitlab
Let's suppose you want to move this data to any other solution in the future.
Gitlab allows that as Mantis?
Let's suppose you want to move this data to any other solution in the future.
Gitlab allows that as Mantis?
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
Stonage IT
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
how would you map users of one system to another without having any pre-existing mapping of the users between the two?
This is an arrogant attitude towards the people who do all the work for the move to git.I second that.
If you're so genius then how would you map users of one system to another without having any pre-existing mapping of the users between the two?I guess this excludes email addresses. At least some people have the same email address on GitLab as well as Mantis.
[…] So you need to create 2 issues, one in Mantis that ask the Gitlab account and one in GitLab that ask the Mantis account.You could probably eliminate one issue (at least the Mantis issue) if you simply demand a verifiable and trustworthy GPG-signed message using a key containing the email address [as an uid] as stored in the Mantis bug tracking system. However, trustworthy would imply a working (non-expired) web of trust link to one of the core developer’s key: problem is, are there any?
And after compare if both are the same.
At least some people have the same email address on GitLab as well as Mantis.
This is an arrogant attitude towards the people who do all the work for the move to git.
I was not asked if I like it to move to git.
Now I am told - hop. hop - to move to git.
THAT is arrogant.
how would you map users of one system to another without having any pre-existing mapping of the users between the two?
Mostly all people use the same user name for their Mantis-GitLab-GitHub account.
What about to try to set user name of Mantis for GitLab?
Of course there will be "unknown" users but also "known" users.
This is an arrogant attitude towards the people who do all the work for the move to git.
I was not asked if I like it to move to git.
It's always the project (and its devs) that makes the rules, not the users.
It's always the project (and its devs) that makes the rules, not the users.
Hum not sure to adhere with this but yes, it is (sadly) how lot of things work.
But not always, sometimes it is the users that define the rules (it is the idea of "marketing").
Imho, the users should be the kings.
Fre;D
Sven, I dont like how you threat Winni.Fred, I fail to see what you find objectionable. I presume by "threat" you meant "treat" and not "threaten", but in either case I think you are over-reacting.
Hum not sure to adhere with this but yes, it is (sadly) how lot of things work.If the users pay the developers, then the developers need to (or must) do whatever it takes to earn there money.
But not always, sometimes it is the users that define the rules (it is the idea of "marketing").
Imho, the users should be the kings.
Please ban me after this post if you want.Why?
Now I am told - hop. hop - to move to git.That was in the context of this thread. The subject of it, he himself has made the "Save your mantis login".
Now I am told - hop. hop - to move to git.
What is "container registry images" that would not be exported?Just curiosity.@WinniMantis is a database frontend.
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?
https://gitlab.com/freepascal.org/mantis_to_gitlab
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):
To clarify:I knew about the version control part in GIT systems.
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.
It's always the project (and its devs) that makes the rules, not the users.
Hum not sure to adhere with this but yes, it is (sadly) how lot of things work.
But not always, sometimes it is the users that define the rules (it is the idea of "marketing").
Imho, the users should be the kings.
Sven, I dont like how you treat Winni.
Winni, like other precious users, helps a lot for fpc, and maybe much more than some pretentious "core" developers.
To cloture the thing, it seems to me that "Stoneage IT" was more related about how the announce of conversion to git was done.
Did you remember the episode of fpc-Nabble that decides to stop to update the mailing list without any warning to nobody, even not user-maintainers?
And the effect that it did?
For such a big change, like moving to git, the minimum should have been to prevent every fpc-Mantis members, via a personal email of the change.
There are thousands (?) of mantis accounts. Most of them abandoned. We can't mail them all. And many would not want that.That's a very good point. This move is the right time to do a little "spring cleaning" (get rid of abandoned accounts.)
There are thousands (?) of mantis accounts. Most of them abandoned. We can't mail them all. And many would not want that.
There are thousands (?) of mantis accounts. Most of them abandoned. We can't mail them all. And many would not want that.
Hum, I was thinking, of course, about Mantis accounts that have submitted patch or participated in the bug tracker.
Really more than thousand, I have doubt.
But ok, let's close the subject, you are too perfect to accept advice.
There are thousands (?) of mantis accounts. Most of them abandoned. We can't mail them all. And many would not want that.
Hum, I was thinking, of course, about Mantis accounts that have submitted patch or participated in the bug tracker.
Really more than thousand, I have doubt.
But ok, let's close the subject, you are too perfect to accept advice.
That indeed could have been done.
I don't know if it hadn't been thought off, or if it had been thought that those people will be on the forum/mail-list anyway.
Unfortunately the remaining few days are completely booked out.
Plenty of people from the teams had to coordinate to get a working schedule, and they are all busy sticking to that time table now.
[snip] mantis accounts [snip] most of them abandoned. We can't mail them all. And many would not want that.