Drupal Updates Maintainers' Credit Permissions for GitLab Issue Migration

The Drupal Association has announced that issue credit permissions are being streamlined as part of Drupal's transition from Drupal.org to GitLab for issue tracking on git.drupalcode.org. This change ensures all project maintainers can grant issue credit, eliminating the previous requirement for specific roles such as "Write to VCS" or "Maintain issues."

With the migration to GitLab, the "Maintain issues" project role managed by Drupal will no longer exist. Additionally, maintainers will now have the ability to grant credit for all closed issue states, rather than being limited to "fixed" and "closed (fixed)" statuses. While this provides greater flexibility, crediting contributions remains at the discretion of individual maintainers.

These updates align Drupal’s credit model with GitLab’s issue tracking system, which lacks a dedicated "fixed" state, instead categorizing issues as either open or closed. The transition will involve the use of labels for issue management, allowing project-specific customizations.

Key priorities in the final phase of the GitLab migration include reviewing roles and permissions to facilitate single sign-on to new.drupal.org, migrating issue credit records, and initiating test project migrations before a broader rollout. Issue fork management will also transition to new.drupal.org alongside the migration process.

Community members can stay informed by joining biweekly asynchronous initiative meetings held on Wednesdays at 19:00 UTC in the #gitlab channel on Drupal Slack. Further details on the migration and related discussions are available on Drupal.org.