haskellPackages.*: drop some inactive maintainers

[wolfgangwalther]

As announced in #521260 (comment), this PR drops some of the inactive maintainers to reduce the number of packages that we need to consider "maintained" on hackage bumps.

There are certainly more inactive maintainers, I just looked at those who did not react to the current haskell-updates PR and then looked at their respective history. I then removed all of their packages, even when they were only pinged for some of the packages.

We might want to adopt some of the package with either the haskell team or individually.

Pinging the removed maintainers, just to make them aware of the change. I do not intend to wait for their response - changes can always be reversed later, if a point can be made why they should.

@raehik @nomeata @arcz @Gabriella439 @dalpd @poscat0x04 @cdepillabout @thoughtpolice @Anton-Latukha @dschrempf @ivanbrennan @peti

Things done

• Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other READMEs.
• Follows the automation/AI policy.

[nomeata]

Thank for taking care of that!

[dschrempf]

I don't think I am inactive. If there is something to fix, let me know!

Maybe the problem is that I do not follow the large PR with many changes per day. This clutters my inbox.

[dschrempf]

I just read through the comment.

In my opinion, the problem is having a single incredibly long master-thread/issue. I don't have time to read through it, I apologize. If there are more targeted issues, it is much easier for me to react on them. Do you think it is possible to have a more targeted workflow?

[wolfgangwalther]

I don't think I am inactive. If there is something to fix, let me know!

Your fast reaction certainly proves that you can be reached! :)

Currently nothing to be fixed. xmonad / one of its tests was broken earlier in the PR, but is not currently I believe.

My data here is certainly blurry for packages like xmonad, which had multiple maintainers, so there could have been nothing to fix anymore once you get to that notification.

Will change that commit.

In my opinion, the problem is having a single incredibly long master-thread/issue. I don't have time to read through it, I apologize. If there are more targeted issues, it is much easier for me to react on them. Do you think it is possible to have a more targeted workflow?

I do agree with that, absolutely. I tried such a workflow once, it didn't really stick.

However, what should normally happen: You get pinged the first time on the new haskell-updates PR and you will "only" see a big comment listing all the failures with your name attached. This is fairly easy to go through. After that you get all the notifications for that PR only, not before.

So until we figure out a better workflow from our side, here's something that could work for you:

• When you get a notification for the haskell-updates PR, read through to find your name and deal with the issue.
• Unsubscribe from the PR again

This way, you will only get notified again, when we explicitly ping you again for another failure :)

[dschrempf]

Thanks for the heads up. I will do that, it is a great idea!

Is there anything to fix for the other packages I will still maintain after this PR is merged? Happy to fix that now.

And thanks for nursing maintainerships! I really appreciate it.

[raehik]

Apologies, I have been terribly inactive. I don't mind being removed for now. I intend to pick up the slack on my own & my co-maintained packages shortly. (Or, if this PR stays open for a few days, I might have resolved my packages by then.)

[cdepillabout]

Could you leave me with just termonad?

Suggested change

	- uusi
	- uusi
	cdepillabout:
	- termonad

Also I believe I'm marked as a maintainer for some of the other Haskell-related stuff in Nixpkgs (like tests and other things). Feel free to remove me there as well.

Thanks for cleaning stuff like this up!

[wolfgangwalther]

Could you leave me with just termonad?

@cdepillabout done.

Also I believe I'm marked as a maintainer for some of the other Haskell-related stuff in Nixpkgs (like tests and other things). Feel free to remove me there as well.

Removed you from the stack version test. All other pings come through the @NixOS/haskell team of which I am only a regular member, not a maintainer. You can either leave the team yourself, or one of @maralorn or @sternenseemann can remove you there.

[peti]

It's fine to remove me from the list of active maintainers. I usually don't pay much attention to large extensive threads (such as the branch merge PRs).

[wolfgangwalther]

Apologies, I have been terribly inactive. I don't mind being removed for now. I intend to pick up the slack on my own & my co-maintained packages shortly. (Or, if this PR stays open for a few days, I might have resolved my packages by then.)

@raehik I have no intent to punish anyone - your intent to keep maintaining is enough for me. Dropped the commit.

[wolfgangwalther]

Is there anything to fix for the other packages I will still maintain after this PR is merged?

@dschrempf the current status report says all good right now.