Problem/Motivation

The Address module requires PHP libraries that must be managed using Composer.

Address is:

Proposed resolution

Establish criteria for contrib module dependency inclusion in core. Candidate criteria:

  • Module is installed on >4% of Drupal sites in the given major version.

As first step, include the Address dependencies in core.

This is only a workaround and will not address all sources of issues and barriers related to Composer-based workflows. However, it should improve site builders experiences in many cases and also remove a significant barrier to hosting distributions on drupal.org.

Remaining tasks

User interface changes

API changes

Data model changes

Comments

nedjo created an issue. See original summary.

nedjo’s picture

nedjo
he/him/his
Primary language English
commented
Issue summary: View changes

Updating summary.

bojanz’s picture

bojanz commented

We can put a thousand contrib libraries in core, but it won't change the fact that Composer is here to stay.

And sure, we need to fix distribution packaging on d.o. Thanks to Mixologic and the DA I believe most of the blockers to doing that are now fixed (Composer endpoint, testbot support, etc). All D8 distributions (Lightning, Open Social, Commerce Base) recommend installation via Composer, and only Lightning is actually downloadable from d.o.

nedjo’s picture

nedjo
he/him/his
Primary language English
commented
Related issues: +#2477789: Use composer to build sites, +#2485011: Infrastructure Requirements to support Composer based workflows

Composer is here to stay

Agreed. But we don't (yet!) expect Drupal users to build core using Composer. Based on analysis of download stats, Misologic suggests in #2477789-131: Use composer to build sites that:

we have a significant userbase that downloads tarballs via a browser and does *not* utilize drush/composer or other 'advanced' build methods

The interim measure I'm suggesting in this issue is intended to help the significant number of users who might have a use for Address but for whom the requirement of managing their code base through Composer is a major barrier.

Thanks to Mixologic and the DA I believe most of the blockers to [fixing distribution packaging on d.o.] are now fixed

From looking at the relevant issues, it looks like there may be significant work outstanding. #2485011: Infrastructure Requirements to support Composer based workflows hasn't been updated in most of a year. Recent comments suggest #2477789: Use composer to build sites may be pushed to the ideas queue or postponed until Drupal 9.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

quietone commented
Status: Active » Closed (won't fix)
Related issues: +#2940733: Site Builder Tool/Project Browser initiative

@nedjo, Thank you for the idea.

The particular proposal doesn't met the Criteria for evaluating proposed changes. In this case, there is not demonstrated demand and support for the change. There for closing as won't fix.

There is ongoing work to improve the composer based workflow in #2940733: Site Builder Tool/Project Browser initiative which may be of interest to anyone following this issue.

Cheers