Andreas Abel

Thanks for making a move on this @ysangkok ! Looking at the screenshots, I would like that all quantitative information is communicated via tables, rather than its loud-reading, simply because...

> If anyone would like new screenshots, please let me know. If it is not too much work, it would make sense to update the screenshots in the OP.

I think whitespace checks should be part of the CI, see e.g. https://github.com/agda/agda/blob/3044510c8966a1876951e807f1393bbc3b5e6169/src/github/workflows/whitespace.yml (configuration at https://github.com/agda/agda/blob/3044510c8966a1876951e807f1393bbc3b5e6169/fix-whitespace.yaml).

> What about the whitespace check in CI? Lifted to https://github.com/haskell/cabal/issues/8316

@sol, the relevant call to `cabal` is likely here: https://github.com/haskell/hackage-server/blob/507e8e557e78d0ff33811f5148ab3254c2390d80/exes/BuildClient.hs#L643 Unfortunately, no test log is made available. This would definitively be an improvement. Would prefixing `cabal test` with `cabal exec`...

@sol: An unexpected way to prevent tests being run on Hackage is to upload the documentation yourself (see #1037). I use this script ``` cabal haddock --haddock-for-hackage | tail -1...

If you are moving to a new house, you can keep everything for a while, but after some years, you have to start thinking how to sort out some things...

@kolmodin > we should spend time on promoting good packages I agree, but this is orthogonal to the issue of name squatting. > * Most package names are not taken,...

I see no problem that a e.g. YAML outer syntax has to be complemented by ad hoc expression syntaxes for certain fields (constraints etc.) that transcend YAML. Having an outer...

> What's wrong with using `Cabal` as a library? I had great success with that. You need it anyway for expression parsing. For the Haskell programmer, there is the obstacle...