Admin message

Due to an influx of spam, we have had to require each new account to be manually approved. Please register an account and then write an email to accountsupport@archlinux.org to get it approved. Sorry for the inconvenience.

Git packaging
followup work ------------- Any followup excluding devtools and dbscripts git support: - [x] rewrite pacman package pacman.conf configs for our repo layout (anthraxx) - [x] migrate ftp dir packages to new layout and rewrite pacman databases - [x] import current repo state into new git state repository (need script) - [x] check archweb adjustments (repo names, source location etc) [PLZ HELP] - [ ] adjust security-tracker for new repo names [PLZ HELP] - [ ] check archiver and archive-cleaner repo names [PLZ HELP] - [x] Adjust Wiki articles that mention svn workflows once migrated [PLZ HELP] - [ ] Collect all wiki articles that need adjustments beforehand [PLZ HELP] - [x] asp deprecation (check missing features we want to port over to devtools) - [x] tool for developers to clone git packages into a local checkout (devtools) - [x] flyspry migration (can be done later) Additional Features (WIP stuff we need to think through) -------------------------------------------------------- - Bug assignment communication ------------- - Inform users one/two weeks in advance - Inform forks like ALARM/Asahi one month in advance milestones ---------- - [x] 0: Finish up the whole basic flow - [x] 0.1 devtools - [x] 0.2 dbscripts - [x] 0.3 gitlab - [x] 1: Early sanaty check - [x] 1.1 Show proposal to 1-2 people already involved in the topic - [x] 1.2 Invite to a small Jitsi round to revisit followup-tasks, communication tasks etc - [x] 2: Review & workflow finalization - [x] 2.1 Propose migration with all workflow details to ADP - [x] 2.2 Finish changes after feedback - [x] 2.3 Notify about final migration timeline - [x] 3: Putting everything together - [x] 3.1 Finish up all required followup tasks (archweb, asp etc) - [ ] 3.2 Try a dry run of the migration on a copy of repos.archlinux.org - [x] 3.3 Communicate a rollout/migration window - [x] 4: Rollout - [ ] 4.0 For how long do we block push access to the repositories? - Foxboron: A full weekend or a full week would be reasonable imo - [ ] 4.1 Shutdown package release and svn access - [ ] 4.2 Update packages, state repository etc - [ ] 4.3 Rollout dbscripts with devops (jitsi live session) - [ ] 4.4 Release followup tasks like devtools, archweb, asp etc. - [x] 5: Profit! 🥳
epic