Offering to maintain Varnish purger

I sent @misc and @javivf, the only maintainers who have been active over the past years, the following message through their Contact tabs:

Hi,

Could you post a comment on my offer to co-maintain Varnish purger ( https://www.drupal.org/project/varnish_purge/issues/3489010 💬 Offering to maintain Varnish purger Active )? I would like to become a co-maintainer of the module to help resolve any pending and future issues.

Thanks in advance,
Dieter Holvoet

Hi,

+1 for a new maintainer/co-maintainer.

I use Varnish Purger on a lot of projects and would like to be able to update to D11.

Hi @avpaderno, any update here? Thanks!

Can we please move forward with this? 8000 installs, still no Drupal 11 release.

+1 from me! It's time!

Reading this issue it looks like @avpaderno may not have yet sent a message to the maintainers(no record is indicated in the issue).

This may end up needing another 14 day waiting period unless @avpaderno did send a message before and just did not put it in the issue queue.

Sending back to active until there is record of contact by queue maintainers as none of us have the necessary access to properly RTBC this.

I've seen issues get burried in this queue in the past.. @dieterholvoet (and only @dieterholvoet) may wish to try pinging @avpaderno on slack in #drupalorg.

I would suggest 📌 Automate the majority of the ownership transfer process (retain human approval) Active could help solve some of the issues of this queue regarding contacting maintainers, recording records of contact etc.

Comment #2 → , two months ago now

I sent @misc and @javivf, the only maintainers who have been active over the past years, the following message through their Contact tabs:

I also attempted to contact the maintainers via their d.o contact form. Still no answer.

+1 for adding a new co-maintainer.

If I can add a comment it may be best to contact https://www.drupal.org/u/deadbeef → for this.

I see all maintainers are from the same company ( https://www.drupal.org/digitalist → ), which means some of them may not even be working there, but deadbeef is head of that agency (by his profile title)

@dieterholvoet has followed the ownership process. Others including myself have reached out to the maintainer without response. @avpaderno , please re-review.

Might be on holiday?

Re everyone else following up:

From a security standpoint it needs to be assumed everyone is creating a false story, this is essentially a supply chain attack and the behavior in this thread very closely resembles the XZ Backdoor attack from last year.

If I were a queue maintainer I would flag this as needing extra scrutiny.

The only reaching out that really matters in the current system is the project ownership queue maintainers (so far they have not indicated they have done so).

If you want to streamline the process I suggest encouraging the adoption of 📌 Automate the majority of the ownership transfer process (retain human approval) Active which would provide validated confirmation earlier in the process.

Beyond that you might want to open a new issues to have the Drupal Association establish mandatory response times from those holding privileged optional roles (we often allow the “volunteer” label to mean “not held accountable” which leads to situations like this where issues can sit for an extended period of time without action).

In a followup to comment #11 , the digitalist company website is based on Webflow, is not Drupal . I'm guessing this company is no longer using Drupal, which explains why this project is no longer being maintained.

I have sent a message on Drupal slack to @misc and @javivf. Let's see if we get a response there.

@cmlara, I'm pretty insulted by your insinuations in comment #14. It's been nearly two months since this offer to co-maintain was openned. Hardly suspect at all. Really, there's 8000 installs of this project and more and more people are getting tasked with Drupal 11 upgrades. Serious Drupal projects that cares about availability and caching in any meaningful way will be using varnish_purger.

This is the message I sent to misc.

Hello Mikke,

I am contacting you because Dieter ( https://www.drupal.org/u/dieterholvoet → ) offered to become co-maintainer for Varnish purger ( https://www.drupal.org/project/varnish_purge → ), a project you created for which you are project owner and maintainer.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3489010 💬 Offering to maintain Varnish purger Active about accepting or declining the offer? Please do not reply via email; we need a reply on the offer issue.
Without a comment posted on that issue in the next 14 days, Dieter will be probably made co-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.

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

As last note: This offer is about being co-maintainer, which is different from being a maintainer. A co-maintainer is a person who does not have all the drupal.org permissions on a project. Even though being co-maintainers could mean having just a single permission, we expect a co-maintainer to have the following permissions on the project: Write to VCS, Edit project, Maintain issues, Administer releases.
If there is any reason for not giving all those permissions, please explain that on https://www.drupal.org/project/projectownership/issues/3489010 💬 Offering to maintain Varnish purger Active .

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

I am going to contact the other maintainers.

The status has been changed because we are waiting for a reply.
Please post a comment after 14 days, if your offer has not been declined. It will show you are still interested in maintaining this project and it will serve as reminder an action is required for this offer.

I contacted all the maintainers. This is one of the messages I sent them.

Hello Colin,

I am contacting you because Dieter ( https://www.drupal.org/u/dieterholvoet → ) offered to become co-maintainer for Varnish purger ( https://www.drupal.org/project/varnish_purge → ), a project for which you are maintainer.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3489010 💬 Offering to maintain Varnish purger Active about accepting or declining the offer? Please do not reply via email; we need a reply on the offer issue.
Without a comment posted on that issue in the next 14 days, Dieter will be probably made co-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.

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

As last note: This offer is about being co-maintainer, which is different from being a maintainer. A co-maintainer is a person who does not have all the drupal.org permissions on a project. Even though being co-maintainers could mean having just a single permission, we expect a co-maintainer to have the following permissions on the project: Write to VCS, Edit project, Maintain issues, Administer releases.
If there is any reason for not giving all those permissions, please explain that on https://www.drupal.org/project/projectownership/issues/3489010 💬 Offering to maintain Varnish purger Active .

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

My offer has not been declined and I'm still interested in maintaining this project.

I added dieterholvoet as co-maintainer.

Thank you @avpaderno and @dieterholvoet!

This is a very important project and is imperative to have strong stewardship.

I have 100% faith in  @dieterholvoet!

Thank you!

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