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:

• Automatic assigning of packagers to Gitlab repositories for issues (Bugbuddy) @anthraxx
• Migration script to convert open Gitlab issues to their packaging repository counterpart @gromit
• Cleaning up the bugtracker
  • Migrate all arch-install-scripts issues to https://github.com/archlinux/arch-install-scripts
  • Migrate all archweb issues to https://github.com/archlinux/archweb
  • Migrate all namcap issues to https://gitlab.archlinux.org/pacman/namcap flyspray issues
  • Migrate all mkinitcpio issues to https://gitlab.archlinux.org/archlinux/mkinitcpio
  • Migrate all mirror issues to ??
  • Clean up all old issues for removed packages
  • Clean up really old (non-responsive) issues in general? 5+ years
  • Write a script to automatically comment on selected amount of bugs with a special cleanup user
  • Bug people to finally fix their broken upstream url issues.
  • Organise a bug day for easy issues (we have plenty).
    • Resolve all FTBFS issues
    • Resolve all issues reported by loqs as they usually contain high quality patches
• Consider porting bugbot to Gitlab's issue RSS feed
• Update header bar to mention Gitlab not Bugs
  • Archweb
  • Wiki
  • Security tracker (Arch common style)
  • Forums
  • AURWeb
  • Reproducible.archlinux.org
  • man.archlinux.org (archmanweb!41 (merged))
• Implement an issue template for Gitlab packaging issues. (see this repo)
• write a modification request on the wiki and help to fix the docs (done here)
• write a news item about the change

Migration plan

Do something smart