Description
Maintenance
We need to start working on a Maintenance plan for Graphene and it's sub-projects: graphene-django, graphene-sqlalchemy, graphql-core, graphql-core-next ... .
Why?
Right now my main focus has diverged from Graphene.
Because of that but also because my main focus is now on @wasmerio (which takes most of my time), we should plan a proper way to maintain Graphene in the long term without being blocked by my explicit approval, so it keeps growing at a healthy pace from contributors willing to take the time to make the project shine.
How we will do it?
Few months ago I've created an internal Slack channel, with people from Yelp, Reddit and other companies to have a direct way of communication with them.
I would love to invite more people to join this channel, so we can discuss the maintainance plan in a realtime fashion.
If you are interested in joining, please write your email as a comment on this issue :)
Ideal Solution
Ideally, we will form a committee of experts that have the knowledge and insight into what Graphene needs in both the short and long term. Done in a way that is not skewed on doing what only one or two companies need, but rather to focus on the community and the global needs.
I do like the way Django and the PSF are doing this, but more ideas will also be more than welcome!
At the same time, because all this years have gave me a lot of insight, I'll keep beign the belevolent dictator for Graphene, but my role will be more on the back side rather than in the front.
Looking forward to hearing your thoughts! :)