In order to move Graphene and the GraphQL Python ecosystem forward I realized is essential to be clear with the community on next steps, so we can move uniformly.
There are few key points that need to happen in the short/mid term, divided into two main sections:
👋 If you have more ideas on how to move the Graphene ecosystem forward, don't hesistate to open a PR
The goal is to improve adoption and sustainability of the project.
- 💎 Add Commercial Support for Graphene - See issue
- Create Patreon page
- Add /support-graphene page in Graphene website
- 📘 Vastly improve documentation - See issue
💰 Apply for Mozilla MOSS sponsorship(not for now)
The goal is to summarize the different improvements that Graphene will need to accomplish for version 3.
In a nushell, Graphene 3 should take the Python 3 integration one step forward while still maintaining compatibility with Python 2.
- 🚀 graphql-core-next GraphQL engine support (almost same API as graphql-core)
- 🔸 GraphQL types from type annotations - See issue
- 📄 Schema creation from SDL (API TBD)
- ✨ Improve connections structure
- 📗 Improve function documentation
- 🔀 Add support for coroutines in Connection, Mutation (abstracting out Promise requirement) - See PR