Ryan Scott
Count me among the people who are eagerly awaiting this move. If I understood Ben correctly when discussing this idea with him on #ghc, then one of the benefits of having head.hackage on GitLab would be that the head.hackage index would automatically regenerate any time a commit lands. This would make things far more streamlined than the status quo, where the index has to be regenerated by hand.
If head.hackage is migrated over to GitLab, would that change how people are expected to use it? That is, would it still be as simple as copying the repository stanza from [1] into one's cabal.project file? Or would that change with a move to GitLab?
There is the question of what would happen to http://head.hackage.haskell.org/. The CI-generated repository is currently deployed via GitLab Pages to http://ghc.gitlab.haskell.org/head.hackage/; the user's experience otherwise does not change. It would be easy to redirect head.hackage.haskell.org there is that is okay with hvr. Cheers, - Ben