Offering to maintain Google customer reviews

Hi rhovland,

You can use this namespace .

Kind regards

Thank you. To finish this and close the issue I need you to add me as a maintainer.

After waiting for google to update our merchant center data I can confirm the module I wrote for this is functioning and is ready for release.

Oh also I need to know if you are interested in remaining as a maintainer of this project

Waiting for a reply

Agreed but didn't change anything? https://www.drupal.org/project/google_customer_reviews →

I guess that talking of namespace did not make clear the request was to be added as maintainer of the project.
Taking over a namespace means being added as new project owner, which is something people without higher drupal.org roles cannot do. Differently, adding a new project maintainer/co-maintainer is something every maintainer (including the project owner) can do.

This is the message I sent to prodigia.

Hello Ángel,

I am contacting you because rhovland ( https://www.drupal.org/u/rhovland → ) offered to become maintainer for Google customer reviews ( https://www.drupal.org/project/google_customer_reviews → ), 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/3508395 💬 Offering to maintain Google customer reviews Active 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, rhovland 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/3508395 💬 Offering to maintain Google customer reviews Active . 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 has been changed 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.

Hi rhovland,

I accept your offer. You can keep us as a maintainer too, please.

Greetings,
Angel Osuna

@prodigia rhovland offered to be maintainer, not project owner: None of the existing maintainers will be removed; the project owner will still be you.

I was unaware there was a project owner I thought all maintainers were effectively owners of the project.
In light of this it seems I was actually intending to become project owner but I did not know there was a difference between the terms.

So @prodigia I would like to become project owner and keep you as a maintainer. Do you accept this request?

Project owner is simply the owner of the project node. In Drupal, only a user account can be a node owner. It is the user account used to create the node, but anybody with the permission to administer nodes can change the node owner.

As for the permissions on a project, a project owner is a maintainer for which the permissions cannot be changed. (By maintainer, on drupal.org we mean a person with all the permissions on a project: Write to VCS, Edit project, Administer maintainers, Maintain issues, and Administer releases.)