There are few requests in the queue to progress the module to be Drupal 9 compatible.
Happy to become co-maintainer and push the module across the line.

Checklist

  • Link to project: Taxonomy Term Reference Tree Widget
  • Record of owner agreement: No.
  • Maintainers: JSON
  • Year of last Drupal.org activity of owner: BartK: 2020
  • Record of attempts to PM owner and maintainers: None.
  • Project covered by Drupal’s security advisory policy: Yes
  • Permission to opt into Drupal’s security advisory policy: Yes

Comments

VladimirAus created an issue. See original summary.

stopopol’s picture

I'm no maintainer myself but I support this request.

dasjo’s picture

it would be great to see more progress happening on this project.

in the spirit of following procedures, @VladimirAus maybe could you add some details to the proposal like existing issues contributed to?
https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or...

coming here via https://github.com/testudio/term_reference_tree-drupal

vladimiraus’s picture

Title: Request to become co-maintainer » Request to become co-maintainer [Taxonomy Term Reference Tree Widget]
Project: Taxonomy Term Reference Tree Widget » Drupal.org project ownership
Version: 8.x-1.x-dev »
Component: Miscellaneous » Maintaining offer
Status: Needs work » Needs review
gisle’s picture

Category: Support request » Task
Issue summary: View changes
Status: Needs review » Postponed (maintainer needs more info)

Hi, and thank you for offering to maintain this.

Before this can be considered by the webmasters, all the information requested according to the procedures for Taking over unsupported (abandoned) projects must be provided. Two items are missing or unknown – please see the checklist I've placed in the issue summary.

To be more precise:

The protocol for becoming a co-maintainer says that before opening an issue here, you're supposed to contact the current project owner via the contact tab on their Drupal.org user profile page (and/or other means of contact that exists) to let them know about the issue you posted regarding maintainership/project status. There is no record of this being done. Please complete this step, and add the details (who, means of contact and when) to the issue summary.

Finally, the procedure for Taking over unsupported (abandoned) projects says:

When opening an issue for a project that has opted into security coverage, you must explicitly say in the issue summary if you have that permission. If you aren't sure about having that permission, write that in the issue summary.

Postponed until the missing information has been added to the issue summary.

avpaderno’s picture

Title: Request to become co-maintainer [Taxonomy Term Reference Tree Widget] » Offering to co-maintain Taxonomy Term Reference Tree Widget
Component: Maintaining offer » Co-maintaining offer
Issue summary: View changes

VladimirAus has the vetted role.

avpaderno’s picture

Assigned: Unassigned » avpaderno
Status: Postponed (maintainer needs more info) » Postponed

I sent a message to the current project owner.

Hello BartK,

I am writing you because Vladimir (https://www.drupal.org/u/vladimiraus) offered to co-maintain the Taxonomy Term Reference Tree Widget module (https://www.drupal.org/project/term_reference_tree), a project you created and for which you are the current project owner.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3184998 saying if you accept or decline the offert? Without any comment on that issue in the next 14 days, Vladimir will be probably made co-maintainer of the module.

Best regards,
kiamlaluno
-- Drupal.org site moderator
-- Drupal.org Git administrator

The other users who have some permissions on that project don't have the permission to administer co-maintainers/maintainers.

dasjo’s picture

thanks kiamaluno for driving this forward! it looks like the 14 days have passed. could we move on with assigning a co-maintainer?

avpaderno’s picture

Status: Postponed » Fixed

I added vladimiraus as co-maintainer of the module.

vladimiraus’s picture

Thanks @kiamlaluno

Status: Fixed » Closed (fixed)

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