Taking over the AI namespace

Moving to Drupal.org PO queue.

Project page: https://www.drupal.org/project/ai →

Been about 2 weeks, no reply from owner. Also sent a contact email. I believe the original owner has moved on from Drupal and works at Vercel. If possible, I could take ownership of this project to facilitate movement. Our goal is to bring in the best of the best AI projects under one umbrella.

I made kevinquillen the new project owner, since the project does not have any commit and shadcn has last logged in five months ago.

As usual, I did not remove any existing maintainer.

Thank you.

Folks, not cool. I'm not active on drupal.org anymore but I was already in agreement with another team for the namespace. We need to review the guidelines here. Two weeks is a short time to take a major ownership decision.

in agreement with another team for the namespace

@shadcn it is against the policy ( 1 → , 2 → , 3 → ) to take namespaces and leave empty to begin with (for >1 years). Now its great, since module is maintained by most active developers and across multiple teams aligning towards Starshot initiative.

I will note that the new maintainers of the namespace appear to be in breach of the Druapl namespace squatting rules as well as per the links given in #10 modules should be ready and code should be avaliable within days not week before obtaining a namespace.

The boiler plate commit published this morning (possibly in response to this issue) can not be considered code avaliable.

@apaderno:
That may need to be reviewed by you and the namespace reverted to .

@shadcn if you do create an issue it may be worth linking it to 🌱 [META] Increase Security of Project Ownership Transfer Process Active as the parent meta.

• Give an estimated timeline for completion. This timelime should be days rather than weeks.
• If you find you can not commit any code within a few days, you should file an issue to have the placeholder removed.

You cannot develop such a module in days. And you have to have a name in order to plan the project accordingly. Following these rules, @shadcn should have asked to remove his placeholder in 2023-03-10... So there is space to improve these texts.

Also if you check the issue queue you can see the team is working towards a plan very actively.

You cannot develop such a module in days. And you have to have a name in order to plan the project accordingly.

Also if you check the issue queue you can see the team is working towards a plan very actively.

The D.O. Rules are that it should be planned and developed before reserving a name.

Namespace changes are a fairly simple search and replace change if needed with minimal impact.

I’m not asserting @shadcn has any right to the namespace given the current rules, only that the same rules that granted the namespace to the new maintainer should be considered on if the namespace should now be returned to the general pool of available names for adoption given the modules issue queue appears to show no firm code exists and the project is only in the planning stages.

a fairly simple search and replace

Kevin has gathered together multiple teams around this namespace to collaborate and merge multiple modules together. Like, it is difficult task to coordinate. While this module has maintainers consisting of at least 3 teams by now, and they are in talks with even more organizations, since I read about scheduled meetings. I think this beautiful namespace is important to achieve this and be used by most active developers instead of being unused.