Upgrade Your Drupal Skills

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

See Advanced Courses NAH, I know Enough
Apr 12 2021
Apr 12

The last 18 months have been difficult for many in our global community. The global COVID-19 pandemic has taken loved ones from us too soon. Social and political upheaval around the world have fractured civil discourse, and set back the cause of civil rights. Economic uncertainty has affected our jobs and our prospects for the future. For some, the present crises have brought up memories of more distant loss.

In a year in which we have all experienced loss, remembrance and reflection helps us heal.

We encourage the Drupal community to share memories of lost friends, colleagues, family, and loved ones- whether that loss was recent or many years past. We encourage you to share and remember the good they brought to our lives.

We encourage you to share your words of hope for civil and societal change.

Whatever your words of hope and remembrance we encourage you to lift each other up.

How to share your words of remembrance:
The comments on this post have been opened, or you can use the hashtag #drupalmemorial on social media to tag your posts to the embedded memorial wall below

Apr 02 2021
Apr 02

Our first Drupal Initiative update was posted in December 2020 showcasing the contributions that drive our community of innovation and highlighting how you can get involved.

Rather than sharing a lengthy report every quarter, we will feature a select number of initiatives monthly to allow for the content to be more easily consumable. Initiatives will rotate so each is featured once per quarter. If you would like to add your group/initiative to these updates, please contact Rachel Lawson.

This month, we reached out to Drupal Diversity & Inclusion, DrupalLadder, Promote Drupal, Event Organizers Working Group, New Front-End Theme, and Drupal Community Working Group, and here is what they tell us about their activities over the last three months.

Join the Drupal Community Summit, Tuesday, 6 April, from 11:00 EDT - 15:00 EDT and hear from Drupal Diversity & Inclusion, Promote Drupal, Event Organizers Working Group, and the Drupal Community Working Group. 

About this initiative 

The Drupal Diversity & Inclusion group seeks to continue the conversation about diversity and inclusion within Drupal. The group organizes regular meetings and curates a resource library.

What have been your priorities in the last three months?

Over the last three months, we've been focused on the early stages of planning for Drupal Diversity & Inclusion Camp, a virtual event focused on centering and lifting up the voices of marginalized folks in the Drupal community. 

What has been your greatest challenge in the last three months?

We would love assistance in planning DDI Camp. We have a proposed budget, and now we need help with selecting and scheduling speakers, choosing a virtual tool to host the event, contacting possible sponsors, planning swag and social events, and much much more.  

And what has been your greatest success in the last three months?

We've been excited about bringing our new leads on board, and the planning for the camp is going well. 

How can people contribute or support the initiative over the next few months?

Please join us for a few upcoming events:

About this initiative 

DrupalLadder is a community initiative to create an onramp for new Drupal users as well as new contributors to the Drupal project, or for those looking to level up their skills.

What have been your priorities in the last three months?

  1. user experience when getting started (create an account, understand next steps); 
  2. adopt an up-to-date theme

What has been your greatest challenge in the last three months?

Demands on contributors' time, and keeping ourselves organized

And what has been your greatest success in the last three months?

Some very skilled contributors have done some very nice work - we're looking forward to launching it!

How can people contribute or support the initiative over the next few months?

  1. Project management
  2. Authoring content - currently requires close attention to detail and rolling with a few frustrations. 
  3. Refactor a few decoupled features that have the right concepts but groped around for the right implementation.

About this initiative 

Promote Drupal Initiative has one main purpose: to create business marketing materials targeted at the decision-makers who choose to adopt Drupal for their business.

What have been your priorities in the last three months?

It's Drupal's 20th birthday this year, plus with the first DrupalFest and DrupalCon next month, there is a lot to celebrate and highlight. As a more long-term goal, it's clear that we need a good core set of evergreen marketing content on Drupal.org.

What has been your greatest challenge in the last three months?

We need to get more organized and make it easier for people to get up and running with contributing to Promote Drupal. Hopefully, we can build on the newly organized roles and committees (see below) and the momentum of the DrupalCon Marketing Committee to take Promote Drupal to the next level!

And what has been your greatest success in the last three months?

Thanks to help from the Drupal Association, the DrupalCon Marketing Committee was formed in March and has been hard at work marketing the upcoming conference. Great work to that team!

Also, we created a common What is Drupal deck and have created evergreen versions of the Drupal Pitch Deck and Drupal 9 one-pager. Now, how to feature this content more prominently on Drupal.org? 

How can people contribute or support the initiative over the next few months?

We would love to grow the Promote Drupal team, and we have some specific roles to fill. Read about the roles and fill in our recruitment form to get involved. 

About this initiative 

The Event Organizers Working Group (EOWG) is concerned with supporting community-led events within the Drupal community. These include camps, summits, training days, contribution days, and meetups.

What have been your priorities in the last three months?

All of the EOWG priorities were focused around our three new initiatives:

  1. Onboarding to the Drupal Community at Events
  2. Drupal Events Platform
  3. Drupal Events Website / Database

During this time, we determined which board members will serve on which initiative, defined each initiative's short-term goals and drafted a call for volunteers for each initiative. I am pretty psyched about what these awesome folks have accomplished. Much love :)

What has been your greatest challenge in the last three months?

Increasing our participation is definitely our biggest challenge. Our event organizer open community meetings have been happening on Zoom for over two years now and just like everyone in the world, I think Zoom fatigue and the challenges of work-life integration can make it difficult for any additional commitments. Many of the organizers are used to attending other camps in a show of support and building community, and for me personally, I am having a tough time missing those connections. By not having the opportunities to meet people in person and talk with other event organizers make it even more difficult for us to attract new members. But I am hopeful that will soon change. 

And what has been your greatest success in the last three months?

Our greatest success was coming together in just three months and collaborating with the Drupal Association with the unveiling of a newly organized web page that will help raise the profile of all Drupal community events happening around the world. Well, I can’t actually tell you what it is. Stay tuned! 

How can people contribute or support the initiative over the next few months?

Sign up to volunteer for one of our three initiatives:  Onboarding to the Drupal Community at Events, Drupal Events Platform, Drupal Events Website / Database. View a description of all of our initiatives here.

About this initiative 

The New Front-End Theme initiative seeks to create a new default front-end theme for Drupal with a modern look and feel.

What have been your priorities in the last three months?

Working toward becoming stable and Drupal's default theme

What has been your greatest challenge in the last three months?

Code-wise, Olivero is in a great place. The difficult part is getting the code into Drupal core. To do this, we frequently have to get sign offs from accessibility maintainers prior to core committers. All of the people within these roles are very busy, and it’s hard to get their attention. This continues to be a challenge, but Mike frequently plays the role of “squeaky wheel” to get attention. The deadline for Olivero to become stable and the default theme for Drupal 9.2 is mid-May 2021, which gives us a bit over a month. We’ll have to step up our momentum if we are going to hit that. 

And what has been your greatest success in the last three months?

