-
Notifications
You must be signed in to change notification settings - Fork 308
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Becoming a maintainer #275
Comments
@jjangga0214 you can help by sending PRs. We are merging ones that are well done and pass tests. Do you have anything in mind? |
@jasonkuhrt Yes, you're of course right. However, a maintainer can collaborate quite more seamlessly. The same story repeats when any contributor(non-maintainer) wants to work with other contributors. That is the one point I think beneficial of being a maintainer. How do you think?
|
That's a noble goal and I can related having tried to do the same in the past. I think the most practical thing though is to do just that. Would you be ok with that? Maybe after a certain amount of time enough PRs would make the case for putting you as a maintainer, but no guarantees right now. |
@jjangga0214 please feel free to just create a new PR and ignore mine, I think it's fine to do this in the situation where a PR author has abandoned their effort. |
Hi, first, thank you for creating and maintaining
graphql-request
.I've been interested in
graphql-request
as well, thus recently contributed a little bit.I personally feel this package plays an essential role in the ecosystem, helping many people, and is worth keeping developing.
Can I be a maintainer to collaborate?
Thanks.
The text was updated successfully, but these errors were encountered: