We’re working toward using GitLab for issues on Drupal.org, now that GitLab CI has replaced DrupalCI. We’re not taking the tools right off the shelf, we’re tuning them to the Drupal community’s collaboration style. Join us for this session to learn about the initiative.
The next big step is rebuilding and migrating Drupal.org’s issue credit system. The Drupal community has come to rely on issue credit to help motivate contributions, especially from organizations. GitLab is not extendable like Drupal, so issue credit needs to be split from issues.
The Drupal community has a single-threaded collaboration style, with multiple contributors, that has unique benefits in a world where contribution for other open source projects often means forks-of-forks-of-forks. By building an integration of GitLab into Drupal.org’s existing issue queue, we’re preserving that collaboration, while gaining the benefits of GitLab’s fork & branch management, merge requests, code review tools, and GitLab CI.
In this session we’ll review our observations of the way the Drupal community collaborates, and talk about how that is informing our integration of GitLab into the Drupal community’s workflow. Since GitLab is rapidly adding features, there is an opportunity to integrate additional tools and workflows, to help increase Drupal innovation.
