-
Notifications
You must be signed in to change notification settings - Fork 23
drupal.org migration
We've moved most of our LocalGov Drupal projects from Github to drupal.org, to make better use of the drupal.org ecosystem and to be able to attribute credits to contributions more effectively.
Most projects now have a home on drupal.org, see https://www.drupal.org/u/localgov
To implement this change, you will need to update your root composer.json to change the namespace of any composer packages that have the localgovdrupal/ namespace on Packagist (https://packagist.org/packages/localgovdrupal/), to the drupal/ namespace managed by drupal.org.
For example, on a default install from the localgov_project, there are (were) two dependencies that use the localgovdrupal namespace.
"localgovdrupal/localgov": "^3.0",
"localgovdrupal/localgov_search_solr": "^1.1",
To update our codebase to use the drupal.org packages, we change this to:
"drupal/localgov": "^3.0",
"drupal/localgov_search_solr": "^1.1",
And run composer update.
composer update -W
localgov_os_places_geocoder_provider (suggested as an optional package by localgov_geo) is not a Drupal module so remains on Github.com therefore it retains the localgovdrupal/ namespace and should not be changed to drupal/ thus:
"localgovdrupal/localgov_os_places_geocoder_provider": "1.x-dev"
New releases will now only be made on drupal.org.
We are enabling all issue queues on drupal.org.
New issues should be created on drupal.org.
Over time we will migrate legacy issues from Github.com where needed.
In time we aim to archive legacy github projects to preserve legacy issues but prevent new issues being created.
We encourage everyone to have a user account on drupal.org.
You can register at https://www.drupal.org/user/register
We also encourage all councils and suppliers to have an organization account on drupal.org.
You can do this at https://www.drupal.org/node/add/organization