Closed (fixed)
Project:
Drupal.org project ownership
Component:
Co-maintaining offer
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
2 Dec 2018 at 07:30 UTC
Updated:
12 Sep 2020 at 08:59 UTC
Jump to comment: Most recent
I use terms_of_use on my production sites. The module needs developing, has many patches, but maintainers is gone away.
Comments
Comment #2
avpadernoComment #3
eojthebrave+1 - Looks like there are a lot of RTBC patches in the queue, and that this module is un-usable without at least some of them. @itcrowd72 have you tried reaching out to the module maintainer via their contact form? They might not have email notifications enabled for the issue queue, and might not have seen this request.
Comment #4
neograph734@itcrowd72, have you reached out to the maintainer via the contact tab? If so and you have gotten no response, you could move this request back to the Drupal.org project ownership queue as per https://www.drupal.org/node/251466.
Comment #5
ivnishdel
Comment #6
ivnishActually
Comment #7
ivnishPlease make me a maintainer
Comment #8
eojthebraveHey @ivnish, as @Neograph734 mentioned if you reach out to the maintainer via their contact form https://www.drupal.org/node/262098/committers and don't get a reply you can move this issue into the "Drupal.org project ownership" queue by changing the value in the Project field. And then, assuming the project qualifies as abandoned, you can be made a maintainer. This is outlined in https://www.drupal.org/node/251466#procedure---own-project and at this point seems like probably the best path forward for this module.
Comment #9
avpadernoComment #10
gisleI frankly don't understand why this has been moved back to the Drupal.org Project Ownership issue queue. There has been multiple requests that the applicant reach out to the maintainers via their contact form, as is also spelled out in the protocol for becoming a co-maintainer – and it has not happened. It should be moved back, as the prerequisites for this request being processed by the webmasters does not yet exist.
The request is 20 months old, and it is not even clear if Andrei Ivnitskii is still interested.
Drupal is not lacking projects to handle registration checkboxes, and this one, as it currently stands, is not even designed to be GDPR compliant. IMHO, this is unnecessary duplication of effort. It should simply be retired as outdated, and community members looking for this functionality should be steered towards a better maintained and GDPR-compliant alternative. I think we got all the checkbox projects listed (including this one), on the project page for the Drupal GDPR team.
I've added a checklist to the issue summary to highlight what is missing and am postponing until the missing items on checklist in issue summary has been filled in.
Comment #11
avpadernoSee the issue listed in the Referenced by field.
Comment #12
ivnishI tried to contact with project owner but without success
YES! I'm interesting!
Yes, I have vetted role
Comment #13
ivnishComment #14
ivnishBUMP!
Comment #15
gisleivnish,
I believe you are in Poland, which is in the EU. That means you need to use a GDPR-compliant form for terms of use.
Have you considered replacing Terms of Use on your production sites with a more modern and GDPR-compliant extension?
These looks like possible candidates:
However, if you want to use Terms of Use, I will not stop you from improving it. I've added you as maintainer.
This would have been resolved in a more timely manner if you had provided all the relevant information in the issue summary. Don't expect me to dig through comments to discover the updates.
Comment #16
gisleMoving to "Fixed".
Comment #17
ivnishThank you gisle!
P.S. this module used in the Russian site, don't worry :)
Comment #18
gisleFor Russian sites, this one exists: https://www.drupal.org/project/fz152
Comment #19
ivnishI know :) But fz152 used when site save user private data. For other cases "Terms of Use" is good solution. For example "private blog"