Taking over the Booking namespace

Created on 31 December 2023, over 1 year ago
Updated 17 January 2024, over 1 year ago

Booking is a very closed related concept to drupal modules I regularly work on from years now.

I noticed the project https://www.drupal.org/project/booking started years ago never had a release.

With no release published after years from the project birth, I'm asking a transfer of ownership to my drupal.org account.

The loss of Richard must certainly have been a bad blow for many people. I've contacted today snufkin [ https://www.drupal.org/user/58645] , the one active maintainer the project via drupal.org contact form to know more about his interest of being part of the project.
Being able to rely on his support, I'd be happy to be added as maintainer instead.

I'm really looking forward to improve Drupal.org features about online reservations.

📌 Task
Status

Fixed

Component

Ownership transfer

Created by

🇮🇹Italy afagioli Rome

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

Comments & Activities

  • Issue created by @afagioli
  • 🇮🇹Italy afagioli Rome

    I've contacted today snufkin [ https://www.drupal.org/user/58645] , the one active maintainer the project via drupal.org contact form ...

  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    These requests need to stay on the project issue queue for 14 days, and moved on the Drupal.org project ownership queue only if the project maintainers have not posted any comment to decline the request.
    When the issue is moved, site moderators will try to contact the project maintainers, except in the case they are not active on drupal.org. (The activities also include logging in, if the site moderator is also a user administrator who can check that.)

  • 🇮🇹Italy afagioli Rome

    This issue currently falls into [1] >5.
    As per [2], issue was moved into "Drupal.org PO" waiting for the availability comment, confirmed by him via mail.

    [1] = https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or...

    [2] = "... move the issue to the Drupal.org project ownership issue queue, by changing the issue's Project field to Drupal.org project ownership. To make it easier for the Drupal.org administrators, please include a link to the project page. If the owner privately agrees to transfer the ownership, ask for a comment on the issue you created."

  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    The procedure says:

    If the owner does not reply after two weeks, move the issue to the Drupal.org project ownership issue queue

    These requests are always placed in the project issue queue for 14 days. The only exception is when the project does not have its issue queue enabled, but a project moderator could still enable it to move the request/offer there.

  • 🇮🇹Italy afagioli Rome

    Thanks for clarifying that.

  • 🇭🇺Hungary snufkin

    I am happy to hand over the project ownership to afagioli. Feel free to remove me, and psynaptic (RIP) from the project.

  • 🇮🇹Italy afagioli Rome

    Thanks Snufkin!

    From what I read:

    If the owner agrees to make you the new owner, but cannot change the project owner, or the owner agrees to your request but does not make any change, move the issue to the Drupal.org project ownership issue queue, by changing the issue's Project field to Drupal.org project ownership.

    I understand one should move this issue into "Drupal.org project ownership".

    Waiting for while and see if the change of ownership will be completed here...

  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    @snufkin Thank you for the quick reply!
    I changed the project owner and removed the previous maintainers, as requested and accepted by snufkin.

  • Assigned to apaderno
  • 🇮🇹Italy apaderno Brescia, 🇮🇹
  • Status changed to Fixed over 1 year ago
  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    (I should change status too.)

  • 🇮🇹Italy afagioli Rome

    Confirming updates.
    Thanks!

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

Production build 0.71.5 2024