Offering to co-maintain Easy Email

Thank you! I will add you as a maintainer. I'm an independent developer, so it's been hard for me to find time to work on this module recently, as I've been overloaded with paid work.

There are a few issues I want to draw your attention to. Most of these are not directly related to the D10 upgrade, but they are architecture changes or wishlist items that I would like to make sure we don't make more difficult as we keep the module up to date. So, these are mainly just FYI to keep in the back of your mind.

📌 Support email translations Needs review
#3224711: Use base fields instead of configurable fields →
✨ Email Templates as Content Entities Active
📌 Add ability to select theme per template Active

For the D10 upgrade, we need to complete the switch to Symfony Mailer. ( ✨ Switch from swift mailer to symphony mailer, please Closed: duplicate ) Last year, I posted 2.1.0-alpha1, which supports Symfony Mailer and removes the Swiftmailer dependency. However, that version uses the backward-compatibility module from Symfony Mailer, which has now been removed. ( 📌 Obsolete the symfony_mailer_bc module Fixed ) I haven't had time to investigate what changes are needed to make it compatible with the latest release.

I'm available on Slack if you have any questions.

Thanks for the quick response! Marking this issue as closed since the co-maintainership has been sorted, but happy to keep the conversation going.

I greatly appreciate the detailed download. Given the structural nature of a number of these changes, I'm inclined to think a major version upgrade might be appropriate, even though the 2.x branch is relatively new. My proposal would be to get the 2.1.x branch D10 ready and then start a 3.0.x branch to address the deeper, structural changes. Given that most the usage for this module is currently in the 8.x-1.x branch, that could mean needing to figure out an upgrade path from that branch all the way up to a 3.0.x branch. Open to discussion on this major version idea.

Given the structural nature of a number of these changes, I'm inclined to think a major version upgrade might be appropriate, even though the 2.x branch is relatively new. My proposal would be to get the 2.1.x branch D10 ready and then start a 3.0.x branch to address the deeper, structural changes.

Yes, this was my plan as well. Let's get the 2.1.x branch working with D10 and Symfony Mailer, and then we can look at the other stuff in 3.0.x.

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