Jonas Hahnfeld <hah...@hahnjo.de> writes: > Am Freitag, den 07.02.2020, 16:28 +0100 schrieb Federico Bruni: >> Il giorno ven 7 feb 2020 alle 10:33, Federico Bruni >> < >> f...@inventati.org >> > ha scritto: >> > I guess that the quality of the issue migration might influence the >> > decision. >> >> I forgot I already investigated the SF -> GitLab migration almost 2 >> years ago: >> http://lilypond.1069038.n5.nabble.com/Allura-SourceForge-to-Gitlab-migration-td211549.html >> >> >> Unfortunately, no progress on the import from Allura: >> https://gitlab.com/gitlab-org/gitlab/issues/21747 >> >> >> So a migration script needs to be written. >> I've uploaded today's dump of SF issues here (165MB): >> https://drive.google.com/open?id=1llmnlKMt-LyhWHGcbSCSdSSKjsT0mTff >> >> >> in case someone wants to play with it... > > Thanks for sharing! I put together a simplistic script to create a > proof-of-concept: https://gitlab.com/lilypond-issues/lilypond/issues > > It's only 1137 issues (now my server is blacklisted for spamming...), > but it has some important features mentioned so far: > * It preserves the issue numbers, and additionally has a link to SF. > * It migrates the current description and all comments. > * It copies the attachments and adds links / previews. > * Status, Type, and Priority are migrated as labels. > * The migrated issue is closed when it was closed on SF. > > Obviously I can't post in other person's names, so it has "Originally > reported / posted by" lines at the beginning of every issue and comment > (unless it had already been migrated from Google Code). Another > shortcoming is that I could not reproduce the threaded structure on SF, > so all comments are sorted chronologically. > > Please all take a look and let me know what you think!
For a first pitch certainly impressive. It's nice that the SHA1 ids have become live. -- David Kastrup My replies have a tendency to cause friction. To help mitigating damage, feel free to forward problematic posts to me adding a subject like "timeout 1d" (for a suggested timeout of 1 day) or "offensive".
