In various other issues it has been discussed about using packagist.org for Drupal modules, however it looks as though the "drupal" namespace is protected.

The vendor is already taken by someone else. You may ask them to add your package and give you maintainership access.

Is there a way we can allow anyone you add a module under the drupal namespace on Packagist?

Comments

timmillwood’s picture

timmillwood
Primary language English
Location 🏴󠁧󠁢󠁷󠁬󠁳󠁿 Wales, UK
commented
Related issues: +#2477789: Use composer to build sites, +#2002304: [META] Improve Drupal's use of Composer, part 1
mile23’s picture

mile23
Primary language English
Location Seattle, WA
commented

Yah, it's taken *by us.* :-)

I believe @crell set that up.

timmillwood’s picture

timmillwood
Primary language English
Location 🏴󠁧󠁢󠁷󠁬󠁳󠁿 Wales, UK
commented

I heard it was by Dries, hence why I assigned to him.

Crell’s picture

Crell commented

The drupal/ namespace is owned by whoever had a package registered in that namespace when that Packagist feature was enabled. I am not one of those people.

We need to do some polite house cleaning and transfer those projects, and thus the namespace, to the Drupal Association. I've been trying to bug people at the DA as well as Dries to look into that for about 2 years now to no avail. I gave up a while ago; someone else can tilt at that windmill.

catch’s picture

catch
he/him
Primary language English
commented
Category: Bug report » Support request

This is effectively an open letter to Dries, which is fine, but since it's not actionable by anyone else and doesn't impact core code at all, moving to support request.

timmillwood’s picture

timmillwood
Primary language English
Location 🏴󠁧󠁢󠁷󠁬󠁳󠁿 Wales, UK
commented
Status: Active » Closed (duplicate)

I'm going to close this as #2547617: Notify Packagist about repository update is kinda the effort needed to overcome this issue.