News and updates from Drupal.org team.

Migrating issues from security.drupal.org to git.drupalcode.org

By greggles on

All security issues have been migrated from the older security.drupal.org site to our GitLab instance at git.drupalcode.org. This is the latest in a series of steps to improve Drupal’s coordinated vulnerability disclosure tools. We hope this will help in a few ways:

GitLab issue migration: thank you Ripple Makers, your projects are next

By drumm on

This is the fifth post in our GitLab issue migration series. So far we’ve covered the immediate changes, the new workflow for migrated projects, how to use it, and what the migration looks like from a contributor’s perspective. This post is about which projects we’re migrating next, and why.

Improvements to Drupal.org project maintainers syncing with GitLab project members

By drumm on

As we migrate more projects to GitLab on git.drupalcode.org, we have discovered improvements to make in the mapping of Drupal.org project maintainers to GitLab’s project members, ensuring that it is a 2-way synchronization.

The next time you update maintainers for your project on Drupal.org, this will update all maintainers’ access in GitLab. Please review project members in GitLab, and under Activity, the Team events. Syncing is now more thorough, so there might be more maintainership and member changes than you expect.

GitLab issue migration: a contributor's perspective

By fjgarlin on

This is the fourth post in our GitLab issue migration series. The earlier posts focused on what is changing and how maintainers should set up their projects. This one is for the rest of us — the people who file bugs, review code, push fixes, and triage queues without wearing a maintainer hat. If your favorite contrib project has just moved its issues to git.drupalcode.org, here's what you need to know.

GitLab issue migration: how to use the new workflow

By fjgarlin on

As more projects are being migrated, we explain the main changes on the workflow when working on GitLab issues for migrated projects.

The old version of the Drupal.org Automatic Updates API is discontinued

By hestenet on

The Drupal Association engineering team is announcing the end of life (EOL) of the first generation of the Automatic Update API, which relies on a different original signing solution for update validation than later versions.

GitLab issue migration: the new workflow for migrated projects

By fjgarlin on

After the first changes to support both internal and external issues were made, we are ready to start migrating project issues to GitLab issues.

GitLab CI: Drupal's strategy to empower a whole ecosystem

By fjgarlin on

In this post, we share our CI strategy for all Drupal contributed modules. We believe that other large open-source projects may want to adopt or learn from the way we implemented a solution to centrally-manage CI while still allowing per-project customization.

GitLab issue migration: immediate changes

By fjgarlin on

Find out what's changing soon before we start the GitLab issue migration.

State of Drupal Open University

By jpvos on

What started as an idea among a couple of people has rapidly expanded into something with global interest. There are now educators teaching Drupal at higher education and universities, which is amazing. It means new people are being introduced to our beloved open source project.

“What if we could open source the teaching materials themselves, and teach others how to teach Drupal?”

Pages

Subscribe to Drupal.org posts