- Issue created by @mahyarss
- Assigned to apaderno
- Status changed to Postponed
7 months ago 6:50pm 28 November 2023 - 🇺🇸United States jastraat
Sorry; I meant to reach out to the Drupal support team after the initial PM to ask what the usual method for re-assigning a project namespace was.
The library module was initially developed for Drupal 6, and its functionality was mostly recreate-able without a custom module even in Drupal 7.
So it totally makes sense that the library namespace should be assigned to a more active project. While there is a version of the module for Drupal 7 and Drupal 7 is not technically unsupported, I doubt there are many existing D7 users of the module and there is no plan to create a Drupal 10 compatible version.
Thank you for checking!
- Status changed to Active
7 months ago 12:09am 29 November 2023 - 🇵🇱Poland mahyarss
Thank you for your reply, and I also appreciate giving me the opportunity to use this name to launch my module. I hope we will have a good cooperation in the future.
- 🇮🇹Italy apaderno Brescia, 🇮🇹
@jastraat Thank you for your reply!
I changed ownership as requested.
- Status changed to Fixed
7 months ago 8:36am 1 December 2023 Automatically closed - issue fixed for 2 weeks with no activity.