Taking over the Moment.js namespace

I have bad experience → in transfer ownership of a project.
Your d.org profile looks trustworthy, but I still ask you to send merge requests first.
If you want me to open an "3.x" branch for D10, I'll do it.

Hello dear Andor,

Thank you for answering me.

I understand. The fact that you are still here is enough :)

As you are comfortable, my goal is to create a version for Drupal 10. So, as a maintainer, I can be active and create a new branch and work together.

@Sweetchuck Please notice that this issue has been created to take over the project namespace, which means the project will be replaced with a different one. Furthermore, for these requests, the person who created the offer will be make project owner.

@apaderno I would like to see a patch or a merge request first.
Somebody, who never contributed to the project before comes out of blue and wants the ownership and I am forced to do so?

I am confused.
@mahyarsbt said:

to publish my new Drupal 10 Moment JS module.

@apaderno said:

the project will be replaced with a different one.

Moment.js@Sweetchuck I apologize I was not clear.
An issue like Taking over the Moment.js namespace is created when somebody wants to use the project machine name (moment, in this case) for a completely different project, which means none of the existing code is kept. The intention is not to port the existing project to Drupal 10, but to replace it with a totally different one that has in common with the old project just the name.
If mahyarsbt wanted to be added as maintainer, or be the new project owner, the issue he should have opened was Offering to maintain Moment.js, which is a totally different issue.

You can ask to see the code that will replace the existing project, and mahyarsbt should commit it in a sandbox. That is surely an acceptable request, to be sure the person who wants to take over the namespace has effectively a project to develop, and he is not just trying to be project owner of an existing project.

As a side note, you are still the project owner of GraphicsMagick PECL. I am not sure to which bad experience in transferring ownership of a project you are referring, since you have never transferred the project ownership of that project.

I still don't understand why do you (or mahyarsbt) need the ownership.

What can you do with the ownership that you can't with patches or merge requests?

@Sweetchuck mahyarsbt wants to commit his project, not to continue with your project. That is why he is taking over the project namespace and needs to be the project owner.
See Taking over an obsolete project's namespace → which explains some of the details I am trying to explain. (Emphasis is mine.)

Taking over an obsolete project's namespace

There are obsolete projects hosted on Drupal.org that are no longer useful. Users who want to create a new project that uses the same namespace as an obsolete project can take the project over by offering to become the new maintainer.

From that text should be clear that:

• The procedure is for obsolete projects
• The person who follows that procedure does not want to continue the develop of the existing project, not even porting the module to Drupal 8/9/10; that's why the text I quoted says Users who want to create a new project