[CCing freetype-devel] Hello Anurag,
>> Ah, thanks. However, 'freetype' would be even better :-) > > Yep, I hope gitlab support is able to help you (the link 404s > anyway, so I believe we can get it), Alas, I got a negative reply – 'freetype' seems to be taken by a private repository. https://forum.gitlab.com/t/getting-freetype-group/41604/2 so a group called 'freetype2' is what we have to take. > but if I understand correctly we can migrate a project from > freetype2 to freetype easily, so I can migrate issues here first and then move the project ownership to freetype :) OK. > Now, Lilypond issue tracker was migrated from sourceforge, but for > freetype we use savannah and from what I have observed , the issue > numbers are all over the place because Savannah does not provide > project specific issues, so unlike lilypond the issue numbers can't > be preserved. I can however preserve the attached files, date of > creation and all the comments. What's necessary is to preserve a link to the original report – and vice versa, this is, the migration script (or another one for post-cleaning-up) should add comments to the original bug reports with a link to the new gitlab issue. > So, here is how a typical migrated gitlab issue would look like: > > Title: [Savannah: <original-issue-number] <original-title> > > Description: <original-description> > > The original thread, and at last a comment by the bot that contains > all the files attached to the original Savannah issue Looks good. Maybe it makes sense to try everything out with a temporary, different account on gitlab that you can delete if everything works as expected. > > Ohh, btw I got a bot account for us: gitlab.com/freetype-bot :-) Regardless whether we do a move it is a good thing to have a FreeType repository on gitlab as a mirror. Werner
