Offering to co-maintain Mailchimp

Checking status on this... hoping we can get a D10 release soon. Thanks.

Not sure if @japerry or someone else contacted the maintainers/owners, but if yes, this can be probably moved to Drupal.org project ownership issue queue, to speed things out.

Moving to the project ownership queue due to lack of response since December.

I contacted four maintainers, including the project owner. This is the message I sent to the project owner.

Hello Lev,

I am contacting you because Jakob ( https://www.drupal.org/u/japerry → ) offered to co-maintain Mailchimp ( https://www.drupal.org/project/mailchimp → ), a project you created, for which you are project owner and maintainer.

Ma you post a comment in https://www.drupal.org/project/projectownership/issues/3326617 💬 Offering to co-maintain Mailchimp Closed: outdated about accepting or declining the offer, and add Jakob as co-maintainer, if you accept the offer? Without a comment posted on that issue in the next 14 days, Jakob will be probably made co-maintainer (user with all the permissions on the project, except the permission to administer co-maintainers/maintainers). None of the current co-maintainers/maintainers will be removed from site moderators, nor will the project owner be changed. A co-maintainer cannot remove the existing co-maintainers/maintainers nor change the project owner.

I am contacting all the users with the permission to administer co-maintainers/maintainers for that project.

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

I changed the status, since we are waiting for a reply.

Hello all -- as I just posted in #3304436-17: Drupal 10 compatibility fixes → , there was just an organizational snafu on our side that prevented the right folks from actually seeing these messages. We've actually been pretty hard at work on a new release of this module, to include D10 compatibility and slated for release by 3/3/23 or sooner. That said, it's open source -- @japerry, if you want to join the team, you're very welcome! Given the above, what's your preference?

@japerry What is your answer to @bdimaggio question?

@japerry any feedback on #9? Otherwise, I'd suggest to close this issue won't fix?

I'm offering to co-maintain Mailchimp as well :). I see that there are some issues with the branch tests → and I would like to get that fixed.

@MegaChriz, we'd absolutely welcome patches in that vein. That said, would you be interested in contributing those through the issue queue without necessarily taking on co-maintainership?

I recognize that this is something of a turnaround from my position in #9, but now that the current batch of maintainers (all 12 of us!) has gotten a process dialed in for consistently maintaining this module, I am a little reluctant to change that process. That said, if you strongly prefer to become a co-maintainer, we'd be happy to accommodate.

@bdimaggio
It's also about updating the branch testing configuration on https://www.drupal.org/node/215311/qa → , that cannot be changed using a patch.
But I can understand that organizing the maintenance of the project can become more complicated if there are many maintainers around. I shall create an issue about updating the branch testing configuration. 🙂

Since bdimaggio answered, this is now an issue for the project maintainers.
The current status is for getting a reply back from japerry. Feel free to choose the status you consider more adapt.

@bdimaggio
I created an issue for updating the testing configuration: 📌 Update Automated testing configuration Fixed . Once that is done, some tests will likely fail. If that is the case, I will create an other issue for fixing these.

Update: thanks for the bump, @apaderno. Have just updated test configuration and would be grateful for fixes if @MegaChriz is still game to provide them.

Going to close this issue out since the latest thread is now on #3350229, but please feel free to reopen if you feel there is something else unresolved here.