Maintenance Plan #884
Comments
|
I'd be happy to share my thoughts and experiences after using graphene/graphene-django in Saleor. Email: maarcin.gebala@gmail.com. |
|
Great news! I'd be happy to help out. Email: hello@jkimbo.com |
|
I'd be interested! Email: dave@dvndrsn.com Some folks from Joor may be interested in joining this discussion too: @pieropalevsky @nbbdog11 please cascade to interested people. |
|
I'd be interested. I have spent the last year plus working with Graphene in production and would love to contribute back to the project. Email: ppalevsky@gmail.com |
|
Also interested. dan@danpalmer.me
… On 3 Jan 2019, at 11:00, Piero Palevsky ***@***.***> wrote:
I'd be interested. I have spent the last year plus working with Graphene in production and would love to contribute back to the project.
Email: ***@***.***
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
I'm also interested :) florian.briand@digital-engine.info |
|
Me too, me@adamj.eu
On Thu, 3 Jan 2019 at 22:23, Florian Briand ***@***.***> wrote:
I'm also interested :) ***@***.***
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#884 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA0WCYE1Q7x-gIJBgEUGCgzSzp0pCSo3ks5u_oLlgaJpZM4ZiyOV>
.
--
Adam
|
|
I'm also interested. I've worked with Graphene in a couple of projects and I'm happy to share my thoughts and contribute back. leotsem@gmail.com |
|
I'm interested. This is a central component for our companies intranet projects. I wouldn't mind donating some time. dennisr@sailrite.com |
|
This is a critical part of my company as well. Please include me as well. nikordaris@gmail.com |
|
I'd like to join forforeach@gmail.com |
|
I'm interested! In the bay area too. |
|
@syrusakbary @patrick91 this project is a major dependency for my team, so I'd be happy to join the discussion and contribute. paulandrewhallett@gmail.com |
|
Invited all :) |
|
I'm interested |
|
I'm in if you'll let me :) |
|
Could you please share the timeline for this with us please? |
|
@syrusakbary We would like to have an update on this. This is an open source community project and there are some great pull requests stuck in the pipeline across grahpene's repositories. What is the proposed timeline and action plan for this? |
|
I'm game, mostly from the documentation/information dissemination side. jessamyn.hodge@gmail.com |
|
I volunteer as tribute: zbyte64@gmail.com |
|
We use it at EquityZen and are interested in joining the conversation and contributing. bryant.khau@equityzen.com |
|
@syrusakbary Now that more than a month have passed and many people have expressed their will to contribute to and maintain the project, what are the next steps? It seems to me that issues and pr are piling up, and the energy to contribute might dissipate if the evolution of this package is blocked by a contribution wall. |
|
Yeah, please please give us an update
|
|
Yesterday we had the meeting. As a summary, here are the things that we talked:
In general, we are going to add more maintainers into the repo so we can start reviewing and merging PRs without my explicit approval. In general, if you contributed to the repos of @graphql-python and you would like to be added as maintainer to a specific repo please let us know and someone will add you. PRs should be merged when a certain number of approvals is reached: 4 for Graphene, 3 for GraphQL-core, 5 or 4 for Graphene-Django, 2 for Graphene-SQLAlchemy... Also, I'm going to be present and helping the transition. But the goals of where Graphene should go in next releases will start coming from the community, collaborators and governors of the ecosystem. |
|
Thanks for the update Syrus!
I’d love to become a maintainer or Graphene/Graphene Django if possible. I believe I’ve contributed to both in the past, and would be keen to keep doing so.
… On 7 Mar 2019, at 20:10, Syrus Akbary ***@***.***> wrote:
Yesterday we had the meeting.
The details are in the doc that @brianmcfeeley posted.
https://docs.google.com/document/d/12-olPz5FHGx3w8kCkNX3FNhhx38abVR1VK-U2ehxHok
As a summary, here are the things that we talked:
Companies & developers interested on moving Graphene / GraphQL Python ecosystem forward
How to move Graphene forward (by using graphql-core-modern and/or graphql-core-next)
Different repos in the ecosystem and people that would like to start governing / maintaining them
How to handle communication between collaborators / maintainers (we will have all the communication in the Slack channel)
In general, we are going to add more maintainers into the repo so we can start reviewing and merging PRs without my explicit approval.
In general, if you contributed to the repos of @graphql-python and you would like to be added as maintainer to a specific repo please let us know and someone will add you.
Also, if you would like to start collaborating or knowing where Graphene is going next please join our Slack channel.
PRs should be merged when a certain number of approvals is reached: 4 for Graphene, 3 for GraphQL-core, 5 or 4 for Graphene-Django, 2 for Graphene-SQLAlchemy...
Also, I'm going to be present and helping the transition. But the goals of where Graphene should go in next releases will start coming from the community, collaborators and governors of the ecosystem.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
I just created a team of "Governors" for the Graphene / GraphQL-Python ecosystem.
They will have the rights for:
|
|
@syrusakbary is the slack still invite only? May I get an invitation please, if so, to brian@trialspark.com |
|
Is snapshottest considered to be a part of the GraphQL-Python ecosystem? I see there are some doubts about its future too, for example syrusakbary/snapshottest#64 and syrusakbary/snapshottest#37 |
|
It might not be the right forum to ask this, but as I'm a member, and already a contributor of aiohttp-graphql, should I move https://github.com/dfee/graphql-ws-next into this organization too? @Cito @syrusakbary ? |
|
@ktosiek only things under the graphql-python namespace are considered. Syrus has a lot of projects :) |
|
@dfee there you are! If you can pass me your preferred email, I can add you to the slack if you aren't already. |
|
i'd be interested in joining kay@9cloud.us |
|
Hello, invitation to Slack channel please: akin@akinadebowale.com. |
|
@akinadebowale @KaySackey sent you invites. |
|
Please invite me to the channel. I'm very much interested in contributing. My email adress: Lars [dot] Blumberg [ätt] posteo.de Thank you. |
|
I would be happy to join: prokher@gmail.com |
|
Hello, I'd like to get involved with |
|
Would also like to be added to the channel: avery.mcintyre@plangrid.com. Thanks! |
|
Go ahead and throw my name in the hat: joshdcannon@gmail.com |
|
I'd love to help out. jaydenwindle@gmail.com |
|
Please add cklarson@gmail.com. |
|
Hi, my company is interested in the sponsorship offered in the Patreon. We signed to donate up but haven't heard anything back. Are those offers still valid? Can you add me to the slack? satshabad@culturebiosciences.com |
|
I'm interested in discussing, and helping with, development of Graphene and related projects. I'm mostly interested in production use of graphene-django. I'd love to be invited to Slack: tomasz.kontusz@gmail.com |
|
I'd like to bump my request to be added, as well. cklarson@gmail.com |
|
Would love to be added to the Slack team - |
|
I would love to be a part of that team. hsagarthegr8@gmail.com |
|
Hey, I'd love to be added as well: |
and others
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! :)
The text was updated successfully, but these errors were encountered: