Offering to maintain Fixed Path Alias

Hi @randalv,

Thank you for offering to help on this module maintenance. I've been taking a look into the issue list for patches or reviews you may participate on, but I didn't found any yet, is it right? It is advisable to have some experience working on project maintenance prior to becoming (co)maintainer. From How to become project owner, maintainer, or co-maintainer → :

If you are a developer who have been working in the issue queues of a Drupal-contributed project, and you find that your work is being ignored by the maintainers/co-maintainers, the patches you've carefully reviewed do not get committed, or there is no progress, you may be interested in becoming a co-maintainer/maintainer or the project owner in order to further the development of the project.

In the issue queue → there are a few issues waiting to be reviewed as well as some others in RTBC. I think that the main task in this moment should be to reach compatibility with Drupal 10 & 11 in that order, keeping compatibility with D9 if possible which eases existing sites upgrade:

1. 📌 Automated Drupal 10 compatibility fixes RTBC
2. 📌 Drupal 11 compatibility fixes for Fixed Path Alias Active

Could you please take a look at them? Ask me for any support you might need.

Hi Manuel,

You're right, I have not yet been involved with issues thus far :) I'll get into that ASAP.

I was hoping we could open a new branch for D10/11 compatibility (2.0.x), and immediately tackle all those issues.
That way, 1.x could remain 'supported' but not maintained for D9, and we can go forward in 2.0.x with modern code (OOP hooks and other newer technologies).

I'll keep you posted!