Request for transferring ownership of Jquery Colorpicker

I agree, we need to cover Drupal 9 as well
I can help with maintaining this module as well.

The present owner is still around. We need to hear his opinion about this. I've sent him a PM asking him to comment here.

I've made gisle and Neslee Canil Pinto full maintainers on the project. It's in your hands. I won't have time to deal with issues on the project for at least a year, that said if you'd like to ask any questions of anything I've done, or discuss strategy on moving forward, I'm happy to talk about it. I leave it to your judgment on adding any other maintainers to the project.

Done. Please note I opened an issue for you on the Vendor Stream Wrapper issue queue.

I have created another isssue related:

https://www.drupal.org/project/projectownership/issues/3164236

g089h515r806,
please do not hijack other issue threads for your own purposes.

In this case, the user was added by the project's maintainer (not by a webmaster).

We have a long standing rule that a webmaster (or anyone else) should not interfere with the decisions made by a maintainer.

Resetting priority (sorry).

g089h515r806

If you have specific issues related to this module then you’re welcome to open issues regarding the issue. I find it aggressive of you to come in here to hijack this thread for a personal vendetta against this contributor. It’s not appropriate behaviour.

Neslee Canil Pinto request too many "Request for transferring ownership" on Drupal.org project ownership, this is one of
them. Most of them not well maintained by him. If he only request several well know module, it is good to Drupal. He request almost 100 well-know Drupal module. So I request to review his behavior, not one module, not several, the issue is "request too many".

After he become the maintainer of views slide show module, he remove aaron from the past maintainers list in the readme file.
https://git.drupalcode.org/project/views_slideshow/commit/5b603bd

Neslee Canil Pinto request to transferring ownership of image url formatter module to him, I reject him. After that he request to become maintainer of image url formatter module by webmaster of drupal.org. I reviewed his profile and commits carefully, I find he request too many "Request for transferring ownership" on Drupal.org project ownership, and find most of them not well maintained by him.

I am here almost 13 years.

I do not have any purpose to hijack Drupal, any community member.

Neslee Canil Pinto request too many "Request for transferring ownership" on Drupal.org project ownership, this is one of
them.

This module needs a D9 release, and Neslee has offered to issue one. As the module maintainer, I'm thankful for that. If you have a problem with the code, open issues in the relevant issue queue(s) to point it out. Coming into threads like this is not appropriate.

After he become the maintainer of views slide show module, he remove aaron from the past maintainers list in the readme file.

That has nothing to do with this module, nor this issue that you are posting in. Posting in this issue, for this module, is not appropriate.

Neslee Canil Pinto request to transferring ownership of image url formatter module to him, I reject him.

If you are the maintainer of that module, that's your right. Posting your complaints in this issue for this module is not appropriate.

We are a community. Drupal is built on the community. Neslee is making an effort to contribute to the community. Your behavior is aggressive towards a contributing member, and I find it very distasteful.

Jaypan

I am sorry to make you confused.

"Neslee is making an effort to contribute to the community.", If this is true， I am OK for it.

Better to help than to criticize. If he has done something you feel is wrong, like removing a maintainer from the file, then open a ticket in the issue queue for the module bringing up this issue. If you see this as a pattern across many modules, open an issue in the Webmaster's Queue: https://www.drupal.org/project/issues/webmasters. But cross-posting in unrelated issues/threads is not the right way to go about solving your issue.

Since g089h515r806 doesn't seem to understand hijacking an issue, I will add a comment here.

Hijacking an issue means using an issue for a different purpose than the one it had. I can understand you see a relation between your comments and the issue, but commenting on every request to become maintainer/co-maintainer done from a user to say to revert what done is considered hijacking. As Jaypan said, if you see any real issue, you can post an issue in the appropriate queue.

@Neslee Canil Pinto I'm around

Great, thank you