Hi everyone, I think it is time to start talking about a roadmap for version 1 of strawberry. I've been using the library on a few side projects and most importantly on PyCon Italia's new website. That has helped a lot in fixing bugs and making sure the API is nice and consistent. Also, we have had contributions from many different people (thank you so much!)[1].

In addition to that, we might start using Strawberry at my current job, Pollen, which means me and/or my coworkers will have time to contribute new features and fix bugs. I recently added @mtszsobczak and @msobas to the core team. Now we have 5 people being able to review and merge PRs 🎉#244, which should be enough to keep the project moving forward (the other 3 are @marcoacierno, @jaydenwindle and me).

We never really had guidelines for how this project should evolve, and now that it is becoming a bit more popular, I think it is time to discuss what we want to see in the future. I have my own ideas, but this project has always been meant to be a community project, not my own :)

I'll make another issue for v2, but I want to start a discussion to see if we all are on the same page about v1.

For me, v1 should be a focus on stability and ease of use. That means making the library production-ready and finalising the base API.

I think we are close to that, but we have one crucial thing that is missing, documentation. I've worked on the website a few months ago (PR is here:strawberry-graphql/strawberry.rocks#3), so we have that ready, but we need to start writing docs. I'll ask some friends for some help on how to structure them, the end goal is to make them as user-friendly as possible, helping people also understand GraphQL concepts along the way.

So this is the feature set I was imagining for v1:

• Flask support (we have a PR for this)
• Basic Django support (we have a Django view that can be used)
• ASGI Support
• Custom scalar support
• Query support
• Mutation support
• Named union support
• Interfaces support
• Renaming field
• Support for resolver as functions (so not just class method resolvers)
• Support for default values on fields
• MyPy support
• Async support
• Support for Pydantic?
• Dev server (I need to test this a bit more, not sure it is working well)
• Documentation
• Subscription support (this needs to be improved and more tested)
• Internal refactor

For later

• Permission support (#244) <- deprecate or mark as experimental
• Pagination support (relay)

Am I missing something? There are some things we are currently working on, but not sure they should be in v1, for example supporting Django models, I think that's a great feature we should have, but I'd get to a stable release first :)
We also have PR for federation, which we might need at Pollen, that's probably going to be merged before v1, but it should not affect what v1 looks like :)

What do you all think?

[1] On that note I've been a bit slow on answering on PRs, PyCon and life are taking a lot of my time right now, but I will have more time soon :)