Sender | Message | Time |
---|---|---|
18 Oct 2024 | ||
sterni | I still don't get what's the best story for handling extensions | 16:21:33 |
sterni | providing the latest Cabal version is sure to get you in trouble with inconsistent deps, right? | 16:21:58 |
19 Oct 2024 | ||
maralorn | 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. | 10:15:44 |
20 Oct 2024 | ||
fredrikr set a profile picture. | 08:09:11 | |
fredrikr changed their display name from fredrikr79 to fredrikr. | 08:09:23 | |
tfc | maralorn: how much work is that roughly in hours per week? | 09:32:50 |
maralorn | In reply to @tfc:matrix.orgIt’s really hard to say. As I wrote, on average one per week seems about right. Biggest problem is, that it is a bit unpredictable when you can do the work. There are a lot of roundtriptimes with hydra and complete blockers because of set rebuilds. Thus this is not something which you can concentrate on for 2 consecutive hours every two weeks on Sunday. It’s more something which you do in small gaps distributed over the week. Of course how much work you invest can also be scaled by you. e.g. you could just not review contributed PRs at all and decide that you personally don’t care about any packages and just set the deadline for other people to fix them. i.e. the core responsibility is not that big and would already help us. | 10:02:03 |
maralorn | The other way around anyone who can do reviews of PRs into haskell-updates would be appreciated. There is actually a fairly simple checklist to go through for a review. And as long as you stay friendly you can’t do much wrong with it. | 10:03:51 |
tfc | hmm, yes, that makes sense. i am interested in nicely working haskell things in nixpkgs, so i will consider joining the effort. | 10:09:36 |
tfc | will you be on the nixcon next week? | 10:09:53 |
maralorn | In reply to @tfc:matrix.orgSadly not. | 10:10:22 |
21 Oct 2024 | ||
MangoIV | 9.8.3 is out 🎉🥳 | 06:39:43 |
MangoIV | https://downloads.haskell.org/~ghc/9.8.3/docs/users_guide/9.8.3-notes.html It ships Cabal* 3.10.3 | 06:40:34 |
MangoIV | In reply to @maralorn:maralorn.de😔 | 09:12:47 |
chreekat | maralorn: how does one even find PRs against haskell-updates? Is there a github-native way to do it, or do you have to get added to some automation somewhere? | 10:08:15 |
chreekat | anyway i'm on board to help out | 10:09:56 |
maralorn | https://github.com/nixos/nixpkgs/pulls?q=is%3Apr+is%3Aopen+head%3Ahaskell-updates | 10:43:21 |
Solid | In reply to @maralorn:maralorn.deI'd love to help out, but I guess an important question is how much experience "a bit" is :) | 10:48:23 |
sterni | MangoIV: you're so slow :p https://github.com/NixOS/nixpkgs/pull/346720/commits/787c1debc83a0353cb8e6530ad7c191fd5deca3c | 10:55:31 |
MangoIV | In reply to @sternenseemann:systemli.orgI was thinking to Write here the second ben annonced in the discourse but I thought this would have been weird. | 10:58:04 |
MangoIV | In reply to @sternenseemann:systemli.orgAbsolutely Lovely. Will this get into 24.11? | 10:58:49 |
MangoIV | You’re the Champ | 10:58:54 |
MangoIV | Any packages that need to be had a look at? | 11:01:41 |
sterni | 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. | 11:02:40 |
sterni | In reply to @mangoiv.:matrix.orgEasily. | 11:02:46 |
sterni | Normally I'm too lazy for a few days when I see the announcement for a new GHC… | 11:03:08 |
sterni | Looks like we either need to accept a broken HLS for a few days or bump hackage again for ghc-lib. Something else I wanted to have a look at, but don't remember right now… | 11:05:34 |
* sterni should really start on the contributing manual section… | 11:07:51 | |
MangoIV | Why Not bump hackage again? | 11:10:11 |
maralorn | In reply to @mangoiv.:matrix.orgBecause it may introduce unrelated breakage and send us into a cat and mouse game. | 12:51:59 |