📣 Call for maintainers

[jkimbo]

Unfortunately it seems that the current maintainers of Graphene no longer have the time to maintain the library so I'm taking the liberty of putting out this call for anyone who wants to get involved with development. Ideally you'll already have already contributed to this library in some way or another.

The current status of the library is:

• v3 is ready to be released (☂️ Graphene v3 #1127) but has stalled because of a desire to bring the various dependant libraries up to date with it first. It's my opinion that v3 should just be released without waiting since it's been in the works for more than 6 months and it's now just stagnating. I will leave that up the new maintainers to make that call though since it will probably require some support once it's been released. Release notes are here: https://github.com/graphql-python/graphene/wiki/v3-release-notes
• The current master branch tracks the v3 beta releases and there is a v2 branch for bugfixes for v2 (https://github.com/graphql-python/graphene/tree/v2)
• The release process is as follows:
  • Update the version in https://github.com/graphql-python/graphene/blob/master/graphene/__init__.py#L44 and commit it
  • Create a new GitHub release with the new version number
  • GitHub will create a new tag and GitHub actions will push a new release to PyPi
  • The release numbers follow semver
• The current documentation is very sparse and needs work to make it more useful
• While Graphene is currently feature complete in terms of creating a compliant GraphQL server, it is lacking a lot of features that developers would expect from a mature GraphQL server library. There is a lot of scope to improve things here.
• There a quite a few gotchas with the API and it can cause a lot of confusion for people who are new to the library. Some of these are outlined here: Explain non-pythonic design and structures #612 (comment)
• Generally issues and pull requests have gone unanswered for quite a while know so there is a lot of housekeeping to do as well

---

Please reply to this issue if you would like to help out with maintaining this library. Once we have a couple of interested people I'll give you admin access and then let you self organise with how you want to proceed.

[Speedy1991]

Working with graphene for about 4 years (also giving workshops ) . I don't have the time to maintain, but willing to review PR's and support with issues/questions

[roylanmartinez]

I have been using Django graphene for at least 4 months so far. I think Graphene is incredibly useful and despite of that it is incredibly underrated. I do not have full time availability but I would like to contribute with this great library maybe building up a page of this repository with a clearer and more complete documentation or something similar.

[AndreCimander]

Maybe https://jazzband.co/ is a good fit?

[rhizoome]

Our project caluma uses graphene, we are committed to it. I wanted to help the project last year, but I wasn't able put much time in. I will talk to the team next week.

[berkcoker]

I can also contribute by reviewing PRs. We have been using graphene for over a year

[reginafcompton]

One of our repos at Brighthive uses Graphene; we've used Graphene for about 6 months. I am interested and (hopefully) able to contribute by: reviewing PRs and writing documentation.

[kevindice]

I'm interested in helping.

[jkimbo]

Thank you everyone. Any help if much appreciated.

@ganwell since you've contributed in the past it would be great to hand over things to you and your team. Could you either join Slack to chat more about it? Or email me, my email is on my GitHub profile.

[jkimbo]

@syrusakbary I'm going to leave this for you to take over now since you've said you're going to devote some more time to the project (I had assumed you weren't able to)

[syrusakbary]

Small update. We started using Graphene at Wasmer, so expect news to come soon regarding updates to the codebase and so :)

[jmorenobl]

Hello guys! is this repository officially dead? it has past 2 months from the last message written by @syrusakbary and still no movement. Can anyone confirm?

[kevindice]

@jmorenobl Seems like we absolutely have community interest in continuing this project. Forking is an option, but ideally, some of us can get added to the GH org.