Hello

Further to #3482144, I am now following the procedure outlined on Drupal.org.

I'd like to take over the namespace of the Partytown module, which currently does not have any committed file, as

  • There has been no activity on this project since it's creation in 2023
  • I have a lot of interest in the integration of PartyTown and Drupal and have enough of a project together for a an inital commit (see the issue fork on #3482144
  • This namespace is the obvious one and I want to avoid creating another one

I've also contacted saki007ster about this via their Drupal.org profile contact form.

Thanks

Comments

rattusrattus created an issue. See original summary.

rattusrattus’s picture

Issue summary: View changes
rattusrattus’s picture

Project: Partytown 🎉 » Drupal.org project ownership
Component: Miscellaneous » Maintaining offer
rattusrattus’s picture

avpaderno’s picture

Component: Maintaining offer » Ownership transfer
Assigned: Unassigned » avpaderno
Category: Support request » Task
Issue summary: View changes

Since both the maintainers are still active on drupal.org, I will contact them.

avpaderno’s picture

These are the message I sent.

Hello Saket,

I am contacting you because James (https://www.drupal.org/u/rattusrattus) created an issue to take over Partytown (https://www.drupal.org/project/partytown), a project you created for which you are project owner and maintainer, to create a project which uses the same namespace.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3533099 about accepting or declining the request? Please do not reply via email; we need a reply on the issue.
Without a comment posted on that issue in the next 14 days, James will be probably made the new project owner and be able to make commits.

In this case, the project has been created on June 29, 2023, but its repository is still empty. If the project is no longer being developed, the request to take over should be accepted.

Project moderators will not change the existing maintainers/co-maintainers.

As last note: The purpose of requests to take over a namespace is not creating a Drupal 9/10/11 release of an existing project; the new project could even have a totally different purpose.

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

Hello Ravikant,

I am contacting you because James (https://www.drupal.org/u/rattusrattus) created an issue to take over Partytown (https://www.drupal.org/project/partytown), a project for which you are maintainer, to create a project which uses the same namespace.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3533099? We are waiting for a reply from the project owner, which could need to know if other maintainers are still developing the existing project.

In this case, the project has been created on June 29, 2023, but its repository is still empty. If the project is no longer being developed, the request to take over should be accepted.

Project moderators will not change the existing maintainers/co-maintainers.

As last note: The purpose of requests to take over a namespace is not creating a Drupal 9/10/11 release of an existing project; the new project could even have a totally different purpose.

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

avpaderno’s picture

Status: Active » Postponed

The status is Postponed because we are waiting for a reply.

Please post a comment after 14 days, if your request 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.

rattusrattus’s picture

Thanks Alberto!

rattusrattus’s picture

Hi Alberto

Just to say that I am still interested in taking over the namespace.

Thanks!

avpaderno’s picture

Status: Postponed » Fixed

@rattusrattus Thank you for confirming that!

I made rattusrattus the new project owner.

rattusrattus’s picture

Amazing. Thanks thanks Alberto!

Status: Fixed » Closed (fixed)

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