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.

Migrate Flyspray issues to Gitlab issues
We want to move all packaging issues to their packaging repository on Gitlab. Flyspray is unmaintained, PHP and just in general not modern and limitting. ### Requirements before moving: * [x] Automatic assigning of packagers to Gitlab repositories for issues (Bugbuddy) @anthraxx * [x] Migration script to convert open Gitlab issues to their packaging repository counterpart @gromit * [x] Cleaning up the bugtracker * [x] Migrate all `arch-install-scripts` issues to https://github.com/archlinux/arch-install-scripts * [x] Migrate all `archweb` issues to https://github.com/archlinux/archweb * [x] Migrate all `namcap` issues to https://gitlab.archlinux.org/pacman/namcap [flyspray issues](https://bugs.archlinux.org/index.php?string=%5Bnamcap%5D&project=1) * [x] Migrate all `mkinitcpio` issues to https://gitlab.archlinux.org/archlinux/mkinitcpio * [x] Migrate all [mirror issues](https://bugs.archlinux.org/index.php?string=mirror&project=1) to ?? * [x] Clean up all old issues for removed packages * [x] ~Clean up really old (non-responsive) issues in general? 5+ years~ * [x] Write a script to automatically comment on selected amount of bugs with a special cleanup user * [x] Bug people to finally fix their broken [upstream url](https://bugs.archlinux.org/index.php?string=upstream+url&project=0) issues. * [x] Organise a bug day for easy issues (we have plenty). * [ ] Resolve all [FTBFS issues](https://bugs.archlinux.org/index.php?string=FTBFS&project=0) * [ ] Resolve all issues reported by [loqs](https://bugs.archlinux.org/index.php?string=&project=0&opened=loqs) as they usually contain high quality patches * [ ] Consider porting bugbot to [Gitlab's issue RSS feed](https://gitlab.archlinux.org/groups/archlinux/packaging/-/issues?format=atom) * [x] Update header bar to mention Gitlab not Bugs * [x] [Archweb](https://github.com/archlinux/archweb/pull/482) * [x] [Wiki](https://gitlab.archlinux.org/archlinux/infrastructure/-/merge_requests/770) * [x] [Security tracker](https://github.com/archlinux/arch-security-tracker/pull/220) ([Arch common style](https://gitlab.archlinux.org/archlinux/archlinux-common-style/-/merge_requests/7)) * [x] [Forums](https://gitlab.archlinux.org/archlinux/infrastructure/-/merge_requests/773) * [x] [AURWeb](https://gitlab.archlinux.org/archlinux/aurweb/-/merge_requests/771) * [x] Reproducible.archlinux.org * [x] man.archlinux.org (https://gitlab.archlinux.org/archlinux/archmanweb/-/merge_requests/41) * [x] Implement an issue template for Gitlab packaging issues. (see [this repo](https://gitlab.archlinux.org/archlinux/packaging/templates)) * [x] write a modification request [on the wiki](https://wiki.archlinux.org/title/ArchWiki_talk:Requests#Modification_requests) and help to fix the docs (done [here](https://wiki.archlinux.org/title/ArchWiki_talk:Requests#Bug_migration)) * [x] write a news item about the change ### Migration plan Do something smart
issue