Taking over the Parallax Toolkit namespace

Given the number of requests to take over project namespaces, and the fact it is unusual for a person to open so many requests for taking over project namespaces, I need to ask it: What would the differences between the existing project and the new project?

According to what I have read in the Drupal site documentation, To create a new project if the desired name is already registered and its maintainer has no more activity to continue, can request to use that name space.

Of course, I know the difference between them, I talked to you about this before, but you did not raise this issue there. https://www.drupal.org/project/videojs/issues/3403895#comment-15332987 💬 Taking over the Video.js (HTML5 Video Player) namespace Closed: outdated .
If you have read it and after the explanations I gave, I asked for your advice. So if my work process was wrong, I wish you would have answered right away.

In any case, if you have noticed, I have not made a new request to get the old name since that date and I am using new names. And I have not followed up on previous requests.

Do I need to post this message to reply similar questions to yours?

but you did not raise this issue there.

I didn't raise any issue because there were few requests to take over existing namespaces, but now the requests are getting too much.

As for 💬 Taking over the Video.js (HTML5 Video Player) namespace Closed: outdated , since there is a person who has been added from another site moderator as maintainer, to continue to develop the existing project, the request to take over the existing namespace cannot be full-filled.
It is not possible to add as new maintainer a person who wants to continue the development of the existing project and, at the same time, add as maintainer a person who wants to wipe out the existing project to commit a completely different project.

Back to the issue at hand: What would the differences between the existing project and the new project be?

I didn't raise any issue because there were few requests to take over existing namespaces, but now the requests from you are getting too much.

Now??
This issue was for 25 Nov 2023 at 15:57 UTC
I asked for your advice on 24 November 2023 at 12:12,
That is, at the same time!

I haven't had any requests since 1 month 1 week ago.
Have I had a new request since that date?

I didn't follow up on past requests anymore!
Did I refer them?

After 2 weeks, I could transfer to Drupal.org project ownership Issues, Right?
Did I transfer?

What does this mean?
I mean, since then stopped requests.

What can I do now? Can I delete my requests?

As for #3403895: Taking over the Video.js (HTML5 Video Player) namespace, since there is a person who has been added from another site moderator as maintainer, to continue to develop the existing project, the request to take over the existing namespace cannot be full-filled.
It is not possible to add as new maintainer a person who wants to continue the development of the existing project and, at the same time, add as maintainer a person who wants to wipe out the existing project to commit a completely different project.

The issue has nothing to do with that project! You are right about this and I am not talking about that project. I asked you in general about getting the name space of the project. If you had said in my answer that the request should not be too much, I would not have made another request.

@apaderno I wanted to express my special thanks for the kindness and help you have given me during this time.

In this opportunity, I want to talk a little to avoid misunderstanding. And also guide me if I am doing wrong.

Considering that 50,967 modules are created in Drupal and only 7,351 of these modules are made for Drupal 10. Most of the modules are either empty and the project creator has not published any version in the past few years or these projects it is for past versions and is obsolete.

The easy and fast way for me is to register other names with suffixes and prefixes and continue my activity without interruption.

But I think this is not true. Maybe it would be better if I got the correct and exact name for the project than, for example, naming my module "the_better_somemodule" module, In this way, the namespaces are increasing in Drupal, which we see a lot similar to, and I don't think it looks interesting, While the original names for the project remain empty or inactive.

>>>>>>> I apologize if my way of thinking and acting was wrong, I would be grateful if you could guide me.

If you notice, in that message I stated the reason why I need to get the new or existing namespace, and both at the beginning and at the end of the message I asked you to tell me if this is correct or not.

Back to the issue at hand: What would the differences between the existing project and the new project be?

But before answering your question.
What do you mean the existing project?
I was talking about obsolete or empty projects. Do you mean the same?

The issue has nothing to do with that project! You are right about this and I am not talking about that project.

This is a quote from comment #3:

Of course, I know the difference between them, I talked to you about this before, but you did not raise this issue there. https://www.drupal.org/project/videojs/issues/3403895#comment-15332987 💬 Taking over the Video.js (HTML5 Video Player) namespace Closed: outdated .

That is a link for #3403895-8: Taking over the Video.js (HTML5 Video Player) namespace → , so you are talking about that project in that comment.

What do you mean the existing project?

Isn't Parallax Toolkitan existing project with committed code? The existing project means the code that is now committed for this project.

Isn't Parallax Toolkitan existing project with committed code? The existing project means the code that is now committed for this project.

Yes, it is true, but since there has been no activity for updating or releasing a new version for several years, And Drupal 7 will be deprecated. I made this suggestion. The version 10 code is very different due to the difference in the structure of Drupal 8 and later. In fact, a new branch can be created for version 10, still I want to create module for parallax library.

From a logical point of view, if the owner of this project gives ownership of the project to another person to continue and develop another version of the parallax module due to his unwillingness to continue development, it does not seem to be a problem.

Finally, the parallax module is available for version 7 and version 10. The previous owner and maintainers still have full access to the project page. Instead of creating other similar names, this name remains active. And the important goal is to open the way for activity.

Of course, I emphasize, this was just my idea that I am doing the right thing and if it doesn't work, I won't do it again.

My friend, dear Singh replied me this message in an email:

Ravindra Singh to me
Hi,

i am happy to do it. will do it today and let you know once done. Thanks for taking ownership of it.

Thanks,
Ravindra

However, I did not pursue this issue. Maybe in the future after completing the modules I am working on and if you approve.

Dear @apaderno You have always helped me and I am very grateful for your guidance and help. As you can see on my account page. You are our mentor and I am proud of this. I am under a lot of pressure to do several projects and I am working hard (at least 12+ hours a day nonstop or more) to get them done and I am having hard days.

I had a request from you, As you were always by my side and guiding me. With a little patience, let me prepare the modules. I will do my best to make the ending of this story satisfactory.

Please close these requests that have been active since the past and I will not submit a new request.

And from now on, I will consult with you before making any request.

Where can I ask more general questions for consultation?

Isn't Parallax Toolkitan existing project with committed code? The existing project means the code that is now committed for this project.

Yes, it is true, but since there has been no activity for updating or releasing a new version for several years, And Drupal 7 will be deprecated. I made this suggestion. The version 10 code is very different due to the difference in the structure of Drupal 8 and later. In fact, a new branch can be created for version 10, still I want to create module for parallax library.

From a logical point of view, if the owner of this project gives ownership of the project to another person to continue and develop another version of the parallax module due to his unwillingness to continue development, it does not seem to be a problem.

Finally, the parallax module is available for version 7 and version 10. The previous owner and maintainers still have full access to the project page. Instead of creating other similar names, this name remains active. And the important goal is to open the way for activity.

Of course, I emphasize, this was just my idea that I am doing the right thing and if it doesn't work, I won't do it again.

My friend, dear Singh replied me this message in an email:

Ravindra Singh to me
Hi,

i am happy to do it. will do it today and let you know once done. Thanks for taking ownership of it.

Thanks,
Ravindra

However, I did not pursue this issue. Maybe in the future after completing the modules I am working on and if you approve.

Dear @apaderno You have always helped me and I am very grateful for your guidance and help. As you can see on my account page. You are our mentor and I am proud of this. I am under a lot of pressure to do several projects and I am working hard (at least 12+ hours a day nonstop or more) to get them done and I am having hard days.

I had a request from you, As you were always by my side and guiding me. With a little patience, let me prepare the modules. I will do my best to make the ending of this story satisfactory.

Please close these requests that have been active since the past and I will not submit a new request.

And from now on, I will consult with you before making any request.

Where can I ask more general questions for consultation?

The version 10 code is very different due to the difference in the structure of Drupal 8 and later.

If you want to be added as maintainer to port a project to Drupal 10, the correct issue to create is the one to offer to become maintainer/co-maintainer of the project, not to take over the project namespace, which is not a quick way to become the new project owner. I hope this is clear.

It can be interpreted as a way to "force" the current project owner to accept you as project owner. That is probably what most of the project owners would do, thinking that a completely different project will be hosted on drupal.org instead of the project they do not have much time to further develop. Try telling them you are going to update the existing project (even to port it to a newer Drupal version), and they will probably reply saying there is no need to make you the new project owner and that being a maintainer is sufficient for what your plans are.

Some of the names I got are not going to be just port to version 10 and it is a completely different project.

As I said before, I had no bad intentions with these requests. Just maybe making sure that I am not limited access in that project or that I will not be removed or limited from the project for no reason in the future. Because I had a bad experience.

I used to be a maintainer in a project and I had problems.
For example, the project owner was no longer available. I messaged her a few times and she was waiting to allow me to push the code because he had restricted my access after some time.

And finally, it disrupted my work. And I was never able to release the new code I wrote for version 10 and still that module stopped on version 7.

I gave you this explanation so that you can be sure that I had no such intention and i hope too this is clear.

I will definitely follow your instructions in the future.

@apaderno:

I would also like to add some of the modules the user took over in October have not yet seen any commits either. If these were “new” modules I believe the namespace squatting rules would be raised as a question:

#3393591: Taking over the Read More Link namespace →
#3394089: Taking over the Vehicle namespace →
#3393614: Taking over the Active Tags namespace →
#3395952: Taking over the Designer namespace →
#3395949: Taking over the Themer namespace →