Package takeover request: servant-openapi3

Announcements
1

Hello,

I would like to request a takeover of the servant-openapi3 package on Hackage. My username is LaurentRDC.

servant-openapi3’s development has unfortunately languished (original repo). In particular, important work to support new Servant features has remained open for review for a while now.
I have previously offered to help with maintenance last year.

In the meantime, I have been maintaining a fork on behalf of my employer. If this package takeover request is granted, I plan to:

  1. Upload a new version from the fork, which unlocks support for many new Servant features such as MultiVerb;
  2. Contribute servant-openapi3 to the main Servant repo;
  3. Offer to become the maintainer for servant-openapi3 in its new home. I spoke to one of the Servant maintainers at Zurihac and they were open to this arrangement.

Note: I have contacted Hackage admins via e-mail a few weeks ago, but I haven’t received an answer. I’m also using this thread as a ping

12 Likes
2

There’s a fork maintained by @shinzui GitHub - shinzui/servant-openapi-hs · GitHub, btw

3

I wonder whether the reason your request wasn’t granted yet, is, that the library (like swagger2 and openapi3) is getting minimal updates every year. If that is the reason, it would be nice of the Hackage trustees to tell you.

Maybe a fork would be a better option? Then you’d also be able to easily switch to your own fork of openapi3 (which is also in the biocad org).

I remember that Scrive has offered to submit patches for openapi3, maybe a collaboration would be possible.

1 Like
4

I haven’t been concerned with openapi3 since it’s been getting releases (e.g. earlier this year), whereas servant-openapi3’s last release was back in 2022.

You’re right that there have been dependency bound updates via revisions. Is that considered enough? In my discussions with other users of Servant, it seems that servant-openapi3 remains the main barrier to adoption of newer features such as MultiVerb

4 Likes