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

New Maintainer Wanted :-) #85

Closed
maelle opened this issue May 13, 2022 · 18 comments
Closed

New Maintainer Wanted :-) #85

maelle opened this issue May 13, 2022 · 18 comments

Comments

@maelle
Copy link
Member

maelle commented May 13, 2022

Or a new maintainer team 😸

If you're interested, please comment in the issue.

For more info, see

@Athene-ai

This comment was marked as spam.

@maelle
Copy link
Member Author

maelle commented May 30, 2022

The gist API is an example in https://httr2.r-lib.org/articles/wrapping-apis.html#github-gists-api

@maelle
Copy link
Member Author

maelle commented Jun 14, 2022

I'm wondering whether I should archive this package @sckott @jthomasmock (or put the call in next week's newsletter once again as it's a fairly general API).

@sckott
Copy link
Contributor

sckott commented Jun 14, 2022

Doesn't matter to me, if you think archiving is the best move, please do.

@jmuhlenkamp
Copy link

I may be interested in maintaining this package. Will need a few (hopefully short) weeks to look under the hood and come to a decision. I'm comfortable with developing R packages, but not familiar with the details of gistr. Would also be open to teaming up with any others who may be interested. Will try to follow-up again by early July.

@maelle
Copy link
Member Author

maelle commented Jun 14, 2022

Ok, let's keep this open, thanks a lot for commenting!

@ScientificProgrammer
Copy link
Contributor

Hi:

I'm interested in helping out as a maintainer. Although I'm not familiar with the gistr package, I have many years of experience coding in C, C++, Python, and, of course, R. Please let me know how I can help.

@maelle
Copy link
Member Author

maelle commented Jun 28, 2022

Thanks a lot @ScientificProgrammer!

Once @jmuhlenkamp comments again, I can give you both access to the repository.

@ScientificProgrammer
Copy link
Contributor

Once @jmuhlenkamp comments again, I can give you both access to the repository.

OK, that sounds good. Once we have access, can you give me some guidance on where I can help most?

At present, I see only one open issue, #84. I read through the thread, and I'm not sure if I understand what's being asked. For example, based on your last reply to the individual who opened the issue, do you think he should simply use the httr2 package to roll his own solution, or, since the issue is open, do you think we should implement a solution for the code base?

I look forward to helping!

@maelle
Copy link
Member Author

maelle commented Jun 29, 2022

Well depending on who ends up being on board, y'all will need to decide whether to keep using crul or to convert the code to using httr2, and also to decide what is in scope.
Thank you!

@ScientificProgrammer
Copy link
Contributor

"Well depending on who ends up being on board, y'all will need to decide...

Thank you for the helpful reply. Just for my clarity, are the existing maintainers leaving the project altogether? Even if that's the case, would they still be available for the new maintainers to ask the occasional question? I'm fine either way, but having the benefit of their knowledge would be very helpful.

@sckott
Copy link
Contributor

sckott commented Jul 1, 2022

I'm available to answer questions, but i won't have time to write any code, etc

@ScientificProgrammer
Copy link
Contributor

I'm available to answer questions, but i won't have time to write any code, etc

Knowing that you'll be avaliable to give occasional input and guidance makes me feel much more confident about taking on a maintainer role. Thank you for all of the great work you've done and for being willing to help out with questions and advice!

@jmuhlenkamp
Copy link

Hi all, great to see some chatter in here! After careful consideration I'm not confident I will have the availability in the near-term to be a proper maintainer. @ScientificProgrammer all yours, thanks in advance!

@ScientificProgrammer
Copy link
Contributor

Hi @jmuhlenkamp

"I'm not confident I will have the availability in the near-term to be a proper maintainer."

I do understand and respect your decision. However, I encourage you to think about joining me. Just having another person available even to discuss the occasional idea is so helpful.


PS: My apologies for the previously deleted comment. It was from a work related account.

@maelle
Copy link
Member Author

maelle commented Jul 4, 2022

@maelle
Copy link
Member Author

maelle commented Jul 4, 2022

@ScientificProgrammer what is your email address? Asking so that rOpenSci community manager @yabellini might send you an invitation to rOpenSci slack workspace.

Also feel free to ask me any question by pinging me in GitHub issues, or using our forum https://discuss.ropensci.org/

@jmuhlenkamp
Copy link

@ScientificProgrammer sure, feel free to include (email) me on any discussions with Scott, if you have specific ideas/thoughts, or looking for someone to look over code changes, etc. Very happy to discuss occasional ideas, etc even without official maintainer status.
[email protected]

@maelle maelle closed this as completed Jul 28, 2022
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

5 participants