Problem/Motivation

I noticed the RTBC list is getting long and you are seeking co-maintainers, so I would like to become a co-maintainer of this module to review and merge (as appropriate) RTBC issues and create a new minor 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 Redirect.

User interface changes

API changes

Data model changes

Comments

Kristen Pol created an issue. See original summary.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Issue summary: View changes

(Co-maintainers and maintainers are different roles, as described in Offering to become a project owner, maintainer, or co-maintainer / Terminology.)

kristen pol’s picture

kristen pol
she/her
Primary language English
Location Santa Cruz, CA, USA
commented

Thanks for the summary update. Yes, co-maintainer :) I want to primarily focus on the RTBC queue first.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Assigned: Unassigned » avpaderno

I will contact the maintainers in the next hour, if they do not reply before I do that. Actually, only the project owner needs to be contacted.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Assigned: avpaderno » Unassigned
Status: Active » Postponed

This is the message I sent to the project owner.

Hello Dave,

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

Ma you post a comment in https://www.drupal.org/project/redirect/issues/3342299 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, which in this case is just you.

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

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

kristen pol’s picture

kristen pol
she/her
Primary language English
Location Santa Cruz, CA, USA
commented

Thanks so much @apaderno!

berdir’s picture

berdir
Primary language German
Location Switzerland
commented

I don't have permission to edit maintainers.

I know I've been neglecting this module, and help is welcome. That said, the module tends to be fairly tricky. It's doing stuff early in bootstrap on every request so performance is critical and there's a lot of complex cases with routing, languages and so on. I would ask that you get in touch about anything that you're not sure about the impact and that any change is covered by tests.

kristen pol’s picture

kristen pol
she/her
Primary language English
Location Santa Cruz, CA, USA
commented

Fair enough. I would only merge changes that I actually understand and actually have tested since this is a VERY high use module. I am typically quite conservative for merging changes so as to not break things. I would be doubly so for this codebase. That said, I imagine there are still plenty of simple fixes in the queue that I’d feel comfortable reviewing and testing and merging.

kristen pol’s picture

kristen pol
she/her
Primary language English
Location Santa Cruz, CA, USA
commented

Also, I can make sure tests are added for any bug fix before it’s allowed to be merged.

berdir’s picture

berdir
Primary language German
Location Switzerland
commented

> That said, I imagine there are still plenty of simple fixes in the queue that I’d feel comfortable reviewing and testing and merging.

There are. Most of the RTBC issues, especially the older ones, are (often overlapping) coding standards stuff, README restructurings and the like that I never found motivation to dig into. Partially because those kind of issues tend to conflict with more useful changes and patches that people are using.

kristen pol’s picture

kristen pol
she/her
Primary language English
Location Santa Cruz, CA, USA
commented

Right… I could focus on those and merge what makes sense and close as outdated or won’t fix for others. Then at least there’s less noise in the queue :)

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Project: Redirect » Drupal.org project ownership
Version: 8.x-1.x-dev »
Component: Miscellaneous » Co-maintaining offer
Assigned: Unassigned » avpaderno
Category: Support request » Task
Status: Postponed » Fixed

I added Kristen Pol as co-maintainer.

kristen pol’s picture

kristen pol
she/her
Primary language English
Location Santa Cruz, CA, USA
commented

Thanks! I’ll start taking a look late next week.

Status: Fixed » Closed (fixed)

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