# Fork \`memory\`? As \`memoria\`?

**URL:** <https://discourse.haskell.org/t/fork-memory-as-memoria/11777>\
**Category:** Learn\
**Created:** [April 5, 2025, 7:01pm UTC](https://discourse.haskell.org/t/fork-memory-as-memoria/11777 "2025-04-05T19:01:15Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![atravers](https://avatars.discourse-cdn.com/v4/letter/a/45deac/32.png) [@atravers](https://discourse.haskell.org/u/atravers)\
**Post date:** [June 8, 2025, 3:27pm UTC](https://discourse.haskell.org/t/fork-memory-as-memoria/11777/15 "2025-06-08T15:27:44Z")

</div>

Apparently not, without a visible (and potentially breaking) change of policy:

[Policy regarding taking over Hackage packages](https://discourse.haskell.org/t/policy-regarding-taking-over-hackage-packages/11121)

> [@](#):
>
> 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.
> 
> With the `cryptonite` family of packages in particular [which includes `memory`], the original author has [taken the position](https://github.com/commercialhaskell/stackage/issues/7336) that:
> 
> - people may have used the package because they trusted the author,
> - the author, being no longer involved, can’t evaluate any new maintainer to be a suitable recipient of that trust,
> - therefore, no ownership transfer maintains / deserves the trust that the package may have originally carried.

(thanks to those who pointed out this connection I missed). [Hence my prior post](https://discourse.haskell.org/t/fork-memory-as-memoria/11777/10). But the lack of maintenance of `basement` (as noted by **Bodigrim** ) now seems to be the bigger _“can o’worms”_…

---

_[View the full topic](https://discourse.haskell.org/t/fork-memory-as-memoria/11777)._