- Issue created by @arisen
- Status changed to Active
almost 2 years ago 8:12pm 11 February 2023 - 🇮🇳India arisen Goa
Contacted the maintainer prestosaurus through the contact tab on 14th Feb 2023.
- 🇮🇹Italy apaderno Brescia, 🇮🇹
As a side note, since the project is covered by the security advisory policy, drupal.org site moderators will not add as co-maintainers/maintainers users who cannot opt projects into security advisory coverage.
Moving this issue in the Drupal.org project ownership queue would just have the effect to make it be moved back in this queue. - 🇮🇳India arisen Goa
Thank you @apaderno for the clarification. Do you have any suggestion on how we can take the project towards Drupal 10 compatibility?
One and only maintainer of this project seems to be inactive on drupal.org for the last few months or maybe years. - 🇮🇹Italy apaderno Brescia, 🇮🇹
If the project maintainer has not replied to any issues for this project, a user who can opt projects into security advisory coverage should offer to be project maintainer.
- 🇺🇸United States prestosaurus Portland, OR
Hi arisen,
I have been out of contact for a while.
I have a fairly large update in progress that I would like to revisit. I also would not mind a co-maintainer if that is something you are interested in. Please give me a week or so to evaluate the current status and I will follow up.
Thank you
- 🇮🇳India arisen Goa
Thank you pretosauras. Looking forward to it.
Happy to help incase needed :) - 🇺🇸United States shelane
I was going to offer until I saw this issue. This is actually the last module I have before I can upgrade to Drupal 10. Any help you need to get that D10 compatible release?
- 🇺🇸United States prestosaurus Portland, OR
Hi @arisen and @shelane.
I have updates that are contained in the latest branch: 9.0.x.
Updates include:
- D10 readiness
- PHPMD and PHPCS clearance
- Updated translation support
- Media reference field support
- And other adjustments to logic
This has also been updated to focus more closely on using only route matching to display avatar/name when a route matches user.login or user.page.
I would greatly appreciate any assistance in testing (it's just me) before tagging a release. And I would be open to co-maintaining. Let me know if that sounds possible.
This branch should remediate some open issues, adjust a couple, and leave the rest as feature requests. Thanks!
- 🇺🇸United States shelane
I did some testing today and it all looks good. There was just one minor detail for code clean up that I created an issue for with a MR ready to go. You might also want to update the default branch so that anyone trying create issue forks are set against the correct branch from the start. This setting has been moved out of the d.o UI and it gets the data from GitLab.
- 🇺🇸United States shelane
Hey @prestosaurus, just wondering if you'll have time soon to cut a release. If you still want a co-maintainer to help with this, let me know or add me. I do have the vetted role for security coverage.
- 🇺🇸United States prestosaurus Portland, OR
D10 release available: https://www.drupal.org/project/user_menu_avatar →
- Status changed to Fixed
over 1 year ago 8:38pm 8 August 2023 Automatically closed - issue fixed for 2 weeks with no activity.