Read our Roadmap to understand how this work falls into priorities set by the Drupal Association with direction and collaboration from the Board and community.Drupal.org updates Healthcare industry page launched
One of our major goals this year is to highlight the power of Drupal in key industries. The Drupal.org industry pages highlight the story of building a custom-tailored solution for each industry using third-party integrations, expert hosting, or even purpose built distributions for the industry. Each page also highlights case studies which show demonstrated success stories using Drupal in each industry. In June we've launched our latest industry page, highlighting the Healthcare industry.Semantic Labels for Development Branches
With a six month release cycle for Drupal core, the environment that project maintainers should test their code against will change fairly frequently. To make it easier for maintainers to keep up to date with testing - we've introduced semantic labels for the core branches. Maintainers can now configure tests against Default — the current development branch of Drupal, Stable — the most recent release of core, and Supported — the current patch/bug-fix branch.
These semantic labels should make it easier for project maintainers to manage testing. We hope to expand on this with a few more labels, and may even extend these semantic labels to the version field that issues are filed against in the future.UTF8MB4 support
As mentioned in last month's update, we've updated the Drupal.org and the sub-sites to support the UTF8MB4 extended character set. While the changes for the sub-sites were deployed in May, we finished up by adding support to Drupal.org itself in June. Among other things, this means that Drupal.org will no longer throw errors if emoji are used in content. 😄Updating our membership CRM
Drupal Association Membership is managed using the CiviCRM platform - and in June we spent a bit of time updating to the latest version and troubleshooting some issues around receipting and renewals. Members can check their current membership status on the membership page. If you're not yet a member or you need to renew, check out our membership certificate offer.Performance improvements
To increase performance on Drupal.org we've updated to the latest version of the Advanced Aggregator module (special thanks to u/mikeytown2). The latest updated includes aggregation of font from the Google fonts api, which should make a material difference in Drupal.org page render times.Better spam moderation tools
A recent surge of spam attacks targeting Drupal.org has lead us to take another pass at updating our spam moderation tools. Spammers continue with a never ending escalation of tactics, and so we are constantly evolving our tools for managing spam. We've implemented some rate limiting protections as well as some new moderation views that will make it easier for us to bulk moderate spam. We'll be continuing with some of this work into July so that we can keep Drupal.org's home free from spam and productive.Infrastructure Infrastructure partner selected
In March we kicked off an RFP process to find a Managed Infrastructure Services vendor to partner with us to help maintain and improve the Drupal.org infrastructure. In June we reached a decision and have selected Tag1 Consulting as our partner. We're now working with Tag1 to audit our current infrastructure, policies, as well as monitoring and alerting systems as we kick off this relationship. Tag1 brings a tremendous amount of experience in Drupal infrastructure management as well as making Drupal performant at scale - and we're grateful to have them on board. With a partner on board to help us manage our infrastructure our internal team will focus on features and issues that support our mission.
As always, we’d like to say thanks to all the volunteers who work with us, and to the Drupal Association Supporters, who made it possible for us to work on these projects. In particular we want to thank:
- Amazee Labs - Renewing Classic Supporting Partner
- Mediacurrent Interactive Solutions - Renewing Classic Supporting Partner
- Digital Bridge Solutions - Renewing Classic Supporting Partner
- Four Kitchens - Renewing Classic Supporting Partner
- Palantir - Renewing Classic Supporting Partner
- Appnovation Technologies Inc. - Renewing Classic Supporting Partner
- Contegix - Renewing Premium Hosting Partner
- Sevaa Group, Inc. - Renewing Classic Technology Partner
If you would like to support our work as an individual or an organization, consider becoming a member of the Drupal Association.
It feels great to build a Drupal tool that has achieved more than 1 million downloads and helps people from different places around the world to create, build and deploy Drupal applications. It's been quite a journey, which took almost four years and required a lot of time and effort. It’s only fitting that I walk you through my Drupal Console journey.
I hope that taking you through my experience working on the Drupal Console will motivate you become part of a project, collaborate or take the first step. So here are the most important milestones.The Beginning: The commit that started all
After been organizing a few hangouts and trying to decide to start a contributed project related to Drupal 8, David Flores pushed the first commit to the project repo. It was just a README.md file but every journey, even those that impact many people, start with one single step. That file marked the beginning of Drupal Console.jmolivas Tue, 07/18/2017 - 15:20
I recently shared the community needs and potential strategies for evolving community governance, which resulted from the Community Discussions we held in person and online throughout April and May. You can find the webinar recording and written transcript, as well as the meeting minutes from all Community Discussions, at https://www.drupal.org/community/discussions.
Many community members who participated in these discussions agreed that the next step to take in this process is to hold a Community Governance Summit. However, we are not yet clear on where and when this event should take place, who should participate, and several other important details. I worked with community members to develop this survey so we can answer those questions.
Please take 5 minutes to take this community survey and tell us your thoughts about the Community Governance Summit. This survey will remain open until 11:59pm EDT on July 28, 2017. We will analyze the findings and report back on what we learned in a follow-up blog post by Friday, August 4.
Thank you for your time and participation.
In last two blog post we discussed the basics of getting started with Drupal Commerce and the steps of e-commerce products creation. As we move forward with our learnings, we will write about how we dealt with those.
There is Business logic which demands few things out of the box where we create custom modules to aid a process. I came across a situation where we had to use Drupal Commerce module but the product was coming from the content type. Even though we had to import the product as commerce…
For the second time, around 100 people gathered in Heidelberg, Germany, for the 2-day Drupal Business & Community Days Heidelberg 2017 conference. Its unique concept combined two session tracks focusing on community and business topics.Josef Dabernig Tue, 07/18/2017 - 07:37
Apart from sprints and BoFs, the two session tracks allowed attendees to switch between community and business focused sessions. The community track focused on sessions in English for a more international crowd, while the business track sessions were held in German and attracted more attendees from the DACH (Germany Austria Switzerland) region.
Here are some of my highlights from the conference:
Die Firma sind wir! by Dietmar „dietmarg“ Giegler and Luca Curella was a talk about how Reinblau switched to holocracy. The cooperative of roughly 18 freelancers is using bi-weekly governance meetings moderated by a facilitator to allow for the improvement of the organisational structure by everyone involved.
Dr. Julia Schönborn (karmajob) in "Der ehrbare Kaufmann“ CSR: Verantwortungsvoll handeln und richtig darüber sprechen shared insights about how Corporate Social Responsibility (CSR) can be used as a holistic approach to focus all efforts of a company with regards to social responsibility.
I found it interesting that this approach has been mostly associated with big corporations in the past while smaller Drupal agencies, for example, also see their social responsibility extended to the contribution of open source code and providing a good working environment.
A look into a possible Future for all of us: React, GraphQL and Drupal by Michael "schnitzel" Schmid from Amazee.io shared all the findings we gained from creating multiple decoupled websites based on React, GraphQL and Drupal.
If you are keen to find out more about the topic, the Decoupled Developer Days are taking place in New York August 19-20, 2017.
Along with these highlights, there were also some other inspiring presentations, and during the 2 days, Drupal Business & Community Days Heidelberg 2017 provided a great way to connect with the German and international Drupal community.
Together with regional experts and enthusiasts for digital and open source we were able to connect and have in-depth collaborations and exchanges in a relaxed environment.
A common problem that I’ve faced, particularly in the last few years, is how to deliver the complex, component driven design that clients want while also giving content authors full flexibility with those components without creating an un-maintainable, or brittle product.
Drupal core announcements: July 17th, 2017 Symfony security fix in Security component (CVE-2017-11365) - Drupal not affected
Symfony contacted the Drupal Security team about today's Symfony security release addressing an issue in UserPasswordValidator. This announcement is to reassure the Drupal community that Drupal 8 is not affected by this fix, as it does not make use of this security component. There is no Drupal 8 release scheduled for this, and there is no action you need to take on your Drupal site(s).
Drupal 8.4.0, the next planned minor release of Drupal 8, is scheduled for Wednesday, October 4, 2017. Minor releases include new features, usability improvements, and backwards-compatible API improvements. Here's what this means now for core patches.
The goal of the alpha phase is to begin the preparation of the minor release and provide a testing target for theme or module developers and site owners. Alpha releases include most of the new features, API additions, and disruptive changes that will be in the upcoming minor version.Drupal 8.4.0-alpha1 will be released the week of July 31
In preparation for the minor release, Drupal 8.4.x will enter the alpha phase the week of July 31. Core developers should plan to complete changes that are only allowed in minor releases prior to the alpha release. (More information on alpha and beta releases.)
- Developers and site owners can begin testing the alpha. (Note for Drush users: Drupal 8.4.x requires Drush 8.1.12.)
- The 8.5.x branch of core will be created, and future feature and API additions will be targeted against that branch instead of 8.4.x. All outstanding issues filed against 8.4.x will be automatically migrated to 8.5.x once it is opened.
- All issues filed against 8.3.x will then be migrated to 8.4.x, and subsequent bug reports should be targeted against the 8.4.x branch.
- During the alpha phase, core issues will be committed according to the following policy:
- Most issues that are allowed for patch releases will be committed to 8.4.x and 8.5.x.
- Drupal 8.3.x will receive primarily critical bugfixes in preparation for its final patch release window. (Drupal 8.2.x and older versions are not supported anymore and changes are not made to those branches.)
- Most issues that are only allowed in minor releases will be committed to 8.5.x only. A few strategic issues may be backported to 8.4.x, but only at committer discretion after the issue is fixed in 8.5.x (so leave them set to 8.5.x unless you are a committer), and only up until the beta deadline.
Roughly two weeks after the alpha release, the first beta release will be created. All the restrictions of the alpha release apply to beta releases as well. The release of the first beta is a firm deadline for all feature and API additions. Even if an issue is pending in the Reviewed & Tested by the Community (RTBC) queue when the commit freeze for the beta begins, it will be committed to the next minor release only.
The release candidate phase will begin the week of September 4, and we will post further details at that time.
See the summarized key dates in the release cycle, allowed changes during the Drupal 8 release cycle, and Drupal 8 backwards compatibility and internal API policy for more information.
As a reminder, we have until the start of the alpha to add great new features to Drupal 8.4.x. Several experimental modules have 8.4.x alpha deadlines:
- Workflows and Content Moderation (must reach beta stability)
- Media (must become stable to provide a stable API for contrib media modules)
- Settings Tray (must become stable)
- Place Blocks (must become stable)
- Inline Form Errors (must become stable)
- Datetime Range (must become stable)
Help is most welcome with issues on the roadmaps for the linked modules now for a great Drupal 8.4.0!