Take over package `conduit-find`

Announcements
1

I intend to take over conduit-find

The latest release cannot be build with modern GHC.

I pushed a PR resolving issues for GHC 9.10.1

2

Feels like a rash and unresearched announcement. A bit of digging could have showed you that Erik de Castro Lopo is not a maintainer gone passive…
I think that takeover requests should have a bit more substance.

5 Likes
3

Pinging @erikd, here, to increase the likelihood that he is aware of this Topic.

Also, he uploaded conduit-find-0.1.0.4 to Hackage only 7 days ago.

1 Like
4

I have updated the package on Hackage.

I responded to the issue over a week ago:

Hackage repo access request · Issue #18 · erikd/conduit-find · GitHub

Erik

5 Likes
5

Last commit in master was 7 years old and there was PR a few years old.
Recently released version has broken tests.
I give up on attempt to become a maintainer and stick with a copy of conduit-find as an internal cabal package.

6

You are totally free to use it as an internal cabal package, but why not contribute?

7 Likes
7

Please follow the procedure outlined here for package takeovers: Taking over a package - HaskellWiki

As you can see, the first step should always be to contact the maintainer and offer your support, then give them some time to respond.

It’s a bit offputting for maintainers to read about package takeovers on discourse because of a PR that was just opened 2 weeks ago.

For GHC compat patches there also is another process (in case the maintainer is unresponsive): hackage-trustees/policy.md at master · haskell-infra/hackage-trustees · GitHub

6 Likes
8

PR was opened 6 years ago.
Maintainer is not author.
I contacted maintainer and author through email and haven’t received a response yet.

9

Sorry, I never saw your email

However, I did update GH, do a new release on Hackage and responded to the ping here.

4 Likes