Problem/Motivation

I would like to become a co-maintainer of this module to merge the Drupal 10 compatibility patch along with any appropriate RTBC issues and create a D10-compatible release.

You can view my profile to see my large history of work. For recent maintainer work, you can see QuantCDN when I have recently spent many hours bug fixing and doing issue triage and releases:

https://www.drupal.org/project/issues/quantcdn

Steps to reproduce

Proposed resolution

Review my profile and, if approved, add me as co-maintainer with appropriate permissions to merge code, manage issues, and create releases.

Remaining tasks

Add Kristen Pol as co-maintainer of Context.

User interface changes

API changes

Data model changes

Comments

Kristen Pol created an issue. See original summary.

avpaderno’s picture

Title: Offer to co-maintain Context to address Drupal 10 compatibility and RTBC issues » Offering to co-maintain Context
Priority: Critical » Normal
Status: Needs review » Active
kristen pol’s picture

Issue summary: View changes

Minor wording change in summary regarding permissions.

avpaderno’s picture

Issue summary: View changes
anybody’s picture

+1 for @Kristen Pol as (Co-)maintainer, thank you so much Kristen! :) Very important project!

anybody’s picture

PS: Perhaps Maintainership (no Co-) might make sense, as the maintainer seem to be inactive?

kristen pol’s picture

Thanks for the summary update. Yes, co-maintainer :) I want to primarily focus on D10 compatibility and the RTBC queue first. I'm totally fine not being a full maintainer though, if I'm given full permissions, that's okay too. I do want to be able to create releases if possible.

avpaderno’s picture

Usually, co-maintainers have all the permissions on the project, except the permission to administer co-maintainers and maintainers.
Just to be sure the offer is understood, it is better to claim which permissions are wanted, which is what comment #7 did.

avpaderno’s picture

As a side note, a co-maintainer can later offer to be maintainer, even months after the offer to be co-maintainer has been done. A co-maintainer who wants to be maintainer should get a "preference" over a user who offers to become maintainer without first being involved with the project.

kristen pol’s picture

Thanks, yes. I was using the "maintainer" term loosely when I added it initially since that's the label for the link/tab on the project page but it is good to be more precise here :)

avpaderno’s picture

There are four users who can administer co-maintainers/maintainers. I am going to contact them as project moderator.

avpaderno’s picture

Status: Active » Postponed

This is the message I sent to the project owner.

Hello Chris,

I am contacting you because Kristen (https://www.drupal.org/u/kristen-pol) offered to co-maintain Context (https://www.drupal.org/project/context), a project for which you are project owner and maintainer.

Ma you post a comment in https://www.drupal.org/project/context/issues/3342293 about accepting or declining the offer? Without a comment posted on that issue in the next 14 days, Kristen will be probably made co-maintainer (user with all the permissions on the project, except the one to administer co-maintainers and maintainers). None of the current co-maintainers/maintainers will be removed from site moderators, nor will the project owner be changed.

I am contacting all the users with the permission to administer co-maintainers/maintainers for that project.

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

I changed status, since we are waiting for a reply.

avpaderno’s picture

In the case there are not replies from the maintainers after 14 days, just ping me on this issue. I will take care of this.

kristen pol’s picture

Thanks so much @apaderno!!!

colan’s picture

Status: Postponed » Fixed

Welcome aboard! Gave Kristen Pol & paulocs Administer Maintainers as well as I'm not around this module much, and I don't believe anyone else with this permission is either. Thanks all.

kristen pol’s picture

Wooohoo! Thanks so much :)

Status: Fixed » Closed (fixed)

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