Closed (won't fix)
Project:
Marvelous
Version:
1.0.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
6 Dec 2024 at 07:58 UTC
Updated:
12 Dec 2025 at 09:28 UTC
Jump to comment: Most recent
Comments
Comment #2
jaydeep_patel commentedComment #3
jaydeep_patel commentedComment #4
jaydeep_patel commentedHello,
I am contributing and fixing the issues in Marvelous theme, Still there are few issues in RTBC sins more than 1month.
I offered to maintain this theme and tried to contact the maintainer through its profile page more than two weeks ago, but I haven't received any updates, So as per the rule I am moving this issue to the "Drupal.org project ownership" issue queue.
Here is the project page link : https://www.drupal.org/project/marvelous
Thanks & Regards
Jaydeep Borsaniya
Comment #5
avpadernoComment #6
jaydeep_patel commentedHi @avpaderno,
Hope you're doing good.!!
It's been more then three weeks since I created this issue but still I didn't get any update from maintainer. So I wanted to check if there’s any update or any further information is needed from my side to help on this.
Thank you so much for your time and consideration. Looking forward to hearing from you!
Best regards,
Jaydeep
Comment #7
avpadernoI apologize for the delay. I will contact the maintainers tomorrow morning.
Comment #8
avpadernoThis is the 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 #9
jaydeep_patel commentedHello @avpaderno,
I hope you're doing well. It's been a month, and I'm still very interested to maintain this theme. I just wanted to follow up and moving this to Active.
Thank you!!
Comment #10
avpadernoThe project is covered by the security advisory policy; project moderators will not add as maintainer/co-maintainer, or project owner, somebody who cannot opt projects into security advisory coverage, as in this case.
I sometimes contact the maintainers, hoping they will reply back accepting the offer. They are the only ones who can decide to add as maintainers/co-maintainers people who cannot opt projects into security advisory coverage, though.
Comment #11
rushikesh raval commentedThanks @jaydeep_patel for your interest to be co-maintainers of this project.
I have given co-maintainer role to you.
Comment #13
rushikesh raval commentedHi @jaydeep_patel, are you interested in actively maintaining this project? I haven’t noticed any activity from you since the co-maintainer role was assigned. Just checking in to confirm your interest.
Comment #14
cmlaraIf you are considering removing the user you may wish to also take into account #3463115: Employees of CMS Minds could use some training assistance where the vendor the user represents has previously been identified as having deficiencies.
#3500263: [META|POLICY] Think of a way to make adding a (co-) maintainer more trustworthy (and its related issues) may also be worth reading for consideration of the concerns related to the adding random users with no significant work history to a module, especially a user lacking the security opt in permission when the module they are applying for is enrolled.
Comment #15
rushikesh raval commented@jaydeep_patel we did not get response from your side since long time So I am closing this issue. If still interested then re-open this issue.