What's in a Driesnote? Interviews from the DrupalCon Dublin "Driesnote" keynote address. Suchi Garg is an IT professional through and through and happened upon PHP and Drupal essentially by accident at work. As of 2017, she has been working exclusively in Drupal for a decade and is still very passionate about code, contribution, the community, and passing on her knowledge through training. She is Technical Services Manager at Acquia.DrupalCon Dublin Community Voices podcasts
- 248: What's in a Driesnote? ASH 'n jam talk community stories. In this podcast, I talk with Acquia Office of the CTO Multimedia Designer, Alena "ASH" Heath about her history in Drupal, this project and what we learned along the way!
- 249: Changing lives, changing the world - voices from the Dublin Driesnote - Hear Vijaya Chandran Mani, Zsófi Major, Drew Gorton, Franck Seferiba Salif Soulama, Suchi Garg, Ronan Dowling, Jack Holding, Sheena Morris, and Crispin Read as featured in DrupalCon Dublin "Driesnote" keynote address.
- 250: Dublin Driesnote Voices - Suchi Garg
Subscribe to the Acquia Podcast in iTunes and rate this episode!
Subscribe via our RSS feed.Skill Level: BeginnerIntermediateAdvanced
DrupalCon is a magical experience where you not only learn new things and make new Drupal friends, but it also inspires and refuels our Drupal passion. We know that not everyone can attend and experience this DrupalCon magic. That's why we created The ULTIMATE DRUPALCON EXPERIENCE SWEEPSTAKES.
One lucky community member could win a flight, hotel, full-pass, and a one-on-one coffee with Dries Buytaert.
In order to achieve a steady stream of innovation in Drupal 8 core, it's important to keep up velocity. To do so we aim to clearly define and scope our top priorities and support the contributors that choose to work on these high impact changes. Another way to do this is through timely reviews and commits of "Reviewed and tested by the community" (RTBC) issues, which is done by the core committer team.
As we've experienced unprecedented contributor growth with the release of Drupal 8, so too has the growth of new ideas, bug fixes, and feature improvements. I'm pleased to announce that we are growing the core committer team in response to these increasing demands, by appointing two new Product Managers (Gábor Hojtsy and Roy Scholten) and a new front-end focused Framework Manager (Lauri Eskola) to the team.
Gábor started working on Drupal back in the 4.3 days, about 14 years ago. Using it for a Hungarian web development community site, he found some parts hard to translate, and immediately got involved to fix those bugs. He has wide ranging experience in managing core itself as the release manager of Drupal 6, setting up localize.drupal.org -- a unique community translations platform --, co-leading major international events such as DrupalCon Szeged and Drupal Dev Days Szeged, and working with 1600+ contributors in the Drupal 8 Multilingual Initiative to level up multilingual support in core. He received the Aaron Winborn award in 2016.
Gábor is looking forward to enable and unblock the community working on all kinds of user facing improvements from the smallest fixes to the larger revamps.
Roy has been working with Drupal for over 10 years. Since bootstrapping the Drupal UX team in 2007 he has consistently focused on making Drupal easier to understand and use. He started contributing with his user interface work for the Views and Panels contributed modules. During the development of Drupal 7 he helped make big usability improvements happen in the D7UX project. These efforts made him a top 30 contributor to Drupal 7 core and he has been a core “usability maintainer” since then.
He collaborated on the redesign of major parts of Drupal 8 and helped define the process for adding big new features to new releases of Drupal 8. He’s a regular speaker at DrupalCons and local events, was part of the Drupal.org Content Working Group advising on an improved content strategy for drupal.org and likes to rewrite your interface texts.
Roy will focus on helping people decide which features and improvements to work on and supporting those design and development efforts that will make Drupal easier to understand, learn and use.
Lauri has been working with Drupal for almost nine years. He is one of the Drupal 8 Theme API maintainers, and he was listed as a top 30 contributor to Drupal 8.
During the last four years, Lauri has made efforts around cleaning up markup and creating the Classy base theme, making improvements to the theme system to improve theming experience, and helping to fix some of the security criticals related to the theme system that were blocking Drupal 8's release. He is also passionate about improving the user experience, and have helped the UX team to implement changes to Drupal’s user interfaces.
Lauri's primary goal is to help user-facing improvements take place. He will also pay attention to enabling improvements to underlying theming systems.
Welcome to the team! :-)
What if we tell you that you can boost your Drupal website's user activity without much effort? Consider implementing voting and rating features: we all love expressing our opinion and pushing the button. The following mini-guide will show you 7 Drupal modules that will help you with that: Voting API, Fivestar and several more. See the full set here.
Staying true to Drupal’s water theme, DrupalCon Baltimore and our partner hotel, Baltimore Hilton, are located in the fun Inner Harbor where you can stroll from the Baltimore Convention Center to restaurants, shopping, and educational destinations like the famous Baltimore Aquarium, USS Constellation, and the Maryland Science Museum. And, the hotels we chose are perfect hubs connecting you to a rewarding DrupalCon and culture experience.
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
Industry Pages Launched
After a great deal of preparation, user research, and content development we've launched the first three 'Drupal in your Industry' pages. These first three pages highlight the power of Drupal in Media and Publishing, Higher Education, and Government. Each of these pages uses geo-targeted content to reach audiences in: the Americas; Europe, the Middle East, and Africa; and the Asia Pacific, Australia and New Zealand regions.
These pages are targeted at evaluators of Drupal in these specific industries. From our research, we've found that these evaluators typically have Drupal on their short list of technology choices, but are not familiar with how a complete solution is built on Drupal, and they're eager to see success stories from their industry peers.
We'll be expanding on this initiative with additional industry pages as time goes on.
Project Application Revamp
In February we completed phases 1 and 2 of the Project Application Process Revamp. This has meant polishing up the security advisory coverage messages that are provided on project pages, adding a new field for vetted users to opt-in to advisory coverage for their projects, and adding security advisory coverage information to the updates xml served from Drupal.org. With these issues complete we'll be able to move forward with Phase 3 (opening the project promotion gates) and Phase 4 (improving code quality signals and incentivizing peer review) as we roll into March.
[Author's note] The project application revamp hit a major milestone in early March with the completion of Phase 3. Now, any user who has accepted the git terms of service may now promote sandbox projects to full projects with releases, and the application process has been re-purposed for vetting users who want the ability to opt into security advisory coverage for their projects. Look for more information in our upcoming March post.
2017 Community Elections are Live
On February 1 we opened self-nominations for one of the two community-at-large seats on the Drupal Association Board of Directors. At the time of this post, self-nominations have closed and now it's time to vote!.
Each year we make incremental improvements to the elections process. This year we've allowed each candidate to present a short 'statement of candidacy' video - and we've updated the ballot to allow easy drag-and-drop ranking of candidates.
Voting closes on March 18th, so make sure to vote soon!
Documentation polish, and new "call-out" templates
As the migration of content into the new documentation system continues, we've continued to polish and improve the tools. In February we made a few small improvements including: help text for maintainers and fixes for links to the discuss page in email notifications. We also made one large improvement: Call-out templates for highlighting warning information or version-specific notes within a documentation page. These templates are available using the CKEditor Templates button when editing any documentation page.
The documentation editor may select from the 'Warning note' template, which will highlight cautionary information in a visually distinct orange section on the page, or the 'Version-specific note' template, which allows users to highlight information that may only be relevant to a specific minor release of Drupal.
Here are two examples of what the call-outs will look like to a documentation reader.
Coding standards testing
DrupalCI continues to accelerate the pace of Drupal development as we make the system more efficient and add new features. In February we enhanced the coding standards testing that was added DrupalCI in January. Using PHPCodeSniffer, ESlint, and CSSlint coding standards results are available in the test results' Build Artifacts directory, including automatically generated patches to fix found issues. We've also begun displaying summary information about coding standards testing on Drupal.org test results. Again we'd like to thank community contributor mile23 for his work on this feature.
More useful error output
We also made DrupalCI's error output more detailed, to make it more immediately clear to developers what the issue with a particular patch might be. Developers will now see messages on the test result bubbles, for example a 'patch failed to apply' error rather than a generic 'CI error' message.
Contrib Documentation Migration
We want to continue to encourage Project maintainers to create documentation guides on their projects using the new documentation content types. Maintainers can then migrate their old documentation content into these new guides, or create new documentation pages. For more information about this process, please consult our guide to contrib documentation.
Help port Dreditor features to Drupal.org
Are you a Drupal.org power user who relies on Dreditor? Markcarver is currently leading the charge to port Dreditor features to Drupal.org, and invites anyone interested in contributing to join him in #dreditor on freenode IRC or the Dreditor GitHub.Infrastructure
Special note: Drupal Association seeks Infrastructure Services vendor
We'd also like to announce a Request for Information. The Drupal Association seeks an infrastructure services vendor to help us manage the underlying infrastructure that supports Drupal.org, our sub-sites, and the services we maintain. Our internal engineering team will continue to manage the sites and services themselves, while this vendor will help us with systems administration, virtual machine management, monitoring and pager responsibilities, disaster recovery, etc.
For more details about this request for information, please see our post on the Association blog.
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. If you would like to support our work as an individual or an organization, consider becoming a member of the Drupal Association. Follow us on Twitter for regular updates: @drupal_org, @drupal_infra
March 9, 2017
The Drupal Association seeks a Infrastructure Services vendor to manage critical infrastructure for the open-source Drupal project. While internal Drupal Association staff will continue to manage the sites and services that the Drupal Association maintains, we will rely on this partner to maintain the underlying infrastructure. We are interested both in partners who offer comprehensive datacenter and infrastructure services, as well as partners who would offer systems administration consulting on our existing hardware.
If your organization is interested in receiving the full Request for Proposals(RFP), please submit a letter of interest to the Drupal Association at email@example.com.
In your letter of interest, please include a brief summary of your organization's experience in managing enterprise infrastructure for Drupal and non-Drupal sites and services at scale, as well as your key team members Drupal.org profile links. Based on demonstrated experience a small selection of vendors will be sent the full RFP.
We request that all interested parties submit their letters of interest by March 24th, 2017.
About the Drupal Association
The Drupal Association is a non-profit organization—US 501(c)(3)—dedicated to helping the open source Drupal project flourish. Drupal powers millions of websites and software applications, from personal blogs to the largest enterprises, media publishers, universities and government agencies.
The Drupal Association provides the support, infrastructure, and funding to: grow the Drupal community, support online collaboration on the software at https://www.drupal.org, and produce and host DrupalCon events and other events around the world. Funds to support these programs come from memberships, sponsorships, and donations. To learn more about the Drupal Association and its mission, visit https://drupal.org/association/.
Proposals to improve the Drupal contribution process have been heavily debated for the last few years.
Until now, the only thing everyone could agree on was the current process was broken.
Currently, many submitted modules are hung out to dry, because very few people have time or energy to fight through the submission process. You are lucky if you get your module accepted within 6 months. Many developers have waited much longer.
We were astonished to learn that our theme, called Breeze, was the first theme project to complete the approval process in 2016. And it was published in September! There were no new theme contributors for the vast majority of 2016.
Fortunately, big changes are finally about to come to the approval process for code on Drupal.org.
User roles are one of the things that is usually dealt with only while developing the website from scratch or when adding new features. Since standardization is the key to consistent results and more streamlined development process, you should have some sort of a strategy when it comes to user roles.
The fun is where the Drupalers are. Stay with us at the partner hotel - Hilton Baltimore - to network and socialize after sessions end. You’re likely to run into an old Drupal friend at the Lobby Bar or meet the person who can answer your Drupal question in the Coffee Bean & Tea Leaf. And, it’s close to the Baltimore Convention Center - Only a 3 minute walk.
As you may know, Drupal 6 has reached End-of-Life (EOL) which means the Drupal Security Team is no longer doing Security Advisories or working on security patches for Drupal 6 core or contrib modules - but the Drupal 6 LTS vendors are and we're one of them!
Today, there is a Highly Critical security release for the Services module to fix a Remote Code Execution (RCE) vulnerability.
The Services module provides a standardized solution for building API's so that external clients can communicate with Drupal.
The module accepts user submitted data in PHP's serialization format ("Content-Type: application/vnd.php.serialized") which can lead to arbitrary remote code execution.
This vulnerability is mitigated by the fact that an attacker must know your Service Endpoint's path, and your Service Endpoint must have "application/vnd.php.serialized" enabled as a request parser.
See the security advisory for Drupal 7 for more information.
Here you can download the Drupal 6 patch.
NOTE: there's a pre-existing, unfixed security issue in the Drupal 6 version of Services from 2013 (see SA-CONTRIB-2013-051 - Services - Cross site request forgery (CSRF)), so using Services in Drupal 6 isn't recommended in general, however, that issue is much less critical than the one announced today.
If you have a Drupal 6 site using the Services module, we recommend you update immediately, or disable the Services module entirely.
If you'd like all your Drupal 6 modules to receive security updates and have the fixes deployed the same day they're released, please check out our D6LTS plans.
Note: if you use the myDropWizard module (totally free!), you'll be alerted to these and any future security updates, and will be able to use drush to install them (even though they won't necessarily have a release on Drupal.org).
Not even three months into 2017, and already two industry articles have appeared that claim that this is "the Year of Decoupled."
If so, this is propitious development for Drupal, and the Acquia Developer Center. Because we've been publishing "decoupled"-related (AKA "headless," AKA "API-First") thinking for a while now.
Wouldn't it make sense to start organizing it into one stream? That's what we thought.
So here's our first installment of a blog series that will point to some of the best thinking on decoupled in general, and decoupled Drupal in particular.Tags: acquia drupal planet
DrupalCon prides itself on its diversity, which comes in many forms, including all the nationalities that are represented. We recognize that there is lack of clarity around the recent U.S. immigration changes, which can make international travel to our event challenging.
To help our international attendees, we created the following list of things to know as you plan your travel.
Given the uncertainty, contact your local U.S. consular office for more information about your travel to the U.S.
Drupal 7's Features module was a complicated way to export configuration - Drupal 8's Configuration Management makes everything much simpler. Let's break it down.
See how a custom module in Drupal 8 leverages data visualization with D3.