apollographql
Call for maintainers: apollo-server-koa
As described in the roadmap, Apollo Server 4 will shift from the model of "9 web framework integrations maintained by a team who only uses one of them and nope, you can't create your own" to "a stable web framework integration API that anyone can use for their favorite web framework".
As part of this, the Apollo Server core team is no longer planning to maintain apollo-server-koa. We think users of Koa are best served if their framework integration is maintained by a team of people who use Koa every day.
This is where you come in! Do you love Koa? Do you use it with Apollo Server? Would you like to be part of a team of community members who maintain apollo-server-koa?
If so, chime in below! We'd love to find a group of people who will maintain the Apollo Server 4 version of apollo-server-koa, and to help us maintain the section of the Apollo Server docs that shows how to use Apollo Server with Koa.
We expect that maintaining this package will be more straightforward than maintaining an Apollo Server integration today, because its only responsibility will be translating Koa's HTTP request and response objects to the formats used by Apollo Server's new API.
At the time that this issue is opened, we are actively looking for interested collaborators; however, the API you'll be implementing isn't yet ready. We can use this issue to get a team together who can get started at some point between an initial alpha release of the new @apollo/server package and the final v4.0.0 release.
If you're reading this, we're ready for you! We feel that Apollo Server 4's API is in a good place for integration authors to start building against. We've written a step-by-step guide and built out a couple of working examples.
If you're here and you're interested, please ping us here on the issue and let us know! I'm happy to answer any questions and help however I'm able.
-- Trevor
