Skip to content
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

Closed
jjangga0214 opened this issue Jul 2, 2021 · 4 comments
Closed

Becoming a maintainer #275

jjangga0214 opened this issue Jul 2, 2021 · 4 comments

Comments

@jjangga0214
Copy link
Contributor

jjangga0214 commented Jul 2, 2021

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.

@jasonkuhrt
Copy link
Member

@jjangga0214 you can help by sending PRs. We are merging ones that are well done and pass tests. Do you have anything in mind?

@jjangga0214
Copy link
Contributor Author

jjangga0214 commented Jul 3, 2021

@jasonkuhrt Yes, you're of course right. However, a maintainer can collaborate quite more seamlessly.
For example, in #130, I volunteered to take the issue. And I want to respect the original author's (@dannycochran) PR, instead of creating a new different PR. To keep work on his branch, I have to create a PR for his PR, which requires him to review and merge. I can wait until my code is completed, and then let him merge, but 'in general', that makes things slow. Because maintainers(e.g. You) on upstream cannot review in real-time. To enable it, I have to create many little PRs against the original author's (@dannycochran in this example) PR, and let him/her review and merge it every time. This is cumbersome.

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?

Do you have anything in mind?

The most fascinating one is #77. And #193.

@jasonkuhrt
Copy link
Member

jasonkuhrt commented Jul 5, 2021

I volunteered to take the issue. And I want to respect the original author's (@dannycochran) PR, instead of creating a new different PR

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.

@dannycochran
Copy link

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants