# Policy regarding taking over Hackage packages

**URL:** <https://discourse.haskell.org/t/policy-regarding-taking-over-hackage-packages/11121>\
**Category:** Uncategorized\
**Created:** [January 3, 2025, 1:50am UTC](https://discourse.haskell.org/t/policy-regarding-taking-over-hackage-packages/11121 "2025-01-03T01:50:42Z")\
**Posts on this page:** 1\
**Showing post:** 41

<div class="post-metadata">

**Author:** ![dyaitskov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/dyaitskov/32/5142_2.png) [@dyaitskov](https://discourse.haskell.org/u/dyaitskov)\
**Post date:** [June 8, 2025, 7:08pm UTC](https://discourse.haskell.org/t/policy-regarding-taking-over-hackage-packages/11121/41 "2025-06-08T19:08:56Z")

</div>

> [@bmillwood](#):
>
> It does not give instructions for what to do if the maintainer can be contacted, doesn’t want to maintain the package, but also doesn’t want anyone to take it over.

I think I encounter an example with conduit-find package.  
I found the package useful and fixed issues, send a PR based on somebody’s else PR a few years old. Last commit in repo was 7 years old. No response until I raised a question about maintenance transfer. Maintainer closed PR without any raising any review issue, but released something as he promised on time. Today I tried to switch from internal cabal package to hackage, but discovered that released package has a few failing tests.

---

_[View the full topic](https://discourse.haskell.org/t/policy-regarding-taking-over-hackage-packages/11121)._