Comments

jaydeep_patel created an issue. See original summary.

jaydeep_patel’s picture

Issue summary: View changes
jaydeep_patel’s picture

Title: Offering to maintain Marvelous Theme » Offering to maintain or co-maintain Marvelous Theme
jaydeep_patel’s picture

Title: Offering to maintain or co-maintain Marvelous Theme » Offering to maintain Marvelous Theme
Project: Marvelous » Drupal.org project ownership
Version: 1.0.x-dev »
Component: Miscellaneous » Maintaining offer
Category: Support request » Task

Hello,
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

avpaderno’s picture

Issue tags: -become maintainer
jaydeep_patel’s picture

Hi @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

avpaderno’s picture

Assigned: Unassigned » avpaderno

I apologize for the delay. I will contact the maintainers tomorrow morning.

avpaderno’s picture

Title: Offering to maintain Marvelous Theme » Offering to maintain Marvelous
Status: Active » Postponed

This is the message I sent.

Hello Rushikesh,

I am contacting you because Jaydeep (https://www.drupal.org/u/jaydeep_patel) offered to become maintainer for Marvelous (https://www.drupal.org/project/marvelous), a project you created for which you are project owner and sole maintainer.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3492162 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, Jaydeep will be probably made 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.

As last note: This offer is about being maintainer, which for us means somebody with all the drupal.org permissions on the project: Write to VCS, Edit project, Administer maintainers, Maintain issues, Administer releases. A person who does not have all those permissions is a co-maintainer.
If there is any reason for not giving all those permissions, please explain that on https://www.drupal.org/project/projectownership/issues/3492162.

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.

jaydeep_patel’s picture

Status: Postponed » Active

Hello @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!!

avpaderno’s picture

Project: Drupal.org project ownership » Marvelous
Version: » 1.0.x-dev
Component: Maintaining offer » Miscellaneous
Assigned: avpaderno » Unassigned
Category: Task » Support request

The 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.

rushikesh raval’s picture

Status: Active » Fixed

Thanks @jaydeep_patel for your interest to be co-maintainers of this project.
I have given co-maintainer role to you.

Status: Fixed » Closed (fixed)

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

rushikesh raval’s picture

Status: Closed (fixed) » Postponed (maintainer needs more info)

Hi @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.

cmlara’s picture

If 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.

rushikesh raval’s picture

Status: Postponed (maintainer needs more info) » Closed (won't fix)

@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.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.