graphene
graphene copied to clipboard
graphql-python
📣 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
masterbranch 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.
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
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.
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.
I can also contribute by reviewing PRs. We have been using graphene for over a year
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.
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.
@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)
Small update. We started using Graphene at Wasmer, so expect news to come soon regarding updates to the codebase and so :)
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?
@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.
I agree with you @kevindice, seems like there is interest in this project. I'm certainly interested and I'm also interested in helping... what do we need to do? I'm not sure if I have the right background to help here but I can try. I'm using graphene-django and I want to keep using it. I don't like the alternatives.
I am interested in helping to release Graphene v3. It's been a very long time.
Any updates here? Looks like there's an effort to move things forward here with some of us willing to take over and recover this community
Hello guys! Is there any roadmap for graphene v3? It seems to be some movement on the project but the documentation is outdated, the are many PRs and Issues. It would nice to have some info on the priorities and maybe more people can help.
Hey guys,
I have been working with graphene for over 2 years now, and have written a handful of custom mutation subclasses, logging classes, authentication integrations, and websocket integrations + tests, and have a handful of design patterns that i've found make working with graphene / django a lot easier (that I had to develop from scratch!).
I would love to bring this code into graphene and make it readily available.
Best, James Davidson
I'm also interested in contributing here. I can triage issues, review PRs and fix bugs. Count me in!
hi @jkimbo ! I am back on the open source train after leaving Apple this week and will be using Graphene as the core infrastructure at my new position. I would love to contribute as much as possible to this package.
I have been using Graphene for the past 4 years, and follow in @jamietdavidson's comments, where I have made advanced additions to Graphene in my apps via request logging, authentication, websockets via subscriptions + Django Channels, testing, among other topics.
I use Graphene based APIs in Python CLI tools as well as the GraphQL Code Generator (https://www.graphql-code-generator.com) to make premade TypeScript SDKs for NextJS apps.
@djstein @jkimbo Would either of you be interested in setting up a call later this week?
We can start the handoff process & start kicking this into high gear.
@jamietdavidson @jkimbo I am free to chat, the quickest way to reach me is on Twitter at (https://twitter.com/d_j_stein)
Great @djstein @jamietdavidson ! Are you both on the Slack workspace? It would be easier to coordinate things there with @tcleonard who has been picking up maintenance recently.
@djstein @jamietdavidson @tcleonard let me know when you schedule a call, currently working on Graphene-SQLAlchemy and would be happy to assist where I can :)
@erikwrede @djstein @jkimbo on Monday, June 27th***, at 11:00 AM PDT, I will be on this Google meet link: https://meet.google.com/ieu-wtxe-tqe
I’ll leave it open for anyone who would like to join. I wish GitHub had direct messages, as I don’t feel comfortable sharing my email on a public thread.
Let’s review and talk about things there! If anyone needs to reschedule, you can also reach me on twitter (jameztdavidson).
Talk soon!
@jamietdavidson see you there! Also reposting the invite to the graphene-slack workspace :) Sharing a mail address should be more private there. Feel free to reach out!
https://join.slack.com/t/graphenetools/shared_invite/enQtOTE2MDQ1NTg4MDM1LTA4Nzk0MGU0NGEwNzUxZGNjNDQ4ZjAwNDJjMjY0OGE1ZDgxZTg4YjM2ZTc4MjE2ZTAzZjE2ZThhZTQzZTkyMmM
sorry gang @jamietdavidson @erikwrede , didn't realize the call was at 11 AM, pretty busy with work today. can we schedule a 5PM chat?
@djstein that's 2am CEST so I sadly won't be able to make it. Nevertheless, you are invited to contact me on the Graphene slack and I'll bring you up to speed ASAP :)
