Upgrade Your Drupal Skills

We trained 1,000+ Drupal Developers over the last decade.

See Advanced Courses NAH, I know Enough
Sep 03 2021
Sep 03

I am pleased to announce that Victoria Spagnolo (quietone), Ben Mullins (bnjmnm), and Cristina Chumillas (ckrina) have accepted our invitations to become new provisional Drupal core committers!

Victoria Spagnolo (provisional release manager)

Victoria Spagnolo (quietone) is based in New Zealand and has been contributing on Drupal.org for over eight years. She is a maintainer for the Drupal core Migrate subsystem as well as multiple contributed projects. Victoria is also an active contributor to the community Bug Smash Initiative, which aims to improve everyone's experiences with Drupal by fixing bugs and reducing bug report response times. She received the New Zealand Open Source Award in 2018 for her contributions to Drupal.

Victoria's patience, empathy, attention to detail, and issue triage skills make her excellently suited to her new role as a provisional core release manager. She will collaborate with current release managers catch and xjm to improve core process, manage technical debt and disruptive changes, and ensure that core releases are shipped on time.

Ben Mullins (provisional frontend framework manager)

Ben Mullins (bnjmnm) is a United States-based Drupal contributor, also active on Drupal.org for over eight years. Ben is a Drupal core accessibility topic maintainer and subsystem maintainer for the Claro theme. He works for Acquia's Drupal Acceleration Team on a variety of Drupal core strategic initiatives and projects.

Ben will be collaborating with lauriii and ckrina as a provisional frontend framework manager. Ben has contributed extensively to helping solve tricky theme and JavaScript development problems without disrupting site owners' experiences, so we look forward to his further input on Drupal's frontend code. Ben's knowledge about accessibility and documentation also adds valuable expertise to our committer team.

Cristina Chumillas (provisional frontend framework manager)

Cristina Chumillas (ckrina) has been contributing to Drupal for over a decade. She is a core usability topic maintainer and also maintains the Claro theme. Cristina contributed design and theme expertise to the Admin UI and JavaScript Modernization Initiative.

Cristina started out her career in the graphic design industry and had formal training in Digital Marketing and UX. While working as a freelancer, she started coding with Drupal and quickly became part of the local community, where she has helped organise many local events in her home city of Barcelona. She joined Lullabot as a front-end developer in 2019.

Cristina is also joining the frontend framework manager team provisionally with lauriii and bnjmnm. Cristina has already brought a wealth of expertise and leadership to the Drupal project, where she has patiently and successfully shepherded many long-running initiatives. We're excited to see her continue the hugely impactful work she’s been doing under this new role.

Please join me in welcoming these new members of our core committer team!

Aug 05 2021
Aug 05

The core committer team is looking for a new provisional committer team facilitator to help coordinate Drupal core release process, team communication, decision-making, and meetings. The committer team facilitator does not need to have technical knowledge about Drupal core.

The core team facilitator role was created in 2019. Several community members have contributed to core committer team facilitation, with Donna Benjamin (kattekrab) initially jumping in and Shannon Vettes (svettes) sharing the responsibilities. Ultimately Pamela Barone (pameeela) formally took on the role in mid-2019 and still holds it now. These contributors have helped keep our release process, communications, and team decision-making sustainable. It's been very helpful.

Now that there is more clarity around the role, we would like to bring another facilitator into the team to share the responsibilities. The person would start as a provisional core committer team facilitator alongside pameeela. The provisional phase of a maintainer role allows an interested contributor to see if the role works for them and the team. The needed time commitment is about 10-15 hours per month.

If you are interested, read more about the role responsibilities, and get in touch with the team!

Nov 30 2020
Nov 30

We are currently planning for Drupal core to drop support for Internet Explorer 11 in Drupal 10 (scheduled to be released in June 2022). Drupal 9 will be supported until late 2023, which means that sites that want to support Internet Explorer 11 can continue using Drupal 9 until then.

Feedback needed from assistive technology stakeholders

WebAIM's survey of screen reader users shows Internet Explorer 11 usage dropping from 23.3% in October 2017 to 10.9% in September 2019. The next edition of their survey is likely to be released at the end of 2021, but we need to finalize our browser support within the next month in order to develop and release Drupal 10 on schedule.

We need feedback from assistive technology users and accessibility stakeholders. Do you or your users still use Internet Explorer 11 with screen readers? Do their screen readers support browsers other than Internet Explorer 11? How feasible is it to upgrade to a different browser for use with your screen reader? We are requesting feedback until December 18th, 2020 January 31st, 2021.

Why would we drop support for Internet Explorer 11?

  • Microsoft stopped developing Internet Explorer 11 in 2015. For that reason it is significantly behind modern browsers that have continued development. Because more and more libraries are adopting the use of those features, there is a significant cost associated with maintaining Internet Explorer 11. For example, the latest major release of CKEditor has dropped support for Internet Explorer 11, which means that Drupal 10 cannot securely support both CKEditor5 and Internet Explorer 11.

  • Microsoft itself has dropped support for Internet Explorer 11 in many of its services, and the rest will drop support in mid-2021.

  • Usage of Internet Explorer 11 has decreased significantly. Drupal doesn’t collect analytics on browser usage from its end users, so we rely on data provided by other projects such as Wikimedia, WebAIM, and Statcounter. For example, in October 2019, Wikimedia had 4.4% of its traffic using Internet Explorer 11. At the same time this year the number had dropped to 1.4%. We assume that the number of Internet Explorer 11 users will continue decreasing before the release of Drupal 10.

  • Supporting Internet Explorer 11 degrades the experience for everyone. We currently supply all users extra code to make Internet Explorer 11 work. This increases the request size and makes page load time slower for everyone.

  • The additional requirements of Internet Explorer 11 demand additional development time that far exceeds the browser's market share. These efforts come at the expense of new features and bug fixes.

What if I need to support Internet Explorer 11?

Even if Drupal 10 drops support for Internet Explorer 11, you can continue using Drupal 9 until late 2023. We recommend advising your users to move to another browser before that. If you believe your users have specific requirements as to why they cannot move from Internet Explorer 11, post them on the Internet Explorer 11 policy discussion.

Would this affect Drupal 7?

No. Drupal 7 remains compatible with Internet Explorer 11. A separate announcement will be issued if that changes.

Edit December 17th, 2020: feedback window extended until the end of January 2021.

About Drupal Sun

Drupal Sun is an Evolving Web project. It allows you to:

  • Do full-text search on all the articles in Drupal Planet (thanks to Apache Solr)
  • Facet based on tags, author, or feed
  • Flip through articles quickly (with j/k or arrow keys) to find what you're interested in
  • View the entire article text inline, or in the context of the site where it was created

See the blog post at Evolving Web

Evolving Web