Offering to co-maintain Multiselect

I am a co-maintainer of the Multiselect module, but I don't have permission to add @bobi-mel as a co-maintainer.

I have taken a look at @bobi-mel's contributions to this and other modules, and think the following information is relevant in making a decision:

• They co-maintain the Darkmode JS → and Site Settings and Labels → modules; and has created releases for Darkmode JS.
• They have been actively engaged fixing issues in the Drupal.org community since creating their Drupal.org user account about 1 year ago (at time-of-writing). Many of their first contributions were for things like READMEs, hook_help, coding standards, etc.; but their recent contributions have been to fix 📌 Drupal 10 compatibility Needs work , and add tests 📌 Drupal 10 compatibility Needs work , fix edge-case bugs 🐛 Main menu inaccessible after disabling Taxonomy Menu Needs review , and so forth.
• They are familiar with Drupal's translation system (which is also important to me!)
• They are familiar with Drupal.org's GitLab CI → and the tools it runs.
• They have asked other module maintainers for co-maintainership of modules that they have contributed to

In conclusion, while I acknowledge that @bobi-mel is new to the Drupal community, I see from their contributions that their skills are growing, and I support giving them a chance to become a co-maintainer.

One additional issue was fixed by me

Add a FunctionalJavascript test for the jQuery.fn.selectAll functionality ✨ Add a FunctionalJavascript test for the jQuery.fn.selectAll functionality Fixed

@bobi-mel I received your contact form notification. I'm no longer maintaining this module. I would suggest you check with the other maintainer @mandclu to see if he wants to add you. It looks like he has permissions currently to add new maintainers.

@bobi-mel thanks for volunteering! I have added you as a maintainer. Welcome aboard. :-)

@mparker17 I have also given you the ability to manage maintainers.

Thanks, everyone!!! I'm happy to join your team

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