Offering to co-maintain Voting API Widgets

@Rajab Natshah: You are welcome to contribute to this module. Please review patches, answer support questions, contribute patches to existing issues, re-roll patches to apply, write tests for issues that need tests, help in the issue queue to debug problems, write documentation, etc.

Maintainer privileges are NOT needed for any of these. But willingness to do all these things IS required for maintainer privileges. You have not contributed to this module at all previously, and without that track record I don't want to give you privileges because experience shows that it will just result in MORE work for me, whereas what I am looking for is someone who will take on some of the workload and REDUCE the amount of time I have to spend on this project.

It seems you just want permission to commit something that you personally want. That's the worst possible reason to give maintainer privileges. If you want to help, then please help - there's nothing stopping you. But don't mistake my reluctance to commit a patch that hasn't been well-tested by community for an inability to make a commit. I am deliberately not committing the jQuery patch that I wrote because if there is a problem, I will be on the hook to respond to thousands of users. Because the community isn't helping, I have to spend a lot more time looking at it myself. If there were some detailed reviews from the community and even some automated tests, then I would be able to commit it without a lot of personal involvement. But I take the maintainership responsibility seriously, and if there is no community review and no community support, I won't commit something until I have time to immediately fix any problems that arise from a problematic commit.

BTW, "works for me" isn't a review, especially with JavaScript that is fundamental to the operation of this module and that is used in a variety of contexts in this module. If the community doesn't review the patch, then I have to do it myself to my standards, when I have time to do it.

Thanks, Tim, for your directions and time.

You are right, I only wanted to release a Drupal 10 supported tag.
To ease with updates and upgrades for number of projects.
#3399269: Update Varbase profile from Varbase ~9.0.0 to ~9.1.0 with Drupal ~10.2.0 and support for PHP 8.2+ →
Switcning to manage the update to Drupal 10 in anothoer way.

I do understand your conserns, It is taken, and I agree with you.
Any one can release, but not all have time for constant maintaines.

Hoping that you do have time to review and release.
On your time.