Closed (fixed)
Project:
Drupal.org project ownership
Component:
Maintaining offer
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
11 Dec 2024 at 20:52 UTC
Updated:
16 Mar 2025 at 14:14 UTC
Jump to comment: Most recent
I'd like to help maintain this module, to help ensure that even sites on Drupal 11 can take advantage of the exciting features of VWO. Also, I would like to help clean up the issue queue.
Checklist
- Link to project: VWO
- Record of owner agreement:
- Maintainers: JSON
- Year of last Drupal.org activity of owner: Anil Kapoor (anilkapoor_vwo):
- Record of attempts to PM owner and maintainers:
2023-12-01: PM by mandclu. - Project covered by Drupal’s security advisory policy: Yes
- Permission to opt into Drupal’s security advisory policy: Yes
Comments
Comment #2
mandclu commentedComment #3
mandclu commentedJust following up on this. It has been just over a month now since I moved this into the project ownership queue.
Comment #4
avpadernoThis is the first message I sent.
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.
Comment #5
avpadernoThis is the other message I sent.
Comment #6
mandclu commentedIt's been 21 days and I still haven't received any response. I am still interested in co-maintaining this project.
Comment #7
avpadernoI added mandclu as co-maintainer.
Comment #8
cmlaraA 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).
Comment #9
mandclu commentedAcquia 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.
Comment #10
avpadernoTransferring 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.