In reply to @tfc:matrix.org
will you be on the nixcon next week?

https://downloads.haskell.org/~ghc/9.8.3/docs/users_guide/9.8.3-notes.html

It ships Cabal* 3.10.3

In reply to @maralorn:maralorn.de
Sadly not.

In reply to @maralorn:maralorn.de

Hey everyone in this channel,

as you might now we have a group called the Haskell maintainers team, which keeps the lights on around here. This is on the one hand awesome for organisational purposes on the other hand I don’t like it because it creates an arbitrary distinction to some of you other contributors who do equally important work.

Anyway the main tasks of the haskell team is opening the haskell-update PRs, herding hydra, and merging those PRs, which we do in a bi-weekly rotation. Additionally we also do most of the reviews and generally fix stuff, recently we had a bit of capacity loss and by now basically only sterni and me are part of that bi-weekly rotation. This is kinda bad, because it binds too much of our capacity, the frequency of merges went done significantly because we are nearly saturated just with dealing with PRs. It would help us tremendously if we could again widen the team by one or two people who take on a small bit of responsibility, the core of which is to take responsibility of the PR every few weeks for 2 weeks. It is not actually that much work, on average just one hour per week would be great support. This role is a bit of a thankless job, but is essential work for the Haskell community.

So if anyone with a bit of experience of fixing stuff in haskellPackages would be interested in supporting us, please reach out. Also don’t hesitate to ask if you have any questions.

In reply to @sternenseemann:systemli.org
MangoIV: you're so slow :p https://github.com/NixOS/nixpkgs/pull/346720/commits/787c1debc83a0353cb8e6530ad7c191fd5deca3c

In reply to @sternenseemann:systemli.org
MangoIV: you're so slow :p https://github.com/NixOS/nixpkgs/pull/346720/commits/787c1debc83a0353cb8e6530ad7c191fd5deca3c

Solid: it's hard to give a formal requirement, but basically we'd want to be confident that new maintainers are familiar enough with the internals and established conventions so that they can handle a rotation on their own and guide drive by contributors.

You also don't have to take on such a big responsibility to help out, it already helps a lot if people follow maintenance and help out occasionally with fixing regressions or unbreaking packages. The probably best thing to start out with is taking over maintenance for specific haskell packages you are personally familiar with and/or use yourself. You'll be notified automatically when there's something to fix and you'll gain experience working with Haskell in nixpkgs. Bonus is that it benefits yourself because the package won't break in the channels on your watch.

In reply to @mangoiv.:matrix.org
You’re the Champ

In reply to @mangoiv.:matrix.org
Why Not bump hackage again?

In reply to @sternenseemann:systemli.org

Solid: it's hard to give a formal requirement, but basically we'd want to be confident that new maintainers are familiar enough with the internals and established conventions so that they can handle a rotation on their own and guide drive by contributors.

You also don't have to take on such a big responsibility to help out, it already helps a lot if people follow maintenance and help out occasionally with fixing regressions or unbreaking packages. The probably best thing to start out with is taking over maintenance for specific haskell packages you are personally familiar with and/or use yourself. You'll be notified automatically when there's something to fix and you'll gain experience working with Haskell in nixpkgs. Bonus is that it benefits yourself because the package won't break in the channels on your watch.