During Midcamp, we organized a multi-day sprint to concentrate on testing. This started with Matt Glaman teaching everyone NightwatchJS (Drupal's core JavaScript testing framework) and making sure everyone is up and running on their local environments.

A lot of people then worked together to create our first Olivero Nightwatch test, which involves checking if an element is visible, scrolling the browser, and rechecking visibility.

Later, we split off to work on more automated tests. Brian Perry led the charge to write a number of PHPUnit tests along with many others, and many of us (including Matthew Radcliffe and Benji Fisher) continued writing NightwatchJS tests to ensure the various functionality of Olivero’s menus (which are deceptively complex).

Outside of testing, we’ve been making slow but steady progress on Olivero’s technical debt and accessibility issues. Mike Herchel has been doing occasional “mini-sprints” with core-committer Lauri Eskola to work on getting RTBC issues committed and into 9.2.x. This has been working very well, and we have one more scheduled in the coming weeks.

How can people contribute or support the initiative over the next few months?

I miss you all. 

Issue reviews (from an accessibility point of view) are always helpful, plus you can find me at DrupalCon North America 2021 if you want to chat about the work we’re doing!

About this initiative 

The mission of the Community Working Group (CWG) is to foster a friendly and welcoming community for the Drupal project and to uphold the Drupal Code of Conduct.

What have been your priorities in the last three months?

We have been working to expand the size of the conflict resolution team, working to identify additional community health-related workshops that we can organizer, the launch of "nudges", continue to offer Code of Conduct contact training and make it a more visible aspect of Drupal events, the 2021 Aaron Winborn Award, and our annual report.

What has been your greatest challenge in the last three months?

Expanding the size of the conflict resolution team. Difficult choices.

And what has been your greatest success in the last three months?

Difficult to say - I'm not really sure.

How can people contribute or support the initiative over the next few months?

Be kind to each other.

Jan 14 2021
Jan 14

Drupal Birthday Cake

Today, on Drupal's 20th birthday, we are kicking off celebrations that will last throughout 2021. Together, let’s celebrate 20 years of Drupal and our Community - the inspired makers that keep Drupal innovative. 

As part of this 20-year milestone, we celebrate our community of more than 100,000 contributors who made Drupal what it is today,” says Heather Rocker, executive director of the Drupal Association. “Success at this scale is possible because the Drupal community exemplifies the values of open source and proves that innovation is sustained by healthy communities.”

To kick things off, we have a few ways for you to get involved:

With so much to celebrate, today's activities are only the beginning. Keep an eye on this blog, the @drupalassoc on Twitter, and Drupal Association on Linked In for more activities throughout 2021. 

Dec 18 2020
Dec 18

Posted on behalf of One Shoe and Exove

What is the vision of Drupal business leaders all around the world on Drupal in 2020? For the fifth year in a row Drupal agencies One Shoe and Exove, together with the Drupal Association, investigated how Drupal company leaders experience the current Drupal business ecosystem. Of course, the year 2020 is marked by the effects of the coronavirus but there’s much more to say about doing Drupal business.

Characteristics of the participants

This year, 83 people participated in the Drupal Business Survey. Out of all the participants, nearly 70 % had a CEO/CTO/COO role in their company. Other roles represented in this survey are mainly founders (15.7%), and Directors (7,2%). 


A majority of the Drupal centric businesses that participated in the survey are located in Europe (49,5%). The rest is located in:

  • North America (33%)
  • South America (3,7%)
  • Asia (12,8%) 
  • Africa (3,7%)

Almost half of the respondents were digital agencies, 20,5% software companies and 18,1% consulting agencies. As we can see from the graph below, most of the respondents are small to midsize companies. The majority of the companies that participated in the survey have been in business for over 8 years. Nearly 40% of all the respondents have been in business for over 14 years. 

We could therefore say that the opinions and experiences of people in this survey are based on years of experience with Drupal business!

Company size
Covid-19 impacts Drupal businesses in various ways

As this year comes to a close, we can only conclude that 2020 turned out differently than expected. It brought company leaders new challenges and opportunities. Generally, we can conclude (for now) that the impact of COVID-19 may be less than initially anticipated and entrepreneurs keep doing excellent Drupal business.

In the survey we asked Drupal agency leaders about their challenges and successes of this year. Many participants cited the coronavirus and its consequences as their top challenge: 

Greatest Challenges

15% of the respondents named 'Covid-19 in general' as the main challenge without further explanation. To provide more detailed information, we have broken down the answers that provide better insight into the impact of the coronavirus on businesses:

  • Covid-19 affecting client projects (13%)

In some cases, the coronavirus outbreak has had an impact on clients and their projects. One leader tells us in the survey: “[Our biggest challenge this year was] covid and seeing a couple of our sectors getting hammered. Seeing projects put on the shelf, cancelled, etc“ But it does not always lead to this. Another participant tells: “We experience uncertainty around some client's future budgets. This has not resulted in any major reductions though.”

  • Covid-19 forces remote working (10%)

Working remotely is, and remains, a major challenge for a lot of companies. “Moving to 100% remote after the pandemic [was the biggest challenge]”. Someone else mentions “remote selling” specifically as a challenge. 

  • Covid-19 affecting (mental) health of employees (8.8%)

It won’t be surprising that another big challenge was “Staff falling ill with covid and/or having children at home so staff is pressured and unable to work”. It’s worth mentioning, though, that many company leaders indicate that covid-19 has a great impact on the mental well-being of their staff but at the same time they are very proud of their team. “We have kept our team together during the covid storm” says one leader in response to the question what their greatest success of the last 12 months is. Another one said: “[Our greatest success is] Outstanding leadership from the senior technical team members (non-exec level).” “Maintaining high morale and supportive culture” someone else adds. 

Many Drupal businesses do thrive in 2020

Doing Drupal business in 2020 is not only about facing challenges - not at all. 
Many participants told us their companies thrived even despite (or due to) the effects of the coronavirus. 

Greatest successes

20% of the answers when asked about greatest success are about thriving despite Covid-19:
“We make it through the COVID months relatively well financially after pivoting to clients who luckily benefited from COVID (increased business).” Another agency leader adds: “[Our greatest success is] navigating my company successfully through a world pandemic with results that exceed the pre-covid prognosis!”.

The pandemic as a catalyst for investments in digital

What’s the success factor of these kinds of Drupal companies? Based on people’s comments, it seems there is a rapid digital adoption driven by covid-19: “[We see] increased demand due to companies going more digital during the pandemic”. Another one tells: “We launched a covid-19 site for a major healthcare client.” And: “We've won our biggest Drupal contract ever. We successfully launched our largest ever project despite coinciding with the early days of lockdown. We are educating our clients that the pandemic should be seen as a catalyst for investment in digital.”  

Another big success is launching successful Drupal projects (20%), such as: “We launched a big popular Drupal site (8.x) for German Government with integration (backend) of services” and “We have been building bigger and more complex websites with Drupal.” 

These findings correlate directly with the answers to the questions about the project pipeline, deal size, and win rate.

Pipeline Development

In the graph above you can see that Drupal project deal size has grown more in comparison with project pipeline or win rates. One business leader explains why: “We choose clients more carefully, because of that average deal size has grown significantly. On the other hand due to the more aggressive competitors sales, we have lost quite many large deals.” What this shift could mean for the future according to one respondent? “The traditional smaller scale Drupal projects are dwindling, of less value. The future is in large scale projects where Drupal is a component of a larger architecture.” Another one mentions the public sector as a profitable one: “Drupal has been "in vogue" in our market right now, especially in the public sector. We see a lot more RFQs compared to last year, and a lot of them are quite sizable.”

The project deal size growth is a very positive indicator and well in line with the Drupal’s growth to the enterprise market. As a part of the sales cost is always fixed and not dependent on the size of the deal, this will lead to bigger margins that will help the companies to develop themselves further.

Expectations for growth from 2021 onwards

The outlook for 2021 and onwards looks positive based on the survey answers. Despite the situation with COVID-19, almost half of the companies expect their business and on-going project situation to improve in the near future.

Only around 20% of the companies expect the situation to weaken in the forthcoming months, and only a fraction of them significantly. This resonates well with the earlier findings of the pandemia accelerating the need for digital services. Drupal being a versatile and flexible platform is gettings its fair share of the positive market development.

Business Impact

Profitable Drupal industries

So, Drupal business is still doing quite well. But in which industries? Each year the Drupal Business Survey asks respondents in which industries their company operates. This is the top 10 of 2020:

Top ten industries

The most popular industry for Drupal projects is the same as in 2019: the Educational sector. With 61,4% this is the sector with the most Drupal projects. It should be noted that “Education” was added to the survey in 2019 and thus 2017 and 2018 show it blank. This is followed by Charities & Non-Profit (55.4%) and Government & Public Administration (50.6%). 

However, if you compare all the industries over the years, the number of Drupal projects in the Charities & Non Profit decreased significantly. This also counts for the Arts & Culture industry. The Drupal platform is evolving towards the higher end of the spectrum with each release adding new sophisticated features. This causes the project sizes to grow which explains the drop in industries that cannot invest heavily on digital platforms. Also, Arts & Culture has been hit by coronavirus this year.

Top ten industries

Reasons for clients to choose Drupal, or not

Why is Drupal so often chosen for digital projects? When clients have previously worked with Drupal, they often choose the framework again (60% of the answers). It showcases the fact that Drupal is a good tool for solving their business problems.

It also appears that the consultancy role of the agency is significant in determining the client's choice of technology. In more than half of the answers given in the survey, the client follows the advice of the agency for choosing Drupal. Other major selling points for Drupal are its open source character, flexibility and security. 

Reasons for choosing Drupal
The main reasons for clients not choosing Drupal are consistent with last year's survey - the same underlying issues still remain today. Main reasons for potential clients choosing other platforms instead of Drupal are: 

  1. Price. For example, prices can increase significantly because Drupal is used at the higher end of the CMS spectrum, and thus development is time consuming and therefore expensive. As one respondent said “Drupal practitioners can handle more complex problems, so they're more expensive”.
  2. Complexity. Wordpress is seen as more user friendly and easier to approach. 
  3. Familiarity. Potential clients don’t seem to know much about Drupal which makes it harder to sell.

Knowing why potential clients are choosing other platforms is key in further developing Drupal and meeting client needs. Reviewing the existing target audience and marketing Drupal for the right audiences, might be things to consider to tackle these obstacles.


One thing is certain: companies - both Drupal agencies and clients - have to adjust their strategy because of covid-19. But looking at the answers given in this study, it appears that Drupal projects are getting bigger and Drupal businesses are growing - provided they operate in the right industries and succeed in working remote. Or, as a Drupal agency leader puts it, "Despite the covid epidemic, we have managed to work together and increase transparency in the business - we are now in many ways better than March." And who knows, the effects of covid-19 may as well accelerate the demand for digital projects.

Dec 07 2020
Dec 07

As part of the Drupal Association’s ongoing mission to foster contribution in the Drupal project, we're bringing you the first edition of a new Initiative Update blog series. The vision is a series with regular updates on initiatives across the Drupal ecosystem, as well as calls to action highlighting where contributors are most needed.

In gathering feedback from the community, we understand it can be difficult to identify the priorities of the Drupal community, the state of current initiatives, and how to contribute. Our goal is to provide a useful overview of current priorities in Drupal and connect you to the individual mentors, initiative leads, and other community organizers who can help you get involved. 

The plan is to provide updates on a regular basis throughout the year. We thank the Wordpress community for their example of a concise initiative update. Based on your feedback on this first edition, this format may evolve. 

If we missed reaching out to you, but you'd like to provide an update on an initiative you are involved in, please feel free to submit your update to this form.


In this release, we have reports from the following initiatives and community groups. This is not a comprehensive list of all initiatives and community groups, just those who were able to provide an update in time for this post:

Active Drupal Core Initiatives

Mike Herchel updates us about Olivero - the new front-end theme

About this Initiative: The New Front End Theme initiative seeks to create a new default front-end theme for Drupal with a modern look and feel.

Where can we read more about your initiative?


What have been your priorities in the last three months?

Getting into core! We're finally in 9.1 as a beta experimental theme. Check it out!

What has been your greatest challenge in the last three months?

Getting it into core was a mad dash at the very end, but we pulled it off thanks to a lot of help from Drupal's core contributors. Those folks are amazing! 

And what has been your greatest success in the last three months?

Getting into a beta status for core

Do you have a "call to action" you want to make to the Drupal Community?

Use it. Find and file bugs!

xjm updates us about Drupal 10 Readiness

About this Initiative: The goal of the Drupal 10 Readiness initiative is to release Drupal 10 in 2022, providing adequate time to update sites while keeping Drupal secure and up to date.

Where can we read more about your initiative?


What have been your priorities in the last three months?

  1. Ensuring that Drupal core is internally compatible with Symfony 5.0 and 5.1 (without using deprecated APIs), so that we can easily release Drupal 10 with a dependency on Symfony 6. (Done!) 
  2. Ensuring Drupal core and its upstream dependencies are fully compatible with PHP 8 as soon as possible so that Drupal 10 can set its minimum dependencies accordingly. (Done!) 
  3. Initial discovery on CKEditor 5 integration for Drupal 10 (Ongoing, challenging) 
  4. Replacing remaining forked jQuery UI code with modern alternatives (Ongoing) 
  5. Reducing jQuery use for an easier upgrade to future versions

What has been your greatest challenge in the last three months?

We have lots of JavaScript work needed, both for integrating CKEditor 5 and for reducing legacy jQuery and jQuery UI use, and few working on it these difficult problems.

And what has been your greatest success in the last three months?

Really great collaboration and problem-solving for upstream blockers to PHP 8 compatibility, and all compatibility issues with Symfony 5 are resolved, We’re now working on Symfony 6 compatibility (that is, addressing deprecations introduced in Symfony 5.1 and 5.2), which is the real goal for us for Drupal 10’s release.

Do you have a “call to action” you want to make to the Drupal Community?

Frontend contributors! We love you and we need your help!

We need help with several big changes related to core’s JavaScript: 

Furthermore, we need help from theme developers and contributors to join a new initiative to build a Starterkit Theme for Drupal core. https://www.drupal.org/project/drupal/issues/3050384 This theme starterkit will replace Classy as the best way to start building a theme for a Drupal site.

Tim Lehnen provides the latest info about Automatic Updates

About this Initiative: The goal of the Automated Updates Initiative is to provide a system to easily and securely update Drupal sites, reducing total cost of ownership for site owners. 

Where can we read more about your initiative?

The best place to stay up to date is in the Automatic Updates issue queue, or by joining us in the #Auto-Updates channel in Drupal Slack.

What have been your priorities in the last three months?

Current Priority: Finishing our implementation of the php-tuf client and server code, so that we can move from our secure signing implementation into our actual updater code. 

Previous Priority: Over the course of the last quarter, the Drupal Association hosted three contribution weeks with Drupal initiative contributors as well as representatives from Joomla and Typo3. We used these contribution sessions to scaffold out the php-tuf library and to align our architectural decisions in ways that will work across the php ecosystem. 

What has been your greatest challenge in the last three months?

Our update process must run the appropriate Composer updates as well, so we are currently attempting to architect a solution to account for the fact that Packagist itself does not yet have a signing solution for third party libraries. 

And what has been your greatest success in the last three months?

The Drupal Automatic Updates initiative has joined forces with both the Typo3 and Joomla communities to share certain foundational components, like our secure signing schema. And speaking of secure signing, we are working closely with the Cloud Native Computing Foudnation's TUF initiative for a robust and standards based signing solution. 

Do you have a "call to action" you want to make to the Drupal Community?

If you're interested in the problem-space of securely signing software, consider contributing to the php-tuf project. If you're more interested in understanding the update process itself, please join us in the Drupal Slack channel!

About this Initiative: The goal of the Decoupled Menus Initiative is to provide the best way for JavaScript front ends to consume configurable menus managed in Drupal.

Where can we read more about your initiative?

The Decoupled Menus Initiative is in the process of organizing the official initiative team. Regular meetings are happening in the #decoupled-menus-initiative in Drupal Slack.

What have been your priorities in the last three months?

The main priority for the initiative has been gathering the initial group of contributors and getting organized. There is a clear path for understanding what a javascript menu component looks like, but there are much more challenging questions to be resolved about how to integrate non-php components into the Drupal core process. 

What has been your greatest challenge in the last three months?

This initiative is in the first stages of getting organized and up to speed. In addition, understanding how to work on non-php for Drupal core is a major challenge. Once official initiative coordinators have been selected they can help to provide the next update.

And what has been your greatest success in the last three months?

Just launching this initiative as an official goal is greatly important. There has been very active conversation between initiative team members, core maintainers, and the drupal association as the organization kicks off. 

Do you have a "call to action" you want to make to the Drupal Community?

If you are an expert in using a javascript front-end for a Decoupled Drupal solution, if you are familiar with open source contribution in the javascript ecosystem, or if you are a competent project manager your insight would be valuable. Please join the initiative's slack channel and regular meetings.

Additional Core Initiatives, Community Initiatives, and Community Group Updates

Jennifer Hodgdon updates us about Documentation and Help

About this Initiative: The goal of the Documentation and Help initiative is to improve the Drupal evaluator, developer, and site builder experiences through improved documentation on Drupal.org, and improve in-application help via a new topic-based help system.

Where can we read more about your initiative?

User Guide: https://www.drupal.org/project/user_guide; Contributor Guide: https://www.drupal.org/community/about/getting-involved-guide-becoming-contributor-guide; Help Topics: https://www.drupal.org/project/drupal/issues/3027054

What have been your priorities in the last three months?

User guide: minor updates and supporting groups making translations. There has been a lot of progress lately on German and French! Help topics: mostly writing new topics, and some progress on other Roadmap issues. 

Contributor Guide: Migrating content from the old Getting Involved Guide.

What has been your greatest challenge in the last three months?

Getting other contributors to review and commit patches, and to provide feedback on plans.

And what has been your greatest success in the last three months?

Migrating most of the content in the Getting Involved Guide to make several new and better-organized areas, such as the Issues documentation at https://www.drupal.org/docs/develop/issues and the Git documentation at https://www.drupal.org/docs/develop/git

Do you have a “call to action” you want to make to the Drupal Community?

You can help with curating and migrating older documentation into the newer documentation content types, or into the new Contributor Guide. Join the #documentation channel in Drupal Slack and another contributor can help you find a place to get involved. 

Elli Ludwigson updates us about Contribution Mentoring

About this Community Group: The Contribution Mentoring Group works to inspire, enable, and encourage new contributors. They also work on the core tools, process, and community to make it easier for new contributors to get involved.

Where can we read more about your initiative?


What have been your priorities in the last three months?

Getting ready for DrupalCon Europe, updating documentation and materials

What has been your greatest challenge in the last three months?

Engagement. It's been difficult to demonstrate value and a clear path to success for contributors and mentors. Also, everyone seems a little low on energy lately and we could use more fresh folks coming into leadership roles.

And what has been your greatest success in the last three months?

Updating the contributor guide! http://drupal.org/community/contributor-guide  

Jennifer Hodgdon and others have reorganized and made everything much more logical. AmyJune continues to do an amazing amount of work at many many virtual events, giving contributors a place to get started with Drupal.

Prior to the last three months Rachel Lawson did a lot to rethink the contribution and mentoring process with the portal we used at DrupalCon Global. Matthew Radcliffe and Gábor Hojtsy did a lot of work on that as well. And Randy Fay is often on hand to help with any and all local development environments and general Drupal troubleshooting.

Do you have a "call to action" you want to make to the Drupal Community?

Without creating any new projects, I'd say we could use an enthusiastic and experienced person to help clean up old issues and polish the documentation work. We could also use more mentors on hand in general for virtual events across various time zones, especially outside the Americas.

Kaleem Clarkson updates us about Event Organizers Working Group

About this Community Group: The Event Organizers Working Group (EOWG) is concerned with supporting community-led events within the Drupal community. These include camps, summits, training days, contribution days, and meetups.

Where can we read more about your initiative?


What have been your priorities in the last three months?

Over the last three months we have mostly focused on finalizing what initiatives we should start with in 2021. 

What has been your greatest challenge in the last three months?

Our greatest challenge has been attracting more global representation at our monthly community meetings. At the beginning of this year, our group made an intentional effort in attracting more global participation. Through our efforts, we were able to recruit two new board members representing India and Ukraine. Another strategy was to change our meeting times to UTC format and alternate between 12pm and 12 am UTC. We are hoping that in 2021 we can increase the number of global camps represented in our open meetings. 

And what has been your greatest success in the last three months?

I think our biggest accomplishment has been confirming our four major initiatives that our group will focus on in 2021. These initiatives will be:

  • Onboarding At DrupalCon Community at Events, 
  • Event Organizers Website Starter Kit
  • Marketing the Events Organizer Group
  • Events Database Website on Drupal.org. 

Each initiative will have committees made up of one Event Organizer’s Working Group board member and volunteers from the Drupal community. For so many reasons, we are all looking forward to working in concert with event organizer volunteers from around the world.

Do you have a “call to action” you want to make to the Drupal Community?

We need all Drupal event volunteers to help spread the word about the Drupal Events Working Group. 

We will be looking for volunteers to serve on the committees of each of our four major initiatives and we can’t do it without you. 

Jess Snyder updates us about Nonprofits

About this Community Group: The Nonprofits Community Group provides a gathering point for all Nonprofit organizations using Drupal, and leads monthly community meetings.

Where can we read more about your initiative?


What have been your priorities in the last three months?

Our top priority continues to be to provide a welcoming place for nonprofit Drupalists to get advice, share knowledge, and discuss the issues we’re all facing in this challenging time.

What has been your greatest challenge in the last three months?

Aside from dealing with the curveballs the past several months have thrown at all of us, nonprofits continue to struggle with the changes in Drupal requirements that have increased the expertise and costs required to build and maintain Drupal sites.

And what has been your greatest success in the last three months?

Aside from seeing new faces on our monthly calls, which we’re always thrilled about, we’re also proud of how our community is encouraging nonprofit orgs to try new features, like Layout Builder, while also discussing the challenges that come with trying new features that are still in flux.

Do you have a “call to action” you want to make to the Drupal Community?

Come and join our monthly call! Held on the third Thursday of the month at 1pm ET/10am PT, it’s free of charge, beginner-friendly, and open to anybody working for or with nonprofits and Drupal. 

Call-in info can be found on our community page (https://www.drupal.org/community/nonprofit-drupal) or in our collaborative notes document (https://nten.org/drupal/notes).

Nico Grienauer updates us about Drupical

About this Initiative: Drupical is a beautified overview of Drupal Events that provides a bird’s-eye view of Drupal community events happening all over the World. 

Where can we read more about your initiative?


What have been your priorities in the last three months?

Getting the new drupical 2.0 ready for launch

What has been your greatest challenge in the last three months?

Finding time beside the global covid problems 

And what has been your greatest success in the last three months?

  • Getting finally access to drupal.org/community/events
  • Finalising the first version of the new drupical fronten now in vue.
  • Getting work done on the new drupal 8/9 drupical backend – found a possible solution, to also display online events on a map :)
  • Getting a link from the drupal main menu to drupical. 

Hopefully it will all be released in time for DrupalCon Europe!

Do you have a “call to action” you want to make to the Drupal Community?

stay healthy, stay at home and see you at one of the next virtual Drupal events!

Chris Teitzel updates us about the Privacy Initiative

About this Initiative: The Privacy Initiative focuses on addressing the increasing importance of managing user privacy in a world with increasing regulation. While the Drupal ecosystem has previously relied on solutions in contributed modules, this initiative proposes Privacy changes in Drupal Core. 

Where can we read more about your initiative?


What have been your priorities in the last three months?

We are continuing to work with the community and project stakeholders to come to a plan for a privacy initiative and/or team that can be involved in core conversations to ensure privacy is taken into account with core features and initiatives. 

What has been your greatest challenge in the last three months?

Funding of the initiative is the next hurdle to jump after receiving confirmation from Dries that he still desires it to be an initiative.

And what has been your greatest success in the last three months?

Receiving confirmation from Dries that he still desires it to be an initiative!

Do you have a "call to action" you want to make to the Drupal Community?

Continued support and talking to maintainers about the need for a formal privacy team/initiative within the community, as well as sponsorships; any individual or organization can be involved.

Tara King updates us about Drupal Diversity & Inclusion

About this Community Group: The Drupal Diversity & Inclusion group seeks to continue the conversation about diversity and inclusion within Drupal. The group organizes regular meetings and curates a resource library.

Where can we read more about your initiative?


What have been your priorities in the last three months?

Drupal Diversity & Inclusion has been working on: 

  • Defining our roles & responsibilities: https://www.drupaldiversity.com/docs/roles-and-responsibilities
  • Recruiting new leaders to our leadership team
  • Holding space for our community to discuss diversity & justice
  • Planning social events for marginalized individuals
  • Developing talks & booth activities for Drupal events (most recently BADCamp)

What has been your greatest challenge in the last three months?

2020 has been our greatest challenge. :)

