Skip to content

New Maintainer Welcome :-) #17

Open

Description

@maelle

(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

Activity

  1. madprogramer commented on Apr 22, 2024

    @madprogramer
    Collaborator

    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 :)

  2. maelle commented on Apr 22, 2024

    @maelle
    MemberAuthor

    @madprogramer thank you! Do you mean you'd like to have the repo transfer to the GitHub organization Data Horde?

  3. madprogramer commented on Apr 22, 2024

    @madprogramer
    Collaborator

    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 Data Horde organization. Unfortuntaely, that does not work.

    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 ropensci repo to merge requests.

    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?

  4. maelle commented on Apr 23, 2024

    @maelle
    MemberAuthor

    👋 @madprogramer!

    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

  5. yabellini commented on Apr 23, 2024

    @yabellini
    Member

    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

  6. lmullen commented on Apr 23, 2024

    @lmullen
    Member

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

  7. madprogramer commented on Apr 25, 2024

    @madprogramer
    Collaborator

    Glad to be aboard :)

  8. maelle commented on Jun 27, 2024

    @maelle
    MemberAuthor

    @madprogramer could you please list yourself as maintainer in the DESCRIPTION file, keeping @lmullen as an "aut"?

  9. claromes commented on Nov 10, 2024

    @claromes
    Collaborator

    Hi @maelle. Is this package currently being maintained by someone?

  10. maelle commented on Nov 12, 2024

    @maelle
    MemberAuthor

    @madprogramer could you please answer the question above?

    @claromes thanks for your interest in the package!

  11. maelle commented on Dec 2, 2024

    @maelle
    MemberAuthor

    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.

  12. madprogramer commented on Dec 2, 2024

    @madprogramer
    Collaborator

    Hi @maelle & @claromes.

    Somehow I did not get @maelle's earlier ping so you have my apologies for the delayed answer.
    You could say I am still maintaining this project, alas the recent Cyberattacks against the Internet Archive have been troublesome. Not only was the IA inaccessible and later read-only, but I have had zero luck in attracting further contributors to the project.

    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.

  13. claromes commented on Dec 16, 2024

    @claromes
    Collaborator

    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.

  14. manuelgirbal commented on Jan 7, 2025

    @manuelgirbal

    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.

  15. madprogramer commented on Jan 8, 2025

    @madprogramer
    Collaborator

    Well, that's fantastic!

    Dear @claromes and @manuelgirbal
    I have given @claromes Triage access and @manuelgirbal Maintainer-level access.

    Please let me know if you need any help.

    BW!

  16. madprogramer commented on Jan 9, 2025

    @madprogramer
    Collaborator

    @claromes , @manuelgirbal are you already on the rOpenSci Slack?
    It would be a good idea to form a chat group on there if possible

  17. manuelgirbal commented on Jan 9, 2025

    @manuelgirbal

    I've just requested access to the channel. Maybe you could provide an invitation link.

  18. yabellini commented on Jan 9, 2025

    @yabellini
    Member

    Invitation are made weekly every Friday.

    Tomorrow you will get an email with the instructions to join our Slack.

  19. maelle commented on Oct 16, 2026

    @maelle
    MemberAuthor

    If this package is now maintained, could this issue be closed? 😄 🙏 @madprogramer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions