Skip to content

GitHub to Drupal.org namespace migration

Background

Most LocalGov Drupal projects have moved from GitHub to Drupal.org, to make better use of the Drupal.org ecosystem and to attribute contribution credits more effectively. Most projects now have a home on Drupal.org — see drupal.org/u/localgov.

In practice this means the Composer namespace for these packages changes from localgovdrupal/ (on Packagist) to drupal/ (managed by Drupal.org).

How to update your codebase

Update your root composer.json to change the namespace of any Composer packages that used the localgovdrupal/ namespace to the drupal/ namespace.

For example, a default install from localgov_project had two dependencies using the localgovdrupal namespace:

    "localgovdrupal/localgov": "^3.0",
    "localgovdrupal/localgov_search_solr": "^1.1",

Change these to the Drupal.org packages:

    "drupal/localgov": "^3.0",
    "drupal/localgov_search_solr": "^1.1",

Then run:

composer update -W

Exception

localgov_os_places_geocoder_provider (suggested as an optional package by localgov_geo) is not a Drupal module, so it remains on GitHub and keeps the localgovdrupal/ namespace. Do not change it to drupal/:

    "localgovdrupal/localgov_os_places_geocoder_provider": "1.x-dev"

What else has changed

New releases

New releases are now made only on Drupal.org.

Issue queues

Issue queues are enabled on Drupal.org, and new issues should be created there. Legacy issues will be migrated from GitHub over time where needed. In time, legacy GitHub projects will be archived to preserve their history while preventing new issues being created.

Drupal.org accounts

Everyone working with LocalGov Drupal is encouraged to hold a Drupal.org user account (register here). Councils and suppliers are also encouraged to create an organisation account (create one here), so that contributions can be credited to them. See the LocalGov Drupal Ladder for a step-by-step walkthrough of setting these up.