- Issue created by @JeroenT
- 🇧🇪Belgium JeroenT 🇧🇪
I contacted https://www.drupal.org/u/cookiepro → .
- 🇯🇵Japan andrechun
I contacted CookiePro's support 10 days ago and they didn't update anything for this module yet. Might be better off to use https://www.drupal.org/project/cookiepro_plus → instead.
- 🇬🇧United Kingdom ikit-claw
If people want the module maintaining I can put in a request to take over the module?
- leymannx Berlin
Yes, 1xINTERNET would like to take over this project. I would like to maintain it. @ikit-claw you put in the request or is it me who has to do it?
- 🇬🇧United Kingdom ikit-claw
@leymannx feel free, if you need a hand you can always add me later on.
- Assigned to gisle
- Status changed to Fixed
about 1 year ago 5:32pm 9 November 2023 - 🇳🇴Norway gisle Norway
Thank you for showing an interest in this project.
The issue was opened to inquire about the project's maintenance status. That post looks like the beginning of the process outlined here: https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or... → The owner was contacted on 2023-08-21, and did not respond. Last activity on Drupal.org by owner was more that two years ago. I am going to change status to "Unsupported" shortly.
According to the project's usage statistics → , it still has around 2600 installs, so it may be worth salvaging. If anyone wants to take over ownership, please follow the process outlined here: How to become project owner, maintainer, or co-maintainer → .
- leymannx Berlin
We followed the process to take over ownership but now this issue has been set to "fixed". Is this right?
Since it's not clear to me what exactly was missing and why this issue was marked "fixed" I again created #3400767: Offering to maintain CookiePro by OneTrust → to restart the process.
- 🇳🇴Norway gisle Norway
This issue was created by JeroenT to get the project tagged as Unsupported. It has now been tagged as Unsupported. This is the reason why the Stautus now is set to "Fixed".
I am not aware of any previous initiated process to take over ownership. (I see that you now have created one.) If one ownership issue already exists, please link to it and I shall take a look at it.
- leymannx Berlin
Ah I thought the "Is [Project Name] still maintained" issue after having the owners contacted is already the last step before ownership moves over.
Anyways, I created the other issue now and tried to contact current owner via contact form today.
- 🇳🇴Norway gisle Norway
Now, we don't conflate different concerns from different people in the same issue. That is spelled out on this page: How to become project owner, maintainer, or co-maintainer → . Quoting:
The site moderators will only consider the offer from one person per issue. Please do not use an issue created by another user, even if that issue has not been completed for some reason; instead, open your own issue.
- 🇮🇹Italy apaderno Brescia, 🇮🇹
@leymannxIs [Project Name] still maintained issues are for marking the project as unsupported, not to change ownership.
We need to keep those issues separated for many reasons, including the fact a project owner could not object to the project being marked as unsupported (and not reply back, letting the project be marked as unsupported), but could be contrary to changing the project owner, or adding new (co-)maintainers (and reply back saying the offer is declined). - leymannx Berlin
Makes perfect sense! Thank you to the both of you, I'll spread the word.
Automatically closed - issue fixed for 2 weeks with no activity.