Taking over the Reservation namespace

The Reservation project has not seen any code commits since December 2014, with releases only for Drupal 7 and earlier. Drupal 7 reached end of life in January 2025, so the project is effectively abandoned and is not covered by Drupal's security advisory policy.

I am developing a modern resource availability and booking module for Drupal 11 that I would like to publish under the reservation namespace. The new module manages bookable resources, their availability slots and live remaining capacity, with a concurrency-safe hold / confirm / release booking API. It is designed as a lean, dependency-free core that other modules can build richer reservation workflows on top of.

The new module is a complete rewrite with no code relationship to the original project. I understand that existing releases and Git commits will be preserved; I will create a new branch and document the transition on the project page.

Current maintainers have been contacted via their drupal.org contact forms, asking them to comment on this issue:

• maulwuff (project owner, created the project in 2008)
• davisben

I maintain a number of contributed projects on drupal.org (see my profile) and am committed to actively maintaining this namespace going forward.