Move all active git.archlinux.org and Github hosted projects to the Arch Linux namespace
- Archive all projects to software heritage
-
Archive some projects to GitLab (@svenstaro?)
- aif
- abs
- kde-build
- srcpac
- wpa_actiond
- server-misc
- pacbuild
- netcfg
- linux-2.6-ARCH
- klibc-extras
- installer
- initscripts
-
Migrate projects
- kde-build
- archboot
- linux
- namcap
- pacman
- pacman-contrib
- cgit
- netctl > Is still actively maintained [name=Giancarlo Razzolini]
- mkinitcpio-nfs-utils >This still is needed, we need to migrate. I plan to migrate it on the mkinitcpio group I've created on gitlab. [name=Giancarlo Razzolini]
- archboot > Is still actively maintained no? [name=Giancarlo Razzolini]
Original issue:
First order of the day: tar up git.archlinux.org and put that onto vostok as an archive. In addition, we always also have the backups.
This requires the consent of git.archlinux.org repository users and needs some communication.
Migrate from git.archlinux.org:
- archiso
- archlinux-keyring
- archweb-retro
- aurweb
- dbscripts
- devtools
- gluebuddy
- infrastructure
- kde-build
- linux
- namcap
- netctl
- pacman-contrib
- pacman
- pyalpm
- svntogit/community
- svntogit/packages
- tu-bylaws
Migrate from GitHub:
- asp
- archweb
- archlinux-repro
- arch-install-scripts
- arch-security-tracker
- archwiki
- arch-boxes
- archlinux-docker
- rebuilder
- contrib
- signstar
- sandcrawler
- arch-historical-archive
- arch-signoff
- arch-repo-management
- archivetools
- conf.archlinux.org
- mkinitcpio
- archbbs
- asknot-ng
If importing from GitHub, in order to migrate the issues, migrate via GitHub import functionality on GitLab via GitHub API token. Ask @svenstaro about this!
Make sure to always set up push mirroring to GitHub for each respective repo migrated to GitLab.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information