Drupal.org Starts Migrating Ripple Maker-Maintained Projects to GitLab Issues

Projects maintained by Ripple Makers have begun moving to GitLab Issues in the next phase of Drupal.org's staged transition. The Drupal Association announced the cohort on 9 July 2026 in a blog post by Neil Drumm, lead architect for Drupal.org. Projects supported by Drupal Certified Partners are also receiving priority as migration batches are scheduled.

The policy changes when projects move rather than whether they move. The Association said every project will eventually be migrated, while member-maintained and partner-supported projects receive earlier places in the rollout. The announcement does not identify the projects in the current batch, state how many are being moved, or provide a completion date.

The Association linked the priority order to the cost of developing and operating the migration infrastructure. It cited engineering work on migration tooling, upgrades to git.drupalcode.org, and integrations that support contribution credit and shared issue forks. The post said member and partner funding also supports Drupal.org, project packaging, GitLab CI, and automatic updates infrastructure. It did not provide a cost breakdown or explain how projects are ordered within each priority group.

After migration, projects manage their issues through GitLab listings and issue boards rather than the former Drupal.org issue interface. Drupal.org's workflow documentation says maintainers can configure boards, while contributors without a suitable GitLab role can manage labels, titles, and descriptions through Drupal.org tools. Contribution records and shared issue forks remain integrated with Drupal.org. Migration or integration defects can be reported through the Drupal.org customizations issue queue, while workflow feedback can be shared in the #gitlab-issues-feedback channel on Drupal community Slack.