📣 Call for maintainers

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 (https://github.com/graphql-python/graphene/issues/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: https://github.com/graphql-python/graphene/issues/612#issuecomment-347066815
* 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.

Start by reviewing the v3 release discussion in issue 1127 and the linked v3 release notes, then inspect the release process described here, including graphene/__init__.py. The issue also identifies sparse documentation and unanswered issues as broader work areas, but it does not define a bounded change or completion test.

Escrito por el modelo de indexación a partir del texto del issue.