Offering to co-maintain VWO

Just following up on this. It has been just over a month now since I moved this into the project ownership queue.

This is the first message I sent.

Hello Anil,

I am contacting you because Martin ( https://www.drupal.org/u/mandclu → ) offered to become co-maintainer for VWO ( https://www.drupal.org/project/vwo → ), a project for which you are maintainer.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3493411 💬 Offering to co-maintain VWO Active about accepting or declining the offer? Please do not reply via email; we need a reply on the offer issue.
Without a comment posted on that issue in the next 14 days, Martin will be probably made co-maintainer.

Project moderators will not remove the existing maintainers/co-maintainers; the project owner will not be replaced either. Maintainers cannot change the project owner; co-maintainers/maintainers can only be removed/added by people who have the permission to administer co-maintainers/maintainers.

I am contacting all the people who can administer co-maintainers/maintainers for the project.

As last note: This offer is about being co-maintainer, which is different from being a maintainer. A co-maintainer is a person who does not have all the drupal.org permissions on a project. Even though being co-maintainers could mean having just a single permission, we expect a co-maintainer to have the following permissions on the project: Write to VCS, Edit project, Maintain issues, Administer releases.
If there is any reason for not giving all those permissions, please explain that on https://www.drupal.org/project/projectownership/issues/3493411 💬 Offering to co-maintain VWO Active .

Best regards,
Alberto Paderno
-- Drupal.org project moderator
-- Drupal.org site moderator

The status has been changed because we are waiting for a reply.
Please post a comment after 14 days, if your offer has not been declined. It will show you are still interested in maintaining this project and it will serve as reminder an action is required for this offer.

This is the other message I sent.

Hello Prathamesh,

I am contacting you because Martin ( https://www.drupal.org/u/mandclu → ) offered to become co-maintainer for VWO ( https://www.drupal.org/project/vwo → ), a project for which you are maintainer.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3493411 💬 Offering to co-maintain VWO Active about accepting or declining the offer? Please do not reply via email; we need a reply on the offer issue.
Without a comment posted on that issue in the next 14 days, Martin will be probably made co-maintainer.

Project moderators will not remove the existing maintainers/co-maintainers; the project owner will not be replaced either. Maintainers cannot change the project owner; co-maintainers/maintainers can only be removed/added by people who have the permission to administer co-maintainers/maintainers.

I am contacting all the people who can administer co-maintainers/maintainers for the project.

As last note: This offer is about being co-maintainer, which is different from being a maintainer. A co-maintainer is a person who does not have all the drupal.org permissions on a project. Even though being co-maintainers could mean having just a single permission, we expect a co-maintainer to have the following permissions on the project: Write to VCS, Edit project, Maintain issues, Administer releases.
If there is any reason for not giving all those permissions, please explain that on https://www.drupal.org/project/projectownership/issues/3493411 💬 Offering to co-maintain VWO Active .

Best regards,
Alberto Paderno
-- Drupal.org project moderator
-- Drupal.org site moderator

It's been 21 days and I still haven't received any response. I am still interested in co-maintaining this project.

I added mandclu as co-maintainer.

A cursory glance indicates that "VWO" may be a registered wordmark with the USPTO (registration number 4663137).

As the project appears it may be currently maintained by VWO representatives I am adding the following information to aid VWO in locating the tools D.O. provides them to enforce their brand protection if they should object to this change in the future:

As @mandclu was only added as a co-maintainer the existing maintainers (with permission to manage maintainers) may remove them at any time through Manage VWO Maintainers → .

Addtionaly a representative authorized to enforce the VWO Trademark may utilize the policy located in How to become project owner, maintainer, or co-maintainer - Transferring a project that used a trademark in its short name → to instruct Site Moderators to not assign privileges to other users in the future.

@mandclu: Given the above you (or Acquia) may wish to (unless you have consent from VWO) consider forking the project instead of committing code as a co-maintainer. Addtionaly I will note any commits made to the repository on D.O. could be considered a derivative work and that the GPL license does not grant derivatives a license to use Trademarks (I have not reviewed the code to evaluate if there is any Trademark usage in the codebase that would not comply with fair-use exemptions).

Acquia has a partnership with VWO, and we sell an offering called Acquia Convert powered by VWO. My goal in becoming a co-maintainer is really to assist the VWO team, in particular to make sure that there are timely releases for new major versions of Drupal, or to otherwise address critical issues.

If the VWO team should decide that this assistance is not needed then they are certainly welcome to rescind my role as co-maintainer, as you describe.

Transferring a project that used a trademark in its short name is about transferring the ownership from somebody who created a project and somebody who has some right on a trademark when a project name (or short name) uses a trademark.
It does not apply in this case because the project owner is probably somebody who has the permission from the organization with the rights on the trademark, and the project owner has not been changed.

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