Takeover maintainance of `microaeson`?
It seems like stan is the only (direct) user of microaeson.
https://github.com/kowainik/stan/blob/78e4ae11a2eba1e338900c00951213087506de7a/stan.cabal#L165
I am not using microaeson so I should/want not maintain it.
@tomjaguarpaw Would you be willing to take over microaeson?
It has been very little effort to maintain it so far.
Yes, I can "maintain" it in the sense that I can keep it building with new GHC, so that stan still builds, but I won't be able to do any more than that (and it sounds like you're saying that no more is required).
Great! Indeed, this is all that is required.
I added you on Hackage and invited you to the repo, and asked to pass Stackage maintainership to you: https://github.com/commercialhaskell/stackage/pull/7845/commits/14e11b82548a61714d805ba54bc0b2124ef36a87