Some of the hardest technology failures arrive without a broken component or a clear error. Two DrupalCamp Poland speakers examine what teams can learn from convincing AI mistakes, system-level performance failures, and automation that still depends on human judgement.
Drupal teams are absorbing fast-moving AI work, deeper performance changes, and new expectations around how Drupal expertise is packaged and delivered. Four DrupalCamp Poland speakers tell The DropTimes where they think the practical learning lies.
Critical ratings are only part of the triage. Project reach varies sharply, and one advisory requires administrators to clean stored data after updating.
...more
A technical design that works well at one scale can become costly as an ecosystem grows. Drupal's update service shows how those costs can fall on a different group from the one that controls the underlying code.
...more
The week’s Drupal calendar stays in person, with a full conference programme in Poland alongside regional community gatherings in Germany and India.
...more
Symfony teams evaluating Vite or Rsbuild no longer have to treat Reprise as an experimental integration. Its 1.0 public API now carries Symfony's backwards-compatibility promise.
...more
Drupal AI integrations can depend on services whose runtimes, build pipelines and credentials sit outside the site's Composer-managed code. The LiteLLM incident shows how that external trust boundary can become part of the security picture.
...more
Practitioners with original lessons from Drupal projects, design, business, or community work can submit them for consideration across seven programme tracks.
...more