Commercial support?

I love this lib - thanks so much for your hard work, @syrusakbary!

With that said, I’d happily contribute to paying for more of your time to extend Graphene, and fill in a few missing pieces that would make it more viable to use in production.

Namely:

• Error catching, per https://github.com/graphql-python/graphql-core/issues/177, and https://github.com/graphql-python/graphql-core/issues/202. System exceptions bubble up to user output by default, which a dangerous default IMO. I’d love to see a cleaner way of logging exceptions and controlling error output that could be defined in one place, rather than defensive try/except blocks in every mutation.

• Core improvements / re-factoring. Thread safety (#43), resolving promise issues (https://github.com/syrusakbary/promise/issues/57), moving to async/await per your comment, etc. There are a few core things that are beyond my immediate experience with how things work under the hood, that seem like they have some potential to throw weird/unexpected issues that are hard to diagnose.

• Documented subscription support/patterns, per #781.

• Docs synced with releases. There have been a few occasions where trying doc examples has thrown errors, such as #812 today or https://github.com/graphql-python/flask-graphql/issues/52 which I ran into a few days ago. When this happens, monkey-patched workarounds are usually suggested by the community, which makes for brittler code.

• Some more tooling to provide official solutions for #772, etc. Calculating the cost of queries, parsing the AST tree and preempting query joins that might be necessary, etc. Outside the purview of the core, perhaps, but necessary stuff at scale that would save devs reinventing the wheel.

• Closing issues faster. This is just a general thing, but there are issues going back 2-3 years that would be good to get unstuck. Much of it might even be redundant now or have other solutions, but clearing the backlog would make a clearer case for using the lib in production, knowing those same issues are unlikely to resurface.

Obviously, your time is valuable and the fact that you’ve put together anything at all - let alone something as cool as Graphene - is amazing, so thank you.

But perhaps there’s a way, as a community, we could buy more of your time to address some of the above? I’d happily chuck in a few bucks on the reg to keep this lib up-to-date.

[leebenson]

It’s disappointing to see that the campaign hasn’t moved in nearly 3 months. Still no further activity on Patreon. This is an incredible library with a ton of promise, but without any commercial backing, I’m not sure how much we can expect to move the needle forward on issues/feature requests.

[syrusakbary]

Hi @leebenson , @patrick91.

Thanks a lot for chiming in for Commercial support, this is something I’ve been thinking for a while. It might permit me to open-source (with license) Quiver, so more companies can have access to it.

As a way of organizing the different tiers for contributing into the project, I was thinking on doing similarly to Vue.js in patreon and Django Rest Framework

• Backer $10 or more per month Support ongoing development Your name will be put in backers.md in the Graphene repository.
• Generous Backer $50 or more per month Support ongoing development Your name will be put at the top of backers.md in the Graphene repository.
• Bronze Sponsor $100 or more per month Support ongoing development Your name or company logo (small) will be put in backers.md in the Graphene repository.
• Silver Sponsor $250 or more per month Support ongoing development Priority support for your engineers Your name or company logo (medium) will be put at
  • the top of backers.md in the Graphene repository;
  • on a dedicated sponsors page on graphene-python.org.
• Gold Sponsor $500 or more per month Support ongoing development Priority support for your engineers A job post on every documentation page Your name or company logo (big) will be put at
  • The homepage of graphene-python.org; (50k+ impressions per month)
  • The top of the project repo’s README. (~6k+ unique visitors per month)
• Platinum Sponsor $2,000 or more per month Support ongoing development Priority support for your engineers A job post on every documentation page Your name or company logo will be put on:
  • The top left of every documentation page on graphene-python.org
  • The homepage of graphene-python.org (at the top of the sponsors section)
  • The top of the project repo’s README.

Thoughts?