Offering to maintain Inline responsive images

Created on 20 July 2024, 9 months ago
Updated 17 September 2024, 7 months ago

Sent email to maintainers on 18 Jul.

I request maintainer access.
I would like to help with inline_responsive_images module including:

  • fix branching
  • stable release
  • support for Gitlab CI
  • D11 support
📌 Task
Status

Fixed

Version

3.0

Component

Maintaining offer

Created by

🇦🇺Australia VladimirAus Brisbane, Australia

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @VladimirAus
  • 🇦🇺Australia VladimirAus Brisbane, Australia
  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    These offers must be first opened in the project issue queue. Only when the project maintainers they have not responded in two weeks since the offer appeared in the project issue queue, the offer can be moved to the Drupal.org project ownership issue queue.

  • 🇮🇹Italy apaderno Brescia, 🇮🇹
  • 🇦🇺Australia VladimirAus Brisbane, Australia

    No response after 2 weeks.

  • Status changed to Needs review 8 months ago
  • 🇦🇺Australia VladimirAus Brisbane, Australia

    Time to maintain that baby!

  • Status changed to Postponed 7 months ago
  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    I contacted the three maintainers.

    Hello Jeroen,

    I am contacting you because Vladimir ( https://www.drupal.org/u/vladimiraus ) offered to become maintainer for Inline responsive images ( https://www.drupal.org/project/inline_responsive_images ), a project for which you are maintainer.

    May you post a comment on https://www.drupal.org/project/projectownership/issues/3462761 about accepting or declining the offer? Please do not reply via email; we need a reply on the offer issue.
    In the case you accept the offer, you can also add Vladimir as maintainer, but this is not necessary, as project moderators can add co-maintainers/maintainers to any project.
    Without a comment posted on that issue in the next 14 days, Vladimir will be probably made maintainer.

    Project moderators will not remove the existing maintainers/co-maintainers; the project owner will not be replaced either. Maintainers cannot change the project owner; co-maintainers/maintainers can only be removed/added by people who have the permission to administer co-maintainers/maintainers.

    As last note: This offer is about being maintainer, which for us means somebody with all the drupal.org permissions on the project: Write to VCS, Edit project, Administer maintainers, Maintain issues, Administer releases. A person who does not have all those permissions is a co-maintainer.
    If there is any reason not give Vladimir all those permissions, please explain that on https://www.drupal.org/project/projectownership/issues/3462761 .

    I am contacting all the people who can administer co-maintainers/maintainers for the project.

    Best regards,
    Alberto Paderno
    -- Drupal.org project moderator
    -- Drupal.org site moderator

    The status has been changed because we are waiting for a reply.
    Please post a comment if none of the maintainers commented to decline the offer.

  • Status changed to Active 7 months ago
  • 🇦🇺Australia jannakha Brisbane!

    any movement on this issue?
    any replies from the original maintainers?

  • 🇦🇺Australia VladimirAus Brisbane, Australia

    No is the answer. I contacted original maintainers 3 months ago to date as per issue issue description. 🤭

  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    The project maintainers have 14 days to reply from the moment a project moderators contact them. I contacted the maintainers 15 days ago, not three months ago.
    Furthermore, in the comment where I quoted the message I sent, there is also written Please post a comment if none of the maintainers commented to decline the offer.

  • Assigned to apaderno
  • Status changed to Fixed 7 months ago
  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    Since the project maintainers have not posted a comment on this issue, nor replied via email (which was not what the message I sent asked them to do), I added vladimiraus as maintainer.

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024