drupal.rss.xml - sfeed_tests - sfeed tests and RSS and Atom files
(HTM) git clone git://git.codemadness.org/sfeed_tests
(DIR) Log
(DIR) Files
(DIR) Refs
(DIR) README
(DIR) LICENSE
---
drupal.rss.xml (277587B)
---
1 <?xml version="1.0" encoding="utf-8"?>
2 <rss version="2.0" xml:base="https://www.drupal.org" xmlns:dc="http://purl.org/dc/elements/1.1/">
3 <channel>
4 <title>Drupal.org</title>
5 <link>https://www.drupal.org</link>
6 <description>Come for the software, stay for the community
7 Drupal is an open source content management platform powering millions of websites and applications. It’s built, used, and supported by an active and diverse community of people around the world.</description>
8 <language>en</language>
9 <item>
10 <title>Ministry of the Interior of the State of North Rhine-Westphalia</title>
11 <link>https://www.drupal.org/case-study/ministry-of-the-interior-of-the-state-of-north-rhine-westphalia</link>
12 <description><div class="field field-name-field-mainimage field-type-image field-label-hidden"><div class="field-items"><div class="field-item even"><img src="https://www.drupal.org/files/styles/case588x306/public/puplicplan_screenshot.jpg?itok=v1d4ZLIH" width="588" height="306" alt="New website of the Ministry of the Interior of the State of North Rhine-Westphalia based on nrwGOV" /></div></div></div><div class="field field-name-field-link field-type-link-field field-label-above"><div class="field-label">Completed Drupal site or project URL:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="https://www.im.nrw/">https://www.im.nrw/</a></div></div></div><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p>Websites for public administration are associated with very special requirements for the content management system, for example with regards to privacy and accessibility. With deGov, publicplan GmbH responds precisely to these requirements and offers the federal, state and local authorities corresponding services based on open source software. On behalf of d-NRW AöR, publicplan has created a system tailored to the requirements of the state of NRW: nrwGOV. The foundation for this was the open source software deGov. The relaunch of the website for the North Rhine-Westphalian Ministry of the Interior was the first major project to be built using nrwGOV. An advantage from which both the users of the open source solution deGov and the state of North Rhine-Westphalia should benefit: The nrwGOV system developed in cooperation with d-NRW AöR is available to all public institutions in the state. Further developments that are useful to general web projects and not specific to the state NRW are fed back into the open source core deGov and are thus available to the entire community.</p></div></div></div></description>
13 <pubDate>Mon, 14 Sep 2020 08:55:04 +0000</pubDate>
14 <dc:creator>Anna Küchler</dc:creator>
15 <guid isPermaLink="false">3170781 at https://www.drupal.org</guid>
16 <comments>https://www.drupal.org/case-study/ministry-of-the-interior-of-the-state-of-north-rhine-westphalia#comments</comments>
17 </item>
18 <item>
19 <title>Molson Coors</title>
20 <link>https://www.drupal.org/case-study/molson-coors</link>
21 <description><div class="field field-name-field-mainimage field-type-image field-label-hidden"><div class="field-items"><div class="field-item even"><img src="https://www.drupal.org/files/styles/case588x306/public/Molson%20Coors%202.png?itok=GU_AKbEE" width="588" height="306" alt="Molson Coors" /></div></div></div><div class="field field-name-field-link field-type-link-field field-label-above"><div class="field-label">Completed Drupal site or project URL:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="https://www.carling.com/age-gate">https://www.carling.com/age-gate</a></div></div></div><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p>A multinational brewing company, formed in 2005 by the merger of Molson of Canada, and Coors of the United States, Molson Coors is the world's seventh-largest brewer by volume. The company is headquartered in Denver and has more than 17,000 employees.</p>
22 <p>Molson Coors faced a number of challenges in its redesign. Time-to-market was a concern, as its previous web platform made it difficult for content editors to create new pages. The new platform also needed the ability to create new templates and mini-sites on-the-go. And a fixed launch date—designed to launch prior to corresponding television advertisements going live—increased the pressure to get things done on time. </p></div></div></div></description>
23 <pubDate>Tue, 11 Aug 2020 15:13:56 +0000</pubDate>
24 <dc:creator>LisaKretsch</dc:creator>
25 <guid isPermaLink="false">3164617 at https://www.drupal.org</guid>
26 <comments>https://www.drupal.org/case-study/molson-coors#comments</comments>
27 </item>
28 <item>
29 <title>Drupal Launches Newest Version of the CMS Already Powering Top Organizations Around The World</title>
30 <link>https://www.drupal.org/about/in-the-news/blog/drupal-launches-newest-version-of-the-cms-already-powering-top-organizations</link>
31 <description><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p><strong id="docs-internal-guid-edf0e26e-7fff-1fac-4158-6ab05a33754e">PORTLAND, Ore. June 3, 2020—</strong><a href="https://www.drupal.org/why-drupal" rel="nofollow">Drupal</a>, the most powerful enterprise open source content management system, is launching the latest—and most comprehensive—upgrade to its popular software today.</p>
32 <p>Drupal 9 comes with even more of the cutting-edge features that Drupal developers and users love. One out of every 30 websites in the world including Lufthansa, the CDC National Prevention Information Network, the European Commission, Médecins Sans Frontières/Doctors Without Borders, NASA, GRAMMYs/Recording Academy and Stanford University trust Drupal as the platform for their ambitious digital experiences.</p>
33 <h2>Drupal 9 - Continuous innovation in technology and user experience</h2>
34 <p>The updated version delivers powerful new features and an enhanced user experience. These features empower Drupal’s vision for the next generation of the web and include: </p>
35 <ul><li><strong>Dramatically easier tools</strong>— a new layout builder, WYSIWYG media management system and content workflow tools make Drupal much easier to use. It enables users to take advantage of Drupal's robust technical architecture more easily than ever before. </li>
36 <li><strong>Continuous innovation</strong>—powerful new features delivered continuously, keeping Drupal at the cutting edge of the web. </li>
37 <li>E<strong>asiest upgrade in a decade</strong>—and Drupal’s commitment to easy upgrades in the future means never having to worry about a major replatforming to stay up to date. </li>
38 </ul><blockquote><p>One of the key reasons Drupal has been successful is we have always made big, forward-looking changes,” says Dries Buytaert, founder and project lead of Drupal. “As a result, Drupal is one of very few CMS platforms that has stayed relevant for 20 years." </p>
39 </blockquote>
40 <p>One of Drupal’s key users says they depend on Drupal’s easy-to-use interface to keep their content up-to-date—even when their developers aren’t immediately available. <br />
41 </p>
42 <p>In a case study about how the <a href="https://www.drupal.org/case-study/aclu-partners-with-tag1-to-raise-most-ever-120m-in-donations-at-mission-critical-moments" rel="nofollow">ACLU uses Drupal</a>, the ACLU team says, "With Drupal's new capabilities to create and administer content, including robust media support ...[and] full layout control, <em>without the aid of developers</em>, ... [Drupal] empowered the ACLU to be more dynamic and responsive to external events." <br />
43 </p>
44 <p>While this new version makes it easier for non-developers to contribute to dynamic web platforms, it also continues to advance the underlying technology at the forefront of digital experiences—enabling developers to build the next generation of the web.</p>
45 <p>"Drupal's API-first architecture puts it years ahead of competitors as a decoupled or headless framework,” says Tim Lehnen, chief technology officer for the Drupal Association. “Drupal can serve as the content hub for rich experiences built with the latest technologies, including modern javascript frameworks like React, Angular, or Vue, or even with emerging channels like digital assistants and AR/VR applications." <br />
46 </p>
47 <p>Buytaert says a key focus was making the process of upgrading as easy as possible for its users. </p>
48 <p>"Drupal's innovation has only accelerated since the release of Drupal 8 four years ago,” says Buytaert. “Historically, major upgrades have been costly. With Drupal 9 we wanted to innovate quickly and provide an easy upgrade path from Drupal 8. We did exactly that! The upgrade from Drupal 8 to Drupal 9 is the easiest major upgrade in the last 10-plus years."</p>
49 <h2>Powered by a global community</h2>
50 <p>Drupal is a true open source project, leveraging the expertise of tens of thousands of developers around the world. Drupal has earned a reputation for security, performance, accessibility and scalability that is unparalleled in the CMS ecosystem. Drupal's core strength has always been its ability to manage structured data—written once, and reused anywhere—and the Drupal community has doubled down on this with Drupal 9. </p>
51 <h2>To upgrade or get started</h2>
52 <p>If you’re ready to experience Drupal, discover how easy it is to build or integrate your digital portfolio by visiting <a href="https://drupal.org/9" rel="nofollow">drupal.org/9</a>. </p>
53 <p>Need some help onboarding with Drupal or building a digital experience from scratch? There are <a href="https://www.drupal.org/drupal-services" rel="nofollow">many agencies in the Drupal community</a> that would be happy to help.</p>
54 <h2>About Drupal and the Drupal Association</h2>
55 <p>Drupal is the open source content management software used by millions of people and organizations around the world, made possible by a community of 100,000-plus contributors and enabling more than 1.3 million users on Drupal.org. The Drupal Association is the non-profit organization dedicated to accelerating the Drupal software project, fostering the community, and supporting its growth.</p>
56 <p><strong id="docs-internal-guid-ccdaa1aa-7fff-6d69-6238-d539a54c691c">### </strong></p>
57 <p><strong id="docs-internal-guid-ccdaa1aa-7fff-6d69-6238-d539a54c691c">For more information contact Heather Rocker, <a href="mailto:heather@association.drupal.org" rel="nofollow">heather@association.drupal.org</a></strong></p></div></div></div></description>
58 <pubDate>Wed, 03 Jun 2020 17:00:00 +0000</pubDate>
59 <dc:creator>hrocker</dc:creator>
60 <guid isPermaLink="false">3143949 at https://www.drupal.org</guid>
61 <comments>https://www.drupal.org/about/in-the-news/blog/drupal-launches-newest-version-of-the-cms-already-powering-top-organizations#comments</comments>
62 </item>
63 <item>
64 <title>Drupal Community Raises $500,000 to Keep World's Leading Independent Open Source Content Management System Nonprofit Thriving</title>
65 <link>https://www.drupal.org/about/in-the-news/blog/drupal-community-raises-500000-to-keep-worlds-leading-independent-open-0</link>
66 <description><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p>FOR IMMEDIATE RELEASE</p>
67 <p><strong>PORTLAND, Ore., May 11, 2020</strong>—The CDC, NIH, and Medecins Sans Frontieres/Doctors Without Borders—among many others—depend on the power of Drupal, the largest independent open source content management system, to keep their websites dynamic and secure. But the cancellation of the Drupal Association’s annual keystone fundraising event—originally scheduled for May 2020—put the nonprofit’s finances in jeopardy.</p>
68 <blockquote><p> <br />
69 COVID-19 has delivered a particularly hard economic hit to non-profits, and the Drupal Association (DA) is no exception,” says Heather Rocker, executive director of the DA. “When we made the decision to cancel DrupalCon North America 2020 for the safety of our attendees, the next question was how to recover those funds so we could continue operations for our community of millions around the world.”</p>
70 </blockquote>
71 <p> <br />
72 Enter #DrupalCares, a global fundraiser conceived with the hopes of bridging the significant funding gap left as a result of the pandemic. While the campaign had a strong start, what really put the fundraising into overdrive was the <a href="https://www.drupal.org/association/drupal-cares-challenge" rel="nofollow">#DrupalCares match challenge</a>, a <a href="https://dri.es/pledging-100000-usd-to-support-the-drupal-association" rel="nofollow">$100,000 matching grant for individual contributions</a> funded by Drupal creator Dries Buytaert and his wife Vanessa. Then a <a href="https://www.drupal.org/association/blog/drupalcares-thanks-to-drupal-businesses-you-can-now-triple-your-impact" rel="nofollow">coalition of Drupal businesses</a> came together to match those contributions again—bringing the potential impact up to $300,000. These contributions, together with the contributions from Drupal service providers and end-users, accelerated the campaign dramatically.<br />
73 <br /><strong>As of today, May 11, 2020, #DrupalCares has raised $500,000, meeting its 60-day goal in just over 30 days. Nearly 150 businesses and organizations, along with over 2,000 individual donors and members donated, to reach the goal in record time. </strong><br />
74 <br />
75 "I'm in awe of how quickly the Drupal community rallied to raise funds for the Drupal Association,” said Dries Buytaert, founder of Drupal. “With this fundraising campaign behind us, the Drupal Association can refocus on key initiatives such as the Drupal 9 launch next month.</p>
76 <p>“DrupalCon has been an important reason for Drupal's success,” said Buytaert. “Even though we'll be gathering virtually this summer, I'm very excited that DrupalCon will live on. I'd like to thank everyone who helped us reach our goals—the Drupal community is stronger than ever."<br />
77 <br />
78 While the nonprofit Drupal Association was impacted by COVID-19, the Drupal ecosystem remains strong. As Buytaert wrote in March, <a href="https://dri.es/is-open-source-recession-proof" rel="nofollow">open source software seems to be recession-proof.</a><br />
79 <br />
80 “Open Source has grown to be more secure, more flexible, and more stable than ever before,” said Buytaert. “Today, the benefits of Open Source are even more compelling than during past recessions.”<br />
81 <br />
82 Open source contribution also provides an excellent opportunity for individuals to expand their skills—or even re-skill—during this time of record unemployment. Drupal has demonstrated once again that the power of community and the open source model make projects like Drupal the best possible investment in uncertain times.<br />
83 <br />
84 In addition to the #DrupalCares campaign, the majority of original <a href="https://events.drupal.org/global2020/sponsors" rel="nofollow">DrupalCon 2020 sponsors</a> allowed the Association to retain their sponsorship dollars as the event prepares to shift to its first-ever virtual <a href="https://events.drupal.org/global2020" rel="nofollow">DrupalCon Global 2020</a>. <br />
85 <br />
86 “Like so many organizations, we had to pivot quickly on a major keystone event, but we also had to pivot quickly on a product launch, as we were planning to introduce Drupal 9, our first major software upgrade in almost five years, at DrupalCon,” says Rocker. “DrupalCon was originally scheduled to host approximately 3,000 attendees in May 2020 in Minneapolis, so we didn’t have time for a ‘wait and see’ approach. I’m grateful to a solid, creative Association staff and the extended leadership of our Drupal community who are willing to do whatever it takes to make this event a success.”<br />
87 <br />
88 “Additionally, Drupal 9 is scheduled to launch on schedule in early June, which is a testament to how dedicated this community is to continuing to be trailblazers—even now, when a delay caused by these world events would have been no surprise,” said Rocker.<br />
89 <br />
90 The #DrupalCares fundraising campaign remains active through May 31, 2020. To learn more about Drupal or make a donation, visit <a href="http://www.drupal.org" rel="nofollow">www.Drupal.org</a>.<br />
91 <br />
92 About Drupal and the Drupal Association<br />
93 Drupal is the open source content management software behind millions of websites and applications, boasting a community of 46,000-plus developers and more than 1.3 million users on Drupal.org. The Drupal Association is the non-profit organization dedicated to accelerating the Drupal software project, fostering the community, and supporting its growth.<br />
94 <br />
95 ###<br />
96 <br />
97 For more information contact Heather Rocker, <a href="mailto:heather@association.drupal.org" rel="nofollow">heather@association.drupal.org</a></p></div></div></div></description>
98 <pubDate>Mon, 11 May 2020 19:08:11 +0000</pubDate>
99 <dc:creator>hrocker</dc:creator>
100 <guid isPermaLink="false">3135589 at https://www.drupal.org</guid>
101 <comments>https://www.drupal.org/about/in-the-news/blog/drupal-community-raises-500000-to-keep-worlds-leading-independent-open-0#comments</comments>
102 </item>
103 <item>
104 <title>Contributing to Drupal: A ‘someday’ hopeful makes his first Core commit with community help</title>
105 <link>https://www.drupal.org/blog/contributing-to-drupal-a-someday-hopeful-makes-his-first-core-commit-with-community</link>
106 <description><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><div class="center">
107 <img alt="Pekens' photo" height="390" src="/files/pekens1_0.jpg" width="400" /><br /><br /></div>
108 <p>Pekens Antoine (<a href="https://www.drupal.org/u/pekens" rel="nofollow">pekens</a>, pictured here) was doing research on content management systems while running a digital marketing agency, and was exploring Drupal, which he viewed as a “well-thought-out system being developed by a lot of smart people,” and with that he “wasn’t sure if a contribution from myself could make a difference.”</p>
109 <p>But Drupal and its community held his interest, and in 2018, he attended his first Drupal event—DrupalCon Nashville. He went on to participate in two Drupal Camps as well thus far. It’s been these in-person experiences that left a lasting impression.</p>
110 <p>“It’s a great feeling to walk up to the maintainer of a project you use every single day and ask them a question,” he says.</p>
111 <p>This feeling was amplified at the New Jersey Drupal Camp afterparty earlier this year, when he met people and they all spontaneously opened up their computers and worked on a Drupal Core issue that had come up in conversation.</p>
112 <p>“I realized that I could probably learn a lot about Drupal from the people at the table,” [who he offers a ‘shout out’ to: @traviscarden, @bnjmnm, @tedbow, and @jrockowitz], “and I wanted to do more than build sites with Drupal—I wanted to help build Drupal. They were kind enough to show me their process.</p>
113 <p>Travis Carden notes: “What I thought was particularly compelling about his story was the fact that he didn't previously view himself as a potential Drupal contributor. He said, ‘I would like to <em>someday</em> be able to contribute.’ But he was eagerly received by the group of us.” </p>
114 <p>Their conversation continued on Slack:</p>
115 <blockquote><p><a href="https://app.slack.com/team/U5BKZ1RQ9" rel="nofollow"><strong>Travis Carden</strong></a> I don't know if you already saw it or not, but your Drupal core patch got committed the same night:<a href="https://www.drupal.org/project/drupal/issues/3110525" rel="nofollow"> https://www.drupal.org/project/drupal/issues/3110525</a> It now appears on your profile:<a href="https://www.drupal.org/u/pekens" rel="nofollow"> https://www.drupal.org/u/pekens</a> Congratulations, and welcome to the ranks of Core contributors! 😀</p>
116 </blockquote>
117 <blockquote><p><a href="https://app.slack.com/team/U6FDJ3DN2" rel="nofollow"><strong>Pekens Antoine</strong></a> Thanks Travis! It feels good, even if I’m just a typo fixer for now 😆. Gotta start somewhere. I really appreciated you guys taking the time to share some knowledge! 🙏</p>
118 </blockquote>
119 <div class="center">
120 <img alt="Travis holding a laptop, telling a story to the camera." height="483" src="/files/Screen%20Shot%202020-03-17%20at%204.02.19%20PM_0.png" width="400" /><br />
121 Travis Carden (<a href="https://www.drupal.org/u/traviscarden" rel="nofollow">traviscarden</a>) sharing this story with Ryan Aslett (<a href="https://www.drupal.org/u/mixologic" rel="nofollow">mixologic</a>) at DrupalCamp NJ.<br />
122 <br /></div>
123 <p>Carden said the whole process happened quickly: “He went from zero to contributor in about half an hour with commit credit the same day.”</p>
124 <p>Now Antoine has plans to continue his contribution, keeping those like himself in mind. “Using Drupal on a daily basis allows me to have some insight that new Drupal users may not have. I often forget that. There’s always something that you can teach or share, even if you only know a little bit. I’ll be keeping an eye out for opportunities to share and collaborate more on Drupal projects in the future.”</p>
125 <p>Antoine reflects on the overall meaning of both choosing Drupal and becoming a Drupal contributor: “Trying to understand every single piece of code for any project its size is impossible to do overnight. The Drupal community understands this. We’re able to grow individually and collectively by sharing and collaborating on the pieces we do understand.”</p></div></div></div></description>
126 <pubDate>Tue, 17 Mar 2020 20:13:13 +0000</pubDate>
127 <dc:creator>Angie Marsh</dc:creator>
128 <guid isPermaLink="false">3120389 at https://www.drupal.org</guid>
129 <comments>https://www.drupal.org/blog/contributing-to-drupal-a-someday-hopeful-makes-his-first-core-commit-with-community#comments</comments>
130 </item>
131 <item>
132 <title>I'm supporting open source: Drupal Association membership drive</title>
133 <link>https://www.drupal.org/association/blog/im-supporting-open-source-drupal-association-membership-drive</link>
134 <description><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p>Today, we're launching a membership drive. You can help by sharing our message and showing your support.</p>
135 <p>Help grow membership by <a href="https://www.drupal.org/association/campaign/certificate-2020" rel="nofollow">visiting our campaign page</a> and <a href="https://www.drupal.org/association/membership/campaign/share" rel="nofollow">sharing with your network</a>. We're supporting the global Drupal project and community with your help! Together, we make the open source community stronger.</p>
136 <h2>Get your 2020 Membership Certificate</h2>
137 <p>Active members can <a href="https://www.drupal.org/association/support/membership-benefits" rel="nofollow">download a personalized certificate</a> now, and one way to contribute to this membership drive is to print out your certificate (or display it on a screen) and share your selfie with us. Tag with #joinDrupalAssoc #OpenSource, #supportOpenSource to show you care.</p>
138 <p id="docs-internal-guid-3b502bc8-7fff-70c5-0d8e-eeee8317fbe6">Our heartfelt thanks to you—members and supporters—for contributing and participating as individuals and organizations.</p>
139 <div class="note-tip">
140 <p id="docs-internal-guid-4c8ff18c-7fff-da59-fc1c-e69b67709eda">Ready to help? Share a post like this or craft your own. </p>
141 <ul><li>
142 <p><a href="https://twitter.com/intent/tweet?text=I'm%20part%20of%20a%20global%20open%20source%20project%20as%20a%20%40DrupalAssoc%20member.%20Join%20with%20me%3A%20https%3A//www.drupal.org/association/campaign/certificate-2020%20%23SupportOpenSource" rel="nofollow">Tweet</a></p>
143 </li>
144 <li>
145 <p><a href="https://www.linkedin.com/shareArticle?mini=true&amp;url=https%3A//www.drupal.org/association/campaign/certificate-2020&amp;title=&amp;summary=I'm%20part%20of%20a%20global%20open%20source%20project%20as%20a%20%40DrupalAssoc%20member.%20Join%20with%20me.%20%23SupportOpenSource&amp;source=%40DrupalAssoc" rel="nofollow">Post on LinkedIn</a></p>
146 </li>
147 </ul></div></div></div></div></description>
148 <pubDate>Wed, 11 Mar 2020 20:59:53 +0000</pubDate>
149 <dc:creator>lizzjoy</dc:creator>
150 <guid isPermaLink="false">3119260 at https://www.drupal.org</guid>
151 <comments>https://www.drupal.org/association/blog/im-supporting-open-source-drupal-association-membership-drive#comments</comments>
152 </item>
153 <item>
154 <title>Be an ambassador!</title>
155 <link>https://www.drupal.org/association/blog/be-an-ambassador</link>
156 <description><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p>Drupal is often spoken about as far more than an open source project, because our global community is vibrant and passionate; a model for other projects to learn from and emulate. There are many ways to be a Drupal ambassador: by mentoring others, by helping people answer why they should use Drupal, and why they should contribute. In addition, I have a few ideas on ways you could be an ambassador for Drupal by sharing about yourself with the global community. By participating, you help put a story behind the people of Drupal, and you show the broader community <a href="https://www.drupal.org/association/individual-membership" rel="nofollow">why the Drupal Association needs support</a>. We'd love to have you involved!</p>
157 <h2><a href="https://www.drupal.org/association/member-testimonials" rel="nofollow">Give a testimonial</a></h2>
158
159 <p><img alt="" height="533" src="/files/member_because_2019_surabhi.jpg" width="400" /><br />
160 ".... because of it's wonderful community which has such inspiring contributors spread around the world. Being a member fills me with immense positive energy :)" — Surabhi Gokte (surabhi-gokte)<br /></p>
161 <p><a href="https://www.drupal.org/association/member-testimonials" rel="nofollow">Get inspiration</a> from the testimonials and share your own.</p>
162 <h2>Be featured on Drupal.org</h2>
163 <p>We're running the banner ad on Drupal.org - visible only to users who don't have an <a href="https://www.drupal.org/association/individual-membership" rel="nofollow">active membership</a>. You may see these banners throughout the year (usually for a week-long run) if you visit without being logged in. To participate, <a href="https://www.drupal.org/user/1184486/contact" rel="nofollow">email me</a> or chat on Slack (lizzjoy). </p>
164
165 <p><img alt="We rely on Drupal. Our team feels responsible to contribute back to the project and participate in its growth. - Baddy Breidert, Drupal Association Board and Co-Founder of 1xINTERNET." height="115" src="/files/mem_banner_baddy_2019-10-29.png" width="401" /><br />
166 Drupal.org banner featuring Baddý Breidert (baddysonja).<br /></p>
167
168 <p><img alt="Thanks to DrupalCon for a boost in motivation. I joined the Drupal Association because being a member in the first place fosters contribution in other areas of the community, too. - Christian Schnabl, Founder &amp; Developer, 42robots." height="154" src="/files/mem_banner_Christian_2019-11-26.png" width="400" /><br />
169 Drupal.org banner featuring Christian Schnabl (snable).<br /></p>
170 <h2>MemberMondays</h2>
171
172 <p><img alt="Monica S. Flores is organizing DrupalCamp Hawaii 2020 and is learning and sharing more ways to foster inclusion in technology with @drupaldiversity. She's been a pianist since childhood, and is interested in learning how to do music composition. Say hi to her at DrupalCon! #MemberMondays" height="332" src="/files/memberMondays_LinkedIn_post.png" width="401" /><br />
173 From this month's #MemberMondays.<br /></p>
174 <p>This month, we've launched social posts about a different member each week. We're calling it #MemberMondays. You can share about yourself in <a href="https://assoc.drupal.org/membermondays-questionnaire" rel="nofollow">this questionnaire</a>.</p>
175 <p>I hope you participate— it would be wonderful to share about you with the global community. If you are interested, but feel you don’t have time or are hesitating, let us know.</p></div></div></div></description>
176 <pubDate>Tue, 21 Jan 2020 19:43:14 +0000</pubDate>
177 <dc:creator>lizzjoy</dc:creator>
178 <guid isPermaLink="false">3107850 at https://www.drupal.org</guid>
179 <comments>https://www.drupal.org/association/blog/be-an-ambassador#comments</comments>
180 </item>
181 <item>
182 <title>Drupal 8.8.0 is available</title>
183 <link>https://www.drupal.org/blog/drupal-8-8-0</link>
184 <description><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><h2>What’s new in Drupal 8.8.0?</h2>
185 <p>The last normal feature release of Drupal 8 includes a stable Media Library as well as several improvements to workspaces and migrations. The new experimental Claro administration theme brings a fresh look to site management. This is also the first release to come with native Composer support.</p>
186 <!--break--><p><a class="link-button" href="/project/drupal/releases/8.8.0">Download Drupal 8.8.0</a></p>
187 <h3>Stable Media Library</h3>
188 <p>The Media Library module allows easy reuse of images, documents, videos, and other assets across the site. It is integrated into content forms and seamlessly fits into CKEditor. You can upload media right from the library and even reuse a combination of uploaded and existing media. Media Library was previously included with Drupal core as a beta experimental module.</p>
189 <p><iframe allow="autoplay; encrypted-media" allowfullscreen="" frameborder="0" height="349" src="https://www.youtube-nocookie.com/embed/3qwvBuSApro" title="A demo of WYSIWYG image embedding in Drupal 8.8" width="620"></iframe></p>
190 <h3>New experimental administration theme</h3>
191 <p>The Claro administration theme was added to Drupal core with <a href="https://www.drupal.org/core/experimental#beta">beta experimental stability</a>. The new theme is clean, accessible, and powerful. Administration pages are more touch-friendly, and color combinations and contrasts are more accessible.</p>
192 <p><iframe allow="autoplay; encrypted-media" allowfullscreen="" frameborder="0" height="349" src="https://www.youtube-nocookie.com/embed/-aFkS0_LEVs" title="An update on Drupal 8's new administration theme called Claro" width="620"></iframe></p>
193 <h3>Significant improvements to Workspaces</h3>
194 <p>It is now possible to define hierarchical workspaces (such as preparing a "New Year's" issue for a magazine under the "winter issue", while both receive changes to be deployed). Workspaces can now work with Content Moderation, and path alias changes can also be staged.</p>
195 <p><iframe allow="autoplay; encrypted-media" allowfullscreen="" frameborder="0" height="349" src="https://www.youtube-nocookie.com/embed/_51rAkhlvIo" title="Hierarchical workspaces in Drupal 8.8.0 demo by Dick Olsson" width="620"></iframe></p>
196 <h3>Native Composer support included</h3>
197 <p>Drupal 8.8.0 is the first release to include native Composer support without reliance on third-party projects to set up Drupal with its dependencies. <a href="https://www.drupal.org/docs/develop/using-composer/starting-a-site-using-drupal-composer-project-templates">New sites can be created using a one-line command</a>.</p>
198 <h3>Migration improvements</h3>
199 <p>The multilingual migration path is still experimental, but has received various updates. This includes handling of vocabulary language settings, term language information, and localization. Modules can now specify whether migrations provided by them are finished or not finished to help audit completeness of available migrations.</p>
200 <h3>New experimental Help Topics module</h3>
201 <p>The existing help system is module based, whereas users intend to complete tasks, not use modules. A new task-based Help Topics beta experimental module has been added to bring in-Drupal help to the next level.</p>
202 <h2>The way to Drupal 9</h2>
203 <p>Drupal 8.8 is the last minor release of Drupal 8 to include significant new features or deprecations prior to 9.0.0. The next (and final) minor release, 8.9, is planned to be a long-term support release that will include all the same changes as Drupal 9.0. It will not contain significant new features compared to 8.8.0, although existing experimental modules may become stable, and small API and UX improvements can still be added.</p>
204 <p>Drupal 8.9.0's planned release date is June 3, 2020, and our target release date for Drupal 9.0.0 is the same day. <a href="https://www.drupal.org/docs/9/how-to-prepare-your-drupal-7-or-8-site-for-drupal-9">Most Drupal 9 preparation steps can be done on your Drupal 8 site, custom code and contributed modules now</a>.</p>
205 <h2>What does this mean for me?</h2>
206 <h3>Drupal 8 site owners</h3>
207 <p>Update to 8.8.0 to continue receiving bug fixes and prepare for 9.0.0 (or 8.9.0). The next bug-fix release (8.8.1) is scheduled for January 8, 2020. (See the <a href="https://www.drupal.org/core/release-cycle-overview#windows">release schedule overview</a> for more information.) As of this release, sites on Drupal 8.6 will no longer receive security coverage. (Drupal 8.7 will continue receiving security fixes until June 3, 2020.)</p>
208 <p>Note that all Drupal 8.8.0 sites (new installs and updates) now require at least PHP 7.0.8.</p>
209 <p><a href="https://www.drupal.org/node/2700999">Updating your site</a> from 8.7.10 to 8.8.0 with <code class="language-php">update.php</code> is exactly the same as updating from 8.7.8 to 8.7.9. Drupal 8.8.0 also has updates to several dependencies. Modules, themes, and translations may need updates for these and other changes in this minor release, so test the update carefully before updating your production site. <a href="https://www.drupal.org/project/drupal/releases/8.8.0">Read the 8.8.0 release notes</a> for a full list of changes that may affect your site.</p>
210 <h3>Drupal 7 site owners</h3>
211 <p><a href="https://www.drupal.org/psa-2019-02-25">Drupal 7 is fully supported by the community until November 2021</a>, and will continue to receive bug and security fixes throughout this time. From November 2021 until at least November 2024, the <a href="https://www.drupal.org/project/d7es">Drupal 7 Vendor Extended Support program</a> will be offered by vendors.</p>
212 <p>The migration path for monolingual Drupal 7 sites is stable, as is the built-in migrationuser interface. For multilingual sites, most outstanding issues have been resolved. Please keep testing and reporting any issues you may find.</p>
213 <h3>Translation, module, and theme contributors</h3>
214 <p>Minor releases like Drupal 8.8.0 include backwards-compatible API additions for developers as well as new features.</p>
215 <p>Since minor releases are backwards-compatible, modules, themes, and translations that supported Drupal 8.7.x and earlier will be compatible with 8.8.x as well. However, the new version does include some changes to strings, user interfaces, <a href="https://www.drupal.org/core/d8-bc-policy">internal APIs</a> and API deprecations. This means that some small updates may be required for your translations, modules, and themes. <a href="https://www.drupal.org/project/drupal/releases/8.8.0">Read the 8.8.0 release notes</a> for a full list of changes that may affect your modules and themes.</p>
216 <p>This release has advanced the Drupal project significantly and represents the efforts of hundreds of volunteers and contributors from various organizations, as well as testers from the <a href="https://www.drupal.org/community#beta-test">Minor release beta testing program</a>. Thank you to everyone who contributed to Drupal 8.8.0!</p>
217 </div></div></div></description>
218 <pubDate>Wed, 04 Dec 2019 10:08:10 +0000</pubDate>
219 <dc:creator>Gábor Hojtsy</dc:creator>
220 <guid isPermaLink="false">3098650 at https://www.drupal.org</guid>
221 <comments>https://www.drupal.org/blog/drupal-8-8-0#comments</comments>
222 </item>
223 <item>
224 <title>Crack the ‘Giving Tuesday’ Code on December 3rd</title>
225 <link>https://www.drupal.org/association/blog/crack-the-giving-tuesday-code-on-december-3rd</link>
226 <description><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p id="docs-internal-guid-f88e7f42-7fff-d35b-4443-2aaf525efc9c"><img alt="Giving Tuesday icon logo globe with heart" class="right" height="200" src="/files/Global%20Logo_0.png" width="200" />Giving Tuesday (known online as <a href="https://www.givingtuesday.org" rel="nofollow">#GivingTuesday</a>) is the Tuesday after the Thanksgiving holiday in the United States, held on December 3, 2019. What began in the States has grown over the years into an international day dedicated to charitable giving at the beginning of the holiday season, whereby hundreds of millions of people give, collaborate and celebrate generosity.</p>
227 <p><em>Coincidentally, givingTuesday.org is built using Drupal! </em></p>
228 <p>At the Drupal Association, we’ve decided to participate for the first time this year. Knowing the Drupal Community likes to have fun and delve into challenges — such as the ever-popular Trivia Night held during DrupalCons — our staff collaborated to create a trivia challenge never before seen, with Drupal project and product questions, Association facts and more. </p>
229 <p>We challenge you to take the quiz on #GivingTuesday December 3rd, and to share with friends to see who can crack this code! <em>Note: Not a literal code!</em> Visit <a href="https://www.drupal.org/giving-tuesday-2019" rel="nofollow">Drupal.org/giving-tuesday-2019</a> on Tuesday for the link.</p>
230 <p>We’ll update the leaderboard and congratulate players throughout the day on December 3! </p>
231 <p>Thanks in advance for playing, and we encourage you to post your trivia score on social media; this may be our most challenging trivia game yet! </p>
232 <p>We hope you'll take a minute to support the Drupal Association and join/renew membership or donate on this international day of giving. At the end of Giving Tuesday, we’ll announce three leaderboard winners: who has won the trivia, who donated the most, and who referred the most new members. The top 10 winners shown on each leaderboard will be entered to win a handcrafted Drupal prize (<em>hint:</em> it might be pictured in this photo)! </p>
233 <p>#GivingTuesday</p>
234
235 <p><img alt="Opening reception with dasjo and lizzjoy in DrupalCon Seattle. photo by hussainweb" height="393" src="/files/46661625495_12c388c4f3_c.jpg" width="501" /><br /><em><a href="https://www.flickr.com/photos/hussainweb/46661625495/" rel="nofollow">photo from DrupalCon Seattle</a> opening reception by Hussain Abbas (hussainweb)</em><br /></p></div></div></div></description>
236 <pubDate>Wed, 27 Nov 2019 22:13:27 +0000</pubDate>
237 <dc:creator>lizzjoy</dc:creator>
238 <guid isPermaLink="false">3097186 at https://www.drupal.org</guid>
239 <comments>https://www.drupal.org/association/blog/crack-the-giving-tuesday-code-on-december-3rd#comments</comments>
240 </item>
241 <item>
242 <title>Drupal Business Survey 2019</title>
243 <link>https://www.drupal.org/association/blog/drupal-business-survey-2019</link>
244 <description><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p><em>This blog has been re-posted and edited with permission from <a href="https://oneshoe.com/blog/drupal-business-survey-2019-results-are-in" rel="nofollow">OneShoe's blog</a>. The following are results from the 2019 Drupal Business Survey conducted by One Shoe and Exove, in partnership with the Drupal Association.</em></p>
245 <p>The annual Drupal Business Survey is an initiative of Drupal agencies One Shoe and Exove, and was published in 2016 for the first time. The survey aims to gather valuable insights from Drupal business leaders to identify opportunities and challenges for the Drupal market. This year, the survey asked Drupal business leaders from all over the world about their experiences with selling Drupal projects, their vision on community contributions and their expectations toward Drupal 9.</p>
246 <p><strong>In total, 118 C-level Drupal agency leaders participated in the 2019 edition of the Drupal Business Survey. These leaders have a total of 118 offices, of which the majority (72 offices) are located in Europe and 36 in the United States.</strong></p>
247 <p class="center"><img alt="World map showing locations of survey respondents with green and red dots" height="368" src="/files/2019_business_survey_respondent_map.png" width="599" /></p>
248 <p>43% of the respondents are CEOs and 35.6% of the respondents are founders of Drupal businesses, mostly working at mid-size Drupal agencies with between 11 and 50 employees (33.9%). The majority of the companies have been in business for more than four years (89.8%).</p>
249 <h3>How is Drupal business doing?</h3>
250 <p>The news is positive for business – the Drupal project pipeline has grown or stayed at the same level as the previous year whilst the average deal size has increased. Drupal project win rates have stayed roughly at the same level and future of Drupal project pipeline is predicted steady based on this year’s responses.</p>
251 <p>Each year the respondents are asked about their Drupal project pipeline, average deal size and project win rate, as well as their expectations for next year. Half of the respondents said that their Drupal project pipeline grew and when compared to last years results, even more than expected. One third of the business leaders responded that their pipeline has stayed approximately the same and only 16.9% stated that their project pipeline shrank.</p>
252 <p>Average deal size has also grown, according to majority of the respondents (65%), and only about 7% answered that their deal size shrunk in 2018.</p>
253 <p class="center"><img alt="Drupal Project Pipeline pie chart - 17% shrank, 33% stayed the same, 50% grew" height="408" src="/files/2019_business_survey_drupal_project_pipeline_pie_chart.png" width="405" /></p>
254 <div>
255 <h3>Popular industries for Drupal projects</h3>
256 <p>Drupal is used for endless types of digital solutions: from easy-to-manage sites to large-scale portals and platforms. As a result, you can find Drupal projects in all kinds of industries. Each year the respondents of the Drupal Business Survey are asked about the type of projects they completed in the past year, and industries in which they use Drupal to create digital experiences.</p>
257 <p>Interestingly, this year the category 'Education' is added for the first time after respondents in the previous edition indicated they missed this category. Education is the most popular industry in which Drupal projects are implemented this year.</p>
258 <p class="center"><img alt="Top 5 industries in which Drupal clients operate - 66,1% education, 65,3% charities &amp; non-profit, 54,2% government &amp; public administration, 49,2% healthcare &amp; medicine, 47,5% arts &amp; culture" height="317" src="/files/2019_business_survey_top_5_industries_bar_graph.png" width="505" /></p>
259 <p>We asked this question also in previous years and when comparing results, we see some differences. Travel &amp; Tourism became a more popular industry in Drupal project implementation with 330% growth when compared to the 2018 Drupal Business Survey results. Furthermore, Telecom, Sports and Logistics &amp; Support grew their popularity whilst Consumer Electronics, Consultancy and Construction decreased popularity in Drupal projects implementation according to the survey data.</p>
260 <p><strong>Top 3 industries which became more popular compared to 2018:</strong></p>
261 <ul><li>Travel &amp; Tourism (+330%)</li>
262 <li>Telecom (+77.78%)</li>
263 <li>Sports (+77.78%)</li>
264 <li>Logistics &amp; Support (+72.73%)</li>
265 </ul><p><strong>Top 3 industries with fewer Drupal projects compared to 2018:</strong></p>
266 <ul><li>Consumer Electronics (-59.09%)</li>
267 <li>Consultancy (-37.74%)</li>
268 <li>Construction (-37.50%)</li>
269 </ul><h3>‘Contributing to Drupal should be a no-brainer’</h3>
270 <p>One of the distinguishing factors and forces behind Drupal's success is the large and active community. For a long time, the slogan for Drupal has been "Come for the software, stay for the community.” Dries Buytaert each year publishes the <a href="https://dri.es/who-sponsors-drupal-development-2019" rel="nofollow" target="_blank">‘Who sponsors Drupal development?’</a> report. According to the 2018–2019 edition, small-to-medium-sized Drupal businesses (fewer than 100 employees) contribute frequently, while larger full-service agencies are not actively contributing to Drupal.</p>
271 <p>According to the Drupal Business Survey, 111 out of the 118 businesses contribute to Drupal and only 7 businesses don’t. What’s the vision of Drupal’s agency leaders about the subject of contributing to Drupal? How do they contribute, and why (not)?</p>
272 <p class="center"><img alt=" 93 - development (contributing modules, patches, documentation or file bug reports), 64 - sponsoring events, 62 - organising events, 55 - marketing (helping get the word out about Drupal), 54 - user support (sharing what you know with other users), 48 - donations, 35 - improivng Drupal's documentation, 26 - translations, 21 - testing, 17 - design &amp; usability (contributing feedback to Drupal's usability), 10 - themes " height="271" src="/files/2019_business_survey_contributions_bar_graph.png" width="601" /></p>
273 <p>The Drupal businesses from the survey contribute in many different ways. It varies from non-technical contributions, like sponsoring events and organising events such as MeetUps and DrupalCamps, to improving Drupal’s documentation or development (contributing modules and patches). Reasons for contributing are, among others, because it feels like ‘the right thing to do’, because of branding and marketing reasons, or in order to give the developers a sense of the community:</p>
274 <p><em>“Drupal has given a lot to our company, so it is only fair to give back. Also, we see that the Drupal business community is not that well served, so it is an easy choice for us to contribute to (besides technical stuff).”</em></p>
275 <p><em>“Without contributions, the Drupal project wouldn't exist. It should be a no-brainer.”, </em></p>
276 <p><em>“ I wouldn't have made a career in Drupal if others wouldn't have contributed before; it's a give and take and everyone should do so.” </em></p>
277 <p><em>I believe in supporting the community that supports me and provides the basis for my income. Also, there are side-benefits to contributing. My contributions have helped me win clients.” </em></p>
278 <h3>Limited time and resources</h3>
279 <p>Even though the vast majority of agencies are aware of the importance of contributing to Drupal, they also face difficulties combining the pro-bono contributions with their day-to-day business. The analysis shows that those who don’t contribute are either sole entrepreneurs or are working at a Drupal company with more than 100 employees. Almost all respondents saying that their business doesn’t contribute, explain that the reason is that they don’t have the time and resources to do so: “In a resource limited business, contribution is difficult to balance with the bottom line. We do what we can. However, the teams are all encouraged to be vocal advocates of Drupal on all Social Media platforms, challenging misconceptions wherever they occur.” Someone else suggests: “Maybe introduce paid development for updating, testing and maintaining core and most used contributed modules.”</p>
280 <h3>Does size matter?</h3>
281 <p>When we compare the size of the Drupal companies with the kind of Drupal contributions, we see that:</p>
282 <ul><li>The larger the Drupal business is in terms of employees, the more often they financially support the Drupal project by – for example – sponsoring an event and/or making donations.</li>
283 <li>Also, larger Drupal businesses tend to contribute to developing (contributing modules, patches, documentation or bug reports) more than smaller ones.</li>
284 <li>The smaller the business, the more often they share knowledge with other users (User Support).</li>
285 <li>Except that, there is no significant difference between the size of the Drupal companies and other types of contributions they make to the Drupal project. All different sizes of organisations contribute in the form of translations, marketing, testing, and contributing to design &amp; usability.</li>
286 </ul><p class="center"><img alt="Line chart with how companies contribute by company size. " height="329" src="/files/2019_business_survey_contributing_ways_line_chart.png" width="599" /></p>
287 <h3>Businesses expect easier Drupal upgrades starting with D9</h3>
288 <p>Drupal 9 is targeted for release in June 2020. We asked the Drupal business leaders what their expectations are toward Drupal 9. The general trend among companies is ‘Finally no hard upgrade path anymore!’ One respondent says: ‘We hope the upgrade path will be smooth, and it will be easier to justify the investment of upgrading.’</p>
289 <p><em>“[I expect] it will become easier to do the operation things, as update core, modules etc. Better media handling and user interface, that it doesn't have this large jumps on functionality changes from one version to another - so the upgrades from 8 to 9, 9 to 10 and so on can go much much smoother than before.”</em></p>
290 <p><em>“[I expect] that we don’t have to reimplement all our customers solutions the way we had to from earlier solutions. I expect that when we have upgraded all our solutions to the latest version of Drupal 8.X, the upgrade to Drupal 9 needs to be smooth and without any major rewriting of code. When upgrading our ecommerce solutions from D6 -&gt; D7 and D7 -&gt; D8, it almost killed our business. We had to basically reimplement the solutions (not upgrade them) and the clients were not willing to pay the actual cost. So we had to invest a lot of money into those upgraded. We are not willing to do the same for D8 -&gt; D9.”</em></p>
291 <p>Business leaders also express their desire for a better interface and a UX enhancements: ‘I hope that D8 will provide a better admin UI and UX, and an improved preview mode.’ Another one says: ‘I hope for focus on the end user experience.’</p>
292 <p>The Drupal community has noted the user experience needs and there is a specific Admin UI modernisation strategic initiative going on – for more information, see <a href="https://www.drupal.org/about/strategic-initiatives/admin-ui-js" rel="nofollow" target="_blank">https://www.drupal.org/about/strategic-initiatives/admin-ui-js</a></p>
293 <p class="center"><img alt=" 32% easier upgrades, 12% better UX/UI, 10% no expectations, 9% other, 8% neutral/negative, 6% more/better functionalities, 4% good business opportunities, 4% increase in popularity, 4% better integrations, 2% losing business, 2% increased stability, 2% ignorance of the market, 2% headless opportunities, 2% just excited" height="561" src="/files/2019_business_survey_expectations_drupal_9_pie_chart.png" width="576" /></p>
294 <div>
295 <p>However, a number of owners also express their doubts. One respondent states:</p>
296 <p><em>“Many clients are still on Drupal 7 without a plan (or desire) for Drupal 8, there is some surprise that Drupal 9 is already on the way. Some may be waiting for Drupal 9 before moving anyway. The D7-D8 move is seen as such a big one that projects may come to a natural end or move away from Drupal before clients ever get to D8 or D9.”</em></p>
297 <p><em>“We think it will be hard to convince people to migrate from Drupal7 to Drupal9. On the other hand we think that project size will continue to grow.”</em></p>
298 <p>The comments about Drupal 7 show that the system is still in wide use and there is a threshold for the clients to upgrade to later versions. The updates have been laborious projects in the past, and now businesses expect this issue will be mitigated with the new release cycle and the release of Drupal 9.</p>
299 <h3>More ease of use of Drupal</h3>
300 <p>We asked the Drupal business leaders what developments they hope to see in the coming years regarding Drupal in general.</p>
301 <p class="center"><img alt=" 26% improved dev/editor/user experience, 10% more/better features, 9% other, 7% ease of updates, 7% more visibility of Drupal, 6% easier development, 6% integration with other services, 5% increased stability, 4% I am happy, 4% suitable for small/mid-budget projects, 4% personalization, 2% easier to contribute, 2% growing the community, 2% headless opportunities, 2% marketing automation capabilities, 2% e-commerce capabilities" height="608" src="/files/2019_business_survey_development_hopes_pie_chart.png" width="594" /></p>
302 <p>The answers given by the respondents were varied, ranging from making Drupal development easier to making Drupal more suitable (again) for small and mid-size projects. However, most of the answers were about the user-friendliness of Drupal: 26% of all the answers had to do with Drupal’s user experience for developers as well as administrators, editors, content managers and end users. Or, as one respondent stated it: “Continued ease-of-use for both semi-technicals/semi-professionals as well as professional developers and UX and UI designers.”</p>
303 <p><em>“A better out-of-the box user experience (in terms of design, media handling &amp; editing, for example). Improved admin experience - e.g. react-based admin interface.”</em></p>
304 <p><em>“I hope that Drupal is going to have a better and more modern UI/UX for the clients, ease to integrate Drupal as API first/headless, from a DX perspective continue to use OOP and modern methods. Ease to do functional tests. Ease to update modules/core with automatic process.”</em></p>
305 <p>The Drupal Business Survey results indicate that businesses are eagerly waiting for the first versions with a radically improved admin user interface. This is something that has already been taken into account; see the Drupal community’s strategic initiative.</p>
306 <p>The second thing that the respondents mention is that they hope the features and capabilities of Drupal will continue to improve or expand (10% of the answers):</p>
307 <p><em>“Continue to develop more content-friendly toolkits/features, expand upon configuration management processes/workflows”</em></p>
308 <p><em>“We see more out of the box features in the platform and more tools suited for enterprises.”</em></p>
309 <p><em>“Closer to a microservices CMS, allowing me to pick the bits I need/want.”</em></p>
310 <h3>Conclusion</h3>
311 <p>The survey shows that Drupal business is doing well, with slight growth in project pipeline and more substantial growth in average deal size. Drupal is used for various types of digital solutions. However the most popular industry for Drupal project implementation is Education based on this year’s survey results. Other top industries include Charities &amp; Non-profit and Government &amp; Public Administration. The fastest growing industry in terms of the number of Drupal implementations this year is Travel &amp; Tourism, with a growth of 330%, followed by Telecom (+77,78%), Sports (+77,78%) and Logistics &amp; Support (+72,73%).</p>
312 <p>Contributions to Drupal have remained active, as 111 out of the 118 businesses taking part in the survey report that they contribute to Drupal. The most common ways of contributing include development as well as sponsoring and organising events. The report shows that those who cannot contribute to Drupal are either sole entrepreneurs or are working at a company with over 100 employees, facing challenges in combining pro bono work with day-to-day business.</p>
313 <p>Drupal business leaders share various hopes on the development of Drupal. The most common ones include improved dev/editor/user experience, more/better features and ease of updates. Expectations towards the upgrade to Drupal 9 are mostly optimistic, the only thing that businesses shared was their concerns that customers may want to move away from Drupal because of the difficult upgrade from 7 to 8.</p>
314 <p>As one of the business leaders states: <em>“Agency leaders play a key role in growing the Drupal community. This survey provides a great way for us to start working together. Next, we need to take the results and come up with strategies for growth!”</em> The findings of this survey – and possible strategies for growth – were discussed at the Drupal CEO Dinner during DrupalCon Amsterdam 2019, where more than 60 Drupal Business leaders from all over the world came together.</p>
315 </div>
316 <p>-----</p>
317 <p>See <a href="https://www.drupal.org/association/blog/drupal-business-survey-2018" rel="nofollow">the 2018 survey results</a>.</p>
318 <p>For more information, please contact Janne Kalliola (<a href="https://www.drupal.org/u/jannekalliola" rel="nofollow">jannekalliola</a>) or Michel van Velde (<a href="https://www.drupal.org/u/michel-van-velde" rel="nofollow">michel-van-velde</a><a href="mailto:michel.vanvelde@oneshoe.com" rel="nofollow">)</a>.</p>
319 <h4><strong>About Exove</strong></h4>
320 <p>Exove delivers digital growth. We help our clients to grow their digital business by designing and building solutions with agile manner, service design methodologies, and open technologies. Our clients include Sanoma, Fiskars, Neste, Informa, Trimble, and Finnlines. We serve also start-up companies, unions and public sector. Exove has offices in Helsinki, Oulu and Tampere, Finland; Tallinn, Estonia; and London, United Kingdom. For more information, please visit <a href="http://www.exove.com" rel="nofollow">www.exove.com</a>.</p>
321 <h4><strong>About One Shoe</strong></h4>
322 <p>One Shoe is an integrated advertising and digital agency with more than 10 years experience in Drupal. With more than 40 specialists, One Shoe combines strategy, UX, design, advertising, web and mobile development to deliver unique results for international clients like DHL, Shell, Sanofi, LeasePlan, MedaPharma and many more. For more information, please visit <a href="http://www.oneshoe.com" rel="nofollow">www.oneshoe.com</a>.</p>
323 <h4><strong>About the Drupal Association</strong></h4>
324 <p>The Drupal Association is the not-for-profit organization dedicated to fostering and supporting the Drupal project, the community and its growth. The Drupal Association helps the global Drupal community with funding, infrastructure, education, promotion, distribution and online collaboration at Drupal.org. For more information, please visit <a href="http://drupal.org/association/" rel="nofollow">drupal.org/association</a><em>.</em></p>
325 </div></div></div></div></description>
326 <pubDate>Wed, 20 Nov 2019 19:57:38 +0000</pubDate>
327 <dc:creator>lizzjoy</dc:creator>
328 <guid isPermaLink="false">3095752 at https://www.drupal.org</guid>
329 <comments>https://www.drupal.org/association/blog/drupal-business-survey-2019#comments</comments>
330 </item>
331 <item>
332 <title>Meet us at Booth 3 at DrupalCon Amsterdam</title>
333 <link>https://www.drupal.org/association/blog/meet-us-at-booth-3-at-drupalcon-amsterdam</link>
334 <description><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p><img alt="Delona at Drupal Association table at GovCon 2019" class="right" height="399" src="/files/delona_association_booth_at_govcon_2019.png" width="400" /></p>
335 <p>Our staff will be at <em>Booth 3</em> ready to talk with you about the Drupal community, how you can get more involved as a contributor, and to hear about your needs. </p>
336 <p>Make sure you....</p>
337 <p>✓ pick up some Drupal stickers</p>
338 <p>✓ show your support by signing up for membership or partner programs</p>
339 <h2><img alt="DrupalCon sticker - be inspired" class="right" height="282" src="/files/drupalcon_nashville_be_inspired.png" width="300" />Session highlights</h2>
340 <ul><li>Tuesday at 16h15, in G107, attend the Drupal Association Townhall with our Executive Director Heather Rocker (<a href="https://www.drupal.org/u/hrocker" rel="nofollow">hrocker</a>), CTO Tim Lehnen (<a href="https://www.drupal.org/u/hestenet" rel="nofollow">hestenet</a>), and our Board Chair Adam Goodman (<a href="https://www.drupal.org/u/adamgoodman" rel="nofollow">adamgoodman</a>). We'll be taking questions and diving into topics important to the community.</li>
341 <li>Wednesday at 11h30, in G107, we're holding our public board meeting. All are welcome to attend!<br />
342 </li>
343 <li>Also on Wednesday, if you're curious about what the Drupal.org Engineering Team is working on, come to the Drupal.org Infrastructure Update session in G103 at 17h15.</li>
344 </ul><p>See you soon!</p></div></div></div></description>
345 <pubDate>Fri, 25 Oct 2019 19:05:17 +0000</pubDate>
346 <dc:creator>lizzjoy</dc:creator>
347 <guid isPermaLink="false">3090216 at https://www.drupal.org</guid>
348 <comments>https://www.drupal.org/association/blog/meet-us-at-booth-3-at-drupalcon-amsterdam#comments</comments>
349 </item>
350 <item>
351 <title>Drupal Association collaborates on new, long-awaited tech initiative as featured on TagTeamTalk</title>
352 <link>https://www.drupal.org/association/blog/drupal-association-collaborates-on-new-long-awaited-tech-initiative-as-featured-on</link>
353 <description><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p>The Drupal Association collaborated on Automatic Updates, one of the <a href="https://drupal.org/about/strategic-initiatives" rel="nofollow">Drupal Core Strategic Initiatives</a> that was funded by the European Commission. We are excited to partner with <a href="https://www.mtech-llc.com/" rel="nofollow">MTech</a>, <a href="https://tag1consulting.com/" rel="nofollow">Tag1 Consulting</a>, and the <a href="https://ec.europa.eu/" rel="nofollow">European Commission</a> FOSSA program on this new initiative and share information with you about its features.</p>
354 <p>Automatic Updates has three components.</p>
355 <h2>Public safety messaging</h2>
356 <p>This feature pulls a feed of alerts from Drupal.org directly into Drupal's administrative interface. This helps ensure that critical <a href="https://www.drupal.org/security/psa" rel="nofollow">Public service announcements (PSA)</a> or <a href="https://www.drupal.org/security" rel="nofollow">Security Advisories</a> (SA) from the <a href="https://www.drupal.org/drupal-security-team/" rel="nofollow">Drupal security team</a> will be seen directly by site owners. </p>
357 <ul><li>
358 <p>This provides yet another communication mechanism before an update so site owners can verify they are ready for an upcoming update, before it lands.</p>
359 </li>
360 <li>
361 <p>The feed of alerts comes directly from the feed of PSAs and SAs that the security team and release managers are already producing. </p>
362 </li>
363 <li>
364 <p>This will vastly increase the ability of the Drupal project to get the word out about critical and highly critical updates - ensuring the community can respond fast. </p>
365 </li>
366 </ul><h2>Readiness checks, or “Pre-flight” checks</h2>
367 <p>These automated and extensible readiness checks are built into the Automatic Updates system to verify that a site doesn't have any blockers that would prevent it from being updated.</p>
368 <ul><li>
369 <p>These checks are slated to run at least every 6 hours on a site via Drupal Cron and will inform site owners if they are ready to auto update their site.</p>
370 </li>
371 <li>
372 <p>Examples of the readiness checks include:</p>
373 <ul><li>
374 <p>Is the site is running on a read-only file system?</p>
375 </li>
376 <li>
377 <p>Have any files included in the update been modified from what they should be? </p>
378 </li>
379 <li>
380 <p>Does the site still need to run database updates, etc.? </p>
381 </li>
382 </ul></li>
383 </ul><p>There’s about 8 or 9 of these readiness checks and some are warnings (Cron isn’t running frequently enough to automatically update the site in a timely manner) and some are errors (the file system is read-only). Warnings won’t stop automatic updates, but errors will.</p>
384 <h2>In place updates</h2>
385 <p>Finally, the key pillar of the automatic updates feature is the update itself. Drupal.org generates a signed and secure package of files which can be overlaid atop the existing site files in order to apply the update. </p>
386 <ul><li>
387 <p>This update package is downloaded as a signed zip file from Drupal.org. The automatic updates module on the site then compares the signature of the zip file using drupal/php-signify, which is based on BSD’s Signify and libsodium to verify the package.</p>
388 </li>
389 <li>
390 <p>It then proceeds to backup the files about to be updated and updates the site.</p>
391 </li>
392 <li>
393 <p>If all goes well, the site is upgraded. If something fails, the backup is restored.</p>
394 </li>
395 <li>
396 <p>Many workflows are supported and you can customize how the updates are performed. Updates can flow through your CI/CD system, be staged for review and approval, and or automatically go live.</p>
397 </li>
398 </ul><p>In the past few weeks, the Drupal Association has been invited to participate in TagTeamTalks, a new recorded talk series about various tech projects supporting the Drupal project. This bi-weekly format provides real-time shared collaboration and informative discussions. </p>
399 <p><a href="http://tag1.com/TagTeamTalks" rel="nofollow">TagTeamTalk</a> launched its <a href="https://tag1consulting.com/blog/drupal-automatic-updates-tagteamtalk-003" rel="nofollow">webinar focused on <strong>Automatic Updates</strong></a><strong> </strong>this week.<strong> </strong>The group dives deep into the nuts and bolts of Drupal's groundbreaking Automatic Updates feature, and the strategic initiative sponsored by the <a href="https://association.drupal.org" rel="nofollow">Drupal Association</a>, <a href="https://www.mtech-llc.com" rel="nofollow">MTech</a>, <a href="https://tag1.com/" rel="nofollow">Tag1 Consulting</a>, and the <a href="https://ec.europa.eu/" rel="nofollow">European Commission</a><strong>.</strong> Guests include <strong>Preston So </strong>(<a href="https://www.drupal.org/u/prestonso" rel="nofollow">prestonso</a>)<strong>,</strong> Contributing Editor at Tag1 and Moderator of the TagTeamTalks; <strong>Michael Meyers </strong>(<a href="https://www.drupal.org/u/michaelemeyers" rel="nofollow">michalemeyers</a>), Managing Director of Tag1; <strong>Lucas Hedding</strong> (<a href="https://www.drupal.org/u/heddn" rel="nofollow">heddn</a>), Senior Architect and Data and Application Migration Expert at Tag1; <strong>Fabian Franz</strong> (<a href="https://www.drupal.org/u/fabianx" rel="nofollow">Fabianx</a>), Senior Technical Architect and Performance Lead at Tag1; and <strong>Tim Lehnen</strong> (<a href="https://www.drupal.org/u/hestenet" rel="nofollow">hestenet</a>) CTO at the Drupal Association. <a href="https://tag1consulting.com/blog/drupal-automatic-updates-tagteamtalk-003" rel="nofollow"><strong>Read the TagTeamTalks blog.</strong></a></p>
400 <p><strong>“</strong>Content marketing is one of the most effective ways to promote your brand and capabilities - it has been a really powerful approach for the organizations that I’ve worked for,” said Michael. “The goal is to give our team an opportunity to talk about the cool things they’re working on and excited about and to share it with people. It helps get the word out about the latest developments in the open source communities we contribute to, and it promotes Tag1’s expertise - it helps us recruit new hires, and drives new business.” </p>
401 <p>Meyers is the Managing Director of Tag1, and has been involved with the Drupal community for over 15 years. He was Founder and CTO of the first venture backed drupal based startup, CTO of the first Top 100 website on Drupal, and VP of Developer Relations at Acquia before joining Tag1. “The great thing about TagTeamTalks is that it doesn’t take a tremendous amount of effort or energy. Our engineers are subject matter experts. We decide on a topic for the week, spend 15 minutes brainstorming a rough outline as a guide, and then record the talk. We don’t want to be rehearsed. The conversation is what makes it dynamic and enjoyable for us to do, and for people to listen to. And, the team loves it because they want to talk about what they are working on, and this format doesn’t take a lot of time away from what they enjoy doing most - writing code.” </p>
402 <p>Hedding is one of the top 20 most active contributors to Drupal 8, and is also the Drupal Core Migrate Sub-system Maintainer, a core contribution mentor, and a D.O. project application reviewer. “Auto Updates has long been one of the most requested Drupal features, it is a capability the platform really needs that will help everyone using Drupal. Now that the alpha is available, we need to early adopters to start using it, we need feedback so we can continue to improve it. We also need to get more people involved in development, and we need to raise more money from organizations to support the project - it might sound like a simple feature, but it is actually really complex and requires a lot of effort. TagTeamTalks are a great way to get the word out and to enlist support from the Drupal community.”</p>
403 <p>Lucas added, “The European Commission provided generous funding for this initiative. The focus has been exclusively or largely around the European Commission’s features and functionality. The funding is running out very soon. There is a need for other people to help continue to build Automatic Updates by adding the features they need with their developers or by providing funding.” </p>
404 <p>“It is critical for us to spread the message and make that call to action; that this is a community-driven effort and that without continued community support, it is not going to be as successful or as robust in the timeframe that we would like,” said Meyers.</p>
405 <p>The first year of funding from the European Commission provided for readiness checking, delivery of update 'quasi-patches,’ and a robust package signing system. The focus of this first phase of the Automatic Updates initiative has been on support for security updates in particular. </p>
406 <p>In the second phase, as yet unfunded, we hope to extend this foundational work in the following ways:</p>
407 <ul><li>
408 <p>Provide more robust composer support. The first phase of the automatic updates project should be compatible with composer-ready sites, but as the site’s composer.json file and vendor directory of a site change from the default, then more controls and though need to be implemented. </p>
409 </li>
410 <li>
411 <p>Create an A/B front-end controller for the site being updated to further increase our confidence in the success of the update, allow for additional post-update testing and provide an easy mechanism to roll-back the update. This is also when updates will be able to move into Drupal core from the contrib project.</p>
412 </li>
413 <li>
414 <p>Expand to more types of updates (particularly further support for contrib updates), and also handle multiple updates in a row, for sites that are several versions behind. </p>
415 </li>
416 </ul><p>To accomplish all of this, we will continue to seek more funding and more partners. </p>
417 <p>“I’m looking forward to seeing where this goes now that we have the first release out, ” said Hedding. “ There’s a larger community needed to get this initiative completed.”</p>
418 <p>The initial alpha version of the <a href="https://drupal.org/project/automatic_updates" rel="nofollow">Automatic Updates</a> module can be tested by the community right now. The plan is to: demonstrate Automatic Updates at DrupalCon Amsterdam this month, complete the scope of the funded work by the European Commission by the end of this year, and stabilize Automatic Updates by DrupalCon Minneapolis in May 2020. </p>
419 <p>“The Automatic Updates initiative is designed to reduce the friction in keeping a Drupal site secure and up-to-date. The team behind the initiative is architecting a robust system, secure by design, and building components that can be shared with the broader PHP community,” said Tim Lehnen.</p>
420 <p>Many thanks to <a href="https://www.mtech-llc.com/" rel="nofollow">MTech</a>, <a href="https://tag1consulting.com/" rel="nofollow">Tag1 Consulting</a>, and the <a href="https://ec.europa.eu/" rel="nofollow">European Commission</a> FOSSA program for funding this initiative. The <a href="https://www.drupal.org/association" rel="nofollow">Drupal Association</a> is proud to be a part of this initiative.</p></div></div></div></description>
421 <pubDate>Thu, 03 Oct 2019 16:40:36 +0000</pubDate>
422 <dc:creator>cbern</dc:creator>
423 <guid isPermaLink="false">3085565 at https://www.drupal.org</guid>
424 <comments>https://www.drupal.org/association/blog/drupal-association-collaborates-on-new-long-awaited-tech-initiative-as-featured-on#comments</comments>
425 </item>
426 <item>
427 <title>#DigitalClimateStrike and Drupal.org - thinking of all our futures</title>
428 <link>https://www.drupal.org/association/blog/digitalclimatestrike-and-drupalorg-thinking-of-all-our-futures</link>
429 <description><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p>You will notice that, <a href="https://www.nbcnews.com/news/us-news/global-climate-strike-which-companies-are-closing-their-doors-n1055621">along with thousands of websites around the world</a>, Drupal.org posted a banner message this week declaring we are opting in to a global <a href="https://digital.globalclimatestrike.net/">Digital Climate Strike</a> on 20th September.</p>
430 <blockquote class="twitter-tweet"><p>Will <a href="https://twitter.com/drupal?ref_src=twsrc%5Etfw">@drupal</a> website add the <a href="https://twitter.com/hashtag/DigitalClimateStrike?src=hash&amp;ref_src=twsrc%5Etfw">#DigitalClimateStrike</a> banner? <a href="https://twitter.com/BaluErtl?ref_src=twsrc%5Etfw">@baluertl</a> requested it and mocked up a visual... <a href="https://t.co/XcIj9Gf173">https://t.co/XcIj9Gf173</a> <a href="https://t.co/Zl0ctyc7G6">pic.twitter.com/Zl0ctyc7G6</a></p>
431 <p>— ClimateAction.tech (@climateActTech) <a href="https://twitter.com/climateActTech/status/1174418534308438018?ref_src=twsrc%5Etfw">September 18, 2019</a></p>
432 </blockquote>
433 <p>Of course, because Drupal.org is an essential service to over a million websites around the world, we have to be sure that we still allow them all to continue to access resources here. As such, the full page banner that will appear on websites on the 20th September will be configured to allow visitors to cancel it, should they need to.</p>
434 <p>Fundamentally, the Drupal Association wants to be a good steward of the environment and recognizes the impact that technology has on environmental issues. We are committed to exploring ways for the Drupal project to reduce its carbon footprint and to become a more eco-friendly platform. Today, we stand with others in the technology industry to educate and inform the general public about some of the ways that the tech industry can support environmental causes.</p>
435 <p>If the environmental sustainability of Drupal websites is a subject as close to your hearts as it is to ours, you might like to know that recently a <a href="https://drupal.slack.com/app_redirect?channel=sustainable">#sustainable</a> Slack channel was created for discussion on the topic.</p>
436 </div></div></div></description>
437 <pubDate>Thu, 19 Sep 2019 18:12:20 +0000</pubDate>
438 <dc:creator>rachel_norfolk</dc:creator>
439 <guid isPermaLink="false">3082412 at https://www.drupal.org</guid>
440 <comments>https://www.drupal.org/association/blog/digitalclimatestrike-and-drupalorg-thinking-of-all-our-futures#comments</comments>
441 </item>
442 <item>
443 <title>My first event: DrupalCamp Atlanta</title>
444 <link>https://www.drupal.org/association/blog/my-first-event-drupalcamp-atlanta</link>
445 <description><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p>Many thanks to Kaleem Clarkson (<a href="https://www.drupal.org/u/kclarkson" rel="nofollow">kclarkson</a>) and his team for organizing a great DrupalCamp Atlanta. I had a time of learning, connecting and being inspired!</p>
446 <p><img alt="Doug Vann, Carole Bernard, and Rudy Dodier in a selfie" height="427" src="/files/20190913_drupalcamp_atlanta_cbern_dougvann_rudydodier.jpg" width="500" /></p>
447 <p>I started my day at DrupalCamp Atlanta by participating in the workshop “Introduction to Drupal,” led by longtime Drupal community member Doug Vann (<a href="https://www.drupal.org/u/dougvann" rel="nofollow">dougvann</a>). Joining me was Rudy Dodier, from Platform.sh. Doug covered everything from the history of Drupal, to setting up a basic website to how the word “system” in Content Management System can be an acronym for: <strong>S</strong>aves <strong>Y</strong>ou <strong>S</strong>ome <strong>T</strong>ime <strong>E</strong>nergy <strong>M</strong>oney.</p>
448 <p>I took copious notes, as I continue to connect the dots to the power of the Drupal project - to how it is leading a digital transformation across industries. I absorbed it all, and was eager to learn more. I met other developers and individuals who contribute so much to the Drupal project and to the Drupal community. From my conversations with Ray Saltini (<a href="https://www.drupal.org/u/rgs" rel="nofollow">rgs</a>) and Mike Anello (<a href="https://www.drupal.org/u/ultimike" rel="nofollow">ultimike</a>) to Suzanne Dergacheva (<a href="https://www.drupal.org/u/pixelite" rel="nofollow">pixelite</a>), I was struck by the level of commitment demonstrated by the community. You'll get a sense for this in Suzanne's <a href="https://docs.google.com/presentation/d/14DtGtEYJU0OgDNxjim8icVT0p-duCbJoZ-i9FQwZyqc/edit#slide=id.g62b60846ef_0_1758" rel="nofollow">slides for her Growing the Drupal Community talk</a>.</p>
449 <p><img alt="Suzanne Dergacheva, Heather Rocker, and Carole Bernard standing together" height="375" src="/files/2019_pixelite_hrocker_cbern_at_drupalcamp_atlanta.jpg" width="500" /></p>
450 <p>Heather Rocker (<a href="https://www.drupal.org/u/hrocker" rel="nofollow">hrocker</a>) also attended and presented at the Career Fair. She spoke about the importance of the Association’s initiative on Diversity, Equity &amp; Inclusion and the benefits that come from actively recruiting and welcoming new individuals (especially those from underrepresented communities) to lend their skills to the project.</p>
451 <p>I realize the extensive number of stories that are within this vast and passionate community, and I am excited to promote and talk about them. I am looking forward to being a communications and marketing advocate for the Drupal community, the Drupal project and the Drupal Association. From the specific needs of developers, to the importance of broadening our audience, to the necessity of career fairs to bring students on the Drupal train, and to the need for marketing to grow Drupal adoption, I heard and learned so much in a short visit to Atlanta. But, what impressed me as much as the day was the contagious enthusiasm for what the community is doing and for what it can accomplish!</p>
452
453 <p><img alt="Slide showing faces of the 8 Atlanta Camp Leaders - ATL Board Members - Kaleem Clarkson, Brandon Firfer, Sarah Golden, Adam Kirby, Trish Smith, Nikki Smith, Dominic Thomas, and Advisor Dave Terry" height="454" src="/files/2019_drupalcamp_atlanta_leadership.jpg" width="680" /><br />
454 The DrupalCamp Atlanta Leadership Team, without whom the event wouldn't have been possible!<br /></p>
455 <blockquote><p><img alt="ATL team onsite together doing a power pose." height="270" src="/files/2019_dc_atl_organizers_team.jpg" width="360" /></p>
456 <p>Thanks to everyone who came out for <a href="https://twitter.com/hashtag/DCATL?src=hash&amp;ref_src=twsrc%5Etfw" rel="nofollow">#DCATL</a> this year! We loved meeting y'all. Let's continue to grow and support the <a href="https://twitter.com/drupal?ref_src=twsrc%5Etfw" rel="nofollow">@drupal</a> community! <a href="https://t.co/q9IgHjVRkA" rel="nofollow">pic.twitter.com/q9IgHjVRkA</a></p>
457 <p>— DrupalCamp Atlanta (@DrupalCamp_ATL) <a href="https://twitter.com/DrupalCamp_ATL/status/1172955093441925122?ref_src=twsrc%5Etfw" rel="nofollow">September 14, 2019</a></p>
458 </blockquote></div></div></div></description>
459 <pubDate>Wed, 18 Sep 2019 17:17:05 +0000</pubDate>
460 <dc:creator>cbern</dc:creator>
461 <guid isPermaLink="false">3082111 at https://www.drupal.org</guid>
462 <comments>https://www.drupal.org/association/blog/my-first-event-drupalcamp-atlanta#comments</comments>
463 </item>
464 <item>
465 <title>Who sponsors Drupal development? (2018-2019 edition)</title>
466 <link>https://www.drupal.org/blog/who-sponsors-drupal-development-2018-2019-edition</link>
467 <description><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p><em>This blog has been re-posted and edited with permission from <a href="https://dri.es/who-sponsors-drupal-development-2019">Dries Buytaert's blog</a>.</em></p>
468 <p><em>An in-depth analysis of how Drupal's development was sponsored between July 1, 2018 and June 30, 2019.</em></p>
469 <p>The past years, I've examined Drupal.org's contribution data to understand who develops Drupal, how diverse the Drupal community is, how much of Drupal's maintenance and innovation is sponsored, and where that sponsorship comes from.</p>
470 <p>You can look at the <a href="https://dri.es/who-sponsors-drupal-development">2016 report</a>, the <a href="https://dri.es/who-sponsors-drupal-development-2017">2017 report</a>, and the <a href="https://dri.es/who-sponsors-drupal-development-2018">2018 report</a>. Each report looks at data collected in the 12-month period between July 1st and June 30th.</p>
471 <p>This year's report shows that:</p>
472 <ul><li>Both the recorded number of contributors and contributions have increased.</li>
473 <li>Most contributions are sponsored, but volunteer contributions remains very important to Drupal's success.</li>
474 <li>Drupal's maintenance and innovation depends mostly on smaller Drupal agencies and Acquia. Hosting companies, multi-platform digital marketing agencies, large system integrators and end users make fewer contributions to Drupal.</li>
475 <li>Drupal's contributors have become more diverse, but are still not diverse enough.</li>
476 </ul><h3 id="0">Methodology</h3>
477 <h4>What are Drupal.org issues?</h4>
478 <p>"Issues" are pages on Drupal.org. Each issue tracks an idea, feature request, bug report, task, or more. See <a href="https://www.drupal.org/project/issues">https://www.drupal.org/project/issues</a> for the list of all issues.</p>
479 <p>For this report, we looked at all Drupal.org issues marked "closed" or "fixed" in the 12-month period from July 1, 2018 to June 30, 2019. The issues analyzed in this report span Drupal core and thousands of contributed projects, across all major versions of Drupal.</p>
480 <h4>What are Drupal.org credits?</h4>
481 <p>In the spring of 2015, after <a href="https://dri.es/a-method-for-giving-credit-to-organizations-that-contribute-code-to-open-source">proposing initial ideas for giving credit</a>, Drupal.org added the ability for people to <a href="https://www.drupal.org/drupalorg/blog/a-guide-to-issue-credits-and-the-drupal.org-marketplace">attribute their work in the Drupal.org issues</a> to an organization or customer, or mark it the result of volunteer efforts.</p>
482 <p><img alt="Example issue credit on drupal org" height="135" src="https://www.drupal.org/files/screenshot_66.jpg" width="632" /></p>
483 <p><em>A screenshot of an issue comment on Drupal.org. You can see that jamadar worked on this patch as a volunteer, but also as part of his day job working for TATA Consultancy Services on behalf of their customer, Pfizer.</em></p>
484 <p>Drupal.org's credit system is truly unique and groundbreaking in Open Source and provides unprecedented insights into the inner workings of a large Open Source project. There are a few limitations with this approach, which we'll address at the end of this report.</p>
485 <h3 id="1">What is the Drupal community working on?</h3>
486 <p>In the 12-month period between July 1, 2018 and June 30, 2019, 27,522 issues were marked "closed" or "fixed", a 13% increase from the <a href="https://dri.es/who-sponsors-drupal-development-2018">24,447 issues in the 2017-2018 period</a>.</p>
487 <p>In total, the Drupal community worked on 3,474 different Drupal.org projects this year compared to <a href="https://dri.es/who-sponsors-drupal-development-2018">3,229 projects in the 2017-2018 period</a> — an 8% year over year increase.</p>
488 <p>The majority of the credits are the result of work on contributed modules:</p>
489 <p><img alt="A pie chart showing contributions by project type: most contributions are to contributed modules." height="603" src="https://www.drupal.org/files/piechart.png" width="1280" /></p>
490 <p>Compared to the previous period, contribution credits increased across all project types:</p>
491 <p><img alt="A graph showing the year over year growth of contributions per project type." height="568" src="https://www.drupal.org/files/bar-graph.png" width="1280" /></p>
492 <p>The most notable change is the large jump in "non-product credits": more and more members in the community started tracking credits for non-product activities such as organizing Drupal events (e.g. <a href="https://www.drupal.org/project/drupalcampdelhi">DrupalCamp Delhi project</a>, <a href="https://www.drupal.org/project/ddd_event_2019">Drupal Developer Days</a>, <a href="https://www.drupal.org/project/drupaleurope">Drupal Europe</a> and <a href="https://www.drupal.org/project/drupalconeur">DrupalCon Europe</a>), promoting Drupal (e.g. <a href="https://www.drupal.org/project/promote_drupal">Drupal pitch deck</a> or community working groups (e.g. <a href="https://www.drupal.org/project/diversity">Drupal Diversity and Inclusion Working Group</a>, <a href="https://www.drupal.org/project/governance">Governance Working Group</a>).</p>
493 <p>While some of these increases reflect new contributions, others are existing contributions that are newly reported. All contributions are valuable, whether they're code contributions, or non-product and community-oriented contributions such as organizing events, giving talks, leading sprints, etc. The fact that the credit system is becoming more accurate in recognizing more types of Open Source contribution is both important and positive.</p>
494 <h3 id="2">Who is working on Drupal?</h3>
495 <p>For this report's time period, Drupal.org's credit system received contributions from 8,513 different individuals and 1,137 different organizations — a meaningful increase from last year's report.</p>
496 <p><img alt="A graph showing that the number of individual and organizational contributors increased year over year." height="568" src="https://www.drupal.org/files/Contrib.png" width="1280" /></p>
497 <p>Consistent with previous years, approximately 51% of the individual contributors received just one credit. Meanwhile, the top 30 contributors (the top 0.4%) account for 19% of the total credits. In other words, a relatively small number of individuals do the majority of the work. These individuals put an incredible amount of time and effort into developing Drupal and its contributed projects:</p>
498 <table><tbody><tr><th>Rank</th>
499 <th>Username</th>
500 <th>Issues</th>
501 </tr><tr><td>1</td>
502 <td><a href="https://www.drupal.org/u/kiamlaluno">kiamlaluno</a></td>
503 <td>1610</td>
504 </tr><tr><td>2</td>
505 <td><a href="https://www.drupal.org/u/jrockowitz">jrockowitz</a></td>
506 <td>756</td>
507 </tr><tr><td>3</td>
508 <td><a href="https://www.drupal.org/u/alexpott">alexpott</a></td>
509 <td>642</td>
510 </tr><tr><td>4</td>
511 <td><a href="https://www.drupal.org/u/rajabnatshah">RajabNatshah</a></td>
512 <td>616</td>
513 </tr><tr><td>5</td>
514 <td><a href="https://www.drupal.org/u/volkswagenchick">volkswagenchick</a></td>
515 <td>519</td>
516 </tr><tr><td>6</td>
517 <td><a href="https://www.drupal.org/u/bojanz">bojanz</a></td>
518 <td>504</td>
519 </tr><tr><td>7</td>
520 <td><a href="https://www.drupal.org/u/alonaoneill">alonaoneill</a></td>
521 <td>489</td>
522 </tr><tr><td>8</td>
523 <td><a href="https://www.drupal.org/u/thalles">thalles</a></td>
524 <td>488</td>
525 </tr><tr><td>9</td>
526 <td><a href="https://www.drupal.org/u/wim-leers">Wim Leers</a></td>
527 <td>437</td>
528 </tr><tr><td>10</td>
529 <td><a href="https://www.drupal.org/u/damienmckenna">DamienMcKenna</a></td>
530 <td>431</td>
531 </tr><tr><td>11</td>
532 <td><a href="https://www.drupal.org/u/berdir">Berdir</a></td>
533 <td>424</td>
534 </tr><tr><td>12</td>
535 <td><a href="https://www.drupal.org/u/chipway">chipway</a></td>
536 <td>356</td>
537 </tr><tr><td>13</td>
538 <td><a href="https://www.drupal.org/u/larowlan">larowlan</a></td>
539 <td>324</td>
540 </tr><tr><td>14</td>
541 <td><a href="https://www.drupal.org/u/pifagor">pifagor</a></td>
542 <td>320</td>
543 </tr><tr><td>15</td>
544 <td><a href="https://www.drupal.org/u/catch">catch</a></td>
545 <td>313</td>
546 </tr><tr><td>16</td>
547 <td><a href="https://www.drupal.org/u/mglaman">mglaman</a></td>
548 <td>277</td>
549 </tr><tr><td>17</td>
550 <td><a href="https://www.drupal.org/u/adci_contributor">adci_contributor</a></td>
551 <td>274</td>
552 </tr><tr><td>18</td>
553 <td><a href="https://www.drupal.org/u/quietone">quietone</a></td>
554 <td>266</td>
555 </tr><tr><td>19</td>
556 <td><a href="https://www.drupal.org/u/timplunkett">tim.plunkett</a></td>
557 <td>265</td>
558 </tr><tr><td>20</td>
559 <td><a href="https://www.drupal.org/u/gauravkapoor">gaurav.kapoor</a></td>
560 <td>253</td>
561 </tr><tr><td>21</td>
562 <td><a href="https://www.drupal.org/u/renatog">RenatoG</a></td>
563 <td>246</td>
564 </tr><tr><td>22</td>
565 <td><a href="https://www.drupal.org/u/heddn">heddn</a></td>
566 <td>243</td>
567 </tr><tr><td>23</td>
568 <td><a href="https://www.drupal.org/u/chrfritsch">chr.fritsch</a></td>
569 <td>241</td>
570 </tr><tr><td>24</td>
571 <td><a href="https://www.drupal.org/u/xjm">xjm</a></td>
572 <td>238</td>
573 </tr><tr><td>25</td>
574 <td><a href="https://www.drupal.org/u/phenaproxima">phenaproxima</a></td>
575 <td>238</td>
576 </tr><tr><td>26</td>
577 <td><a href="https://www.drupal.org/u/mkalkbrenner">mkalkbrenner</a></td>
578 <td>235</td>
579 </tr><tr><td>27</td>
580 <td><a href="https://www.drupal.org/u/gvso">gvso</a></td>
581 <td>232</td>
582 </tr><tr><td>28</td>
583 <td><a href="https://www.drupal.org/u/dawehner">dawehner</a></td>
584 <td>219</td>
585 </tr><tr><td>29</td>
586 <td><a href="https://www.drupal.org/u/e0ipso">e0ipso</a></td>
587 <td>218</td>
588 </tr><tr><td>30</td>
589 <td><a href="https://www.drupal.org/u/drumm">drumm</a></td>
590 <td>205</td>
591 </tr></tbody></table><p>Out of the top 30 contributors featured this year, 28 were active contributors in the 2017-2018 period as well. These Drupalists' dedication and continued contribution to the project has been crucial to Drupal's development.</p>
592 <p>It's also important to recognize that most of the top 30 contributors are sponsored by an organization. Their sponsorship details are provided later in this article. We value the organizations that sponsor these remarkable individuals, because without their support, <a href="https://dri.es/the-privilege-of-free-time-in-open-source">it could be more challenging for these individuals to be in the top 30</a>.</p>
593 <p>It's also nice to see two new contributors make the top 30 this year — <a href="https://www.drupal.org/u/alonaoneill">Alona O'neill</a> with sponsorship from <a href="https://www.hook42.com/">Hook 42</a> and <a href="https://www.drupal.org/u/thalles">Thalles Ferreira</a> with sponsorship from <a href="https://ciandt.com/">CI&amp;T</a>. Most of their credits were the result of smaller patches (e.g. removing deprecated code, fixing coding style issues, etc) or in some cases non-product credits rather than new feature development or fixing complex bugs. These types of contributions are valuable and often a stepping stone towards towards more in-depth contribution.</p>
594 <h3 id="3">How much of the work is sponsored?</h3>
595 <p>Issue credits can be marked as "volunteer" and "sponsored" simultaneously (shown in jamadar's screenshot near the top of this post). This could be the case when a contributor does the necessary work to satisfy the customer's need, in addition to using their spare time to add extra functionality.</p>
596 <p>For those credits with attribution details, 18% were "purely volunteer" credits (8,433 credits), in stark contrast to the 65% that were "purely sponsored" (29,802 credits). While there are almost four times as many "purely sponsored" credits as "purely volunteer" credits, volunteer contribution remains very important to Drupal.</p>
597 <p><img alt="Contributions by volunteer vs sponsored" height="568" src="https://www.drupal.org/files/volunteer.png" width="1280" /></p>
598 <p>Both "purely volunteer" and "purely sponsored" credits grew — "purely sponsored" credits grew faster in absolute numbers, but for the first time in four years "purely volunteer" credits grew faster in relative numbers.</p>
599 <p>The large jump in volunteer credits can be explained by the community capturing more non-product contributions. As can be seen on the graph below, these non-product contributions are more volunteer-centric.</p>
600 <p><img alt="A graph showing how much of the contributions are volunteered vs sponsored." height="568" src="https://www.drupal.org/files/type_0.png" width="1280" /></p>
601 <h3 id="4">Who is sponsoring the work?</h3>
602 <p>Now that we've established that the majority of contributions to Drupal are sponsored, let's study which organizations contribute to Drupal. While 1,137 different organizations contributed to Drupal, approximately 50% of them received four credits or less. The top 30 organizations (roughly the top 3%) account for approximately 25% of the total credits, which implies that the top 30 companies play a crucial role in the health of the Drupal project.</p>
603 <p><img alt="Top conytinuying organizations" height="1563" src="https://www.drupal.org/files/companies.png" width="1280" /></p>
604 <p><em>Top contributing organizations based on the number of issue credits.</em></p>
605 <p>While not immediately obvious from the graph above, a variety of different types of companies are active in Drupal's ecosystem:</p>
606 <table><thead><tr><th>Category</th>
607 <th>Description</th>
608 </tr></thead><tbody><tr><td>Traditional Drupal businesses</td>
609 <td>Small-to-medium-sized professional services companies that primarily make money using Drupal. They typically employ fewer than 100 employees, and because they specialize in Drupal, many of these professional services companies contribute frequently and are a huge part of our community. Examples are Hook42, Centarro, The Big Blue House, Vardot, etc.</td>
610 </tr><tr><td>Digital marketing agencies</td>
611 <td>Larger full-service agencies that have marketing-led practices using a variety of tools, typically including Drupal, Adobe Experience Manager, Sitecore, WordPress, etc. They tend to be larger, with many of the larger agencies employing thousands of people. Examples are Wunderman, Possible and Mirum.</td>
612 </tr><tr><td>System integrators</td>
613 <td>Larger companies that specialize in bringing together different technologies into one solution. Example system agencies are Accenture, TATA Consultancy Services, Capgemini and CI&amp;T.</td>
614 </tr><tr><td>Hosting companies</td>
615 <td>Examples are Acquia, Rackspace, Pantheon and Platform.sh.</td>
616 </tr><tr><td>End users</td>
617 <td>Examples are Pfizer or bio.logis Genetic Information Management GmbH.</td>
618 </tr></tbody></table><p>A few observations:</p>
619 <ul><li>Almost all of the sponsors in the top 30 are traditional Drupal businesses with fewer than 50 employees. Only five companies in the top 30 — Pfizer, Google, CI&amp;T, bio.logis and Acquia — are not traditional Drupal businesses. The traditional Drupal businesses are responsible for almost 80% of all the credits in the top 30. This percentage goes up if you extend beyond the top 30. It's fair to say that Drupal's maintenance and innovation largely depends on these traditional Drupal businesses.</li>
620 <li>The larger, multi-platform digital marketing agencies are barely contributing to Drupal. While more and more large digital agencies are building out Drupal practices, no digital marketing agencies show up in the top 30, and hardly any appear in the entire list of contributing organizations. While they are not required to contribute, I'm frustrated that we have not yet found the right way to communicate the value of contribution to these companies. We need to incentivize each of these firms to contribute back with the same commitment that we see from traditional Drupal businesses</li>
621 <li>The only system integrator in the top 30 is CI&amp;T, which ranked 4th with 795 credits. As far as system integrators are concerned, CI&amp;T is a smaller player with approximately 2,500 employees. However, we do see various system integrators outside of the top 30, including Globant, Capgemini, Sapient and TATA Consultancy Services. In the past year, Capgemini almost quadrupled their credits from 46 to 196, TATA doubled its credits from 85 to 194, Sapient doubled its credits from 28 to 65, and Globant kept more or less steady with 41 credits. Accenture and Wipro do not appear to contribute despite doing a fair amount of Drupal work in the field.</li>
622 <li>Hosting companies also play an important role in our community, yet only Acquia appears in the top 30. Rackspace has 68 credits, Pantheon has 43, and Platform.sh has 23. I looked for other hosting companies in the data, but couldn't find any. In general, there is a persistent problem with hosting companies that make a lot of money with Drupal not contributing back. The contribution gap between Acquia and other hosting companies has increased, not decreased.</li>
623 <li>We also saw three end users in the top 30 as corporate sponsors: Pfizer (453 credits), Thunder (659 credits, up from 432 credits the year before), and the German company, bio.logis (330 credits). A notable end user is Johnson &amp; Johnson, who was just outside of the top 30, with 221 credits, up from 29 credits the year before. Other end users outside of the top 30, include the European Commission (189 credits), Workday (112 credits), Paypal (80 credits), NBCUniversal (48 credits), Wolters Kluwer (20 credits), and Burda Media (24 credits). We also saw contributions from many universities, including the University of British Columbia (148 credits), University of Waterloo (129 credits), Princeton University (73 credits), University of Austin Texas at Austin (57 credits), Charles Darwin University (24 credits), University of Edinburgh (23 credits), University of Minnesota (19 credits) and many more.</li>
624 </ul><p><img alt="A graph showing that Acquia is by far the number one contributing hosting company." height="568" src="https://www.drupal.org/files/company2.png" width="1280" /></p>
625 <p><img alt="Contributions by system integrators" height="568" src="https://www.drupal.org/files/company3.png" width="1280" /></p>
626 <p>It would be interesting to see what would happen if more end users mandated contributions from their partners. Pfizer, for example, <a href="https://dri.es/why-large-organizations-are-choosing-to-contribute-to-drupal"><em>only</em> works with agencies that contribute back to Drupal</a>, and uses Drupal's credit system to verify their vendors' claims. The <a href="https://www.youtube.com/watch?v=dN_zar8J2G0">State of Georgia started doing the same</a>; they also made Open Source contribution a vendor selection criteria. If more end users took this stance, it could have a big impact on the number of digital agencies, hosting companies and system integrators that contribute to Drupal.</p>
627 <p>While we should encourage more organizations to sponsor Drupal contributions, we should also understand and respect that some organizations can give more than others and that some might not be able to give back at all. Our goal is not to foster an environment that demands what and how others should give back. Instead, we need to help foster an environment worthy of contribution. This is clearly laid out in <a href="https://www.drupal.org/about/values-and-principles">Drupal's Values and Principles</a>.</p>
628 <h3 id="5">How diverse is Drupal?</h3>
629 <p>Supporting diversity and inclusion within Drupal is essential to the health and success of the project. The people who work on Drupal should reflect the diversity of people who use and work with the web.</p>
630 <p>I looked at both the gender and geographic diversity of Drupal.org contributors. While these are only two examples of diversity, these are the only diversity characteristics we currently have sufficient data for. Drupal.org recently rolled out support for <a href="https://www.isdnetwork.org/what-is-diversity.html">Big 8/Big 10</a>, so next year we should have more demographics information</p>
631 <h4>Gender diversity</h4>
632 <p>The data shows that only 8% of the recorded contributions were made by contributors who do not identify as male, which continues to indicate a wide gender gap. This is a one percent increase compared to last year. The gender imbalance in Drupal is profound and underscores the need to continue fostering diversity and inclusion in our community.</p>
633 <p><img alt="A graph showing contributions by gender: 75% of the contributions come from people who identify as male." height="498" src="https://www.drupal.org/files/gender_0.png" width="1280" /></p>
634 <p>Last year I wrote a post called about <a href="https://dri.es/the-privilege-of-free-time-in-open-source">the privilege of free time in Open Source</a>. It made the case that Open Source is <em>not</em> a meritocracy, because not everyone has equal amounts of free time to contribute. For example, research shows that women still spend more than double the time as men doing unpaid domestic work, such as housework or childcare. This makes it more difficult for women to contribute to Open Source on an unpaid, volunteer basis. It's one of the reasons why Open Source projects suffer from a lack of diversity, among others including hostile environments and unconscious biases. Drupal.org's credit data unfortunately still shows a big gender disparity in contributions:</p>
635 <p><img alt="A graph that shows that compared to males, female contributors do more sponsored work, and less volunteer work." height="356" src="https://www.drupal.org/files/male-female.png" width="1280" /></p>
636 <p>Ideally, over time, we can collect more data on <a href="https://dri.es/offering-more-inclusive-user-demographic-forms">non-binary gender designations</a>, as well as segment some of the trends behind contributions by gender. We can also do better at collecting data on other systemic issues beyond gender alone. Knowing more about these trends can help us close existing gaps. In the meantime, organizations capable of giving back should consider financially sponsoring individuals from underrepresented groups to contribute to Open Source. Each of us needs to decide if and how we can help give time and opportunities to underrepresented groups and how we can create equity for everyone in Drupal.</p>
637 <h4>Geographic diversity</h4>
638 <p>When measuring geographic diversity, we saw individual contributors from six continents and 114 countries:</p>
639 <p><img alt="A graph that shows most contributions come from Europe and North America." height="570" src="https://www.drupal.org/files/geography.png" width="1280" /></p>
640 <p><img alt="Contributions per capita" height="569" src="https://www.drupal.org/files/continents.png" width="1280" /></p>
641 <p><em>Contribution credits per capita calculated as the amount of contributions per continent divided by the population of each continent. 0.001% means that one in 100,000 people contribute to Drupal. In North America, 5 in 100,000 people contributed to Drupal the last year.</em></p>
642 <p>Contributions from Europe and North America are both on the rise. In absolute terms, Europe contributes more than North America, but North America contributes more <a href="https://en.wikipedia.org/wiki/Per_capita">per capita</a>.</p>
643 <p>Asia, South America and Africa remain big opportunities for Drupal, as their combined population accounts for 6.3 billion out of 7.5 billion people in the world. Unfortunately, the reported contributions from Asia are declining year over year. For example, compared to last year's report, there was a 17% drop in contribution from India. Despite that drop, India remains the second largest contributor behind the United States:</p>
644 <p><img alt="A graph showing the top 20 contributing countries." height="1117" src="https://www.drupal.org/files/countries_0.png" width="1280" /></p>
645 <p><em>The top 20 countries from which contributions originate. The data is compiled by aggregating the countries of all individual contributors behind each issue. Note that the geographical location of contributors doesn't always correspond with the origin of their sponsorship. Wim Leers, for example, works from Belgium, but his funding comes from Acquia, which has the majority of its customers in North America.</em></p>
646 <h3 id="6">Top contributor details</h3>
647 <p>To create more awareness of which organizations are sponsoring the top individual contributors, I included a more detailed overview of the top 50 contributors and their sponsors. If you are a Drupal developer looking for work, these are some of the companies I'd apply to first. If you are an end user looking for a company to work with, these are some of the companies I'd consider working with first. Not only do they know Drupal well, they also help improve your investment in Drupal.</p>
648 <table><tbody><tr><th>Rank</th>
649 <th>Username</th>
650 <th>Issues</th>
651 <th>Volunteer</th>
652 <th>Sponsored</th>
653 <th>Not specified</th>
654 <th>Sponsors</th>
655 </tr><tr><td>1</td>
656 <td><a href="https://www.drupal.org/u/kiamlaluno">kiamlaluno</a></td>
657 <td>1610</td>
658 <td>99%</td>
659 <td>0%</td>
660 <td>1%</td>
661 <td></td>
662 </tr><tr><td>2</td>
663 <td><a href="https://www.drupal.org/u/jrockowitz">jrockowitz</a></td>
664 <td>756</td>
665 <td>98%</td>
666 <td>99%</td>
667 <td>0%</td>
668 <td>The Big Blue House (750), Memorial Sloan Kettering Cancer Center (5), Rosewood Marketing (1)</td>
669 </tr><tr><td>3</td>
670 <td><a href="https://www.drupal.org/u/alexpott">alexpott</a></td>
671 <td>642</td>
672 <td>6%</td>
673 <td>80%</td>
674 <td>19%</td>
675 <td>Thunder (336), Acro Media Inc (100), Chapter Three (77)</td>
676 </tr><tr><td>4</td>
677 <td><a href="https://www.drupal.org/u/rajabnatshah">RajabNatshah</a></td>
678 <td>616</td>
679 <td>1%</td>
680 <td>100%</td>
681 <td>0%</td>
682 <td>Vardot (730), Webship (2)</td>
683 </tr><tr><td>5</td>
684 <td><a href="https://www.drupal.org/u/volkswagenchick">volkswagenchick</a></td>
685 <td>519</td>
686 <td>2%</td>
687 <td>99%</td>
688 <td>0%</td>
689 <td>Hook 42 (341), Kanopi Studios (171)</td>
690 </tr><tr><td>6</td>
691 <td><a href="https://www.drupal.org/u/bojanz">bojanz</a></td>
692 <td>504</td>
693 <td>0%</td>
694 <td>98%</td>
695 <td>2%</td>
696 <td>Centarro (492), Ny Media AS (28), Torchbox (5), Liip (2), Adapt (2)</td>
697 </tr><tr><td>7</td>
698 <td><a href="https://www.drupal.org/u/alonaoneill">alonaoneill</a></td>
699 <td>489</td>
700 <td>9%</td>
701 <td>99%</td>
702 <td>0%</td>
703 <td>Hook 42 (484)</td>
704 </tr><tr><td>8</td>
705 <td><a href="https://www.drupal.org/u/thalles">thalles</a></td>
706 <td>488</td>
707 <td>0%</td>
708 <td>100%</td>
709 <td>0%</td>
710 <td>CI&amp;T (488), Janrain (3), Johnson &amp; Johnson (2)</td>
711 </tr><tr><td>9</td>
712 <td><a href="https://www.drupal.org/u/wim-leers">Wim Leers</a></td>
713 <td>437</td>
714 <td>8%</td>
715 <td>97%</td>
716 <td>0%</td>
717 <td>Acquia (421), Government of Flanders (3)</td>
718 </tr><tr><td>10</td>
719 <td><a href="https://www.drupal.org/u/damienmckenna">DamienMcKenna</a></td>
720 <td>431</td>
721 <td>0%</td>
722 <td>97%</td>
723 <td>3%</td>
724 <td>Mediacurrent (420)</td>
725 </tr><tr><td>11</td>
726 <td><a href="https://www.drupal.org/u/berdir">Berdir</a></td>
727 <td>424</td>
728 <td>0%</td>
729 <td>92%</td>
730 <td>8%</td>
731 <td>MD Systems (390)</td>
732 </tr><tr><td>12</td>
733 <td><a href="https://www.drupal.org/u/chipway">chipway</a></td>
734 <td>356</td>
735 <td>0%</td>
736 <td>100%</td>
737 <td>0%</td>
738 <td>Chipway (356)</td>
739 </tr><tr><td>13</td>
740 <td><a href="https://www.drupal.org/u/larowlan">larowlan</a></td>
741 <td>324</td>
742 <td>16%</td>
743 <td>94%</td>
744 <td>2%</td>
745 <td>PreviousNext (304), Charles Darwin University (22), University of Technology, Sydney (3), Service NSW (2), Department of Justice &amp; Regulation, Victoria (1)</td>
746 </tr><tr><td>14</td>
747 <td><a href="https://www.drupal.org/u/pifagor">pifagor</a></td>
748 <td>320</td>
749 <td>52%</td>
750 <td>100%</td>
751 <td>0%</td>
752 <td>GOLEMS GABB (618), EPAM Systems (16), Drupal Ukraine Community (6)</td>
753 </tr><tr><td>15</td>
754 <td><a href="https://www.drupal.org/u/catch">catch</a></td>
755 <td>313</td>
756 <td>1%</td>
757 <td>95%</td>
758 <td>4%</td>
759 <td>Third &amp; Grove (286), Tag1 Consulting (11), Drupal Association (6), Acquia (4)</td>
760 </tr><tr><td>16</td>
761 <td><a href="https://www.drupal.org/u/mglaman">mglaman</a></td>
762 <td>277</td>
763 <td>2%</td>
764 <td>98%</td>
765 <td>1%</td>
766 <td>Centarro (271), Oomph, Inc. (16), E.C. Barton &amp; Co (3), Gaggle.net, Inc. (1), Bluespark (1), Thinkbean (1), LivePerson, Inc (1), Impactiv, Inc. (1), Rosewood Marketing (1), Acro Media Inc (1)</td>
767 </tr><tr><td>17</td>
768 <td><a href="https://www.drupal.org/u/adci_contributor">adci_contributor</a></td>
769 <td>274</td>
770 <td>0%</td>
771 <td>100%</td>
772 <td>0%</td>
773 <td>ADCI Solutions (273)</td>
774 </tr><tr><td>18</td>
775 <td><a href="https://www.drupal.org/u/quietone">quietone</a></td>
776 <td>266</td>
777 <td>41%</td>
778 <td>75%</td>
779 <td>1%</td>
780 <td>Acro Media Inc (200)</td>
781 </tr><tr><td>19</td>
782 <td><a href="https://www.drupal.org/u/timplunkett">tim.plunkett</a></td>
783 <td>265</td>
784 <td>3%</td>
785 <td>89%</td>
786 <td>9%</td>
787 <td>Acquia (235)</td>
788 </tr><tr><td>20</td>
789 <td><a href="https://www.drupal.org/u/gauravkapoor">gaurav.kapoor</a></td>
790 <td>253</td>
791 <td>0%</td>
792 <td>51%</td>
793 <td>49%</td>
794 <td>OpenSense Labs (129), DrupalFit (111)</td>
795 </tr><tr><td>21</td>
796 <td><a href="https://www.drupal.org/u/renatog">RenatoG</a></td>
797 <td>246</td>
798 <td>0%</td>
799 <td>100%</td>
800 <td>0%</td>
801 <td>CI&amp;T (246), Johnson &amp; Johnson (85)</td>
802 </tr><tr><td>22</td>
803 <td><a href="https://www.drupal.org/u/heddn">heddn</a></td>
804 <td>243</td>
805 <td>2%</td>
806 <td>98%</td>
807 <td>2%</td>
808 <td>MTech, LLC (202), Tag1 Consulting (32), European Commission (22), North Studio (3), Acro Media Inc (2)</td>
809 </tr><tr><td>23</td>
810 <td><a href="https://www.drupal.org/u/chrfritsch">chr.fritsch</a></td>
811 <td>241</td>
812 <td>0%</td>
813 <td>99%</td>
814 <td>1%</td>
815 <td>Thunder (239)</td>
816 </tr><tr><td>24</td>
817 <td><a href="https://www.drupal.org/u/xjm">xjm</a></td>
818 <td>238</td>
819 <td>0%</td>
820 <td>85%</td>
821 <td>15%</td>
822 <td>Acquia (202)</td>
823 </tr><tr><td>25</td>
824 <td><a href="https://www.drupal.org/u/phenaproxima">phenaproxima</a></td>
825 <td>238</td>
826 <td>0%</td>
827 <td>100%</td>
828 <td>0%</td>
829 <td>Acquia (238)</td>
830 </tr><tr><td>26</td>
831 <td><a href="https://www.drupal.org/u/mkalkbrenner">mkalkbrenner</a></td>
832 <td>235</td>
833 <td>0%</td>
834 <td>100%</td>
835 <td>0%</td>
836 <td>bio.logis Genetic Information Management GmbH (234), OSCE: Organization for Security and Co-operation in Europe (41), Welsh Government (4)</td>
837 </tr><tr><td>27</td>
838 <td><a href="https://www.drupal.org/u/gvso">gvso</a></td>
839 <td>232</td>
840 <td>0%</td>
841 <td>100%</td>
842 <td>0%</td>
843 <td>Google Summer of Code (214), Google Code-In (16), Zivtech (1)</td>
844 </tr><tr><td>28</td>
845 <td><a href="https://www.drupal.org/u/dawehner">dawehner</a></td>
846 <td>219</td>
847 <td>39%</td>
848 <td>84%</td>
849 <td>8%</td>
850 <td>Chapter Three (176), Drupal Association (5), Tag1 Consulting (3), TES Global (1)</td>
851 </tr><tr><td>29</td>
852 <td><a href="https://www.drupal.org/u/e0ipso">e0ipso</a></td>
853 <td>218</td>
854 <td>99%</td>
855 <td>100%</td>
856 <td>0%</td>
857 <td>Lullabot (217), IBM (23)</td>
858 </tr><tr><td>30</td>
859 <td><a href="https://www.drupal.org/u/drumm">drumm</a></td>
860 <td>205</td>
861 <td>0%</td>
862 <td>98%</td>
863 <td>1%</td>
864 <td>Drupal Association (201)</td>
865 </tr><tr><td>31</td>
866 <td><a href="https://www.drupal.org/u/gabesullice">gabesullice</a></td>
867 <td>199</td>
868 <td>0%</td>
869 <td>100%</td>
870 <td>0%</td>
871 <td>Acquia (198), Aten Design Group (1)</td>
872 </tr><tr><td>32</td>
873 <td><a href="https://www.drupal.org/u/amateescu">amateescu</a></td>
874 <td>194</td>
875 <td>0%</td>
876 <td>97%</td>
877 <td>3%</td>
878 <td>Pfizer, Inc. (186), Drupal Association (1), Chapter Three (1)</td>
879 </tr><tr><td>33</td>
880 <td><a href="https://www.drupal.org/u/klausi">klausi</a></td>
881 <td>193</td>
882 <td>2%</td>
883 <td>59%</td>
884 <td>40%</td>
885 <td>jobiqo - job board technology (113)</td>
886 </tr><tr><td>34</td>
887 <td><a href="https://www.drupal.org/u/samuelmortenson">samuel.mortenson</a></td>
888 <td>187</td>
889 <td>42%</td>
890 <td>42%</td>
891 <td>17%</td>
892 <td>Acquia (79)</td>
893 </tr><tr><td>35</td>
894 <td><a href="https://www.drupal.org/u/joelpittet">joelpittet</a></td>
895 <td>187</td>
896 <td>28%</td>
897 <td>78%</td>
898 <td>14%</td>
899 <td>The University of British Columbia (146)</td>
900 </tr><tr><td>36</td>
901 <td><a href="https://www.drupal.org/u/borisson_">borisson_</a></td>
902 <td>185</td>
903 <td>83%</td>
904 <td>50%</td>
905 <td>3%</td>
906 <td>Calibrate (79), Dazzle (13), Intracto digital agency (1)</td>
907 </tr><tr><td>37</td>
908 <td><a href="https://www.drupal.org/u/g%C3%A1bor-hojtsy">Gábor Hojtsy</a></td>
909 <td>184</td>
910 <td>0%</td>
911 <td>97%</td>
912 <td>3%</td>
913 <td>Acquia (178)</td>
914 </tr><tr><td>38</td>
915 <td><a href="https://www.drupal.org/u/adriancid">adriancid</a></td>
916 <td>182</td>
917 <td>91%</td>
918 <td>22%</td>
919 <td>2%</td>
920 <td>Drupiter (40)</td>
921 </tr><tr><td>39</td>
922 <td><a href="https://www.drupal.org/u/eiriksm">eiriksm</a></td>
923 <td>182</td>
924 <td>0%</td>
925 <td>100%</td>
926 <td>0%</td>
927 <td>Violinist (178), Ny Media AS (4)</td>
928 </tr><tr><td>40</td>
929 <td><a href="https://www.drupal.org/u/yas">yas</a></td>
930 <td>179</td>
931 <td>12%</td>
932 <td>80%</td>
933 <td>10%</td>
934 <td>DOCOMO Innovations, Inc. (143)</td>
935 </tr><tr><td>41</td>
936 <td><a href="https://www.drupal.org/u/tr">TR</a></td>
937 <td>177</td>
938 <td>0%</td>
939 <td>0%</td>
940 <td>100%</td>
941 <td></td>
942 </tr><tr><td>42</td>
943 <td><a href="https://www.drupal.org/u/hass">hass</a></td>
944 <td>173</td>
945 <td>1%</td>
946 <td>0%</td>
947 <td>99%</td>
948 <td></td>
949 </tr><tr><td>43</td>
950 <td><a href="https://www.drupal.org/u/joachim-namyslo">Joachim Namyslo</a></td>
951 <td>172</td>
952 <td>69%</td>
953 <td>0%</td>
954 <td>31%</td>
955 <td></td>
956 </tr><tr><td>44</td>
957 <td><a href="https://www.drupal.org/u/alex_optim">alex_optim</a></td>
958 <td>171</td>
959 <td>0%</td>
960 <td>99%</td>
961 <td>1%</td>
962 <td>GOLEMS GABB (338)</td>
963 </tr><tr><td>45</td>
964 <td><a href="https://www.drupal.org/u/flocondetoile">flocondetoile</a></td>
965 <td>168</td>
966 <td>0%</td>
967 <td>99%</td>
968 <td>1%</td>
969 <td>Flocon de toile (167)</td>
970 </tr><tr><td>46</td>
971 <td><a href="https://www.drupal.org/u/lendude">Lendude</a></td>
972 <td>168</td>
973 <td>52%</td>
974 <td>99%</td>
975 <td>0%</td>
976 <td>Dx Experts (91), ezCompany (67), Noctilaris (9)</td>
977 </tr><tr><td>47</td>
978 <td><a href="https://www.drupal.org/u/paulvandenburg">paulvandenburg</a></td>
979 <td>167</td>
980 <td>11%</td>
981 <td>72%</td>
982 <td>21%</td>
983 <td>ezCompany (120)</td>
984 </tr><tr><td>48</td>
985 <td><a href="https://www.drupal.org/u/voleger">voleger</a></td>
986 <td>165</td>
987 <td>98%</td>
988 <td>98%</td>
989 <td>2%</td>
990 <td>GOLEMS GABB (286), Lemberg Solutions Limited (36), Drupal Ukraine Community (1)</td>
991 </tr><tr><td>49</td>
992 <td><a href="https://www.drupal.org/u/lauriii">lauriii</a></td>
993 <td>164</td>
994 <td>3%</td>
995 <td>98%</td>
996 <td>1%</td>
997 <td>Acquia (153), Druid (8), Lääkärikeskus Aava Oy (2)</td>
998 </tr><tr><td>50</td>
999 <td><a href="https://www.drupal.org/u/idebr">idebr</a></td>
1000 <td>162</td>
1001 <td>0%</td>
1002 <td>99%</td>
1003 <td>1%</td>
1004 <td>ezCompany (156), One Shoe (5)</td>
1005 </tr></tbody></table><h3 id="7">Limitations of the credit system</h3>
1006 <p>It is important to note a few of the current limitations of Drupal.org's credit system:</p>
1007 <ul><li><strong>The credit system doesn't capture all code contributions.</strong> Parts of Drupal are developed on GitHub rather than Drupal.org, and often aren't fully credited on Drupal.org. For example, Drush is maintained on GitHub instead of Drupal.org, and companies like Pantheon don't get credit for that work. The <a href="https://www.drupal.org/association">Drupal Association</a> is working to integrate GitLab with Drupal.org. GitLab will provide support for "merge requests", which means contributing to Drupal will feel more familiar to the broader audience of Open Source contributors who learned their skills in the post-patch era. Some of GitLab's tools, such as in-line editing and web-based code review will also lower the barrier to contribution, and should help us grow both the number of contributions and contributors on Drupal.org.</li>
1008 <li><strong>The credit system is not used by everyone.</strong> There are many ways to contribute to Drupal that are still <a href="https://www.palantir.net/blog/drupal-sustainability-contribution-credit-and-impact">not captured in the credit system</a>, including things like event organizing or providing support. Technically, that work could be captured as demonstrated by the various non-product initiatives highlighted in this post. Because using the credit system is optional, many contributors don't. As a result, contributions often have incomplete or no contribution credits. We need to encourage all Drupal contributors to use the credit system, and raise awareness of its benefits to both individuals and organizations. Where possible, we should automatically capture credits. For example, translation efforts on <a href="https://localize.drupal.org/">https://localize.drupal.org</a> are not currently captured in the credit system but could be automatically.</li>
1009 <li><strong>The credit system disincentives work on complex issues.</strong> We currently don't have a way to account for the complexity and quality of contributions; one person might have worked several weeks for just one credit, while another person might receive a credit for 10 minutes of work. We certainly see a few individuals and organizations trying to game the credit system. In the future, we should consider issuing credit data in conjunction with issue priority, patch size, number of reviews, etc. This could help incentivize people to work on larger and more important problems and save smaller issues such as coding standards improvements for new contributor sprints. Implementing a scoring system that ranks the complexity of an issue would also allow us to develop more accurate reports of contributed work.</li>
1010 </ul><p>All of this means that the actual number of contributions and contributors could be significantly higher than what we report.</p>
1011 <p>Like Drupal itself, the Drupal.org credit system needs to continue to evolve. Ultimately, the credit system will only be useful when the community uses it, understands its shortcomings, and suggests constructive improvements.</p>
1012 <h3 id="8">A first experiment with weighing credits</h3>
1013 <p>As a simple experiment, I decided to weigh each credit based on the adoption of the project the credit is attributed to. For example, each contribution credit to Drupal core is given a weight of 11 because Drupal core has about 1,1 million active installations. Credits to the <a href="https://www.drupal.org/project/webform">Webform module</a>, which has over 400,000 installations, get a weight of 4. And credits to <a href="https://www.drupal.org/project/commerce">Drupal's Commerce project</a> gets just 1 point as it is installed on fewer than 100,000 sites.</p>
1014 <p>The idea is that these weights capture the end user impact of each contribution, but also act as a proxy for the effort required to get a change committed. Getting a change accepted in Drupal core is both more difficult and more impactful than getting a change accepted to Commerce project.</p>
1015 <p>This weighting is far from perfect as it undervalues non-product contributions, and it still doesn't recognize all types of product contributions (e.g. product strategy work, product management work, release management work, etc). That said, for code contributions, it may be more accurate than a purely unweighted approach.</p>
1016 <p><img alt="Top contributing individuals based on weighted credits." height="1563" src="https://www.drupal.org/files/names.png" width="1280" /></p>
1017 <p><em>The top 30 contributing individuals based on weighted Drupal.org issue credits.</em></p>
1018 <p><img alt="Top contributing organizations based on weighted credits." height="1564" src="https://www.drupal.org/files/top30.png" width="1280" /></p>
1019 <p><em>The top 30 contributing organizations based on weighted Drupal.org issue credits.</em></p>
1020 <h3 id="9">Conclusions</h3>
1021 <p>Our data confirms that Drupal is a vibrant community full of contributors who are constantly evolving and improving the software. It's amazing to see that just in the last year, Drupal welcomed more than 8,000 individuals contributors and over 1,100 corporate contributors. It's especially nice to see the number of reported contributions, individual contributors and organizational contributors increase year over year.</p>
1022 <p>To grow and sustain Drupal, we should support those that contribute to Drupal and find ways to get those that are not contributing involved in our community. Improving diversity within Drupal is critical, and we should welcome any suggestions that encourage participation from a broader range of individuals and organizations.</p>
1023 </div></div></div></description>
1024 <pubDate>Thu, 12 Sep 2019 22:24:22 +0000</pubDate>
1025 <dc:creator>Dries</dc:creator>
1026 <guid isPermaLink="false">3081024 at https://www.drupal.org</guid>
1027 <comments>https://www.drupal.org/blog/who-sponsors-drupal-development-2018-2019-edition#comments</comments>
1028 </item>
1029 <item>
1030 <title>Drupal Association Announces Newly Appointed Board Members</title>
1031 <link>https://www.drupal.org/about/in-the-news/blog/drupal-association-announces-newly-appointed-board-members</link>
1032 <description><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p><strong>Portland, OR</strong><strong> - </strong>The Drupal Association, an international nonprofit organization, welcomes its newly appointed board members to help advance its mission to unite a global open source community to build, secure, and promote Drupal. The Association’s Board of Directors ratified the appointment of five new board members in September, including: Grace Francisco, Lo Li, Owen Lansbury, Ryan Szrama and Leslie Glynn, who was elected for the community-at-large seat.</p>
1033 <p>“We are excited to have these amazing individuals join us in our efforts to broaden our reach into diverse communities and to grow Drupal adoption. They bring a wide range of experiences and expertise to the Association that will enhance our opportunities to reach new audiences, support the Drupal community and elevate the Drupal project around the world,” said Adam Goodman, Drupal Association Board Chair. “We welcome Grace’s significant work in developer relations, developer marketing and program management; Leslie’s experience as a developer and project manager long emphasized by her years of contributions as a Drupal community member; Owen’s creative problem-solving, local Drupal association and DrupalCamp experience and business leadership skills; Lo’s extensive work in content management, brand promotion and tech platforms alongside her advocacy for women in technology; and Ryan’s product and service development and business skills coupled with his strong relationships in the Drupal community. We look forward to working with all of our new board members to achieve the Association’s strategic goals.”</p>
1034 <p><img alt="grace's headshot photo" class="left" height="170" src="/files/grace_headshot_6_16-7.jpg" width="113" />Grace Francisco joined MongoDB in July as Vice President, Worldwide Developer Relations. Prior to that, she served as Vice President of Developer Relations and Education at gaming platform Roblox where she doubled the size of active developers to 2+ million. A seasoned developer relations leader with over 20 years of experience in software, she has co-authored three patents and led worldwide developer initiatives at Microsoft, Intuit, Yodlee and Atlassian. Francisco graduated cum laude and holds a BBA in Business Management from Golden Gate University.</p>
1035 <p>“I am super excited to join the Drupal Association board,” said Francisco. “I first encountered the Drupal project back in 2010 while I was at Microsoft doing outreach to open source projects - building bridges to open source communities. It’s wonderful now, almost a decade later, to help from the other side to build bridges from Drupal to other tech organizations to broaden Drupal’s adoption.”</p>
1036 <p><img alt="leslieg's headshot photo" class="left" height="170" src="/files/Leslie%20Glynn%20Photo.jpg" width="113" />Leslie Glynn has more than thirty years of experience in the tech field as a software developer and project manager. She has been a freelance Drupal Project Manager and Site Builder since 2012. Glynn is very active in the Drupal community as an event organizer (Design 4 Drupal, Boston and NEDCamp), sprint organizer, mentor, trainer and volunteer. She is the winner of the 2019 Aaron Winborn Award. This annual award recognizes an individual who demonstrates personal integrity, kindness, and above-and-beyond commitment to the Drupal community.</p>
1037 <p>“Being a volunteer at numerous Drupal camps and DrupalCons has given me the opportunity to meet and learn from many diverse members of the Drupal community,” said Glynn. “I hope to bring that knowledge and experience to my work on Drupal Association initiatives. One of the things I would like to help with is growing Drupal adoption through new initiatives that reach out to underrepresented and diverse groups through an increased presence at secondary schools and universities and to groups, such as Girls Who Code, in the tech space.”</p>
1038 <p><img alt="owen's headshot photo" class="left" height="121" src="/files/2019_OwenLansbury_Headshot_Col.jpg" width="121" />Owen Lansbury is co-founder of PreviousNext, an independent Australian digital design and development company that has been one of the world's most prolific code contributors to the Drupal project. With 25 years’ professional experience and a background in Fine Art, Digital Media and User Experience Design, Lansbury blends creative problem solving with the business skills required to sustain his own company and work successfully with complex customers. He is also an active leader within the Australian and New Zealand Drupal community, bringing DrupalCon to Sydney in 2013, acting as Track Chair at several regional events and chairing the DrupalSouth Steering Committee.</p>
1039 <p>Lansbury said, “As a long-term Drupal community contributor in Australia and New Zealand, I'm excited about the opportunity to bring my grassroots experience to the Association board at a global level. I've always been a bit jealous of our developers contributing code to Drupal, so being able to contribute my own business and community leadership experience to the Association board is a great opportunity for me to give something back at a global level."</p>
1040 <p><img alt="lo's headshot photo" class="left" height="131" src="/files/Lo%20Li%20Photo.png" width="118" />Lo Li is the Senior Vice President, CIO of Global Consumer Solutions at Equifax. She has spent the past two decades leading global multi-billion dollar corporations for some of the world’s most renowned hospitality and retail brands in the world, working with hundreds of teams dispersed in the UK, China, Singapore and India. Some of her work includes the creation for dynamic pricing and predictive analytics engines for global hotels; and scaling big data and Agile to enable business transformation at large retailers including double digit growth plans for digital and international presence. She brings a deep understanding of how to translate corporate visions and strategies into simple, elegant solutions - using her international business acumen and technology background as both a business enabler and a competitive differentiator. Li, who is multilingual - fluent in Mandarin, Portuguese, Spanish and English - is the recipient of several industry accolades and serves on the Board of Directors for several national nonprofit organizations. She received her Bachelor’s and Master’s degree from the University of Georgia.</p>
1041 <p>Li said, “I am thrilled to join the Drupal Association board because of the incredible open source community that has been fostered. The nurturing and growth of communities, like the one we have at Drupal, are the very catalyst to help organizations leap forward and provide an incubator for new ideas and thought leadership amongst digital citizens. It's truly an honor to be able to help shape the future of such a great organization!”</p>
1042 <p><img alt="ryan's headshot photo" class="left" height="94" src="/files/Ryan%20Szrama_Board%20Member_082819.JPG" width="142" />Ryan Szrama co-founded Commerce Guys in 2009 to offer Drupal-based eCommerce consulting and development services. He was the project lead of Drupal’s most popular eCommerce framework, Drupal Commerce, from its creation to its eventual use on over 60,000 websites. In 2016, Ryan acquired control of Commerce Guys from his partners, leading the company to rebrand to Centarro and launch new product and support offerings that enable teams to build with confidence on Drupal Commerce.</p>
1043 <p>"My personal goals align perfectly with the mission of the Drupal Association: uniting a global open source community to build Drupal,” said Szrama. “I've been privileged to build a career in this community as a long-time contributor turned business owner, and I'm continually inspired by the members of this board to think bigger and give back more. I hope to apply my knowledge and experience to board initiatives that empower more people to better themselves and their organizations by using and contributing to Drupal."</p>
1044 <p>The newly-elected members will join the following <a href="https://www.drupal.org/node/2838099#dries" rel="nofollow">Association board members</a>, continuing their service in the upcoming term: </p>
1045 <ul><li>
1046 <p>Baddý Sonja Breidert, 1xINTERNET</p>
1047 </li>
1048 <li>
1049 <p>Dries Buytaert, Acquia</p>
1050 </li>
1051 <li>
1052 <p>Luma Dahlbacka, Charles Schwab &amp; Co</p>
1053 </li>
1054 <li>
1055 <p>Suzanne Dergacheva, Evolving Web</p>
1056 </li>
1057 <li>
1058 <p>Adam Goodman, Northwestern University’s Center for Leadership</p>
1059 </li>
1060 <li>
1061 <p>Mike Lamb, Pfizer</p>
1062 </li>
1063 <li>
1064 <p>Audra Martin-Merrick, Red Backpack Limited</p>
1065 </li>
1066 <li>
1067 <p>George Matthes, Johnson &amp; Johnson</p>
1068 </li>
1069 <li>
1070 <p>Vishal Mehrotra, Tata Consultancy Services</p>
1071 </li>
1072 <li>
1073 <p>Ingo Rübet, BOTLabs GmbH</p>
1074 </li>
1075 <li>
1076 <p>Michel van Velde, One Shoe</p>
1077 </li>
1078 </ul><p><strong>About Drupal</strong></p>
1079 <p>Drupal is one of the leading content management software platforms that has been used to create millions of websites around the world. There are 46,000 plus developers with 1.3 million users on Drupal.org, and Drupal has the largest open source community in the world. Drupal has great standard features, easy content authoring, reliable performance and excellent security. What sets it apart is its flexibility; modularity is one of its core principles. Its tools help you build the versatile, structured content that ambitious web experiences need.</p>
1080 <p><strong>About Drupal Association</strong></p>
1081 <p>The Drupal Association is an international non-profit organization that engages a broad audience about Drupal, the leading CMS open source project. The Association promotes Drupal adoption through the work and initiatives of a worldwide community of dedicated contributors, and support from individual and organizational members. The Drupal Association helps the Drupal community with funding, infrastructure, education, promotion, distribution and online collaboration. <strong>For more information, visit <a href="https://www.drupal.org/drupalorg" rel="nofollow">Drupal.org</a>.</strong></p>
1082 <p>###</p></div></div></div></description>
1083 <pubDate>Wed, 11 Sep 2019 16:49:36 +0000</pubDate>
1084 <dc:creator>cbern</dc:creator>
1085 <guid isPermaLink="false">3080663 at https://www.drupal.org</guid>
1086 <comments>https://www.drupal.org/about/in-the-news/blog/drupal-association-announces-newly-appointed-board-members#comments</comments>
1087 </item>
1088 <item>
1089 <title>WYSIWYG media embedding in Drupal 8.8</title>
1090 <link>https://www.drupal.org/blog/wysiwyg-media-embedding-in-drupal-88</link>
1091 <description><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p><em>This blog has been re-posted and edited with permission from <a href="https://dri.es/wysiwyg-media-embedding-in-drupal-8-8">Dries Buytaert's blog</a>.</em></p>
1092 <p>I'm excited to share that when Drupal 8.8 drops in December, Drupal's WYSIWYG editor will allow media embedding.</p>
1093 <p><iframe allow="autoplay; encrypted-media" allowfullscreen="" frameborder="0" height="360" src="https://www.youtube-nocookie.com/embed/sTc2JJzs9iU" title="A YouTube video" width="640"></iframe></p>
1094 <p>You may wonder: <em>Why is that worth announcing on your blog? It's just one new button in my WYSIWYG editor.</em></p>
1095 <p>It's a big deal because Drupal's media management has been going through a decade-long transformation. The addition of WYSIWYG integration completes the final milestone. You can read more about it on <a href="https://wimleers.com/blog/media-embedding-drupal-8.8">Wim's blog post</a>.</p>
1096 <p>Drupal 8.8 should ship with complete media management, which is fantastic news for site builders and content authors who have long wanted a simpler way to embed media in Drupal.</p>
1097 <p>Congratulations to the Media Initiative team for this significant achievement!</p>
1098 </div></div></div></description>
1099 <pubDate>Tue, 10 Sep 2019 21:34:20 +0000</pubDate>
1100 <dc:creator>Dries</dc:creator>
1101 <guid isPermaLink="false">3080471 at https://www.drupal.org</guid>
1102 <comments>https://www.drupal.org/blog/wysiwyg-media-embedding-in-drupal-88#comments</comments>
1103 </item>
1104 <item>
1105 <title>Welcome Carole Bernard to the Drupal Association</title>
1106 <link>https://www.drupal.org/association/blog/welcome-carole-bernard-to-the-drupal-association</link>
1107 <description><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p id="docs-internal-guid-11fb8256-7fff-40ec-2a30-5f7fb52d3958"><img alt="Carole Bernard's Drupal.org user profile photo" class="left" height="189" src="/files/styles/grid-2/public/user-pictures/picture-3622807-1566404483.png" width="140" />The Drupal Association (DA) is pleased to announce the recent hire of Carole Bernard as the Director of Marketing and Outreach. She and her team will focus on increasing visibility for the Drupal Association and opportunities for Drupal adoption through marketing, community engagement, volunteer management and public relations activities.</p>
1108 <p>With extensive nonprofit and public sector experience, Bernard has served in senior leadership roles for more than 15 years at local, regional and national organizations. </p>
1109 <p>Bernard, a Boston native, began her career as a speechwriter for the Mayor of Boston. She then worked as the Director of Public Information for the largest human service agency in New England, Action for Boston Community Development, Inc. She started her own consulting business in 2015, providing strategic communications, fundraising and executive management services to nonprofit organizations in the Washington, DC area. She recently served as the Director of Communications and Marketing for Sickle Cell Disease Association of America, Inc. She also has worked for Paralyzed Veterans of America, National Center for Women and Children and the National Minority AIDS Council as their Director of Communication.</p>
1110 <p>“I am so excited to be a part of the dynamic team at the Drupal Association,” says Bernard. “I am blown away by the passion and commitment of the Drupal community, and I look forward to working with everyone to tell the DA story, to showcase the Drupal project, to broaden the organization’s reach to new audiences and to increase opportunities for Drupal adoption around the world through strategic communications and outreach efforts.”</p>
1111 <p>“We want to continue to position Drupal as the leading open-source CMS for ambitious digital experiences that reach audiences across multiple channels around the world,” says Heather Rocker, DA Executive Director. “We also want to expand our efforts to bring new entities and individuals to the table to participate in our global community. We are excited to have Carole join us and to help us lay out and execute a plan that leverages all of the DA assets for growth, inclusion, awareness and participation.”</p>
1112 <p>Bernard received her bachelor’s degree in Political Science from Framingham State College and her master’s degree in Journalism from Boston University.</p></div></div></div></description>
1113 <pubDate>Tue, 27 Aug 2019 18:50:33 +0000</pubDate>
1114 <dc:creator>hrocker</dc:creator>
1115 <guid isPermaLink="false">3077495 at https://www.drupal.org</guid>
1116 <comments>https://www.drupal.org/association/blog/welcome-carole-bernard-to-the-drupal-association#comments</comments>
1117 </item>
1118 <item>
1119 <title>Drupal 8.7.0 is available</title>
1120 <link>https://www.drupal.org/blog/drupal-8-7-0</link>
1121 <description><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><h2>What’s new in Drupal 8.7.0?</h2>
1122 <p>This release introduces powerful features that will help us all take Drupal to a whole new level. The new stable JSON:API core module as well as the intuitive and accessible stable Layout Builder are game-changing.</p>
1123 <!--break--><p><a class="link-button" href="/project/drupal/releases/8.7.0">Download Drupal 8.7.0</a></p>
1124 <h3>Layout Builder is stable</h3>
1125 <p>The Layout Builder module was originally introduced as an experimental module in Drupal 8.5.0. As of Drupal 8.7.0, Layout Builder is now stable and ready for production use! It provides a powerful, accessible, mobile-friendly page building tool that is fully compatible with revisions, workflows, and in-context previews.</p>
1126 <p>The Layout Builder enables site builders to rapidly create layout templates for content that speed up the development process. It also permits content authors to easily customize individual pages with unique layouts.</p>
1127 <p>The interface allows drag-and-drop management of your content blocks. It additionally supports keyboard controls and toggling the content preview on and off to give the content editor complete control of their experience while building their layouts.</p>
1128 <p>The result of all these features is a state-of-the art content management solution that streamlines mass-production while also supporting unique creation. 123 individuals and 68 organizations contributed to this feature. More than 40 of the individual contributors volunteered some or all of their time.</p>
1129 <p>Check out this demonstration based on the core Umami demo:</p>
1130 <p><iframe allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" frameborder="0" height="349" src="https://www.youtube-nocookie.com/embed/oB28lfIUcNU" width="620"></iframe></p>
1131 <p>The team is working on implementing translation support for layouts in a future release.</p>
1132 <h3>New stable JSON:API support</h3>
1133 <p>JSON:API support is now included as a stable core feature. The <a href="https://jsonapi.org/">JSON:API specification</a> is an easy and fast way to build decoupled applications. Drupal core's JSON:API module is feature-complete and easy to use with robust out-of-the-box support and simple setup. JSON:API makes it simpler than ever to build ambitious projects. 147 contributors and 76 organizations contributed to this new feature. Among the individual contributors, more than 50 volunteered some or all of their time.</p>
1134 <p>For example, by simply navigating to a URL like <code class="language-php">https://example.com/jsonapi/node/article</code>, you can get a list of available articles on your site, and filter further from there, to display your Drupal content in decoupled websites, mobile applications, and so on.</p>
1135 <p><iframe allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" frameborder="0" height="349" src="https://www.youtube-nocookie.com/embed/zEsNlAeYRn8" width="620"></iframe></p>
1136 <h3>Improvements in experimental Media Library</h3>
1137 <p>The experimental Media Library has numerous significant improvements in this release. The Media Library is built on top of the stable Media module, which allows reuse of images, documents, and even embedded remote media like YouTube videos. Items in the Media Library can be managed with drag-and-drop. This release improves the design and accessibility of the user interface, allows inline media creation in the library, and provides more flexible grid and table views. 310 contributors and 122 organizations contributed to this new feature. More than 100 individuals volunteered some or all of their time!</p>
1138 <p>Check out this demonstration based the core Umami demo with Media Library enabled:</p>
1139 <p><iframe allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" frameborder="0" height="349" src="https://www.youtube-nocookie.com/embed/R3DT99QllGQ" width="620"></iframe></p>
1140 <p>There are various tasks left to make Media Library stable in a future release, including WYSIWYG integration.</p>
1141 <h3>Revisionable menus and taxonomy terms</h3>
1142 <p>Custom menu links and taxonomy terms are now revisionable, which allows them to be used in editorial workflows (similarly to nodes, media, and custom blocks). The Entity system now also provides a new Update API to support conversion of further entity types. It supports converting the schema of any content entity type between non-revisionable or non-translatable and revisionable or translatable, which also works when there is pre-existing data for the entity type whose schema is being changed. All these changes improve core support for the <a href="https://dri.es/an-update-on-the-workflow-initiative-for-drupal-8-4-8-5">Workspaces module</a>.</p>
1143 <h3>New features in the Umami demo profile</h3>
1144 <p>The Umami food magazine demo is now more accessible and demonstrates more features out of the box, including a new welcome tour, Layout Builder integration for recipes, and multilingual features. The profile now includes a curated set of Spanish translations, and more languages are in the works. 187 contributors and 84 organizations have contributed to Umami, with more than 60 individuals volunteering some or all of their time.</p>
1145 <p>Umami empowers first-time users to spin up a Drupal project in no time so that they can use to evaluate Drupal and learn about its major components.</p>
1146 <h3>On the way to Drupal 9</h3>
1147 <p>Drupal 8.7.0 includes optional support for Twig 2 (for sites that can patch their Composer configuration). Optional support for Symfony 4 also received a lot of contributions and should be complete in 8.8. This is important work, because <a href="https://www.drupal.org/blog/plan-for-drupal-9">Drupal 9 is planned for June 3, 2020</a> and will update various dependencies, primarily Symfony. Testing Drupal with updated third-party dependencies will help us get better feedback on our compatibility with these dependencies and any difficulties sites encounter when upgrading.</p>
1148 <h2>What does this mean for me?</h2>
1149 <h3>Drupal 8 site owners</h3>
1150 <p>Update to 8.7.0 to continue receiving bug fixes. The next bugfix release (8.7.1) is scheduled for June 5, 2019. (See the <a href="https://www.drupal.org/core/release-cycle-overview#windows">release schedule overview</a> for more information.) As of this release, sites on Drupal 8.5 will no longer receive security coverage. (Drupal 8.6 will continue receiving security fixes until December 4, 2019.)</p>
1151 <p>Note that new Drupal 8.7.0 installs now require at least PHP 7.0.8. <a href="https://www.drupal.org/node/3044409">Existing sites still work on at least PHP 5.5.9 for now, but will display a warning</a>. Drupal security updates will begin requiring PHP 7 as early as Drupal 8.8.0 (December 2019), so <strong>all users are advised to update to at least PHP 7.0.8 now</strong>.</p>
1152 <p><a href="https://www.drupal.org/node/2700999">Updating your site</a> from 8.6.15 to 8.7.0 with <code class="language-php">update.php</code> is exactly the same as updating from 8.6.14 to 8.6.15. Drupal 8.7.0 also has updates to several dependencies. Modules, themes, and translations may need updates for these and other changes in this minor release, so test the update carefully before updating your production site. <a href="https://www.drupal.org/project/drupal/releases/8.7.0">Read the 8.7.0 release notes</a> for a full list of changes that may affect your site.</p>
1153 <h3>Drupal 6 and 7 site owners</h3>
1154 <p><a href="https://www.drupal.org/psa-2019-02-25">Drupal 7 is fully supported by the community until November 2021</a>, and will continue to receive bug and security fixes throughout this time. From November 2021 until at least November 2024, the <a href="https://www.drupal.org/project/d7es">Drupal 7 Vendor Extended Support program</a> will be offered by vendors.</p>
1155 <p><a href="https://www.drupal.org/drupal-6-eol">Drupal 6 is no longer supported</a>.</p>
1156 <p>You can now use the stable migration path for monolingual Drupal 6 and 7 sites with the built-in upgrade user interface. For multilingual sites, there is experimental support; please keep testing and reporting any issues you may find.</p>
1157 <h3>Translation, module, and theme contributors</h3>
1158 <p>Minor releases like Drupal 8.7.0 include backwards-compatible API additions for developers as well as new features.</p>
1159 <p>Since minor releases are backwards-compatible, modules, themes, and translations that supported Drupal 8.6.x and earlier will be compatible with 8.7.x as well. However, the new version does include some changes to strings, user interfaces, <a href="https://www.drupal.org/core/d8-bc-policy">internal APIs</a> and API deprecations. This means that some small updates may be required for your translations, modules, and themes. <a href="https://www.drupal.org/project/drupal/releases/8.7.0">Read the 8.7.0 release notes</a> for a full list of changes that may affect your modules and themes.</p>
1160 <p>This release has advanced the Drupal project significantly and represents the efforts of hundreds of volunteers and contributors from various organizations, as well as testers from the <a href="https://www.drupal.org/community#beta-test">Minor release beta testing program</a>. Thank you to everyone who contributed to Drupal 8.7!</p>
1161 </div></div></div></description>
1162 <pubDate>Wed, 01 May 2019 14:27:18 +0000</pubDate>
1163 <dc:creator>Gábor Hojtsy</dc:creator>
1164 <guid isPermaLink="false">3051955 at https://www.drupal.org</guid>
1165 <comments>https://www.drupal.org/blog/drupal-8-7-0#comments</comments>
1166 </item>
1167 <item>
1168 <title>Remembering Rachel Olivero</title>
1169 <link>https://www.drupal.org/forum/general/community-spotlight/2019-02-22/remembering-rachel-olivero</link>
1170 <description><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even">
1171 <p><figure class="image right"><img alt="Rachel Olivero, smiling in a red dress." height="183" src="/files/rachel_olivero.jpeg" width="275" /><br /><figcaption><em>Rachel Olivero, courtesy of National Federation of the Blind</em></figcaption><br /></figure></p>
1172 <p>Earlier this month we saw the passing of <a href="https://www.drupal.org/u/rachelolivero">Rachel Olivero</a>. Rachel touched a lot of people in both the Drupal and accessibility communities. She worked at the <a href="https://nfb.org/">National Federation of the Blind</a>, as the Director of Organizational Technology. I am not sure that this is where she was first exposed to Drupal, but she became involved in the community after attending DrupalCon in her hometown of Baltimore in 2017. It was there where she participated in her first code sprint and contributed her <a href="https://www.drupal.org/project/drupal/issues/2873389">first bug report</a>.</p>
1173 <p>After attending the first-ever <a href="https://events.drupal.org/baltimore2017/nonprofit-summit">Nonprofit Summit at DrupalCon Baltimore</a>, Rachel stepped up to lead an accessibility breakout at <a href="https://events.drupal.org/nashville2018/nonprofit-summit">DrupalCon Nashville</a>. She was always willing to share her knowledge and never got annoyed no matter how many times she was asked her whether the &lt;aside&gt; element was ever useful to a screen reader. Fortunately, about 20 minutes of the <a href="https://www.youtube.com/watch?v=EYPM69Udod8">accessibility roundtable was recorded</a>. She engaged with a few folks throughout the week, many remember her from Drupal Trivia Night.</p>
1174 <p>As a technical user who was blind, her opinion was sought often in the Slack Channel. She also engaged with the <a href="https://www.drupaldiversity.com/">Drupal Diversity and Inclusion</a> team. Rachel was active in Twitter and other social media platforms too, where she engaged with other members of the Drupal community. As a person who was blind, transgender, and a lesbian, Rachel understood a lot about the importance of diversity.</p>
1175 <p>Rachel became involved in the <a href="https://www.nten.org/">NTEN</a> <a href="https://www.nten.org/event/community-practice-drupal-community-call/">Drupal Community of Practice</a> calls a few years ago, when she came on a monthly call to share some accessibility knowledge. Subsequently, she became a more regular attendee of these calls. Johanna Bates and Rachel were slated to co-present a session on accessible content entry for content editors at the upcoming <a href="https://www.nten.org/ntc/">NTEN 19NTC in Portland</a>. This would have been her first ever NTEN NTC.</p>
1176 <p>Rachel also served on the <a href="https://www.nten.org/ntc/ntc-accessibility-committee/">NTEN NTC’s first-ever accessibility committee</a>, contributing her knowledge to <a href="http://www.sigaccess.org/welcome-to-sigaccess/resources/accessible-conference-guide/">making conferences more accessible</a>. This is a perfect example of how willing Rachel was to share her expertise and experience with others. She was generous with her knowledge, kind, collaborative, and extremely funny. The loss of her warmth, humor, and brilliance in the Drupal community, the nonprofit tech community, and in the a11y community is a massive and sad loss.</p>
1177 <p>This fall Rachel contributed an article to the latest 24 accessibility series, <a href="https://www.24a11y.com/2018/more-than-just-the-tab-key/">Not Your Father’s Navigation Strategy: There’s More Than Just the TAB Key</a>. She argued for developers to invest in proper semantic markup so that screen reader users can make full use of their assistive technology. This annual series of articles really draws on a Who's Who of accessibility.</p>
1178 <p>Rachel was also the president of the NFB’s Amateur Radio Division. As a modern HAM enthusiast, she was <a href="https://github.com/RachelOlivero">active on GitHub</a> working to create a Software-defined radio (SDR) scanner that could continuously record a set of frequencies for on-demand playback. She was interested in public safety.</p>
1179 <p>Rachel had been working on NFB.org’s new Drupal 8 site for a long time. She was so excited to see it launch at the end of January. Rachel had recently been promoted at the NFB to Director of Technology. This launch was a huge piece of her work, and the site looks amazing. It is terrific to see how she was able to modernize the NFB’s website and leverage Drupal to help her create a modern responsive website.</p>
1180 <p>As Rachel said in an <a href="https://www.facebook.com/nationalfederationoftheblindofmaryland/posts/rachel-olivero-rachel-olivero-as-a-child-i-was-blessed-with-family-that-always-e/1330167303705818/">NFB Facebook campaign</a>:</p>
1181 <blockquote><p>“I’m lucky, and thankful, that blindness hasn’t caused a lot of resistance in my life. From the support of family during my early years to the encouragement of friends, to the emergency management director who I never saw blink an eye when I said, “I want to take the CERT class. You can teach me to get people out from under a collapsed wall too, right?” to all those who supported my gender transition. I’ve generally never felt that I couldn’t do something as a blind person. However, it’s the love, hope, and determination of my family in the National Federation of the Blind, that has given me the extra strength and answered the, ‘but how do I…” And that is <a href="https://twitter.com/hashtag/whyimafederationist">#WhyImAFederationist</a>”</p>
1182 </blockquote>
1183 <p>Rachel was also quoted in a very recent Vox.com article by s.e. smith, <a href="https://www.vox.com/the-goods/2019/2/5/18210912/websites-ada-compliance-lawsuits">Websites need to be more accessible for disabled people</a>. Rachel clearly identified that “Accessibility is still a sidebar when it comes to web development.”</p>
1184 <p>A few community members shared memories of Rachel:</p>
1185 <p>What I admired most about Rachel was her willingness to help at any level necessary and the kindness with which she acted. She was enthusiastic about building community and eager to contribute. She regularly gave time, experience, resources (like her server space, and other infrastructure) and energy to connecting people and working for a future in which technology would be accessible to all. Her unique perspective brought insight, empathy and patience to her work, and I’m sad that the world has lost such a passionate champion for inclusion. </p>
1186 <p>- <em>Nikki Stevens (drnikki)</em></p>
1187 <hr /><p>Rachel was the kind of person who immediately made you feel at ease when you were spending time with her, even if you had just met. She was great about making sure that nobody got left out, and was quick to invite new or shy people at events who might have eaten alone to come sit with her and her friends instead.</p>
1188 <p>She was generous with her time whenever I asked to bounce an idea off of her to see if what I was considering suggesting would actually be helpful for the blind community or not, and she never made me feel like a bother when I asked for her thoughts. To the contrary, she always seemed happy to help. She was encouraging when I was right, and gracious when I was wrong; she never made me feel stupid about an idea if I was off-base, and instead provided valuable insight that I apply to my work to this day.</p>
1189 <p>Rachel was an awesome woman, and I wish that we had gotten to spend more time together. The Drupal community (and the world at large) will definitely be feeling her loss. I hope that we can all put what she has given to each of us to good use to carry forward what was always her mission - to make the world better for people. </p>
1190 <p>- <em>Helena McCabe (helenasue)</em></p>
1191 <hr /><p>Rachel Olivero was really an adventurous spirit. I remember a NFB conference several years ago when Rachel mused "I've always wanted to ride a mechanical bull - y'know do as Texans do in Texas". After fighting the management of the establishment, who were not inclined to let her ride, she got to ride - for a full 30 seconds:-). Everyone at Deque will miss her. Rachel is an inspiration to all those who strive to be true to themselves and the cause of digital equality.</p>
1192 <p>- <em>Preety Kumar</em></p>
1193 <hr /><p>In 2007, Rachel was one of the first accessibility experts I worked with after I joined Deque and I was always impressed with her technical strength and her ability to keep people at the center of any discussion. I remember the demonstration she made to Wal-Mart’s checkout team, that the shopping cart was inaccessible. Their response was getting off-track into technical mumbo-jumbo when Rachel loudly interrupted, “excuse me...excuse me. The point is that I want to put money in your pocket but since the shopping cart won’t work for me, I can’t do that. Do you want me to put my money in Target’s pocket instead?!?!” I always enjoyed working with her on any project and will miss her.</p>
1194 <p>- <em>Wes Dillon</em></p>
1195 <hr /><p>Rachel Olivero will always be an an accessibility super hero to me. From the moment I met her, I knew she was wicked smart and a powerful force for good. She moved a11y forward through her technical work and leadership at NFB and Humana.</p>
1196 <p>Every time I hung out with Rachel, I felt like I was on an a11y adventure. She could even make javascript and aria entertaining. I loved how she used quotes from “Green Eggs and Ham” to show how accessible a live chat module could be. She had the whole room laughing and learning. Her joy was contagious and inspiring.</p>
1197 <p>Our friendship grew each time we were together...from AHG to NFB to CSUN, to Penn State Web Conf and more. I think some of my favorite memories are from the “accessibility slumber party” at the Margarita Inn with Rachel, Elle, Sharron and others. Elle had brought together a team of a11y experts to solve big problems...we worked night and day...because we care so deeply about equal access for all.</p>
1198 <p>A world without Rachel seems impossible to me. And then I remember how with Rachel, nothing seemed impossible. So I guess we all have to find our way to keep Rachel’s positive energy moving forward. Now It is up to each of us to make Rachel’s a11y dreams become a reality.</p>
1199 <p>So with that, I raise a glass of cherry coke (one of her favs) and toast “To Rachel! To A11Y &amp; Beyond!”</p>
1200 <p>- <em>Glenda Sims</em></p>
1201 <hr /><p>I enjoyed talking with Rachel at both of her DrupalCons. We mostly talked shop. I was very impressed with her knowledge and patience dealing with people interested in learning. I remember talking about getting organizations like the NFB to approach technology more as makers than consumers. We also talked about challenges with procurement and the work that she was doing to revise how technology was purchased. She seemed hopeful and focused. She was clearly a big thinker.</p>
1202 <p>By being involved in the Drupal community, Rachel reminded a lot of us of the importance of building our tools to work for everyone.</p>
1203 <p>We were all looking forward to working with her more. She will be missed.</p>
1204 <div class="note">
1205 <p>In lieu of flowers, the family requests that memorial donations be made to the National Federation of the Blind to support projects in which Rachel personally invested her time, treasure, and talent.</p>
1206 <p>Contributions can be mailed to National Federation of the Blind, 200 East Wells Street, Baltimore, Maryland, 21230, or given online at <a href="https://nfb.org/donate">https://nfb.org/donate</a>.</p>
1207 </div>
1208 </div></div></div></description>
1209 <pubDate>Fri, 22 Feb 2019 14:23:04 +0000</pubDate>
1210 <dc:creator>mgifford</dc:creator>
1211 <guid isPermaLink="false">3035076 at https://www.drupal.org</guid>
1212 <comments>https://www.drupal.org/forum/general/community-spotlight/2019-02-22/remembering-rachel-olivero#comments</comments>
1213 </item>
1214 <item>
1215 <title>Plan for Drupal 9</title>
1216 <link>https://www.drupal.org/blog/plan-for-drupal-9</link>
1217 <description><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><div class="note-tip">
1218 <p><strong>Update</strong>: Since the publication of this blog Drupal 9 is closer than ever. To learn what you need to do to be ready for the upcoming release, please consult our pages on <a href="/about/9">Preparing for Drupal 9</a>.</p>
1219 </div>
1220
1221 <p><em>This blog has been re-posted and edited with permission from <a href="https://dri.es/plan-for-drupal-9">Dries Buytaert's blog</a>. Unfortunately Dries' blog does not allow for comments at the moment, feel free to post them here.</em></p>
1222
1223 <p>At <a href="https://www.drupaleurope.org/">Drupal Europe</a>, I announced that Drupal 9 will be released in 2020. Although I explained <a href="https://dri.es/drupal-7-8-and-9">why we plan to release in 2020</a>, I wasn't very specific about when we plan to release Drupal 9 in 2020. Given that 2020 is less than thirteen months away (gasp!), it's time to be more specific.</p>
1224 <h3 id="1">Shifting Drupal's six month release cycle</h3>
1225 <p><img alt="A timeline that shows how we shifted Drupal 8's release windows" src="https://dri.es/files/cache/drupal/drupal-8-shifted-release-windows-640w.jpg" /></p>
1226 <p><em>We shifted Drupal 8's minor release windows so we can adopt Symfony's releases faster.</em></p>
1227 <p>Before I talk about the Drupal 9 release date, I want to explain another change we made, which has a minor impact on the Drupal 9 release date.</p>
1228 <p>As announced over two years ago, <a href="https://dri.es/the-transformation-of-drupal-8-for-continuous-innovation">Drupal 8 adopted a 6-month release cycle</a> (two releases a year). <a href="https://symfony.com/">Symfony</a>, a PHP framework which Drupal depends on, uses a similar release schedule. Unfortunately the timing of Drupal's releases has historically occurred 1-2 months before Symfony's releases, which forces us to wait six months to adopt the latest Symfony release. To be able to adopt the latest Symfony releases faster, we are moving Drupal's minor releases to June and December. This will allow us to adopt the latest Symfony releases within one month. For example, Drupal 8.8.0 is now scheduled for December 2019.</p>
1229 <h3 id="2">We hope to release Drupal 9 on June 3, 2020</h3>
1230 <p>Drupal 8's biggest dependency is Symfony 3, which has an end-of-life date in November 2021. This means that after November 2021, security bugs in Symfony 3 will not get fixed. Therefore, we have to end-of-life Drupal 8 no later than November 2021. Or put differently, by November 2021, <em>everyone</em> should be on Drupal 9.</p>
1231 <p>Working backwards from November 2021, we'd like to give site owners at least one year to upgrade from Drupal 8 to Drupal 9. While we could release Drupal 9 in December 2020, we decided it was better to <a href="https://www.drupal.org/project/drupal/issues/3007300">try to release Drupal 9 on June 3, 2020</a>. This gives site owners 18 months to upgrade. Plus, it also gives the Drupal core contributors an extra buffer in case we can't finish Drupal 9 in time for a summer release.</p>
1232 <p><img alt="A timeline that shows we hope to release Drupal 9 in June 2020" src="https://dri.es/files/cache/drupal/drupal-9-targeting-june-2020-640w.jpg" /></p>
1233 <p><em>Planned Drupal 8 and 9 minor release dates.</em></p>
1234 <h3 id="3">We are building Drupal 9 in Drupal 8</h3>
1235 <p>Instead of working on Drupal 9 in a separate codebase, we are building Drupal 9 in Drupal 8. This means that we are adding new functionality as backwards-compatible code and experimental features. Once the code becomes stable, we deprecate any old functionality.</p>
1236 <p>Let's look at an example. As mentioned, Drupal 8 currently depends on Symfony 3. Our plan is to release Drupal 9 with Symfony 4 or 5. Symfony 5's release is less than one year away, while Symfony 4 was released a year ago. Ideally Drupal 9 would ship with Symfony 5, both for the latest Symfony improvements and for longer support. However, Symfony 5 hasn't been released yet, so we don't know the scope of its changes, and we will have limited time to try to adopt it before Symfony 3's end-of-life.</p>
1237 <p>We are currently working on <a href="https://www.drupal.org/project/drupal/issues/2937984">making it possible to run Drupal 8 with Symfony 4</a> (without requiring it). Supporting Symfony 4 is a valuable stepping stone to Symfony 5 as it brings new capabilities for sites that choose to use it, and it eases the amount of Symfony 5 upgrade work to do for Drupal core developers. In the end, our goal is for Drupal 8 to work with Symfony 3, 4 or 5 so we can identify and fix any issues before we start <em>requiring</em> Symfony 4 or 5 in Drupal 9.</p>
1238 <p>Another example is our support for reusable media. Drupal 8.0.0 launched without a media library. We are currently working on <a href="https://dri.es/an-update-on-the-media-initiative-for-drupal-8-4-8-5">adding a media library to Drupal 8</a> so content authors can select pre-existing media from a library and easily embed them in their posts. Once the media library becomes stable, we can deprecate the use of the old file upload functionality and make the new media library the default experience.</p>
1239 <h3 id="4">The upgrade to Drupal 9 will be easy</h3>
1240 <p>Because we are building Drupal 9 in Drupal 8, the technology in Drupal 9 will have been battle-tested in Drupal 8.</p>
1241 <p>For <strong>Drupal core contributors</strong>, this means that we have a limited set of tasks to do in Drupal 9 itself before we can release it. Releasing Drupal 9 will only depend on removing deprecated functionality and upgrading Drupal's dependencies, such as Symfony. This will make the release timing more predictable and the release quality more robust.</p>
1242 <p>For <strong>contributed module authors</strong>, it means they already have the new technology at their service, so they can work on Drupal 9 compatibility earlier (e.g. they can start updating their media modules to use the new media library before Drupal 9 is released). Finally, their Drupal 8 know-how will remain highly relevant in Drupal 9, as there will not be a dramatic change in how Drupal is built.</p>
1243 <p>But most importantly, for <strong>Drupal site owners</strong>, this means that it should be much easier to upgrade to Drupal 9 than it was to upgrade to Drupal 8. Drupal 9 will simply be the last version of Drupal 8, with its deprecations removed. This means we will not introduce new, backwards-compatibility breaking APIs or features in Drupal 9 except for our dependency updates. As long as modules and themes stay up-to-date with the latest Drupal 8 APIs, the upgrade to Drupal 9 should be easy. Therefore, we believe that a 12- to 18-month upgrade period should suffice.</p>
1244 <h3 id="5">So what is the big deal about Drupal 9, then?</h3>
1245 <p>The big deal about Drupal 9 is … that it should not be a big deal. The best way to be ready for Drupal 9 is to keep up with Drupal 8 updates. Make sure you are not using deprecated modules and APIs, and where possible, use the latest versions of dependencies. If you do that, your upgrade experience will be smooth, and that is a big deal for us.</p>
1246 <p><em>Special thanks to <a href="https://www.drupal.org/u/g%C3%A1bor-hojtsy">Gábor Hojtsy</a> (Acquia), <a href="https://www.drupal.org/u/webchick">Angie Byron</a> (Acquia), <a href="https://www.drupal.org/u/xjm">xjm</a>(Acquia), and <a href="https://www.drupal.org/u/catch">catch</a> for their input in this blog post.</em></p>
1247 </div></div></div></description>
1248 <pubDate>Wed, 12 Dec 2018 18:38:05 +0000</pubDate>
1249 <dc:creator>Dries</dc:creator>
1250 <guid isPermaLink="false">3020100 at https://www.drupal.org</guid>
1251 <comments>https://www.drupal.org/blog/plan-for-drupal-9#comments</comments>
1252 </item>
1253 <item>
1254 <title>Drupal's commitment to accessibility</title>
1255 <link>https://www.drupal.org/blog/drupals-commitment-to-accessibility</link>
1256 <description><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p><em>This blog has been re-posted and edited with permission from <a href="https://dri.es/drupal-commitment-to-accessibility">Dries Buytaert's blog</a><a href="https://dri.es/drupal-commitment-to-accessibility">.</a> Please leave your comments on the original post.</em></p>
1257 <p class="center"><img alt="" height="640" src="https://www.drupal.org/files/figure-opening-doors-Driesblog.jpg" width="1280" /></p>
1258 <p>Last week, <a href="https://wptavern.com/">WordPress Tavern</a> picked up <a href="https://dri.es/why-drupal-layout-builder-is-so-unique-and-powerful">my blog post about Drupal 8's upcoming Layout Builder</a>.</p>
1259 <p>While I'm grateful that WordPress Tavern covered Drupal's Layout Builder, it is not surprising that the majority of <a href="https://wptavern.com/drupal-8-7-to-introduce-layout-builder-contributors-face-accessibility-challenges">WordPress Tavern's blog post</a> alludes to the potential challenges with accessibility. After all, <a href="https://wptavern.com/wordpress-accessibility-team-delivers-sobering-assessment-of-gutenberg-we-have-to-draw-a-line">Gutenberg's lack of accessibility has been a big topic of debate</a>, and a point of frustration in the WordPress community.</p>
1260 <p>I understand why organizations might be tempted to de-prioritize accessibility. Making a complex web application accessible can be a lot of work, and the pressure to ship early can be high.</p>
1261 <p>In the past, I've been tempted to skip accessibility features myself. I believed that because accessibility features benefited a small group of people only, they could come in a follow-up release.</p>
1262 <p>Today, I've come to believe that accessibility is not something you do for a small group of people. Accessibility is about promoting inclusion. When the product you use daily is accessible, it means that we all get to work with a greater number and a greater variety of colleagues. Accessibility benefits everyone.</p>
1263 <p>As you can see in <a href="https://www.drupal.org/about/values-and-principles">Drupal's Values and Principles</a>, we are committed to building software that everyone can use. Accessibility should always be a priority. Making capabilities like the Layout Builder accessible is core to Drupal's DNA.</p>
1264 <p><a href="https://www.drupal.org/about/values-and-principles">Drupal's Values and Principles</a> translate into our development process, as what we call an <a href="https://www.drupal.org/core/gates#accessibility">accessibility gate</a>, where we set a clearly defined "must-have bar." Prioritizing accessibility also means that we commit to trying to iteratively improve accessibility beyond that minimum over time.</p>
1265 <p>Together with the accessibility maintainers, we jointly agreed that:</p>
1266 <ol><li>Our first priority is <strong>WCAG 2.0 AA conformance</strong>. This means that in order to be released as a stable system, the Layout Builder must reach Level AA conformance with <a href="https://www.w3.org/WAI/standards-guidelines/wcag/">WCAG</a>. Without WCAG 2.0 AA conformance, we won't release a stable version of Layout Builder.</li>
1267 <li>Our next priority is <strong>WCAG 2.1 AA conformance</strong>. We're thrilled at the greater inclusion provided by these new guidelines, and will strive to achieve as much of it as we can before release. Because these guidelines are still new (formally approved in June 2018), we won't hold up releasing the stable version of Layout Builder on them, but are committed to implementing them as quickly as we're able to, even if some of the items are after initial release.</li>
1268 <li>While <strong>WCAG AAA conformance</strong> is not something currently being pursued, there are aspects of AAA that we are discussing adopting in the future. For example, the new <a href="https://www.drupal.org/project/ideas/issues/2928103">2.1 AAA "Animations from Interactions"</a>, which can be framed as an achievable design constraint: anywhere an animation is used, we must ensure designs are understandable/operable for those who cannot or choose not to use animations.</li>
1269 </ol><p>Drupal's commitment to accessibility is one of the things that makes Drupal's upcoming Layout Builder special: it will not only bring <a href="https://dri.es/why-drupal-layout-builder-is-so-unique-and-powerful">tremendous and new capabilities</a> to Drupal, it will also do so without excluding a large portion of current and potential users. We all benefit from that!</p>
1270 </div></div></div></description>
1271 <pubDate>Wed, 05 Dec 2018 19:58:14 +0000</pubDate>
1272 <dc:creator>Dries</dc:creator>
1273 <guid isPermaLink="false">3018346 at https://www.drupal.org</guid>
1274 <comments>https://www.drupal.org/blog/drupals-commitment-to-accessibility#comments</comments>
1275 </item>
1276 <item>
1277 <title>State of Drupal presentation (April 2018)</title>
1278 <link>https://www.drupal.org/blog/state-of-drupal-presentation-april-2018</link>
1279 <description><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><div class="entry__content" itemprop="articleBody">
1280 <p><em>This blog has been re-posted and edited with permission from <a href="https://dri.es/state-of-drupal-presentation-april-2018" rel="nofollow">Dries Buytaert's blog</a>. Please leave your comments on the original post.</em></p>
1281 <p class="center"><img alt="Cowboy Dries at DrupalCon Nashville" height="510" src="/files/cowboy-dries-at-drupalcon-nashville-742x1114.jpg" width="742" /></p>
1282 <p><em>© <a href="https://www.flickr.com/photos/155787132@N07/">Yes Moon</a> </em></p>
1283 <p>Last week, I shared my <a href="https://dri.es/tag/state-of-drupal">State of Drupal presentation</a> at Drupalcon Nashville. In addition to <a href="https://dri.es/files/state-of-drupal-april-2018.pdf">sharing my slides</a>, I wanted to provide more information on how you can participate in the various initiatives presented in my keynote, such as growing Drupal adoption or evolving our community values and principles.</p>
1284 <h3>Drupal 8 update</h3>
1285 <p>During the first portion of my presentation, I provided an overview of Drupal 8 updates. Last month, the Drupal community celebrated an important milestone with the successful <a href="https://dri.es/drupal-8-5-0-released">release of Drupal 8.5</a>, which ships with improved features for content creators, site builders, and developers.</p>
1286 <p>Drupal 8 continues to gain momentum, as the number of Drupal 8 sites has grown 51 percent year-over-year:</p>
1287 <p class="center"><img alt="Drupal 8 site growth" height="417" src="/files/drupal-8-site-growth-742x1114.jpg" width="742" /></p>
1288 <p><em>This graph depicts the number of Drupal 8 sites built since April 2015. Last year there were 159,000 sites and this year there are 241,000 sites, representing a 51% increase year-over-year.</em></p>
1289
1290 <p>Drupal 8's module ecosystem is also maturing quickly, as 81 percent more Drupal 8 modules have become stable in the past year:</p>
1291 <p class="center"><img alt="Drupal 8 module readiness" height="417" src="/files/drupal-8-module-readiness-742x1114.jpg" width="742" /></p>
1292 <p><em>This graph depicts the number of modules now stable since January 2016. This time last year there were 1,028 stable projects and this year there are 1,860 stable projects, representing an 81% increase year-over-year.</em></p>
1293
1294 <p>As you can see from the <a href="https://www.drupal.org/core/roadmap">Drupal 8 roadmap</a>, improving the ease of use for content creators remains our top priority:</p>
1295 <p class="center"><img alt="Drupal 8 roadmap" height="417" src="/files/drupal-8-roadmap-742x1114.jpg" width="742" /></p>
1296 <p><em>This roadmap depicts Drupal 8.5, 8.6, and 8.7+, along with a column for "wishlist" items that are not yet formally slotted. The contents of this roadmap can be found at <a href="https://www.drupal.org/core/roadmap">https://www.drupal.org/core/roadmap</a>.</em></p>
1297
1298 <h3>Four ways to grow Drupal adoption</h3>
1299 <p>Drupal 8 was released at the end of 2015, which means our community has had over two years of real-world experience with Drupal 8. It was time to take a step back and assess additional growth initiatives based on what we have learned so far.</p>
1300 <p>In an effort to better understand the biggest hurdles facing Drupal adoption, we interviewed over 150 individuals around the world that hold different roles within the community. We talked to Drupal front-end and back-end developers, contributors, trainers, agency owners, vendors that sell Drupal to customers, end users, and more. Based on their feedback, we established four goals to help accelerate Drupal adoption.</p>
1301 <p class="center"><img alt="Lets grow Drupal together" height="416" src="/files/lets-grow-drupal-together-742x1114.jpg" width="742" /></p>
1302 <h4>Goal 1: Improve the technical evaluation process</h4>
1303 <p>Matthew Grasmick recently completed an exercise in which he <a href="http://matthewgrasmick.com/compare-php-frameworks">assessed the technical evaluator experience of four different PHP frameworks</a>, and discovered that <a href="https://www.youtube.com/watch?v=9E34hSVFE94">Drupal required the most steps to install</a>. Having <a href="https://dri.es/three-ways-we-can-improve-drupal-evaluator-experience">a good technical evaluator experience is critical</a>, as it has a direct impact on adoption rates.</p>
1304 <p>To improve the Drupal evaluation process, we've proposed the following initiatives:</p>
1305 <table><thead><tr><td>Initiative</td>
1306 <td>Issue link</td>
1307 <td>Stakeholders</td>
1308 <td>Initiative coordinator</td>
1309 <td>Status</td>
1310 </tr></thead><tbody><tr><td>Better discovery experience on Drupal.org</td>
1311 <td><a href="https://www.drupal.org/drupalorg/roadmap">Drupal.org roadmap</a></td>
1312 <td>Drupal Association</td>
1313 <td><a href="https://www.drupal.org/u/hestenet">hestenet</a></td>
1314 <td>Under active development</td>
1315 </tr><tr><td>Better "getting started" documentation</td>
1316 <td><a href="https://www.drupal.org/node/2956879">#2956879</a></td>
1317 <td>Documentation Working Group</td>
1318 <td><a href="https://www.drupal.org/u/grasmash">grasmash</a></td>
1319 <td>In planning</td>
1320 </tr><tr><td>More modern administration experience</td>
1321 <td><a href="https://www.drupal.org/node/2957457">#2957457</a></td>
1322 <td>Core contributors</td>
1323 <td><a href="https://www.drupal.org/u/ckrina">ckrina</a> and <a href="https://www.drupal.org/u/yoroy">yoroy</a></td>
1324 <td>Under active development</td>
1325 </tr></tbody></table><p>To become involved with one of these initiatives, click on its "Issue link" in the table above. This will take you to Drupal.org, where you can contribute by sharing your ideas or lending your expertise to move an initiative forward.</p>
1326 <h4>Goal 2: Improve the content creator experience</h4>
1327 <p>Throughout the interview process, it became clear that ease of use is a feature now expected of all technology. For Drupal, this means improving the content creator experience through a modern administration user interface, drag-and-drop media management and page building, and improved site preview functionality.</p>
1328 <p>The good news is that all of these features are already under development through the <a href="https://dri.es/an-update-on-the-media-initiative-for-drupal-8-4-8-5">Media</a>, <a href="https://dri.es/an-update-on-the-workflow-initiative-for-drupal-8-4-8-5">Workflow</a>, <a href="https://dri.es/an-update-on-the-layout-initiative-for-drupal-8-4-8-5">Layout</a> and <a href="https://www.drupal.org/node/2926656">JavaScript Modernization</a> initiatives.</p>
1329 <p>Most of these initiative teams meet weekly on <a href="https://www.drupal.org/slack">Drupal Slack</a> (see the <a href="https://calendar.google.com/calendar/embed?src=happypunch.com_eq0e09s0kvcs7v5scdi8f8cm70%40group.calendar.google.com">meetings calendar</a>), which gives community members an opportunity to meet team members, receive information on current goals and priorities, and volunteer to contribute code, testing, design, communications, and more.</p>
1330 <h4>Goal 3: Improve the site builder experience</h4>
1331 <p>Our research also showed that to improve the site builder experience, we should focus on improving the three following areas:</p>
1332 <ul><li>The configuration management capabilities in core need to support more common use cases out-of-the-box.</li>
1333 <li>Composer and Drupal core should be better integrated to empower site builders to manage dependencies and keep Drupal sites up-to-date.</li>
1334 <li>We should provide a longer grace period between required core updates so development teams have more time to prepare, test, and upgrade their Drupal sites after each new minor Drupal release.</li>
1335 </ul><p>We plan to make all of these aspects easier for site builders through the following initiatives:</p>
1336 <table><thead><tr><td>Initiative</td>
1337 <td>Issue link</td>
1338 <td>Stakeholders</td>
1339 <td>Initiative coordinator</td>
1340 <td>Status</td>
1341 </tr></thead><tbody><tr><td>Composer &amp; Core</td>
1342 <td><a href="https://www.drupal.org/node/2958021">#2958021</a></td>
1343 <td>Core contributors + Drupal Association</td>
1344 <td>Coordinator needed!</td>
1345 <td>Proposed</td>
1346 </tr><tr><td>Config Management 2.0</td>
1347 <td><a href="https://www.drupal.org/node/2957423">#2957423</a></td>
1348 <td>Core contributors</td>
1349 <td>Coordinator needed!</td>
1350 <td>Proposed</td>
1351 </tr><tr><td>Security LTS</td>
1352 <td><a href="https://www.drupal.org/node/2909665">2909665</a></td>
1353 <td>Core committers + Drupal Security Team + Drupal Association</td>
1354 <td>Core committers and Security team</td>
1355 <td>Proposed, under discussion</td>
1356 </tr></tbody></table><h4>Goal 4: Promote Drupal to non-technical decision makers</h4>
1357 <p>The fourth initiative is unique as it will help our community to better communicate the value of Drupal to the non-technical decision makers. Today, marketing executives and content creators often influence the decision behind what CMS an organization will use. However, many of these individuals are not familiar with Drupal or are discouraged by the misconception that Drupal is primarily for developers.</p>
1358 <p>With these challenges in mind, the <a href="https://www.drupal.org/association">Drupal Association</a> has launched the <a href="https://www.drupal.org/promotedrupal">Promote Drupal Initiative</a>. This initiative will include building stronger marketing and branding, demos, events, and public relations resources that digital agencies and local associations can use to promote Drupal. The Drupal Association has set a goal of fundraising $100,000 to support this initiative, including the hiring of a marketing coordinator.</p>
1359 <p class="center"><img alt="$54k raised for the Promote Drupal initiative" height="418" src="/files/54k-raised-for-the-promote-drupal-initiative-742x1114.jpg" width="742" /></p>
1360 <p>Megan Sanicki and her team have already raised $54,000 from over 30 agencies and 5 individual sponsors in only 4 days. Clearly this initiative resonates with Drupal agencies. Please consider how you or your organization can contribute.</p>
1361 <h3>Fostering community with values and principles</h3>
1362 <p>This year at DrupalCon Nashville, over 3,000 people traveled to the Music City to collaborate, learn, and connect with one another. It's at events like DrupalCon where the impact of our community becomes tangible for many. It also serves as an important reminder that while Drupal has grown a great deal since the early days, the work needed to scale our community is never done.</p>
1363 <p>Prompted by feedback from our community, I have spent the past five months trying to better establish the <a href="https://dri.es/defining-drupal-values-and-principles">Drupal community's principles and values</a>. I have shared an "alpha" version of Drupal's values and principles at <a href="https://www.drupal.org/about/values-and-principles">https://www.drupal.org/about/values-and-principles</a>. As a next step, I will be drafting a charter for a new working group that will be responsible for maintaining and improving our values and principles. In the meantime, I invite every community member to provide feedback in <a href="https://www.drupal.org/project/issues/governance">the issue queue of the Drupal governance project</a>.</p>
1364 <p class="center"><img alt="Values and principles alpha" height="415" src="/files/values-and-principles-1-0-alpha-742x1114_0.jpg" width="742" /></p>
1365 <p><em>An overview of Drupal's values with supporting principles.</em></p>
1366
1367 <p>I believe that taking time to highlight community members that exemplify each principle can make the proposed framework more accessible. That is why it was very meaningful for me to spotlight three Drupal community members that demonstrate these principles.</p>
1368 <h4>Principle 1: Optimize for Impact - Rebecca Pilcher</h4>
1369 <p>Rebecca shares a remarkable story about Drupal's impact on her Type 1 diabetes diagnosis:</p>
1370 <iframe allow="autoplay; encrypted-media" allowfullscreen="" frameborder="0" height="360" src="https://www.youtube.com/embed/TNatUGl9trE" width="640"></iframe><h4>Principle 5: Everyone has something to contribute - Mike Lamb</h4>
1371 <p>Mike explains why Pfizer contributes millions to Drupal:</p>
1372 <iframe allow="autoplay; encrypted-media" allowfullscreen="" frameborder="0" height="360" src="https://www.youtube.com/embed/diP95t6dto0" width="640"></iframe><h4>Principle 6: Choose to Lead - Mark Conroy</h4>
1373 <p>Mark tells the story of his own Drupal journey, and how his experience inspired him to help other community members:</p>
1374 <iframe allow="autoplay; encrypted-media" allowfullscreen="" frameborder="0" height="360" src="https://www.youtube.com/embed/aGNAPvBLvdE" width="640"></iframe><h3>Watch the keynote or download my slides</h3>
1375 <p>In addition to the community spotlights, you can also watch a <a href="https://www.youtube.com/watch?v=8HkOdpNT8Ec?start=1170">recording of my keynote</a> (starting at 19:25), or you can <a href="https://dri.es/files/state-of-drupal-april-2018.pdf">download a copy of my slides</a> (164 MB).</p>
1376 <iframe allow="autoplay; encrypted-media" allowfullscreen="" frameborder="0" height="360" src="https://www.youtube.com/embed/8HkOdpNT8Ec?start=1170" width="640"></iframe></div>
1377 <div class="entry__meta__date"></div>
1378 </div></div></div></description>
1379 <pubDate>Tue, 24 Apr 2018 16:11:49 +0000</pubDate>
1380 <dc:creator>Dries</dc:creator>
1381 <guid isPermaLink="false">2965744 at https://www.drupal.org</guid>
1382 <comments>https://www.drupal.org/blog/state-of-drupal-presentation-april-2018#comments</comments>
1383 </item>
1384 <item>
1385 <title>Kevin Thull, from behind the camera</title>
1386 <link>https://www.drupal.org/forum/general/community-spotlight/2018-04-24/kevin-thull-from-behind-the-camera</link>
1387 <description><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p><img alt="Kevin Thull holding Aaron Winborn award" class="right" height="622" src="/files/Kevin_thull_web_1.jpg" width="350" />Chances are if you've attended any of the Drupal camps in North America you've run into <a href="https://www.drupal.org/u/kthull" rel="nofollow">Kevin Thull</a>. He's the fellow that is dashing from room to room before the first session begins to set up the AV equipment and checking in with presenters making sure they all "push the red button". Because of him, we are all able attend the sessions we miss while busy elsewhere. He is personally responsible for recording over 800 sessions and donating countless hours of his time.</p>
1388 <p>Not only does he record sessions at camps, he also helps organize Midwest Drupal Camp. For this next year he has been charged as their fearless leader. He will be working on their web team, arranging catering, organizing the venue, as well as doing all the audio visual.</p>
1389 <p>This year at DrupalCon Nashville the Drupal Community awarded Kevin the Aaron Winborn award. The Aaron Winborn award is presented annually to an individual who demonstrates personal integrity, kindness, and above-and-beyond commitment to the Drupal community. Kevin's commitment to capturing knowledge to share with the whole community is truly inspirational. He has provided a platform that helps tie local Drupal Communities together.</p>
1390 <p>The Drupal Community Spotlight Committee's AmyJune Hineline (<a href="http://www.drupal.org/u/volkswagenchick" rel="nofollow">volkswagenchick on drupal.org</a>)<strong> </strong>sat with Kevin before Nashville and asked him some questions about contributing to the Drupal Community.</p>
1391 <p>Ironically, AmyJune had chosen to write this spotlight on Kevin a few weeks before DrupalCon. AmyJune had asked him if he was coming to Nashville and he relayed that he had a prior commitment to attend another conference for his job. Unbeknownst to us, during the interview Kevin knew he had been awarded the honor and managed to keep it a secret. While he did mention that the marketing conference only ran through Wednesday, AmyJune was pleasantly surprised to see him take the stage.</p>
1392 <blockquote><p>Well, not too surprised, after all he truly deserves the honor.</p>
1393 </blockquote>
1394 <p><strong>How long have you been involved in the Drupal community?</strong></p>
1395 <p>I’m not involved with Drupal through my employer, I work in Marketing, but I got into Drupal through freelance.</p>
1396 <p>My first meet up was when the Using Drupal 6 book first came out. I would say that is when I first started getting involved in the community. So, that's close to 10 years now.</p>
1397 <p>I started recording Drupal Camps back in 2013. The official Chicago Camp was having issues and so we as a far western Suburban group decided to have our own camp. I thought I could do some of the logistics and session recordings since that's what I do for work. I had the same setup with video cameras in the back of the room and I spent countless hours rebuilding these presentations. It's a similar process, but it's a very a different presentation between a marketer and someone from the Drupal community giving a presentation on diversity. A marketer might have 20 slides, but a Drupal talk may have 104.</p>
1398 <p>Everybody at the time was telling me I was insane for doing this, but my response was, "Nope, it's important."</p>
1399 <p>In 2014 was the first MIDCamp and we were able to get the DA recording kits. But that was not great either. There was a lot of setup, they were expensive to ship them back and forth, they didn't work terribly well, so that's when Avi Schwab ( <a href="https://www.drupal.org/u/froboy" rel="nofollow">https://www.drupal.org/u/froboy</a>) and I started collaborating. He did all the setup for the laptops and I did all the running around from room to room and post production. We brainstormed and I started doing research. The next Suburban Camp is when I had my first test kit for what I am using today.</p>
1400 <p><strong>I saw that you recorded Pacific Northwest Drupal Summit remotely this year? Can you share that experience with us?</strong></p>
1401 <p>That's a funny story. It was the same weekend as Jersey Camp and I tend to favor camps I have already recorded. They had committed before Pacific Northwest Drupal Summit and when Amber Matz saw me at BADCAmp, I explained the conflict. I told her I had started working on the next step and would be shipping the kits to camps. I sat with her and showed her how the kit worked and she said it didn't seem too difficult, and we said "Let's do this".</p>
1402 <p>I got a new case, sent 5 kits to them. It's funny how talking with the organizers of camps helps all of this come together. Because later at New England Camp, I was explaining to one of their organizers how I was shipping kits and he suggested labeling the cables. I thought that was brilliant so I got a label maker and labeled all the cables. I wrote out more a detailed instruction guide, and all these things were things I had been meaning to do.</p>
1403 <p>I sent 5 kits, insured FedEx for around $50, whereas the DA sends this giant pelican case that must cost hundreds of dollars. That was part of the plan originally; we wanted something lightweight and easy to use. I heard they had an 84% capture rate which is a great start. The issue is that non-Macs recordings have no sound and so I have to lay up the backup recording into the video. A lot of times that back up recorder gets turned off or stopped for some reason.</p>
1404 <p>While I was in Florida I started working on pinpointing why non-Mac machines don't have audio. Later, I had mixed success at MIDCamp, I captured a couple, some didn't work, one being an Ubuntu build. At lunch I worked with that presenter to test various setups and we found a setup that worked. Once I can crack that nut, then shipping with even more instructions will increase the capture rates.</p>
1405 <p><strong>Now that you're capturing some camps remote, how does that cut into how much you like to travel?</strong></p>
1406 <p>I do like to travel, but there are a couple of issues. A) I can't be everywhere. B) I am potentially doing 13 or 14 camps this year. Which is cool now, but it may not be cool in couple of years. And C) I don't do Drupal at work and when I first starting doing this I was using all my PTO. I don’t do any Drupal at work, but I brought back all kinds of information and my boss recognized that. She said I could count those as remote days, but of course there's a limit.</p>
1407 <p>There is a balance to be found between visiting the camps and sending the kits remotely.</p>
1408 <p><strong>What are some of your favorite camps?</strong></p>
1409 <p>Everybody asks me that, that question is not fair. I like them all. It's generally the places I know the most people and/or I go ahead of time to play before camp starts. I am not a solo traveller, so if I know a lot of people at the camp I tend to like those: Badcamp, Twin Cities, St. Louis, Texas (cuz of Austin), and Montreal.</p>
1410 <p><strong>What are the things you like to do before a camp that makes it more fun?</strong></p>
1411 <p>HaHaHa, eat and drink all the things. Bar Crawls, Food Crawls, you name it.</p>
1412 <p><strong>Have you given any thought to helping with camps outside the States?</strong></p>
1413 <p>I would like to, but it’s a time and cost issue. The camps now reimburse my travel expenses. To fly to a European camp - I don’t know if that would be in their budget.</p>
1414 <p>It’s interesting, <a href="https://www.drupal.org/u/dinarcon" rel="nofollow">Mauricio Dinarte</a> tailed me for a few camps and he wanted, and he did, get some kits to start recording Nicaragua. One day he tweeted that he saw my kits at Drupal Camp Antwerp. It’s cool to see how these things grow organically. There’s not a camp that goes by where someone from the community doesn’t ask me about how everything works.</p>
1415 <h3>Congratulations Kevin!</h3>
1416 <blockquote><p>Kevin’s not just the guy who reminds us all to push the red button. He is the guy who loans out his phone when a presenter is doing a live demo and needs an internet hotspot. He is the guy spending hours during and after Drupal Camps piecing together audio and video for maximum quality. The Drupal Community has so much to thank him for, the Aaron Winborn award couldn’t have been awarded to anyone more deserving.</p>
1417 </blockquote>
1418 <p><a href="https://www.youtube.com/watch?v=nFxLfML0U28&amp;feature=youtu.be&amp;t=3m59s" rel="nofollow"><img alt="Youtube video screenshot showing Kevin Thulls award acceptance" height="309" src="/files/Aaron_winborn_Kevin_thull_web_1.png" width="550" /></a></p>
1419 <p><a href="https://youtu.be/nFxLfML0U28?t=3m59s" rel="nofollow">Link to Kevin Thull Youtube acceptance</a></p>
1420 <h3>On Kevin, from the community:</h3>
1421 <blockquote><p>“It has become a no-brainer to invite Kevin to Florida DrupalCamp and have him record and post all of our sessions online. He makes it easy for us to share our great content with a world-wide audience by coming prepared, making it easy for presenters, and uploading the video almost immediately. He’s a true asset to the community.” - <a href="https://www.drupal.org/u/ultimike" rel="nofollow">Mike Anello</a> (Florida Camp)</p>
1422 </blockquote>
1423 <hr /><blockquote><p>"His never-ending abundance of energy and positive contributions in the form of Drupal Camp video services in the US is unmatched. At the camps where I’ve spoken or helped organize he has been a great person to work with through the whole process - helpful and organized across the board." - <a href="https://www.drupal.org/u/aimeerae" rel="nofollow">Aimee Degnan Hannaford</a> (BADCamp)</p>
1424 </blockquote>
1425 <hr /><blockquote><p>“We appreciated Kevin’s willingness to send recording equipment and documentation to our event so that we could record sessions, even though he couldn’t be there. He was encouraging and helpful all along the way.” <a href="https://www.drupal.org/u/amber-himes-matz" rel="nofollow">Amber Matz</a> (PNWDS Portland)</p>
1426 </blockquote>
1427 <hr /><p>Thank you Kevin for your contribution to community, for sharing your story with us, and for being a most excellent secret keeper! And thank you to the hundreds of volunteers that make Drupal Camps, Cons, meetups and picnics a success every year. And thank you AmyJune Hineline (<a href="http://www.drupal.org/u/volkswagenchick" rel="nofollow">volkswagenchick on drupal.org</a>)<strong> </strong>for this most excellent Drupal Community Spotlight article!</p>
1428 <p>Top image credit: <a href="https://twitter.com/jordana_f/status/984541118670036993?s=21" rel="nofollow">Image by Jordana F</a></p></div></div></div></description>
1429 <pubDate>Tue, 24 Apr 2018 13:17:07 +0000</pubDate>
1430 <dc:creator>volkswagenchick</dc:creator>
1431 <guid isPermaLink="false">2965651 at https://www.drupal.org</guid>
1432 <comments>https://www.drupal.org/forum/general/community-spotlight/2018-04-24/kevin-thull-from-behind-the-camera#comments</comments>
1433 </item>
1434 <item>
1435 <title>Drupal core - Moderately critical - Cross Site Scripting - SA-CORE-2018-003</title>
1436 <link>https://www.drupal.org/sa-core-2018-003</link>
1437 <description><div class="field field-name-field-project field-type-entityreference field-label-inline clearfix"><div class="field-label">Project:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="/project/drupal">Drupal core</a></div></div></div><div class="field field-name-drupalorg-sa-date field-type-text field-label-inline clearfix"><div class="field-label">Date:&nbsp;</div><div class="field-items"><div class="field-item even">2018-April-18</div></div></div><div class="field field-name-field-sa-criticality field-type-text field-label-inline clearfix"><div class="field-label">Security risk:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="/security-team/risk-levels" class="moderately-critical" title="AC - Access complexity: Complex or highly specific (multi-step, unintuitive process with high number of dependencies)
1438 A - Authentication: User-level access (basic/commonly assigned permissions)
1439 CI - Confidentiality impact: Certain non-public data is released
1440 II - Integrity impact: Some data can be modified
1441 E - Exploit (Zero-day impact): Theoretical or white-hat (no public exploit code or documentation on development exists)
1442 TD - Target distribution: Default or common module configurations are exploitable, but a config change can disable the exploit"><strong>Moderately critical</strong> 12∕25 AC:Complex/A:User/CI:Some/II:Some/E:Theoretical/TD:Default</a></div></div></div><div class="field field-name-field-sa-type field-type-text field-label-inline clearfix"><div class="field-label">Vulnerability:&nbsp;</div><div class="field-items"><div class="field-item even">Cross Site Scripting</div></div></div><div class="field field-name-field-sa-cve field-type-text field-label-inline clearfix"><div class="field-label">CVE IDs:&nbsp;</div><div class="field-items"><div class="field-item even">CVE-2018-9861</div></div></div><div class="field field-name-field-sa-description field-type-text-long field-label-above"><div class="field-label">Description:&nbsp;</div><div class="field-items"><div class="field-item even"><p>
1443 CKEditor, a third-party JavaScript library included in Drupal core, has <a href="https://ckeditor.com/blog/CKEditor-4.9.2-with-a-security-patch-released/" rel="nofollow">fixed a cross-site scripting (XSS) vulnerability</a>. The vulnerability stemmed from the fact that it was possible to execute XSS inside CKEditor when using the <code class="language-php">image2</code> plugin (which Drupal 8 core also uses).
1444 </p>
1445 <p>
1446 We would like to thank the CKEditor team for patching the vulnerability and coordinating the fix and release process, and matching the Drupal core security window.
1447 </p></div></div></div><div class="field field-name-field-sa-solution field-type-text-long field-label-above"><div class="field-label">Solution:&nbsp;</div><div class="field-items"><div class="field-item even"><ul><li>If you are using Drupal 8, update to <a href="https://www.drupal.org/project/drupal/releases/8.5.2" rel="nofollow">Drupal 8.5.2</a> or <a href="https://www.drupal.org/project/drupal/releases/8.4.7" rel="nofollow">Drupal 8.4.7</a>.
1448 </li><li>The Drupal 7.x <a href="https://www.drupal.org/project/ckeditor" rel="nofollow">CKEditor contributed module</a> is not affected if you are running CKEditor module 7.x-1.18 and using CKEditor from the CDN, since it currently uses a version of the CKEditor library that is not vulnerable.</li>
1449 <li>If you installed CKEditor in Drupal 7 using another method (for example with the <a href="https://www.drupal.org/project/wysiwygw" rel="nofollow">WYSIWYG</a> module or the CKEditor module with CKEditor locally) and you’re using a version of CKEditor from 4.5.11 up to 4.9.1, update the third-party JavaScript library by <a href="https://ckeditor.com/ckeditor-4/download/" rel="nofollow">downloading CKEditor 4.9.2 from CKEditor's site</a>.</li>
1450 </ul></div></div></div><div class="field field-name-field-sa-reported-by field-type-text-long field-label-above"><div class="field-label">Reported By:&nbsp;</div><div class="field-items"><div class="field-item even"><ul><li><a href="https://www.drupal.org/user/3560461" rel="nofollow">Kyaw Min Thein </a></li>
1451 </ul></div></div></div><div class="field field-name-field-sa-fixed-by field-type-text-long field-label-above"><div class="field-label">Fixed By:&nbsp;</div><div class="field-items"><div class="field-item even"><ul><li><a href="https://www.drupal.org/user/3339830" rel="nofollow">Marek Lewandowski </a> of the CKEditor team</li>
1452 <li><a href="https://www.drupal.org/user/184556" rel="nofollow">Wiktor Walc</a> of the CKEditor team</li>
1453 <li><a href="https://www.drupal.org/u/wim-leers" rel="nofollow">Wim Leers</a></li>
1454 <li><a href="https://www.drupal.org/u/xjm" rel="nofollow">xjm </a> Of the Drupal Security Team</li>
1455 <li><a href="https://www.drupal.org/user/395439" rel="nofollow">Lee Rowlands </a> of the Drupal Security Team</li>
1456 <li><a href="https://www.drupal.org/user/99340" rel="nofollow">Daniel Wehner</a></li>
1457 <li><a href="https://www.drupal.org/user/210762" rel="nofollow">Hai-Nam Nguyen</a></li>
1458 <li><a href="https://www.drupal.org/user/1602706" rel="nofollow">Matthew Grill</a></li>
1459 </ul></div></div></div></description>
1460 <pubDate>Wed, 18 Apr 2018 15:34:09 +0000</pubDate>
1461 <dc:creator>Drupal Security Team</dc:creator>
1462 <guid isPermaLink="false">2962129 at https://www.drupal.org</guid>
1463 </item>
1464 <item>
1465 <title>Dries Buytaert Shares His View on Decoupled Drupal: When, Why, and How</title>
1466 <link>https://www.drupal.org/blog/dries-buytaert-shares-his-view-on-decoupled-drupal-when-why-and-how</link>
1467 <description><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p><em>The following blog was written by Drupal Association Signature Hosting Supporter, <a href="https://www.drupal.org/open-social" rel="nofollow">A</a><a href="https://www.drupal.org/acquia" rel="nofollow">cquia</a>. </em></p>
1468 <p class="center"><img alt="" height="236" src="/files/GettyImages.jpg" width="365" /></p>
1469 <p>More and more developers are choosing content-as-a-service solutions known as decoupled CMSes, and due to this trend, people are asking whether decoupled CMSes are challenging the market for traditional CMSes.</p>
1470 <p>By nature, decoupled CMSes lack end-user front ends, provide few to no editorial tools for display and layout, and as such leave presentational concerns almost entirely up to the front-end developer. Luckily, Drupal has one crucial advantage that propels it beyond these concerns of emerging decoupled competitors.</p>
1471 <p>Join Dries Buytaert, founder of Drupal and CTO at Acquia, as he shares his knowledge on how Drupal has an advantage over competitors, and discusses his point-of-view on why, when, and how you should implement decoupled Drupal.</p>
1472 <p>Dries will touch on:</p>
1473 <ul><li>His thoughts on decoupled CMSes - where is the CMS market headed and when?</li>
1474 <li>His opinion on whether decoupled CMSes will replace traditional CMSes</li>
1475 <li>The advantages of decoupled Drupal vs. emerging decoupled competitors</li>
1476 <li>Considerations when determining if decoupled Drupal is right for your project</li>
1477 </ul><h3><a href="https://www.acquia.com/resources/webinars/dries-buytaert-shares-his-view-decoupled-drupal-when-why-and-how?cid=7010c000002ZXzYAAW&amp;ct=online-advertising&amp;ls=drupalpremiumbenefits-dries&amp;lls=pro_ww_drupalassociationpremiumbenefits_2018" rel="nofollow"><strong>Click here to watch the webinar.</strong></a></h3>
1478 <hr /><h2><img alt="" height="280" src="/files/dries_0_0.jpg" width="300" /></h2>
1479 <h3>Dries Buytaert</h3>
1480 <p>CHAIRMAN, CHIEF TECHNOLOGY OFFICERACQUIA, INC.</p>
1481 <p>Dries Buytaert is an open source developer and technology executive. He is the original creator and project lead for <a href="http://drupal.com/" rel="nofollow">Drupal</a>, an open source platform for building websites and digital experiences. Buytaert is also co-founder and chief technology officer of Acquia, a venture-backed technology company. Acquia provides an open cloud platform to many <a href="https://www.acquia.com/resources/acquia-tv/conference/acquia-worlds-greatest-digital-experiences" rel="nofollow">large organizations</a>, which helps them build, deliver and optimize digital experiences. A <a href="https://en.wikipedia.org/wiki/Young_Global_Leaders" rel="nofollow">Young Global Leader</a> at the <a href="http://www.weforum.org/" rel="nofollow">World Economic Forum</a>, he holds a PhD in computer science and engineering from Ghent University and a Licentiate Computer Science (MsC) from the University of Antwerp. He was named CTO of the Year by the Massachusetts Technology Leadership Council, New England Entrepreneur of the Year by Ernst &amp; Young, and a Young Innovator by MIT Technology Review. He blogs frequently on <a href="http://buytaert.net/tag/drupal" rel="nofollow">Drupal</a>, <a href="http://buytaert.net/tag/open-source" rel="nofollow">open source</a>, <a href="http://buytaert.net/tag/startup-lessons" rel="nofollow">startups</a>, <a href="http://buytaert.net/tag/business" rel="nofollow">business</a>, and <a href="http://buytaert.net/tag/the-future" rel="nofollow">the future</a> at <a href="http://buytaert.net/" rel="nofollow">d</a><a href="https://dri.es/" rel="nofollow">ri.es</a>.</p>
1482 <p><a href="http://www.linkedin.com/in/buytaert" rel="nofollow">LinkedIn</a></p>
1483 <p><a href="https://twitter.com/Dries" rel="nofollow">Twitter</a></p>
1484 <hr /><p><a href="https://www.acquia.com/resources/webinars/dries-buytaert-shares-his-view-decoupled-drupal-when-why-and-how?cid=7010c000002ZXzYAAW&amp;ct=online-advertising&amp;ls=drupalpremiumbenefits-dries&amp;lls=pro_ww_drupalassociationpremiumbenefits_2018" target="_blank" rel="nofollow">https://www.acquia.com/resources/webinars/dries-buytaert-shares-his-view-decoupled-drupal-when-why-and-how?cid=7010c000002ZXzYAAW&amp;ct=online-advertising&amp;ls=drupalpremiumbenefits-dries&amp;lls=pro_ww_drupalassociationpremiumbenefits_2018</a></p></div></div></div></description>
1485 <pubDate>Mon, 16 Apr 2018 18:04:33 +0000</pubDate>
1486 <dc:creator>natalie_wright</dc:creator>
1487 <guid isPermaLink="false">2944828 at https://www.drupal.org</guid>
1488 <comments>https://www.drupal.org/blog/dries-buytaert-shares-his-view-on-decoupled-drupal-when-why-and-how#comments</comments>
1489 </item>
1490 <item>
1491 <title>Implementation Guide on Headless and Decoupled CMS</title>
1492 <link>https://www.drupal.org/association/supporters/blog/implementation-guide-on-headless-and-decoupled-cms</link>
1493 <description><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p><em>The following blog was written by Drupal Association Signature Hosting Supporter, <a href="https://www.drupal.org/open-social" rel="nofollow">A</a><a href="https://www.drupal.org/acquia" rel="nofollow">cquia</a>. </em></p>
1494 <p><img alt="" height="500" src="/files/Drupal-%20Coupled%20vs.%20Decoupled.png" width="1000" /></p>
1495 <p>The rapid evolution of diverse end-user clients and applications has given rise to a dizzying array of digital channels to support.</p>
1496 <p>Websites in the past were built from monolithic architectures utilizing web content management solutions that deliver content through a templating solution tightly “coupled” with the content management system on the back-end.</p>
1497 <p>Agile organizations crave flexibility, and strive to manage structured content across different presentation layers consistently in a way that’s scalable.</p>
1498 <p>Accomplishing this efficiently requires that teams have flexibility in the front-end frameworks that dominate the modern digital landscape. That’s why decoupled and headless CMS is taking off. That’s why you’re here. But now you need the right technology to support the next phase of the web and beyond.</p>
1499 <h3><a href="https://www.acquia.com/resources/ebooks/how-guide-headless-and-decoupled-cms?cid=7010c000002ZXzYAAW&amp;ct=online-advertising&amp;ls=drupalpremiumbenefits-decoupled&amp;lls=pro_ww_drupalassociationpremiumbenefits_2018" rel="nofollow"><strong>Download this eBook on headless and decoupled CMS</strong></a></h3></div></div></div></description>
1500 <pubDate>Mon, 02 Apr 2018 21:03:18 +0000</pubDate>
1501 <dc:creator>natalie_wright</dc:creator>
1502 <guid isPermaLink="false">2957964 at https://www.drupal.org</guid>
1503 <comments>https://www.drupal.org/association/supporters/blog/implementation-guide-on-headless-and-decoupled-cms#comments</comments>
1504 </item>
1505 <item>
1506 <title>Drupal core - Highly critical - Remote Code Execution - SA-CORE-2018-002</title>
1507 <link>https://www.drupal.org/sa-core-2018-002</link>
1508 <description><div class="field field-name-field-project field-type-entityreference field-label-inline clearfix"><div class="field-label">Project:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="/project/drupal">Drupal core</a></div></div></div><div class="field field-name-drupalorg-sa-date field-type-text field-label-inline clearfix"><div class="field-label">Date:&nbsp;</div><div class="field-items"><div class="field-item even">2018-March-28</div></div></div><div class="field field-name-field-sa-criticality field-type-text field-label-inline clearfix"><div class="field-label">Security risk:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="/security-team/risk-levels" class="highly-critical" title="AC - Access complexity: None (user visits page)
1509 A - Authentication: None (all/anonymous users)
1510 CI - Confidentiality impact: All non-public data is accessible
1511 II - Integrity impact: All data can be modified or deleted
1512 E - Exploit (Zero-day impact): Exploit exists (documented or deployed exploit code already in the wild)
1513 TD - Target distribution: Default or common module configurations are exploitable, but a config change can disable the exploit"><strong>Highly critical</strong> 24∕25 AC:None/A:None/CI:All/II:All/E:Exploit/TD:Default</a></div></div></div><div class="field field-name-field-sa-type field-type-text field-label-inline clearfix"><div class="field-label">Vulnerability:&nbsp;</div><div class="field-items"><div class="field-item even">Remote Code Execution </div></div></div><div class="field field-name-field-sa-cve field-type-text field-label-inline clearfix"><div class="field-label">CVE IDs:&nbsp;</div><div class="field-items"><div class="field-item even">CVE-2018-7600</div></div></div><div class="field field-name-field-sa-description field-type-text-long field-label-above"><div class="field-label">Description:&nbsp;</div><div class="field-items"><div class="field-item even"><p>
1514 A remote code execution vulnerability exists within multiple subsystems of Drupal 7.x and 8.x. This potentially allows attackers to exploit multiple attack vectors on a Drupal site, which could result in the site being completely compromised.
1515 </p>
1516 <p>
1517 The security team has written an <a href="https://groups.drupal.org/security/faq-2018-002" rel="nofollow"> FAQ</a> about this issue.
1518 </p>
1519 <p><em>Edited 2020, February 13 to fix links to patch files.</em></p></div></div></div><div class="field field-name-field-sa-solution field-type-text-long field-label-above"><div class="field-label">Solution:&nbsp;</div><div class="field-items"><div class="field-item even"><p>Upgrade to the most recent version of Drupal 7 or 8 core. </p>
1520 <ul><li><strong>If you are running 7.x, upgrade to <a href="https://www.drupal.org/project/drupal/releases/7.58" rel="nofollow">Drupal 7.58</a>.</strong> (If you are unable to update immediately, you can attempt to apply <a href="https://git.drupalcode.org/project/drupal/commit/2266d2a83db50e2f97682d9a0fb8a18e2722cba5" rel="nofollow">this patch</a> to fix the vulnerability until such time as you are able to completely update.)</li>
1521 <li><strong>If you are running 8.5.x, upgrade to <a href="https://www.drupal.org/project/drupal/releases/8.5.1" rel="nofollow">Drupal 8.5.1</a>.</strong> (If you are unable to update immediately, you can attempt to apply <a href="https://git.drupalcode.org/project/drupal/commit/5ac8738fa69df34a0635f0907d661b509ff9a28f" rel="nofollow">this patch</a> to fix the vulnerability until such time as you are able to completely update.)</li>
1522 </ul><p>Drupal 8.3.x and 8.4.x are no longer supported and we don't normally provide security releases for <a href="https://www.drupal.org/core/release-cycle-overview" rel="nofollow">unsupported minor releases</a>. However, given the potential severity of this issue, we <em>are</em> providing 8.3.x and 8.4.x releases that includes the fix for sites which have not yet had a chance to update to 8.5.0. </p>
1523 <p>Your site's update report page will recommend the 8.5.x release even if you are on 8.3.x or 8.4.x. Please take the time to update to a supported version after installing this security update. </p>
1524 <ul><li>If you are running 8.3.x, upgrade to <a href="https://www.drupal.org/project/drupal/releases/8.3.9" rel="nofollow">Drupal 8.3.9</a> or apply <a href="https://cgit.drupalcode.org/drupal/rawdiff/?h=8.5.x&amp;id=5ac8738fa69df34a0635f0907d661b509ff9a28f" rel="nofollow">this patch</a>.</li>
1525 <li>If you are running 8.4.x, upgrade to <a href="https://www.drupal.org/project/drupal/releases/8.4.6" rel="nofollow">Drupal 8.4.6</a> or apply <a href="https://cgit.drupalcode.org/drupal/rawdiff/?h=8.5.x&amp;id=5ac8738fa69df34a0635f0907d661b509ff9a28f" rel="nofollow">this patch</a>.</li>
1526 </ul><p>This issue also affects Drupal 8.2.x and earlier, which are no longer supported. If you are running any of these versions of Drupal 8, update to a more recent release and then follow the instructions above.</p>
1527 <p>This issue also affects Drupal 6. Drupal 6 is End of Life. For more information on Drupal 6 support please contact a <a href="/project/d6lts" rel="nofollow">D6LTS vendor</a>.</p></div></div></div><div class="field field-name-field-sa-reported-by field-type-text-long field-label-above"><div class="field-label">Reported By:&nbsp;</div><div class="field-items"><div class="field-item even"><ul><li> <a href="/u/Jasu_M" rel="nofollow">Jasper Mattsson</a> </li>
1528 </ul></div></div></div><div class="field field-name-field-sa-fixed-by field-type-text-long field-label-above"><div class="field-label">Fixed By:&nbsp;</div><div class="field-items"><div class="field-item even"><ul><li> <a href="https://www.drupal.org/u/Jasu_M">Jasper Mattsson</a> </li>
1529 <li><a href="https://www.drupal.org/user/2582268">Samuel Mortenson </a> Provisional Drupal Security Team member </li>
1530 <li><a href="https://www.drupal.org/user/124982">David Rothstein </a> of the Drupal Security Team</li>
1531 <li><a href="https://www.drupal.org/user/65776">Jess (xjm)</a> of the Drupal Security Team</li>
1532 <li><a href="https://www.drupal.org/user/102818">Michael Hess </a> of the Drupal Security Team</li>
1533 <li><a href="https://www.drupal.org/u/larowlan">Lee Rowlands </a> of the Drupal Security Team</li>
1534 <li><a href="https://www.drupal.org/user/49851">Peter Wolanin </a> of the Drupal Security Team</li>
1535 <li><a href="https://www.drupal.org/u/alexpott">Alex Pott </a> of the Drupal Security Team</li>
1536 <li><a href="https://www.drupal.org/u/dsnopek">David Snopek</a> of the Drupal Security Team</li>
1537 <li><a href="https://www.drupal.org/u/pere-orga">Pere Orga </a> of the Drupal Security Team</li>
1538 <li><a href="https://www.drupal.org/u/drumm">Neil Drumm</a> of the Drupal Security Team</li>
1539 <li><a href="https://www.drupal.org/u/cashwilliams">Cash Williams </a> of the Drupal Security Team</li>
1540 <li><a href="https://www.drupal.org/u/dawehner">Daniel Wehner</a></li>
1541 <li><a href="https://www.drupal.org/u/tim.plunkett">Tim Plunkett</a></li>
1542 </ul><h2> Contact and more information</h2>
1543 <p>The Drupal security team can be reached by email at security at drupal.org or via the contact form.</p>
1544 <p>Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.</p>
1545 </div></div></div></description>
1546 <pubDate>Wed, 28 Mar 2018 18:14:10 +0000</pubDate>
1547 <dc:creator>Drupal Security Team</dc:creator>
1548 <guid isPermaLink="false">2956770 at https://www.drupal.org</guid>
1549 </item>
1550 <item>
1551 <title>Thunder, the Drupal 8 Distribution for Professional Publishing</title>
1552 <link>https://www.drupal.org/blog/thunder-the-drupal-8-distribution-for-professional-publishing</link>
1553 <description><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><blockquote><p><em><strong>Thunder is proud sponsor of the Media and Publishing Summit ahead of the DrupalCon in Nashville. Meet us on 9th April and during the DrupalCon to learn more about Thunder and how it is used in professional publishing.</strong></em></p>
1554 </blockquote>
1555 <p><img alt="" height="405" src="/files/Thunder1.png" width="620" /></p>
1556 <h3><a href="https://thunder.org/" rel="nofollow">https://thunder.org/</a></h3>
1557 <p>Thunder is the Drupal 8 distribution for professional publishing. Thunder was designed by Hubert Burda Media and released as open-source software under the GNU General Public License in 2016. As members of the Thunder community, publishers, partners, and developers build custom extensions and share them with the community to further enhance Thunder.</p>
1558 <p>Thunder consists of the current Drupal 8 functionality, lots of handpicked publisher-centric modules with custom enhancements (our own Thunder Admin Theme, the Paragraphs module, the Media Entity module, the Entity Browser module, and lots more), and an environment which makes it easy to install, deploy and add new functionality (e.g. the Thunder Updater).</p>
1559 <p>To learn more about Thunder projects, read these case studies: German magazine Mein Schöner Garten (<a href="https://www.drupal.org/case-study/gardening-magazine-for-hubert-burda-media" rel="nofollow">Gardening Magazine for Hubert Burda Media</a>), US magazine American Heritage (<a href="https://www.drupal.org/case-study/american-heritage-magazine-migration-drupal-8" rel="nofollow">American Heritage Magazine Migration – Drupal 8</a>), and Serbian television and radio station PannonRTV (<a href="https://www.drupal.org/case-study/news-portal-for-media-house-pannonrtv" rel="nofollow">News portal for media house – PannonRTV</a>).</p>
1560 <h4>About the idea:</h4>
1561 <p>We at the Thunder Core Team believe that publishers do not compete with each other through technology, but rather through content and brands. That is why the German publisher Hubert Burda Media established the Thunder community which aims to join forces among media companies by sharing code and innovation power. The goal is to innovate faster and spend less money overall by working together.</p>
1562 <p>The Thunder community’s core product is the open-source content management system Thunder. Community members develop useful modules, use them for their own purposes and share them with the community by publishing them under the GNU General Public License. Neither Hubert Burda Media nor the other publishers in the community charge anyone for their contributions.</p>
1563 <p>Any company publishing content professionally is welcome as a member of the Thunder community - both as user and as contributor. Anyone can join by contributing to the distribution. The usefulness and richness of Thunder’s functionality directly benefit from the number of contributors.</p>
1564 <h3>Why Drupal was chosen: </h3>
1565 <p>For Burda, Drupal is the content management platform of choice. It is a free and open-source content-management framework written in PHP and distributed under the GNU General Public License.</p>
1566 <p>The standard Drupal core already provides the essential features, e.g. user management, menu management, RSS feeds, taxonomy, page layout customization, and system administration. It is easily adaptable and extensible with thousands of modules provided by a global community of users and developers. In addition, developers at Hubert Burda Media have had previous good experiences with Drupal. Drupal is therefore a tried and tested basis and has become even better with Drupal 8.</p>
1567 <h3>Describe the project (goals, requirements and outcome): </h3>
1568 <p>Thunder started as a way to share innovation and synergies among the many different brands and products within the Burda Corporation to save costs and speed up the time to market. It did not take long until we realized that the model that worked within the very diverse Burda universe would be useful for almost all digital publishers. That was when we decided to open source the distribution.</p>
1569 <p>Due to its open source basis on Drupal 8, all features and functionality within Thunder are available to anyone wishing to benefit from Burda’s industry experience. Individual brands can add modules to tailor the system to their specific needs. Many of those “specific” customizations will prove to be valuable to more than just the organizations they originated from. We therefore designed Thunder in a way that we can easily incorporate those add-ons into the main distribution and share the features among all brands.</p>
1570 <p><img alt="" height="394" src="/files/Thunder2.png" width="620" /></p>
1571 <h4>Goals:</h4>
1572 <p>We aim at becoming the best open-source content management system for professional publishing. In this, we focus on the creation of content. We want to help editors to create articles, to add media, to build landing pages, in short, to share their stories with the world.<br />
1573 We want Thunder to be a CMS jointly developed by its users and are therefore working towards building a community of publishers, IT agencies, and anyone else who shares our ideas and contributes to Thunder.</p>
1574 <p>Our aim in doing so is to stay very close to the Drupal community and the Drupal core instead of creating a Thunder fork. Whenever we want to implement a new functionality or solve a problem, we try to do this in Drupal core or in the modules Thunder uses instead of fixing things in the distribution.</p>
1575 <h4>Time spent:</h4>
1576 <p>It’s difficult to measure the time spent on the development of Thunder, as this is an ongoing process. Currently, there are four developers employed by Hubert Burda Media working on the distribution full-time, plus several external developers. They focus on the advancement of Thunder as well as Drupal core and the contrib modules used in the distribution. A community manager is working on coordinating and growing the Thunder community of publishers, developers, and other partners.</p>
1577 <h4>Timeline and Milestones:</h4>
1578 <ul><li>30th August 2015: Repository and first commits for Thunder</li>
1579 <li>September 2015: playboy.de – the first website running on Thunder</li>
1580 <li>November 2015: instyle.de – the second website running on Thunder as well as proof of concept of the sharing model</li>
1581 <li>17th March 2016: Official press release about Thunder</li>
1582 <li>October 2016: produceretailer.com is the first professional non-Burda website running on Thunder</li>
1583 <li>30th January 2017: Release of Thunder 1.0</li>
1584 <li>March 2016: One year after the official launch of the Thunder initiative, 15 websites (we know of) are running on Thunder.</li>
1585 <li>1st June 2017: Release of Thunder 2.0</li>
1586 <li>20th July 2017: Release of Thunder Admin Theme</li>
1587 <li>20th November 2017: First community event, the Thunder Day in Hamburg</li>
1588 </ul><h4>Results:</h4>
1589 <p>We released Thunder 1.0 in January 2017. One year later, at least 60 professional websites that we know of now run on Thunder. In the meantime, we have also released Thunder 2.0 and the Thunder Admin Theme.</p>
1590 <p>Publishing houses grabbed the idea of working together. The Austrian publisher kurier.at, for example, contributed to the liveblog module used in Thunder and developed a new functionality to split text paragraphs.</p>
1591 <p>In community matters, we talked to more than 300 companies worldwide. We established the “Certified Thunder Integrator” program to help publishers to find IT agencies as well as IT agencies to find customers. As of now, there are more than 20 companies certified or in the certification process.</p>
1592 <p>We aim at bringing people together to share experiences. For this purpose, we introduced a Slack team for the Thunder community as well as several social media accounts. Furthermore, we organized the first community event – the Thunder Day – with around 120 participants in November 2017.</p>
1593 <h4>Challenges and how we resolved them:</h4>
1594 <h5></h5>
1595 <p><img alt="" height="447" src="/files/thunder4.png" width="620" /></p>
1596 <h5>Updating:</h5>
1597 <p>Distributions such as Thunder face the problem of losing control after the installation. How should a distribution actually deliver features and updates? We thought a lot about this problem and introduced the Thunder Updater, the “Thunder way to keep your site up to date”. Thunder checks if installed configurations have been changed – if not, they can be updated. Otherwise, you will get a message telling you there’s an update pending and what to do if you wish to have it. This functionality is currently an integral part of the distribution but we plan to detach it and publish it as a module on drupal.org soon so that everybody can use it.</p>
1598 <h5>Testing:</h5>
1599 <p>Writing an Admin Theme is very difficult because Drupal offers so many possibilities to adapt things: If you change something it can have unexpected effects in unexpected places. To avoid surprises, we developed Sharpeye, a visual regression tool. It takes screenshots and compares them in automated tests. This gives us a good overview. We open sourced the tool and you can download it here: github.com/BurdaMagazinOrg/sharpeye</p>
1600 <h4>Technical details, tips, and tricks:</h4>
1601 <h5>Tooling:</h5>
1602 <p>We invested a lot of time into automated testing but it was well worth the effort, not only for Thunder but also for Drupal core and the contrib modules we use since we discovered a lot of bugs there too.</p>
1603 <h5>Development process:</h5>
1604 <p>We don’t use a closed issue tracker but publish our tickets on drupal.org, thereby creating transparency. We use Github rather than drupal.org for the development because the developer experience is much better.</p>
1605 <h3>Organizations involved: </h3>
1606 <p><a href="https://www.drupal.org/thunder" rel="nofollow">Thunder</a></p>
1607 <p>Modules/Themes/Distributions</p>
1608 <h3>Key modules/theme/distribution used: </h3>
1609 <ul><li><a href="https://www.drupal.org/project/paragraphs" rel="nofollow">Paragraphs</a></li>
1610 <li><a href="https://www.drupal.org/project/media_entity" rel="nofollow">Media entity</a></li>
1611 <li><a href="https://www.drupal.org/project/entity_browser" rel="nofollow">Entity Browser</a></li>
1612 <li><a href="https://www.drupal.org/project/thunder_admin" rel="nofollow">Thunder Admin Theme</a></li>
1613 </ul><p><img alt="" height="289" src="/files/Thunder3.png" width="620" /></p>
1614 <h3>Why these modules/theme/distribution were chosen: </h3>
1615 <h3>Requirements / Key modules</h3>
1616 <h4>Storytelling</h4>
1617 <p>In professional publishing, it’s all about the story. It has to be easy to create a story, to extend it, to change its narrative strand, and to enrich it with multimedia content. We use the Paragraphs module for this. Instead of putting all their content in one WYSIWYG body field including images and videos, end-users can now choose on the fly between pre-defined Paragraph Types independent from one another. Paragraph Types can be anything you want from a simple text block or image to a complex and configurable slideshow. This allows editors to structure an article into sub-elements which can easily be created, edited, and reorganized.</p>
1618 <h4>Media Handling</h4>
1619 <p>Editors want to enrich their articles with pictures, videos, content from social media, and whatever else you might think of. Paragraphs are one part of this, the other is the combination of the Media Entity module and the Entity Browser module. With those modules, editors can easily upload new content but also find and reuse existing entities.</p>
1620 <h4>SEO</h4>
1621 <p>Search engine optimization plays a major role in every editor’s life. Thunder therefore gas a plethora of different adjusting screws, from several meta tags for Facebook, Twitter, and Open Graph up to the simple XML sitemap.</p>
1622 <h4>Scheduled Publishing</h4>
1623 <p>The editor’s daily life is a lot about planning. With Thunder, you can schedule articles, ensuring they will be published at a given date and time. Even more importantly, you can also schedule the time at which an article or a picture should not be shown on the website anymore, e.g. if the contract period for a photograph has ended or an event announcement isn’t useful anymore.</p>
1624 <h4>Improved Authoring Experience</h4>
1625 <p>Our primary focus is making the editors’ work with Thunder as easy as possible. In order to achieve this, we created the Thunder Admin Theme based on findings of user tests and a survey conducted with editors working with Thunder.</p>
1626 <h4>Detailed Module List</h4>
1627 <p>Find a detailed list of the modules we use in Thunder here: <a href="https://burdamagazinorg.github.io/thunder-documentation/modules" rel="nofollow">burdamagazinorg.github.io/thunder-documentation/modules</a></p>
1628 <h3>Community contributions: </h3>
1629 <p>Since we get a lot from the Drupal community, we give our best to contribute back, e.g. by fixing the bugs we find through automated tests and by supporting Drupal events and code sprints with developer time, talks, and sponsoring. Christian Fritsch, a member of the Thunder Core Team, contributed a lot of his time to the media initiative. Ingo Rübe, the initiator of Thunder, is a member of the Drupal Association’s Board of Directors.</p>
1630 <h3>Project team: </h3>
1631 <ul><li>Daniel Bosen - Lead Developer</li>
1632 <li>Christian Fritsch - Senior Developer</li>
1633 <li>Mladen Todorovic - Senior Developer</li>
1634 <li>Volker Killesreiter - Senior Developer</li>
1635 <li>Julia Pradel - Community Manager</li>
1636 <li>Ingo Rübe - Initiator of Thunder</li>
1637 <li>Collin Müller - Head of Strategic Development</li>
1638 </ul><h3>Team members: </h3>
1639 <ul><li><a href="https://www.drupal.org/u/danielbosen" rel="nofollow">daniel.bosen</a></li>
1640 <li><a href="https://www.drupal.org/u/chrfritsch" rel="nofollow">chr.fritsch</a></li>
1641 <li><a href="https://www.drupal.org/u/mtodor" rel="nofollow">mtodor</a></li>
1642 <li><a href="https://www.drupal.org/u/volkerk" rel="nofollow">volkerk</a></li>
1643 <li><a href="https://www.drupal.org/u/juliapradel" rel="nofollow">juliapradel</a></li>
1644 </ul></div></div></div></description>
1645 <pubDate>Tue, 27 Mar 2018 23:41:58 +0000</pubDate>
1646 <dc:creator>natalie_wright</dc:creator>
1647 <guid isPermaLink="false">2956541 at https://www.drupal.org</guid>
1648 <comments>https://www.drupal.org/blog/thunder-the-drupal-8-distribution-for-professional-publishing#comments</comments>
1649 </item>
1650 <item>
1651 <title>Drupal 7 and 8 core highly critical release on March 28th, 2018 PSA-2018-001</title>
1652 <link>https://www.drupal.org/psa-2018-001</link>
1653 <description><div class="field field-name-drupalorg-sa-date field-type-text field-label-inline clearfix"><div class="field-label">Date:&nbsp;</div><div class="field-items"><div class="field-item even">2018-March-21</div></div></div><div class="field field-name-field-sa-description field-type-text-long field-label-above"><div class="field-label">Description:&nbsp;</div><div class="field-items"><div class="field-item even"><ul><li>Advisory ID: DRUPAL-PSA-2018-001</li>
1654 <li>Project: Drupal Core</li>
1655 <li>Version: 7.x, 8.x</li>
1656 <li>Date: 2018-March-21</li>
1657 </ul><!--break--><h2>Description</h2>
1658 <p>There will be a security release of <strong>Drupal 7.x, 8.3.x, 8.4.x, and 8.5.x on March 28th 2018 between 18:00 - 19:30 UTC</strong>, one week from the publication of this document, that will fix a highly critical security vulnerability. The Drupal Security Team urges you to reserve time for core updates at that time because exploits <em>might</em> be developed within hours or days. Security release announcements will appear on the <a href="https://www.drupal.org/security" rel="nofollow">Drupal.org security advisory page</a>.</p>
1659 <p>While Drupal 8.3.x and 8.4.x are no longer supported and we don't normally provide security releases for <a href="https://www.drupal.org/core/release-cycle-overview" rel="nofollow">unsupported minor releases</a>, given the potential severity of this issue, we <em>are</em> providing 8.3.x and 8.4.x releases that include the fix for sites which have not yet had a chance to update to 8.5.0. The Drupal security team strongly recommends the following:</p>
1660 <ul><li>Sites on 8.3.x should immediately update to the 8.3.x release that will be provided in the advisory, and then plan to update to the latest 8.5.x security release in the next month.</li>
1661 <li>Sites on 8.4.x should immediately update to the 8.4.x release that will be provided in the advisory, and then plan to update to the latest 8.5.x security release in the next month.</li>
1662 <li>Sites on 7.x or 8.5.x can immediately update when the advisory is released using the normal procedure.</li>
1663 </ul><p>The security advisory will list the appropriate version numbers for all three Drupal 8 branches. Your site's update report page will recommend the 8.5.x release even if you are on 8.3.x or 8.4.x, but temporarily updating to the provided backport for your site's current version will ensure you can update quickly without the possible side effects of a minor version update.</p>
1664 <p>This will not require a database update.</p>
1665 <p>Patches for Drupal 7.x and 8.3.x, 8.4.x, 8.5.x and 8.6.x will be provided.</p>
1666 <p>The CVE for this issue is CVE-2018-7600. The Drupal-specific identifier for the issue is SA-CORE-2018-002.</p>
1667 <p>The Security Team or any other party is not able to release any more information about this vulnerability until the announcement is made. The announcement will be made public at <a href="https://www.drupal.org/security" rel="nofollow">https://www.drupal.org/security</a>, over Twitter, and in email for those who have subscribed to our email list. To subscribe to the email list: log in on drupal.org, go to your user profile page and subscribe to the security newsletter on the Edit » My newsletters tab.</p>
1668 <p>Journalists interested in covering the story are encouraged to email <a href="mailto:security-press@drupal.org" rel="nofollow">security-press@drupal.org</a> to be sure they will get a copy of the journalist-focused release. The Security Team will release a journalist-focused summary email at the same time as the new code release and advisory.</p>
1669 <p>If you find a security issue, please report it at <a href="https://www.drupal.org/security-team/report-issue" rel="nofollow"> https://www.drupal.org/security-team/report-issue</a>.</p>
1670 <p> updated 2018-03-22: Added information about database updates</p>
1671 <p> updated 2018-03-27: Added information about patches </p>
1672 <p> updated 2018-03-28: Added information about CVE and identifiers </p></div></div></div></description>
1673 <pubDate>Wed, 21 Mar 2018 19:13:16 +0000</pubDate>
1674 <dc:creator>Drupal Security Team</dc:creator>
1675 <guid isPermaLink="false">2955027 at https://www.drupal.org</guid>
1676 <comments>https://www.drupal.org/psa-2018-001#comments</comments>
1677 </item>
1678 </channel>
1679 </rss>