-
Notifications
You must be signed in to change notification settings - Fork 9
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 Welcome :-) #17
Comments
Hi! I would like to request maintenance on the package in the name of our group Data Horde. Data Horde has developed multiple archival projects over the years and we would be honored to help maintain an internet archive package that will see routine use :) |
@madprogramer thank you! Do you mean you'd like to have the repo transfer to the GitHub organization Data Horde? |
Hi again, To be clear I saw the maintainer request from this month's rOpenSci newsletter. For some reason, I misremembered that groups on GitHub could act as users. So what I suggested was that ropensci would still own the repo but they could add a maintainer role to the What is possible is for an organization to fork a repo. Then a single user ( ideally me :) ) would have to act as a maintainer on the So I think I am volunteering as @madprogramer, but my intention is to bring organizational resources from Data Horde while keeping this package in the ropensci ecosystem. Does that make better sense? |
Thanks for clarifying and thanks so much for volunteering. I've now invited you to the rOpenSci GitHub organization and to a team with admin access to this repository. You'll get an invitation to our Slack workspace from our community manager @yabellini (invitations are sent weekly). Feel free to tell us whether your collaborators on this package also need an invitation. Here's our cheatsheet for maintainers: https://devguide.ropensci.org/maintenance_cheatsheet.html and our guidance for taking over a package: https://devguide.ropensci.org/maintenance_changing_maintainers.html#taking-over-maintenance-of-a-package cc @ropensci/admin |
Welcome, @madprogramer. I will need an email to send the invitation; you can share it with me here or send me an email to yabellini@ropensci.org |
@madprogramer Thanks very much for taking over the maintenance of this package. Very much appreciated! If you ever have queries, feel free to let me know. |
Glad to be aboard :) |
@madprogramer could you please list yourself as maintainer in the DESCRIPTION file, keeping @lmullen as an "aut"? |
Hi @maelle. Is this package currently being maintained by someone? |
@madprogramer could you please answer the question above? @claromes thanks for your interest in the package! |
I sent another reminder to @madprogramer by email after the reminder here and by Slack. If I get no answer within one week, @claromes I will transfer maintenance over to you. Thanks a lot for your interest. |
Somehow I did not get @maelle's earlier ping so you have my apologies for the delayed answer. If @claromes wants to join as a co-maintainer that would be fine by me. I can also help facilitate communication between claromes and the Internet Archive as I don't believe I have seen you on either the forums, IRC or ad hoc Discord communities. |
Hey @madprogramer, thanks for the reply. Oh! It's good to know you're around and that the project hasn't been abandoned. I'll stick to being just a user for now. |
Hi! I'd like to offer some help in case you need it, @madprogramer . I'm mostly a data analyst but I can handle other tasks as well. |
Well, that's fantastic! Dear @claromes and @manuelgirbal Please let me know if you need any help. BW! |
@claromes , @manuelgirbal are you already on the rOpenSci Slack? |
I've just requested access to the channel. Maybe you could provide an invitation link. |
Invitation are made weekly every Friday. Tomorrow you will get an email with the instructions to join our Slack. |
(or new maintainer team)
If you're interested, please comment in the issue or email
info@ropensci.org
.For more info, see
@ropensci/admin @lmullen
The text was updated successfully, but these errors were encountered: