On Mon, 20 Jan 2020, Andreas Tille wrote: > Hi Yaroslav,
> On Mon, Jan 20, 2020 at 10:50:07AM -0500, Yaroslav Halchenko wrote: > > > I think it would be helpful if you would remove the old repository > > > in neurodebian-team. > > shouldn't I (you) just "move" it on salsa under debian-med and then push > > updated branches? so if anyone clones old url, it would get redirected > > to the new one? > > otherwise I would probably need not just to remove it (imagine ppl doing > > debcheckout on stable debian with older urls) but add some README > > describing the move > I admit I have no idea how I can technically move a repository. Since I googled up https://docs.gitlab.com/ee/user/project/settings/ Navigate to your project’s Settings > General > Advanced settings. Under “Transfer project”, choose the namespace you want to transfer the project to. Confirm the transfer by typing the project’s path as instructed. so I should be able to transfer over to debian-med. May be rename yours into nibabel-med-initial so I could do it? > do not have permission to remove from neurodebian-team I doubt that any > move is possible. Thus I simply forked. I agree with you that it would > be better to inform the user directly. I was simply trusting that any > user of the repository would read out the current Vcs-Git fields from > unstable - but I agree with you that its not sure that every user will > do this. > In any case the old repository is now lagging behind the new one in > med-team. That's the worst situation while your suggestion to simply > drop a README there would be the best. Simply removing it and let users > seek in case they do not find anything is somewhere inbetween those two > situations. ;-) let's try moving first? ;) -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
signature.asc
Description: PGP signature
