lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RFC] switch to GitLab / gitlab.com


From: Jonas Hahnfeld
Subject: Re: [RFC] switch to GitLab / gitlab.com
Date: Sun, 09 Feb 2020 23:21:01 +0100
User-agent: Evolution 3.34.3

Am Sonntag, den 09.02.2020, 22:50 +0100 schrieb Jonas Hahnfeld:
> Am Freitag, den 07.02.2020, 16:28 +0100 schrieb Federico Bruni:
> > Il giorno ven 7 feb 2020 alle 10:33, Federico Bruni 
> > <
> > address@hidden
> > 
> > > 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...)

Correction: It's only issue #2965 that akismet considers spam. Oh well,
if I read the documentation correctly, migrating into a private
repository and then making it public disables spam checking...
So I'll let my server run the script over night and check the result
tomorrow.

Cheers
Jonas

Attachment: signature.asc
Description: This is a digitally signed message part


reply via email to

[Prev in Thread] Current Thread [Next in Thread]