Ludovic Courtès <l...@gnu.org> writes: > Hello Guix, > > Key dates defined in GCD 002 are: > > • By June 5th, all Git repos are migrated to Codeberg; > > • On a flag day between May 21st and June 5th, guix.git is migrated > (meaning that nobody pushes to Savannah after that date). > > How about Sunday May 25th for the guix.git migration? (We can discuss > details on this one separately.) > > The only way I can think of to prevent accidental pushes to guix.git is > by removing commit rights for all of us on Savannah. If we do that, all > other active repositories must have been migrated before (which I think > is doable: it takes a minute to import a repo and those other > repositories are less critical.) > > What do people think? >
Sounds good! > > For now, I’m happy to start migrating the dormant repositories > (bootstrappable, dhcp, gnunet, videos, emacs-guix). A few days later I > can move the rest (guix-artwork, guix-cuirass, maintenance, > guix-consensus-documents). > > Chris, can you migrate data-service, build-coordinator, nar-herder, and > qa-frontpage whenever is convenient for you? > > An open question is the strategy to adopt for migrated repositories > (apart from guix.git); do we: > > 1. remove them entirely from Savannah? > > 2. “fork” them by adding a commit in their Savannah copy that removes > all files and/or amends README to state that the repository has > moved¹? > That would make a ton of dead links to cgit. How about writing on the savannah page and README that the repository is archived with the new url? Or even as a header to all files. > Thoughts? > > Thanks, > Ludo’. > > ¹ Example: > > https://github.com/guix-science/guix-science/commit/9e39ef9a9cc74a01797c4c2fd8d7a97431c463bd Have a nice day, Noé
signature.asc
Description: PGP signature
