graphql-go / graphql-go/graphql

Centralized resource for plans and discussion

Open
#196 4 comments 6 reactions 0 assignees View on GitHub
discussion
Dominant language
Go
Stars
10.1k
Forks
845
PR merge metrics
No merged PRs in 30d

Description

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.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.