Problem/Motivation

Project page: https://www.drupal.org/project/tombstones

The Tombstones module doesn't have any D10 or D11 releases. We're using it on our project and are interested in keeping it supported.

I've contacted bryjbrown (current maintainer) at Monday, July 14th, using the Contact form, didn't get any response so far.

There are a couple of issues I've made MRs for:
* #3535756: Incorrect response status code handling
* #3535753: Missing closing div element in node--tombstone.html.twig
* #3228123: You have requested a non-existent service "path.alias_storage"
* #3535752: D11 support

As a maintainer, I plan to focus on bugfixes, support, and opting into security coverage.

Comments

abramm created an issue. See original summary.

abramm’s picture

abramm
Primary language Ukrainian
Location Lutsk
commented
Project: Tombstones » Drupal.org project ownership
Version: 8.x-1.x-dev »
Component: Miscellaneous » Maintaining offer

Didn't get any response in 14 days, moving to Drupal.org project ownership issue queue.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Category: Support request » Task

I apologize for the delay in handling this. I will contact the maintainers tomorrow.

avpaderno’s picture

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

bryjbrown logged in at least once in the past 14 days.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

Hello Bryan,

I am contacting you because Vadym (https://www.drupal.org/u/abramm) offered to become maintainer for Tombstones (https://www.drupal.org/project/tombstones), 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/3536568 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, Vadym 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 is different from being co-maintainer. A maintainer is a person who has all the drupal.org permissions on a 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/3536568. We need this to know it was intentional and not a misunderstanding on what the offer required.

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

The status is Postponed 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.

avpaderno’s picture

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

bryjbrown commented

Hello, apologies for the delay in response. I approve of the offer to transfer ownership.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

@bryjbrown Thank you for the quick answer. The offer is to be maintainer, though, not the new project owner.

avpaderno’s picture

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

I added abramm as maintainer.

abramm’s picture

abramm
Primary language Ukrainian
Location Lutsk
commented

Thank you @bryjbrown!
I've merged a few bugfixes and prepared a new 2.0.0 release (following semantic versioning, which is now a requirement).
Feel free to contact me if you have any suggestions.

Status: Fixed » Closed (fixed)

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