Centralized resource for plans and discussion

[bbuck]

I'm making this as a general issue. @chris-ramon and @sogko have been working to try and improve the reaction time the library has in regards to issue resolution (such as making me a collaborator) but I feel like we still need to take a few more steps to get this project opened up and moving along at a good pace. Some prime examples of what I'm referencing (despite work being done by the core guys) are things like #183 that's been open since Jan 30 and, as a potentially large change to the API needs more input/discussion from the core guys.

I know @sogko has tried to organize things with Gitter, but I've never heard much from anyone on those channels (in regards to getting project organization stuff done) and I'd like to have a place where we can openly chat about things or sort out what you see my role (and maybe others) as collaborators are. I'm honored to receive the status but have yet to do anything with it (like above, getting #183 resolved as a quick example) for fear that it may go against the wishes of the other people working on this project or perhaps they have another idea bout how to approach the problem.

We should probably schedule some time where we do a hangout or some screen share, or some other form of live discussion so we can coordinate. If not live, at least a platform we can potentially get daily/weekly (keyword here is regular) discussion about the future of the project, plans, current issues and any other topics relevant to keeping the community around this project here, active and engaged.

EDIT

The goal here is to foster some kind of discussion/recommendations on ways to carry these things out, or discussion about availability to commit to things like regular meetings/reviews or agreeing to regular periods to review the overall project.

[object88]

What degree of input & dedication are you looking for? I have an interest in this project as a consumer, and would like to contribute back, but I have not delved into any internals, and do not have any personal needs that the service doesn't address (yet?). Is my participation here appropriate?

[bbuck]

Right now my goal is to find some way to reliably communicate between owners, collaborators and contributors/consumers on a regular basis. I understand people can be busy but the silence that goes between @sogko and @chris-ramon contributing to the project usually see a stagnation of long issues, and since I was given the opportunity to become a collaborator myself I haven't had the ability to discuss with @chris-ramon and @sogko where they want to take this project so I haven't really felt comfortable acting on my new "permissions" so to speak.

I'd like to clear up #183, as I mentioned in the original post -- and there are several other issues that have been around. I'd like to get scheduled updates into the project rolling on a more reliable schedule (whether that's me focusing on them or one of the owners or contributors). All of this could be alleviated with a resource with which the community could participate and owners/callaborators agree to check and address new concerns like once a week or something.

[iamsaso]

the first thing that needs to be addressed is 15 open pull requests...

[ijsnow]

Hey all. What's the status of this project? I read through #182 and saw that there was going to be more of a community effort to keep this moving forwards. However I saw that the progress still seems pretty slow. I would assume that means that this is fairly stable although the first line of the README says it's "A work-in-progress implementation of GraphQL for Go" and there are many issues and PR's going unhandled.

I am going to be integrating graphql into a go project soon and am just trying to get an idea of the state of things. This project seems to be the most complete and to have been around the longest but I don't want to choose a project that will die out over time. The alternative I'm seeing right now is https://github.com/neelance/graphql-go which seems like a more active project though it's not quite as complete yet