Hi all,
see https://blog.codeberg.org/new-storage-limits-on-codeberg-what-you-need-to-know.html for news on codeberg storage usage - 750 MB for git repos per user/org. This is definitely going to affect guix organization, at least long term (should probably contact Codeberg regarding larger limit as guix itself is hundreds of MB, and there are other repos, so I can imagine the organization is going to be at least close to the limit if not over it), and the users as well. Seems the AGit approach might have to become a requirement at one point in the future for the guix repo - forking might go over the limit. Even now I can imagine there will be users who wouldn't want to take more than half of the storage limit just by forking guix (I am assuming the storage taken on codeberg is same as if you clone and look at .git contents, I haven't verified that though) The storage quota is not in place for now, they don't mention when it will be. I hope I haven't spread any falsehoods here in these not so good news. If I did, sorry and feel free to correct me please! Regards Rutherther 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? > > > 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¹? > > Thoughts? > > Thanks, > Ludo’. > > ¹ Example: > > https://github.com/guix-science/guix-science/commit/9e39ef9a9cc74a01797c4c2fd8d7a97431c463bd
