All prior context for this issue is in this previous issue: https://www.drupal.org/project/projectownership/issues/3377119

Since then I have attained the ability to opt projects in to security coverage, which was the blocker to transferring the ownership before.

I again need to change the default branch in Gitlab and cannot, so am being hampered in my efforts to maintain this module.

I reached out to Blazey to remedy this issue with my permissions via their Drupal.org contact form on 27th June 2024 and have not received a response.

Comments

Eli-T created an issue. See original summary.

avpaderno’s picture

Title: Transfer project ownership of Computed Breadcrumbs from blazey to Eli-T » Offering to maintain Computed Breadcrumbs
Project: Drupal.org project ownership » Computed Breadcrumbs
Version: » 1.2.x-dev
Component: Ownership transfer » Miscellaneous
Category: Task » Support request

These issues still need to be first opened in the project issue queue. After 14 days, if the project owner has not replied to decline or accept the offer, the issue can be moved on the Drupal.org project ownership queue.

avpaderno’s picture

Also, to be able to change the default branch, it is sufficient to be maintainers for that project, which on the Gitlab side means to be maintainer. (A co-maintainer without both the Administer maintainers and the Write to VCS permissions is a Gitlab developer.)

eli-t’s picture

Project: Computed Breadcrumbs » Drupal.org project ownership
Version: 1.2.x-dev »
Component: Miscellaneous » Maintaining offer

Thanks @avpaderno!

Moving this back to the Drupal.org project ownership queue after no response after two weeks.

avpaderno’s picture

avpaderno’s picture

Assigned: Unassigned » avpaderno
Category: Support request » Task
Status: Active » Postponed

blazey logged in at least once in the past seven days. I am going to contact him.

avpaderno’s picture

This is the message I sent.

Hello Blazej,

I am contacting you because Elliot (https://www.drupal.org/u/eli-t), who is already co-maintainer, offered to become maintainer for Computed Breadcrumbs (https://www.drupal.org/project/computed_breadcrumbs), a project you created for which you are project owner and maintainer.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3461473 about accepting or declining the offer? Please do not reply via email; we need a reply on the offer issue.
In the case you accept the offer, you can also add Elliot as maintainer, but this is not necessary, as project moderators can add co-maintainers/maintainers to any project.
Without a comment posted on that issue in the next 14 days, Elliot 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 not to give Elliot all the permissions a project maintainer has, please explain that on https://www.drupal.org/project/projectownership/issues/3461473.

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 leave a comment when 14 days are passed without any comment from blazey.

avpaderno’s picture

@eli-t Are you still interested in this?

eli-t’s picture

@avpaderno yes

avpaderno’s picture

Status: Postponed » Fixed

I gave you the only permission you needed. Now you can change the default branch.

eli-t’s picture

@avpaderno thank you so much for all your help

avpaderno’s picture

I apologize for the delay. There are so many issues to handle that I cannot remember for which of them I contacted the maintainers more than 14 days ago.

Status: Fixed » Closed (fixed)

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