drupal.org migration

Background

We are planning to move all 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, we will need to change the namespace of composer packages from the localgovdrupal/ namespaces on Packagist (https://packagist.org/packages/localgovdrupal/), to the drupal/ namespace managed by drupal.org.

We will set a date to make the changes and publish new releases on drupal.org. Before we do, we would like to share the plan and invite feedback, questions or suggestions.

The plan

Once we’re ready to release, we will:

• Update namespaces in all projects composer.json to replace localgovdrupal/ with drupal/
• Update "name" to drupal/{project_name}
• Update "require" entries from localgovdrupal/{project_name} to drupal/{project_name}
• Update “require-dev” from localgovdrupal/{project_name} to drupal/{project_name}
• Update any defined “patches” if needed.
• Make a new release on drupal.org for each project.
• Minor version bump (ideally we don’t want to bump the major version to avoid potential issues where we’ve defined version constraints between modules for example "localgovdrupal/localgov_base": "^1.3.1 || ^2.0.0")
• Release an update of localgov_project with the new /drupal namespace.
• Advise everyone to update their root composer.json to replace localgovdrupal/ projects with drupal/ projects.

New releases will then only be made on drupal.org.

Issue queues

Over time we want to move to using issue queues on drupal.org.

This will not happen immediately for all projects.

Some projects will have issue queues on Drupal.org, some on Github.com

We will aim to:

• Only have one issue queue for each project.
• Be clear where issues are being tracked for each project.
• Archive github projects to preserve legacy issues but prevent new issues being created.