Composer provides a tremendously valuable tool for developers for dependency management, but whether composer support is provided through packagist.org directly or through the façade at Drupal.org (see issue #2576285: Drupal.org Composer Service (façade)) there is concern that composer could represent a single point of failure.

This plan issue is to explore options for making composer support more robust.

Ideas

  • Packagist.org could aggregate from the Drupal.org json facade.
  • Packagist.org could mirror Drupal.org packages
  • Drupal.org could federate packagist.org

Comments

hestenet created an issue. See original summary.

hestenet’s picture

hestenet
He/Him
Location Portland, OR 🇺🇸
CreditAttribution: hestenet at Drupal Association commented
Status: Active » Postponed

Postponing until the initial composer support is in place - though we can certainly plan here.

hestenet’s picture

hestenet
He/Him
Location Portland, OR 🇺🇸
CreditAttribution: hestenet at Drupal Association commented
Issue tags: +Composer, +packagist
Parent issue: » #2551607: [meta] Path forward for Composer support
Mixologic’s picture

Mixologic
He/Him/His
Primary language English
Location Portland, OR
CreditAttribution: Mixologic at Drupal Association commented
Status: Postponed » Closed (works as designed)

This is actually, pretty robust.