We have struggled with volunteer burnout, due to both COVID-19 and the US election cycle. Many folks have very limited time to give and even less energy, so we have focused on activities that support folks rather than new programming. 

And what has been your greatest success in the last three months?

We are thrilled to have three new individuals on our leadership team: Tearyne Almendariz as Careers Lead (https://www.drupal.org/u/ninelivesblackcat), Monica Flores as Resources Contributor (https://www.drupal.org/u/monicadear) and Esaya Jokonya as Booth Contributor (https://www.drupal.org/u/esayaj). 

Do you have a “call to action” you want to make to the Drupal Community?

Please join our meetings! We are making 2021 plans, and focusing on careers & job hunting for marginalized folks. We’d love to have more hiring managers and HR professionals involved in that work. Bring your ideas and we can work together to make the Drupal community more diverse & inclusive.

Alex Moreno-Lopez updates us about Drupal Swag Shop working group

About this Community Group: The Drupal Swag Shop working group is an initiative to offer sustainably sourced Drupal branded merchandise that both promotes Drupal and generates revenue for the Drupal Association.

Where can we read more about your initiative?

https://www.drupal.org/project/swagshop and, of course, visit the Swag Shop itself, at https://www.drupal.org/swag

What have been your priorities in the last three months?

On one hand, helping local DrupalCamps and DrupalCon to collaborate with the shop. On the other hand we’ve been trying to make sure the products available were event specific.

What has been your greatest challenge in the last three months?

Coordinating information and people, and particularly everything related to vouchers, discount codes has been particularly challenging

And what has been your greatest success in the last three months?

Watching other Drupal camps getting interested in using the swag shop and discovering that it gives them a good value as well. For example, NedCamp: https://nedcamp.org/

Do you have a “call to action” you want to make to the Drupal Community?

We need more people to talk about the initiative, and if you know a local camp, encourage the organisers to join the initiative.

Rain Breaw Michaels updates us about Accessibility

About this Community Group: Drupal's official Accessibility maintainers, as well as a number of community experts in accessibility issues focus on ensuring that all other features and initiatives within Drupal maintain our commitment to accessibility for all.

Where can we read more about your initiative?


What have been your priorities in the last three months?

Our main priority has been helping the Claro and Olivero themes reach a high enough accessibility standard to make it into core. We believe that these two projects will have a significant impact on enhancing Drupal’s position as an accessible authoring platform out of the box. 

A secondary priority has been increasing community involvement, and this is where we will focus our principal efforts over the next three months.

What has been your greatest challenge in the last three months?

Our greatest challenge is limited time and resources, largely due to the additional strain that COVID lockdowns and distance learning/remote working has put on our maintainers. 

An additional challenge is that our documentation is woefully out of date. This makes it more difficult for us to easily onboard potential contributors.

And what has been your greatest success in the last three months?

We held a public review of Olivero with the National Federation of the Blind (NFB). This is the start of what we hope may be a long standing relationship, as well as a new process for evaluating the accessibility of core contributions. We also added a new provisional topic maintainer, Ben Mullins!

Do you have a “call to action” you want to make to the Drupal Community?

Yes! Please review issues tagged with #accessibility, and find ones to fix, or that you would like to bring to our monthly office hours! You don’t have to be an expert. 

Become accessibility champions for initiatives that interest you and start conversations with us early so that we can help you find the right resources for evaluation and feedback. 

Finally, our documentation needs to be brought up to date, and your help would be welcome. 

Kay VanValkenburgh updates us about DrupalLadder

About this Initiative: DrupalLadder is a community initiative to create an onramp for new Drupal users as well as new contributors to the Drupal project, or for those looking to level up their skills.

Where can we read more about your initiative?

https://www.drupal.org/project/drupalladder and https://drupalladder.org

What have been your priorities in the last three months?

Feature development focused on

  1. usability for learners and
  2. connecting Ladder info to corresponding official docs

What has been your greatest challenge in the last three months?

User experience design of the website

And what has been your greatest success in the last three months?

Seeing the value of the broad concepts and fitting together some of the major features

Do you have a “call to action” you want to make to the Drupal Community?

Help us by sharing information about how you work effectively - reach back to the people following in your footsteps and give them clear, adaptable paths to success

Drupal participation in Google Summer of Code

About this Initiative: Google Summer of Code is an annual program to promote technology education while supporting Open Source projects. Drupal has been a participant in Google Summer of Code for more than a decade.

Where can we read more about your initiative?

https://groups.drupal.org/google-summer-code – our community collaboration location  https://summerofcode.withgoogle.com/ – Google’s official program website  https://www.drupal.org/node/2415225 – where to get started for students (good read for potential mentors too). Read the 12 steps to help any student can get started on their own @ https://groups.drupal.org/node/535795

What have been your priorities in the last three months?

Google Summer of Code? an annual program for university students organized by Google with projects managed by open source organization mentors such as us (Drupal!). GSoC takes place during “summertime in North America” and wrapped up October with a very successful project. 

As a community, our initiative’s team of volunteers and mentors priority was supporting our student Vishal contributing to Drupal for several months. It was our responsibility to help the student learn more than writing code for a module. As mentors, we helped the student learn project management tools with professionally managed issue queues and techniques such as SCRUM. e reviewed code and tested modules with feedback helping a student who didn’t have a background in Drupal. As a community of volunteers, we made it a priority to ensure that our selected student would be as successful as possible.

What has been your greatest challenge in the last three months?

Finding mentors and project ideas. If you’re interested in mentoring, please realize that we pair each student with on average 3-5 mentors per project. Mentoring is not a full-time gig and can be accomplished with a few hours per week. Even if you simply have an idea for a project without becoming a mentor, please contact us at @ https://groups.drupal.org/node/536212

And what has been your greatest success in the last three months?

Vishal Chaudhary ( https://www.drupal.org/u/vishalghyv ) was Drupal’s Google Summer of Code 2020 student and obviously our greatest success in the last year. The fact that Drupal continues to find at least one student every year who becomes a truly amazing member of our community provides evidence GSoC was a success in 2020. 

Find Vishal’s code below and read about his journey through his @vishal38785">weekly GSoC blog and review his work on the Commerce Fraud project page

We also conducted an interview with Vishal, one of his mentors, and the creator of Drupal Commerce:

[embedded content]

Do you have a “call to action” you want to make to the Drupal Community?

Do you have a project idea and/or want to be a mentor? Please edit our 2021 project idea page @ https://groups.drupal.org/node/536212 with your idea. Even a few sentences or a link to an existing module page that can be ported to D8/9 works.

About this Community Group: The mission of the Community Working Group (CWG) is to foster a friendly and welcoming community for the Drupal project and to uphold the Drupal Code of Conduct.

Where can we read more about your initiative?


What have been your priorities in the last three months?

  1. The Community Health Team has been developing “nudge” templates to be used in issue queues to encourage all participants to engage in positive discourse: https://www.drupal.org/project/drupal_cwg/issues/3129687
  2. Offering discounted Code of Conduct enforcement training for Encouraging representatives from DrupalCamps and other events: https://www.drupal.org/community/cwg/blog/a-different-kind-of-contribution-become-a-trained-drupal-event-code-of-conduct
  3. Offering discounted Mental Health First Aid training for Drupal community members: https://www.drupal.org/community/cwg/blog/online-mental-health-first-aid-workshop-october-27-2020

Do you have a “call to action” you want to make to the Drupal Community?

Come to our session at DrupalCon Europe to learn more about what we’re doing and how you can get involved! https://events.drupal.org/europe2020/sessions/how-community-working-group-helping-make-healthier-community-panel

Local and Regional Updates

Andrii Podanenko and Alla Petrovska update us about Drupal Virtual Cafe Ukraine and the Drupal Ukraine Community

About this Community Group: The Drupal Ukraine Community represents the interests of the Drupal developers, users, and site owners in Ukraine.

Where can we read more about your initiative?




What have been your priorities in the last three months?

Supporting the Ukraine Drupal community during the pandemic.

What has been your greatest challenge in the last three months?

Finding the available speakers for Drupal Virtual Cafes.

And what has been your greatest success in the last three months?

We have organized three Drupal Virtual Cafes with 2 speakers per each event and 60+attendees from Europe and North America.

Do you have a "call to action" you want to make to the Drupal Community?

Connect with the Ukraine Drupal Community. We have the capacity to organize, but need support to find available speakers.

We need to have more information about bottlenecks for organizing virtual DrupalCamps. We have planned DrupalCamp Kyiv 2021, but unsure about the details.

We want your feedback!

We hope that this first edition of our quarterly update has been useful. Because this first edition is an experiment, we’d very much like your feedback as a contributor or potential contributor to Drupal. 

  • What do you think about the length? 
  • Would it be more helpful to organize by code and non-code initiatives, or by some other method? 
  • Does quarterly seem like the right cadence? 
  • What would make the calls to action more clear for how to get involved?

Please let us know any ideas you have to help keep the community more informed and able to understand how to get involved.

Jun 06 2019
Jun 06

One of the chartered responsibilities of the Drupal Community Working Group (CWG) is to work to develop and support community initiatives that promote the health of the Drupal community and help to prevent conflict and burnout. One of the ways that we do this is by organizing workshops designed to provide community leaders with the knowledge, tools, and resources they need to help keep our community a friendly and welcoming place.

Following feedback from last year’s Teamwork and Leadership workshop at DrupalCon Nashville, we decided to narrow the focus and audience for our next workshop. One of the things we’ve observed over the last year in the Drupal community is that many of the issues we’ve seen have had to do with communication breakdowns between various individuals and groups. Following internal discussion in late 2018, we decided that one way to begin addressing this issue was by bringing together leaders in the community representing different groups and interests for a workshop focused on communication skills at DrupalCon Seattle.

In early 2019, we interviewed a number of potential facilitators suggested by Drupal Association board chair Adam Goodman and selected Megan Bernard, a professor of communication studies who specializes in promoting meaningful and inclusive learning and collaboration. Based on Prof. Bernard’s recommendation, we decided to spread this year’s workshop out over two days (April 10-11) in a dedicated meeting room provided by the Drupal Association, who generously covered all fees and expenses.

After finalizing the logistics, we then reached out to those who had attended last year’s workshop, as well as additional community members involved with community governance, camp organizing, core and contrib maintainers, the Drupal Security Team, Drupal Diversity & Inclusion, and the Drupal Association. The workshop facilitator suggested that we keep the size of the workshop to around 20 people, focusing on individuals who are well-connected in the community in hopes that they can help distribute the lessons learned in the workshop. 17 people attended some or all of the first day of the workshop, and 18 attended some or all of the second. In total, community members from 10 different countries spread across 4 different continents were represented.

Day one of the workshop included introductions, a discussion of needs, assets, and challenges faced by various groups within the Drupal community, and a discussion of shared context and perspective. We talked about different ways that other online communities help communicate context about their users, such as identifying the primary language, pronouns, and location in comment threads. During our discussion, Neil Drumm pointed out there was already an active issue led by justafish and others to allow users to display this kind of information, and one of the first action items we agreed on was helping it get implemented on Drupal.org as quickly as possible.

Another topic of discussion centered around creating pre-written template responses that maintainers and/or other privileged users could use in issue threads to “nudge” users in the right direction and realign communication when conversations start trending away from our community standards. We discussed badges and other ways to promote positive communication in our issues threads and other community spaces. In addition, we also talked about better ways to on-board new members into the project and foster an ongoing sense of community. One insight was that small cohorts of 6-8 people are far more effective than 1:1 mentoring at building community engagement.

In our second day, we dug more deeply into the concepts of emotional intelligence, de-escalation practices, and different forms of conflict. One of our exercises was a case study challenge, where different groups were tasked with finding different ways to resolve typical kinds of conflicts often seen in Drupal and other open source communities.

We also spent time talking about different ways to apply some of the things we had learned to our own community, and next steps. We agreed as a group to focus on three main areas:

  1. Setting context in issue queues. This work had already been mostly completed in https://www.drupal.org/node/2961229 so it was really just a matter of working with DA staff to get it implemented on Drupal.org.

  2. Nudges. A group of us decided to do more research into pre-written templates to use in issue queues, forums, and Slack to gently steer things back in the right direction when conversations were starting to go in a negative direction.

  3. Improving Drupal.org user on-boarding and cohorts. In addition to better identifying new users on the site, we agreed to look into various ways to help community members join small cohorts, organized by industry, technology, geography, or other criteria. We felt it was important that this be an opportunity that’s open to existing community members as well as new ones.

The folks assigned to each area agreed to find a time to meet in the coming weeks and to involve other interested community members as well. The CWG also identified several opportunities to improve and streamline its internal processes and communication practices.

By developing and communicating best practices that can be shared across the community, the hope is that we can help build structures for self-guided conflict resolution among community members and support more effective communication overall.

Apr 25 2019
Apr 25

Earlier this month at DrupalCon Seattle, the Drupal Community Working Group (CWG) announced plans to begin the process of reviewing the Drupal Code of Conduct. The Drupal Code of Conduct, which is maintained and upheld by the CWG, governs interactions between community members. It is distinct from the DrupalCon Code of Conduct, which governs interactions at DrupalCon and other in-person events and is maintained and enforced by Drupal Association staff.

The current Drupal Code of Conduct was adopted in 2010 and last revised in 2014. Over the last two years, the CWG has received consistent feedback from the community that the Drupal Code of Conduct should be updated so that it is clearer and more actionable:

  • A set of recommendations for improving the Code of Conduct was shared as one of the high-level findings from the community discussions facilitated by Whitney Hess in April and May 2017.

  • 63% of respondents to a community governance survey held in July 2017 said that updating our codes of conduct should be prioritized as part of the process of overhauling community governance.

  • Improving the community code of conduct so that it is clearer and more actionable was also one of the key takeaways of the community governance discussions that occurred in the fall of 2017.

Over the last year, the CWG has been working on implementing changes to its charter to make the group more accountable to the community-at-large and provide a sustainable foundation for future growth. Now that those changes are complete, the CWG is now able to shift focus to the process of reviewing and improving the Drupal Code of Conduct.

To that end, we have set up a survey at https://forms.gle/rhKHorXXnp3wPQn2A for community members to share their thoughts, both about the current Code of Conduct and the next steps in the process. The results of this survey will help the CWG determine how, when, and who is involved in reviewing and updating the Code of Conduct.

We will be accepting responses through May 31, 2019, and we encourage as many community members to participate as possible.

Jan 17 2019
Jan 17

When we say DrupalCon, the upcoming DrupalCon Seattle 2019 event is probably what first comes to mind. But while we have been selecting sessions, setting up BoFs, and letting you know about the additions to our Con, we at the Drupal Association have also been looking ahead to DrupalCons of the future. We are excited to share those with you now.

In the past, we used to announce the next DrupalCon location during the closing session of the previous Con. This was a lot of fun, but created some logistical problems for the events team, and made it difficult to do all the work we need to do to secure our next con locations. It is a multi-year process to secure a venue for DrupalCon, so we've made some changes that help us coordinate with venues, hotels, and partners without relying on a veil of secrecy.

You first saw this change during the DrupalCon Nashville Closing Session, where we announced both 2019 (Seattle) and 2020 (Minneapolis).

We're taking these changes a step further by looking far into the future to announce the North American DrupalCons for 2021, 2022, 2023 and 2024. We're thrilled to announce the selected cities, as well as share the process that went into making these selections.

Where DrupalCon is going

Together with each of our partner cities, we're excited to announce the upcoming locations for DrupalCon North America:

  • DrupalCon Boston North America 2021 Online (April 12-16)
  • DrupalCon Portland 2022 (Oregon, April 25-29)
  • DrupalCon Pittsburgh 2023 (June 5-9)
  • DrupalCon Portland 2024 (Oregon, May 6-10)

Want to understand the process that goes into city selection? The search for each location starts four or more years before the event, and you can read on for the inside scoop into how this plan came together. Wondering why all the selected cities are in the USA? We encourage you to read our prior blog about why the sustainable choice for North American locations is in the United States for the foreseeable future.

How we got here 

Planning for the future

Historically, DrupalCon locations have been contracted a couple of years before they happened, in a city where we were excited to host the community, that we revealed in a fun fashion at our Closing Session the prior year.

However, announcing the new event only a year in advance—and selecting new cities for every event—created some logistical problems; conference center venues large enough to host DrupalCon are often booked four or more years in advance. This has meant that cities we would love to visit have often simply been booked during the dates that would work with our community needs, or are too expensive because we couldn't make multi-year commitments - which took a lot of options off the table.

In benchmarking ourselves with comparable conferences (in size, audience, and program), it became clear that many established organizations were booking multiple years in advance. This is in part due to the availability of desirable cities, but also that securing locations in the future equates to more competitive pricing.

As the Drupal Association matures and starts leading change in the community and in the open source world, we determined it was best to look farther into the future for our largest annual conference.

Creating a location pattern that the community can count on

We took a serious look at data from past attendance, the locations we're trying to reach, and where we see the most traction from the community.

In analyzing data from DrupalCons dating back to DrupalCon Austin 2014, we were able to deduce some high-level insights about our attendees:

  • 88% of attendees at DrupalCon North America come from the United States
  • In hosting a DrupalCon in a coastal city in the USA, attendance from the regional community local to those cities can be 13-17% higher than the regional attendance we see in other cities (not counting those who travel greater distances).
  • Conversely, when hosting a Con in the center of the country, attendance decreases significantly from the coastal audiences and does not significantly increase from the hosted-area region.

With the majority of our conference attendees in mind, we set out to host our conference in coastal cities, where, by ‘showing up’ our community has proven they want to go. This led us to primarily work on sourcing East Coast and West Coast cities for the upcoming years.

With our upcoming DrupalCon Seattle 2019 on the West Coast, and DrupalCon Minneapolis 2020 in the middle of the USA, we aimed to host DrupalCon 2021 on the East Coast, and from there, jump between the coasts for the foreseeable future.

The benefits of repeating cities

As we did with timing and location, we also stepped back to ask ourselves, why do we move this conference every year? The logical answer is that it makes the conference more accessible to new audiences in different areas. But our past attendee data doesn't support this conclusion. So we asked ourselves again: If it isn't bringing in large numbers of new first-time attendees, why do we search for a new city every year?

We had heard anecdotally that it was because ‘Drupalers like to go on vacation in new cities’ and that ‘it helps grow the community in a new city,’ but these answers aren't well supported by the data, so we decided to re-evaluate our strategy.

When we release our RFP to the world, we work internally with the Drupal Association Board to determine our Selection Criteria. A lot of this hasn’t changed because the Con hasn’t changed drastically in a few years. The top 5 things that we evaluated in each city’s bid were:

  • Large/versatile venue - Could the venue fit our 150+ sessions, 3,000 people for lunch, and the breadth of programming offered at our Cons?
  • Popular tourist area - Do people want to go there? Is there a wealth of activities for them post-sessions each day?
  • Strong business community - Do we already have partners in the city? Is it a place our sponsors have expressed as a city where they’d like to do business?
  • Tech-focused city - Is the city supportive of tech and open source? Are there businesses and organizations that may participate in our event because we are in their city?
  • Large and strong Drupal community - Does this city have a community that has hosted a successful camp in the past? Is there a solid community that regularly meets and would help support the planning of a Con?

It had been a few years since we selected new DrupalCon cities, so reviewing and updating the criteria seemed prudent. We added and changed the following criteria:

  • CHANGE: In the venue criteria, we included the ability to change the program around, since as the community grows and changes, we want to be able to flex our program.
  • ADD: Welcoming to all attendees. We wanted to make sure that topics such as legislative actions, political climates, and inclusiveness of the cities were taken into account to ensure that we were placing our Con in a city where all members of our community would feel welcome.
  • CHANGE: When DrupalCons were mostly managed by the community, the need for a large and strong community was imperative to the success of a Con. Since the Drupal Association has taken on the bulk of planning, pricing, and executing of the Con, the need for the community to be of a certain size is no longer a qualifying factor. In fact, by changing the focus, we could look at cities that didn’t have large community groups at the time, but maybe a Con could inspire one.

When we examined our search criteria and started matching it up with real cities that we could reach out to, the list became short. With that reality, it became apparent that we would need to begin repeating cities. We seized the opportunity to proactively address that reality.

In speaking with tech event leaders from other communities and organizations, it was helpful to get a fuller understanding regarding the benefits of repeating a city location:

  • Time: Securing multiple years can save an organization time, money and peace of mind. By doing this, you eliminate the need to do site visits and RFP gathering again the following year.
  • Staff Capacity: By hosting an event somewhere you’ve already been, the staff does not need to learn a new floor plan, crew, process, regulations, etc. It is estimated that in eliminating these normal challenges of a new venue, that the staff capacity can be reduced by 25%, freeing them up to focus on the event itself.
  • Negotiation: Planners can gather information on the facility once and focus on strategic negotiating, which translates to consistent concessions and commissions with minimal increases in rates/pricing annually.
  • Cost Savings: Event budgets can be determined early, giving the planner more time to focus on the important things like planning for the success of the event. And, if you have done all of this well in the beginning, you will have the peace of mind to know that you are prepared for surprises that inevitably come along.
  • Relationships: Multiyear contracts require a partnership. Planners, venues, and hotel partners can create a strategic plan to build the event and their services. In working with a crew for more than one year, improvements can be made and the crew is better prepared to serve the attendees the next time around.

Getting from ideas to contracts

We released our RFP on August 13, 2018, on the Drupal Association blog. It was also sent to multiple cities that met our criteria. Within our RFP, we shared our tight timeline, with the goal of signing contracts for 2021, 2022, 2023, and 2024 by the end of 2018. Below is a glimpse into the work that transpired between launch date and sign date.

  • September 4, 2018. Is the date that we requested cities submit their detailed bids. Per our RFP, we had multiple questions about space needs, catering, AV, diversity and inclusion, internet, hotels, and more.
  • September 5-11. Partnering with our fantastic production partner, Groundswell Marketing, we reviewed the proposals to see if any questions arose initially about the information provided. Most proposals were 30+ pages of information with pricing grids, proposed hotel blocks, and ‘why our city’ info. We ask each city for some hard numbers on regular items like a gallon of coffee or the hourly rate of an AV technician. This helps us immediately get a picture of a Con cost.
  • September 11 - September 17. For cities we hadn’t been to before, the next step was to interview the city via a Zoom call to better understand how they were a good fit for our conference. Questions like ‘how would attendees be made to feel welcome in your city?’ and ‘How easy and affordable is it to get from the airport to the Convention Center?’ are asked in our initial determination.
  • September 18 - 21. Once we determined cities that met our criteria, we dug a bit deeper into each city’s numbers. We laid out the entire Con on their floor plans to determine if we could fit and how. We inquired about real quotes for line items like our AV and our internet. We costed out catering estimates and space rental.
  • September 24 - October 26. With our list in hand, we did our due diligence visiting possible future Con locations. In these meetings we reviewed the space and discussed how the attendee experience would feel. We met representatives from various departments of the Convention Center’s team to negotiate pricing and discuss pain points. We also did a whirlwind tour of the city to get a feel of what attendees would see/do after the Con each day.
  • October 29 - November 14. We reviewed all of this information with the Drupal Association leadership team and collaboratively determined the priority of cities based on our search criteria. Going further, we then included data points on pricing, incentives, conference dates, etc, to come to a final recommendation for each year.
  • November 15 - December 3. Built a working budget with concrete numbers for each preferred city to get an accurate future picture of finances. This involved getting future pricing on catering, network, hotel rates, etc. Worked back and forth with the city to negotiate down pricing.
  • December 5. Presented recommendation to the Drupal Association Board for buy-in and support.
  • December 6 - 27. Requested contracts from our preferred venues and hotels. Each city has one Convention Center, and at least 5 hotels, so in asking for these hotels, we had about 20 contracts to review. By looping in our legal team and our insurance group, we were able to further negotiate terms that make committing to future years smart, sustainable, and safe.
  • December 28. Signed the last contract and sent it off to the cities. Signing before the end of the year met a contracting deadline that gave us a lot of financial benefits.
  • End of December. CELEBRATED the end of this intense and action-packed process, and the future of sustainable and secured DrupalCon programming.

Serving our community

We aim toward growing adoption, one of the Drupal Association’s main goals. In planning ahead and setting ourselves up for a sustainable and fiscally responsible future conference plan, we can allocate our resources better to focus on creating a successful event that drives to this goal. By making these decisions now, we work to strengthen the foundation of the Association in order to continually work to serve our incredible and growing open source community.

We appreciate the questions and interest that community members have had in this process and were happy to do a deep dive to show you the planning, strategy, and work involved in selecting a city for a future DrupalCon. We invite you to share your thoughts and comments below, and we look forward to seeing you at a Con in the future.

Jan 05 2019
Jan 05

The Drupal Community Working Group is pleased to announce that nominations for the 2019 Aaron Winborn Award are now open. This annual award recognizes an individual who demonstrates personal integrity, kindness, and above-and-beyond commitment to the Drupal community. It will include a scholarship and stipend to attend DrupalCon and recognition in a plenary session at the event.

Nominations are open to not only well-known Drupal contributors, but also people who have made a big impact in their local or regional community. If you know of someone who has made a big difference to any number of people in our community, we want to hear about it. The winner of the award will receive a $1200 USD DrupalCon travel stipend as well as a ticket to DrupalCon. 

This award was created in honor of long-time Drupal contributor Aaron Winborn, whose battle with Amyotrophic lateral sclerosis (ALS) (also referred to as Lou Gehrig's Disease) came to an end on March 24, 2015. Based on a suggestion by Hans Riemenschneider, the Community Working Group, with the support of the Drupal Association, launched the Aaron Winborn Award.

Nominations are open until March 1, 2019. A committee consisting of the Community Working Group members and past award winners will select a winner from the nominations. Current members of the CWG and previous winners are exempt from winning the award.

Previous winners of the award are:

2015: Cathy Theys
2016: Gábor Hojtsy
2017: Nikki Stevens
2018: Kevin Thull

If you know someone amazing who should benefit from this award you can make your nomination here.

Dec 05 2018
Dec 05

The Values & Principles Committee has formed and has started its work. It has started by looking at Principle 8.

Principle 8: Every person is welcome; every behavior is not

The Drupal community is a diverse group of people from a wide variety of backgrounds. Supporting diversity, equity, and inclusion is important not just because it is the right thing to do but because it is essential to the health and success of the project. The people who work on the Drupal project should reflect the diversity of people who use and work with the software.  In order to do this, our community needs to build and support local communities and Drupal events in all corners of the world. Prioritizing accessibility and internationalization is an important part of this commitment.

The expectation of the entire Drupal community is to be present and to promote dignity and respect for all community members. People in our community should take responsibility for their words and actions and the impact they have on others.

Our community is, by default, accepting with one exception: we will not accept intolerance. Every person is welcome, but every behavior is not. Our community promotes behaviors and decisions that support diversity, equity, and inclusion and reduce hatred, oppression, and violence. We believe that safety is an important component of dignity and respect, and we encourage behaviors that keep our community members safe. Our Code of Conduct is designed to help communicate these expectations and to help people understand where they can turn for support when needed.

Why are we doing this?

As Dries said, when announcing the first iteration of the Drupal Values & Principles, the Drupal project has had a set of Values & Principles for a very long time. Historically, they were mostly communicated by word of mouth and this meant that some in our community were more aware of them than others.

Writing down the Values & Principles was a great first step. What we need to do now is continually refine the common understanding of these Values & Principles across our whole community and ensure that they are built-in to everything we do.

How will we work?

The Values & Principles are held very closely to the heart of the members of our community and we absolutely recognise that any work on them must be inclusive, clear, structured and accountable.

We are, therefore, going to be open about the work we are doing. While there are members of a committee that will focus on this task, it is not the committee’s job to make decisions “behind closed doors”. Instead, the committee is responsible for enabling the whole community to refine and communicate our common Values & Principles.

We will record actions and progress in the Drupal Governance Project so that all in our community will be able to have the necessary input.

How will we communicate?

We will continue to post updates on the Drupal Community Blog and, as already mentioned, you will always be able to see and, most importantly, participate in issues in the Governance Project. We even have a board on ContribKanban!

Who is on the committee?

Hussain Abbas (hussainweb) works as an Engineering Manager at Axelerant. He started writing programs in 1997 for school competitions and never stopped. His work focus is helping people architect solutions using Drupal and enforcing best practices. He also participates in the local developer community meetup for PHP in general and Drupal in particular. He often speaks at these events and camps in other cities.

Alex Burrows (aburrows), from UK, is the Technical Director of Digidrop and has over 10 years working in Drupal, as well as an avid contributor and a member of the Drupal Community Working Group. As well as this he is a DrupalCamp London Director and Organizer and the author of Drupal 8 Blueprints book.

Jordana Fung (jordana) is a freelance, full-stack Drupal developer from Suriname, a culturally diverse country where the main language is Dutch. She has been steadily increasing her participation in the Drupal community over the past few years and currently has a role on the Drupal Community Working Group. She loves to spend her time learning new things, meeting new people and sharing knowledge and ideas.

Suchi Garg (gargsuchi), living in Melbourne Australia is a Tech Lead at Salsa Digital. She has been a part of the Drupal community for more than 12 years as a site builder, developer, contributor, mentor, speaker and trainer. She had been a part of the Indian community before moving to Australia and is now an active Drupal community down under.

John Kennedy (johnkennedy), lives in Boston, works as a Product Manager for AWS. Over 10 years in Drupal as a site-builder, developer, speaker and on the business side. Co-organiser of Drupal Camp London 2012-2015. PM for Acquia Lightning and the Drupal 8 Module Acceleration Program.

Rachel Lawson (rachel_norfolk), UK and the Community Liaison at the Drupal Association will finally be providing logistical support to the committee and helping wherever she can. Having been in the Drupal community for 11 years as a site builder, a contributor and a mentor, she has had opportunity to experience how the community understands its collective Values & Principles.

In order to be as transparent and forthcoming as possible we wanted to address the fact that there are currently 2 CWG members on the committee. The initial call for people to join the Values & Principles committee happened at the same time as the Community Working Group was calling for new members and, as luck would have it, Alex Burrows applied for both.

In October 2018 a current member of the CWG, Jordana Fung joined the Values & Principles committee and at same time he was being vetted for potential membership to the CWG, Alex joined the Values & Principles committee as well. After the vetting process, Alex officially became a member of the CWG in November. So as it stands now, there are 2 CWG members on the V&P committee.

There are a few possible options going forward, some are:

  • Both CWG members continue for now (whilst the V&P committee is in the very early formation stages) and then possibly:
    • One member drops off
    • They act as a team and only one member (whichever is available) participates in meetings
  • The CWG decides which member is on the VP committee
    • We may need to add another member to the VP committee to take the place of the member that will no longer attend.

So, what’s next?

We have started by compiling a summary of feedback from the community so far that relates to the project’s Values & Principles from such places as the Whitney Hess Interviews, community-led conversations around governance and some anonymized feedback from the Governance Taskforce. We will be adding this summary to an issue in the project.

Call to action

We recognize, though, that what we really want to understand is how you understand what we already have written in Principle 8. THis is how we intend to do that…

The members of the committee have each written stories from their own memories of the Drupal community that demonstrate Principle 8 in action.

We invite you all to write your own stories, from your memories of the Drupal community, other tech communities or indeed any other aspect of life, that demonstrate Principle 8 to you. You should add your story to this issue we have created:

Add my story about Principle 8

One thing we do ask, though, is that you only add your own stories (as many as you like!) and NOT comment or question others’ stories. All stories are valid.

By the end of the year, we hope to have a rich set of stories that show how we, as a global community, interpret Principle 8 and we can then look to see if any changes need to be made to the words or, maybe, it is more a case of linking the Principle to the stories or providing other statements supporting Principle 8.

Nov 21 2018
Nov 21

The Drupal Community Working Group is happy to announce the addition of Alex Burrows (aburrows). Based in Surrey, United Kingdom, Alex has been contributing to the Drupal project and community for more than a decade. He is one of the lead organizers of Drupalcamp London, and a frequent speaker at other Drupal events. Alex also serves as a volunteer police constable in his local community.

The CWG would also like to announce that both Josef Dabernig (dasjo) and Manjit Singh (Manjit.Singh) have agreed to serve as Subject Matter Experts (SMEs) to the CWG. SMEs are not full members of the group, but can be called upon on an as-needed basis for issues that might require specific knowledge or expertise. SMEs are subject to the same Code of Ethics as full members of the CWG.

Adam Hill and Emma Karayannis are also officially stepping down as members of the CWG. We would like to thank both Adam and Emma for their invaluable contributions to the group and for their ongoing contributions to the Drupal community.

The CWG continues to seek new members and SMEs as it seeks to increase the diversity of its membership. It is our hope that by expanding our membership, the CWG will be able to better serve the community in a more proactive manner. If you think you or someone you know might be a good fit for the CWG and are interested in learning more, please reach out to us via email at [email protected].

In other news, the CWG recently proposed a set of changes to its charter to address feedback and concerns raised by the community over the last year and a half. We are accepting feedback from the community through November 23 before finalizing the proposal.

The CWG is responsible for promoting and upholding the Drupal Code of Conduct and maintaining a friendly and welcoming community for the Drupal project. To learn more about the group and what we’ve been up to over the last year, check out our recently-published annual report.

Nov 08 2018
Nov 08

This is a public update on the work of the Governance Task Force.

Drupal is one of the most successful open source projects in the world. Governance is fundamental to the project's success.

The community and the code has been built from the ground up. And as the code has grown, so has the community.

When communities are first emerging it's easy to bring newcomers along, but over time the community begins to mature, change, and then needs to adapt. Challenges and opportunities emerge as evolution occurs, and our community needs to navigate them strategically.

A Governance Task Force has been meeting weekly since May to put together the strategic proposal we now share with you. We've synthesized ideas, discussions, and experiences from people we've interviewed, and we've revisited the themes that emerged from the community listening project run by Whitney Hess and by previous governance discussions.

This Drupal Governance Task Force 2018 Proposal serves two purposes.

Firstly, it's clear that for community evolution to occur there needs to be broad agreement and buy-in. People are comfortable jumping in and building a new module, but community change and action is hard. People talked to us openly about the unclear processes and barriers holding back community progress.

We heard strong perceptions that support from Dries or the Drupal Association is needed before initiatives could be created or scaled; real or otherwise, this is affecting community progress and action. Speaking to people from the Drupal Association, the Community Working Group and other initiative leaders, they also feel limitations. But to change their terms of reference and priorities they also need to have a community directive.

The community is stronger and more influential than we sometimes assume  --- when we are speaking together.

That's why at the heart of this proposal is a new community governance structure.

The second purpose of the proposal is to create a starting point --- a framework. We’ve been practical, highlighting a range of actions that form a backbone for community evolution. It’s not a defined roadmap, and it’s not a list of every idea we had or heard. We welcome the discussion, debate and idea generation that this document will spark. We want to hear your solutions on how to get change done, and what you would like to contribute.

We strived to make practical recommendations with the potential to make progress, lower barriers, and help our community to continue to evolve with time.

Throughout this process we have heard people say they believe change is necessary. Change is necessary for the longevity of Drupal the project and the code. Change is necessary to create a new generation of Drupallers — the people we want to help build ambitious things and to have the chance to build a career within our community.

It is hard to not feel the project is at a crossroads. We’ve climbed the mountain of Drupal 8, we sit at the peak and look to the valley below.

Where we go next, and who we take with us, is up to you.

We hope this proposal helps.

David, Ela, Stella, Lyndsey, Rachel, Hussain, and Adam

File attachments:  Drupal-Governance-Task-Force-Proposal-2018.pdf

About Drupal Sun

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

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

See the blog post at Evolving Web

Evolving Web