 Hi and welcome to the Drupal Association's update to the community. I'm Heather, the executive director of the Drupal Association and today I'm joined by members of our leadership team, Angie, Kerry and Tim. We're going to give you a not so brief but very informative overview of everything that we've got going on since we last met and DrupalCon North America and also in Amsterdam. And I wanted to start by introducing, virtually introducing our staff. As you can see, we've got a fairly small but very mighty staff of individuals that are located around the globe that serve full time with the Drupal Association. And I want to personally thank all of them. It's been a particularly challenging year, given a lot of financial and operational impact, not to mention the pivot to DrupalCon, which we'll talk about. So I personally thank each of them for all the hard work that they do. Also giving hard work, time, talent and treasure is our Drupal Association Board of Directors. Hopefully you've had a chance to meet all the individuals here, but if you haven't, please take a moment to reach out during DrupalCon Global and chat and network and get to know them as well. So I wanted to start by talking about the Drupal Cares campaign. So when we started off 2020 in January, we were pretty solely focused on executing DrupalCon Minneapolis as our big fundraiser and event, and also the myriad of programs that we that we had as part of our mission and vision. Enter COVID-19, which I know has had an impact on everyone that's watching, but it definitely had an impact on the Drupal Association as well. So in March, we shared a statement with our community, because we wanted people to be in the fold with us to understand what those effects were for the Drupal Association. As you can see from our initial financial projections, we were looking at an impact of anywhere from about half a million to over a million dollars. So with that said, we then invited the community to join us in solving that problem. And the way that we did that in conjunction with the community was by launching Drupal Cares. So we started that we asked the community to help us really use charitable giving as a way to fund our emergency funding gap. And while things really got off to a nice start, what really kicked it into gear and gave the campaign a lot of excitement was the matching gift from Dries and Vanessa. So they came to the table and said that we'll match every new donation and new or renew membership up to $100,000 and that really inspired our community. Inspired by that inspiration, the Drupal businesses got together and said, hey, we want to do the same thing. So they said we want to inspire our other business colleagues to get into this as well. And they did their match as well so that every dollar that you contributed had not double but triple the impact on the campaign. This is a look at the companies that got together for that that business match and thank you baddie at one X internet for putting this graphic together for us. And thank you to all of these companies for stepping up with Dries and Vanessa to help us triple that impact. As a result, other members of the community wanted to help as well and did some really creative and encouraging things. You might have been involved with pixels for Drupal. Hopefully you were involved with the Drupal 9 module challenge Jeff Geerling gave a dollar for every like and view on his YouTube channel. And we really had a lot of all that come together so between individuals and businesses and community initiatives. We were thrilled to say that at the end of just over a month we were able to reach our half million dollar emergency funding gap goals. And that really took over 150 businesses and organizations. Over 2300 individual donors and members participated in this and so as I said in the blog that went out, we were excited humbled appreciative and energized by by what the community helped us to accomplish. And because of that we give you our Drupal friends. As Dries said in the press release that went out about meeting our goals. It was really important not only that the community came together, but the speed with which the community helped us meet this funding gap. Not only made sure that Drupal Association could go on and meet our mission, but that we could do it quickly and refocus on things and one of those big things was the Drupal 9 launch which was immediately on the heels of the Drupal Cares campaign. And really quickly wanted to talk about the pivot to Drupal con global obviously you know a little bit about it because you're here, and we thank you for participating as an attendee in this journey. So we knew at the beginning of the year we were planning to be in Minneapolis in May for our traditional in person event. As you can imagine, we quickly learned throughout the spring that that was not going to be feasible or safe and the rights. It wasn't the right idea for our community. So we decided that we could not meet in person, but we still had to figure out given contracts obligations lack of force measure what we actually could do next. And luckily we were able to pivot and create a virtual conference for you. And where we were really committed in doing this was we could have just said hey, forget it we're going to wait until next year but coming off of the Drupal Cares campaign we were so inspired by the community that we wanted to create an event that everybody together. We also saw this as a way to be more global so while a traditional in person event required a certain level of travel and accessibility to be able to participate. This was the idea that hey some of those accessibility barriers are gone. Let's make this a conference as much as possible for everybody in our community. One of my favorite outcomes of the pivot to Drupal Con global being an online event was our ability to provide so many more scholarships and grants for people to attend. The last time I looked at the list we had over 150 people attending Drupal Con as a result of being scholarship to the event. Many of those have never been to Drupal Con before and frankly some of them don't even know that much about Drupal. So this is an excellent way for us to open those doors and get people into the Drupal pipeline that may not have known about us before. And of course none of this would have been possible without our amazing event volunteers. So as I mentioned a lot of planning had been done to prepare for Drupal Con Minneapolis. This is an overview of the volunteers that did a lot of that program committee work. So the sessions that you're seeing are really curated by this group of volunteers and the speaker teams. And then the newest group of the steering committee was brought on only about six weeks ago as we looked at how we could really enhance both the pivot to the online event and also our enhanced main stage content. The Drupal 9 launch but we actually had a project within a project with the Drupal 9 launch and that was creating a new Drupal logo. So part of the impetus was not only to be ready for the Drupal 9 launch but to create a Drupal logo that we call Evergreen. And what we mean by that is regardless of version there is a consistent branding element to the Drupal software projects and 611 helped us with that logo and created this cool video that we'll show you now. Thank you again to 611 who not only worked on this project for us but did it pro bono as a thank you to the Drupal Association and as part of their giving to the Drupal Cares campaign. As you can see we have a new Drupal logo that that is flows into the logo for both Drupal Con and the Drupal Association so we have that consistency going across as a thread. And we're ready now for Drupal 10 where we'll have the consistency the we won't have the need for a new logo and as you can see there is an opportunity if you want to do the version along with us. The Drupal 9 launch so we had Drupal Cares we got our emergency funding we had the new logo all things are in place for us to launch Drupal 9. So it launched not only launch it in the year that it was planned but on the original month and day that it was playing so it launched not only within the window but in the first possible window for launch so that's a huge huge accomplishment for this community and just many many Drupal thanks to everybody involved in making that happen. As I can say about the Drupal 9 launch and the community's impact on Drupal 9 Dries put together a great video that tells the story much better than I can so I'd like for you to watch that now. I could make it do exactly what I needed to do. So if you'd like more information about Drupal 9 or even the toolkit that we've put together for the community you can get those resources on Drupal.org and there's a Drupal 9 landing page that we have put together for you. One of my favorite things about the launch was the celebrate Drupal initiative so if you go to celebrate Drupal.org you'll see photos videos and lots of fun content where community members all around the world celebrated the launch. It's still open and you can still contribute so let's keep celebrating Drupal all throughout 2020. And while you're here at DrupalCon Global don't forget to check out the sessions that apply directly to Drupal 9 and you can learn more about those here and check it out in the Hopin platform. With that I'd like to let my colleague Angie talk to you about the great work that she's doing in our finance and operations. Thanks Heather. Hi everybody I'm Angie Saban director of finance and operations, and I wanted to talk for a moment about diversity equity and inclusion. So, there are values and principles inherent to our work that tied directly to diversity equity and inclusion. In fact, our Drupal values and principles explicitly state the importance of diversity and equity and inclusion. Principle 8 says 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's 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. Back on June 3, Heather, our executive director published the statement of support following the George Floyd tragedy. We acknowledge in this statement as we do now that we have work to do and we're committed to doing this work. I borrowed these slides from the Dreesnow at Seattle. So this is just a good reminder of the demographics in technology at large but also for open source. So the demographics for open source are a little bit worse actually than tech overall. So I wanted to talk for a minute about our internal efforts around diversity equity and inclusion. So I'm sharing this in the hopes that perhaps you can borrow some of the things that we're doing or just get a better sense of how we're trying to advance things. So feel free to reach out to me if you have questions about any of this. But I'm just going to say a little bit about what we're doing specifically. So we know that this journey start from within and this year has marked the most active in the history of the Drupal Association in terms of diversity equity and inclusion efforts. So this is a list of highlights from what we've done. We know we still have a long way to go and that the work requires consistent commitment from leadership in order to embed equity into the organization. So first off, not really the first thing that we've done but most recently the whole staff took an anti-racism training through the Diversity and Resiliency Institute of El Paso. Again this is a start and by no means the only training we will take but given the events of recently unfolding in the U.S. particularly we felt that an anti-racism training was a good place to start. And with our budget we're going to be continuing to commit to investing in our competency around diversity equity and inclusion. We also are working with an assessment tool that will help us develop a work plan in coming years. This will be one of many ways that we approach building a work plan and I'll talk more about this in a few minutes. We have a Slack channel that we recently launched that allows staff to share resources and also talk about their own personal experiences. It's sort of a safe space for the team to have those important conversations. We are also in the process of moving our bank accounts to a community development financial institution. So those are banks that share a common goal of expanding economic opportunity and low income communities by providing access to financial products and services for residents and businesses and underserved communities. So we're super excited about that. The slide represents visually the layers of an organization. And the tool I mentioned in the previous slide is the tool that we're using. I was lucky enough to go through a year and a half long cohort locally where I live that helped me understand how to utilize the tool so I've been able to lead the staff through that and we're sort of in the middle of working on that now. But there are nine domains to the tool that really look at every aspect of the organization. It provides best practices and examples of how other organizations are doing the work and ultimately will result in a work plan for us that will span multiple years. This will not be the only work that we do but this hopefully will be a really pivotal part of what we're doing. So in addition to all the stuff that we're doing internally, we're also developing a new program with the help of community members focused on training. And I want to take a moment to thank when Anelo specifically for reaching out to us about this and really being such an amazing resource of information. So you can see here the outcomes that we are looking to achieve with this program. So we're currently building out the program, both from the perspective of developing a cohort of trainers and also partnering with organizations that will help connect potential students. This is the first phase of the program and it's going to be a pilot phase so that we can learn and fine tune as we go. So stay tuned for more information about that in coming months and please reach out to me if this is something that you're interested in taking part of or learning more about. So we know that learning is important and taking action is important. And while we learn, we want to continue to build the programs and also look at how we change the organization from within. So we're approaching this work humbly and we acknowledge that there's always something new to learn. So we definitely want to hear from the community and collaborate when appropriate. So you can always reach out to me or leadership on the team. When you have feedback. And we just really want to welcome you to to be involved. So changing gears a little bit. As you probably all know, we had the need some for some emergency funding so I'm going to take a moment to talk about the final financial health of the organization. I wrote a blog, I believe back in April, with more information about how we calculated the gap range. But this slide will tell you a little bit about where we're currently at. The gap was related to a combination of factors, including some costs for the in person event we had originally planned in Minneapolis. Those costs could not be recovered. And it also factored in the revenue that we would normally net for an in person event. So we're very close to meeting our goal for ticket sales. And I'll have a better sense of the numbers as we wrap up things next week. Things are looking really great. And that's a large part to the generosity of the community. So I just want to thank you again for that. I'm going to hand things over to Kerry, our director of fund development to talk more about fundraising efforts. Thank you, Angie. To start, we can't really talk about fund development and in engagement without first giving a huge thing to thanks to our triple con global sponsors. Most of these organizations were initially triple kind Minneapolis sponsors and then after COVID hit, they pledged to keep their marketing dollars in place with the Drupal Association, regardless of what the outcome of the event was. So please be sure to visit them in the expo hall to have conversations, get some cool demos, win prizes, and thank them for being here. This event would not have been possible without them. There are many ways that organizations and individuals can engage and invest in the Drupal Association and the project from sponsorships, memberships charitable giving contribution sponsored scholarships and technical initiatives. There are many, many ways to get involved. But why support the Drupal Association. Drupal is one of the largest and longest running independent open source communities in the world. And as the nonprofit behind the community were dedicated to accelerating the software project fostering the community and supporting its growth. But what does that look like and what does that mean to you specifically. If you attend Drupal con, if you visit Drupal.org, if you contribute if you rely on the security of the Drupal software, if you've received a scholarship to be here, if it's important for you to see a more diverse and inclusive project. This is just some of the work that we do. To barely to put it very simply, we create the spaces for international community to thrive. I appreciate how Matt Westgate put it during our Drupal CARES fundraiser. Drupal, the software is the engine. We'll always have that and people will continue to work on that. The Drupal Association is the car. It's the vehicle to which we put the engine and to make things move with doors that open to include and invite other people into the project. One key way that organizations can support the Drupal Association is through our supporting partner program. I'd also like to thank all of our Drupal Association supporters, supporting partners, funding from the organizations is key to support all of the non Drupal con related work that we're highlighting here today. A huge thank you to our enterprise, diamond, premium and classic supporting partners and community. That's a new tier that I'll talk about. Any organization can join our supporting partner program. It is particularly important for organizations that are using Drupal and making significant cost savings by not having any licensing fees. Supporters fund the critical work of the Drupal Association's engineering team and the Drupal project contributors. Based on your level of investment, you're underwriting anywhere from one to 10 weeks of Drupal.org infrastructure and project contribution testing fees. So you can think of it like an infrastructure investment plus so much more. There really are a lot of business advantages to joining our supporting partner community. But don't just take my words for it. Here's what some of our supporters and sponsors have to say about contributing and supporting the Drupal Association. Our programs offer thought leadership, accreditation, networking opportunities, talent acquisition support, industry visibility, and they allow you to participate in a change that you want to see by amplifying our collective voice and advocating through the Drupal Association. And now moving on to Drupal Association individual memberships. Because it really is not just about organizations. Members really do make the Drupal Association mission possible too. So I'd really like to encourage all of you to participate in our ongoing individual membership campaign. You can join us while you're here at the conference at the Drupal Association booth or online at Drupal.org slash join. Just some quick updates about a lot of the work that we've been doing to these two key programs during the first half of the year. For individual members, you may have seen some feature updates. We've added the option to pay for membership monthly installments. We've added new tiers for individuals who have the capacity or the desire to give more. We've offered the ability to disable certain ad programs if you're logged in as a member on Drupal.org. And we've provided marketplace credits to organizations for each member of staff who has a membership. For our supporting partner program, in an effort to grow participation from all types of organizations, we've launched a lower priced community tier, which I mentioned earlier, as a way to replace organizational memberships and get people into some of these key business benefits as well. We've added the enterprise tier, which was designed with a focus on larger organizations and their unique business needs. And we've also added new benefits, including complimentary individual memberships for staff and a lot of new marketing opportunities and visibility under Drupal.org. So if you have any questions about that, please come find us or visit us at the booth and stay tuned for new feature improvements like bulk individual membership purchases, updating payment tools to support more currency types, offering lower tiers for regions around the world to participate more easily, and offering businesses the ability to become certified organizations. If you want to hear about any of these new improvements or tell us what's important to you as an individual or an organization, we'd love to hear from you and see you at the booth at DrupalCon Global. So please visit us. We're going to have DA staff and board members throughout the week giving lightning talks, and we'll just be hanging out if you want to come by and say hello. So thanks for your time. I'd like to next introduce our Drupal Association CTO, Tim Lennon. Thanks, Kerry. The first thing I'd like to talk about today is contribution recognition. An open source project thrives on contribution from all of the individuals and organizations around the world who support the Drupal Association and the Drupal project. In particular, I'd like to talk about the ways that we recognize contribution today, which is through contribution credits on Drupal.org, a way that when you contribute code or non-code contributions, you can be recognized by project maintainers, event organizers for those things that you have done for the community. And indeed, you can also indicate that your organization has sponsored you to do that work, and they can receive recognition as well. And this virtuous cycle of contribution and recognition helps to feed into our programs. It's something that's going to become part of things like the certification program that Kerry has referred to and things like the Drupal Steward program that I'm going to be talking about a little bit later on. There are still some problems that we need to solve with our contribution recognition system in Drupal. As much as I think we are the forefront of contribution recognition in open source, there are still things that we need to do. So we want to more completely measure the different kinds of contribution activity that already take place in the Drupal community and have a way to recognize that easily. And then we want to use all of the contributions that we recognize to encourage more people and more organizations to become the makers who build Drupal. We want to expand that community of contributors by recognizing those contributions in a powerful way. To help us with this process, we announced at DrupalCon Amsterdam that we were forming a contribution recognition committee. And these are all of the members of that committee that have been working since Amsterdam to help provide new tools and techniques for doing contribution recognition. As the Drupal Association liaison to that committee, I can tell you that they're all passionately committed. The committee itself has had to take a temporary pause because of the COVID-19 situation and having to take care of both family and business concerns as individuals. It's an all volunteer committee. But despite that they've already accomplished some great things and that means that we don't have to slow down in our work. Some of the things that we're going to be doing moving forward, again, recognizing more kinds of contribution. We've done a survey with the community on behalf of the committee to gather those things that you think might be missing from the current contribution credit system. And we're going to try and make the process of crediting contribution easier, reduce the friction, make it a simpler process to record and approve the contributions that people have been doing. So moving on from there, I want to talk about some Drupal.org highlights. These are just a few of really the many things that we've done in the last six months to a year. It's been kind of a banner year from an engineering perspective. So I'm really excited about lots of these changes. One of the ones that's kind of close to mind at this current time as we head into Drupal con global is community events on Drupal.org. So we worked with the events organizing working group to come up with new features for Drupal.org itself that update and modernize the way that we learn about Drupal community events. So this feature living on Drupal.org basically replaces some of the functionality that existed on groups that Drupal.org and allows you to submit your events, whether you run a Drupal camp, a meetup, whether you're doing some other Drupal related conference, any of those things can be submitted. And this is provided as a feed that you can access from Drupal.org API and therefore these can be pulled into the Drupal cal service if you've used that before and basically help our global community understand where the conversations are taking place about the future of Drupal so everyone can participate. For the engineers in the audience listening right now we've made some significant updates to Drupal.org's packaging and Drupal CI systems. So these are the systems that actually deliver new releases of modules or of Drupal core itself and the systems that allows to test new code contributions as they come into Drupal. So on the packaging side the part that produces the tar GZ or zip files that you download when you're installing Drupal. One of the challenges for the Drupal infrastructure team has been expanding that system to support composer fully. Composers the dependency management system that lets you get external libraries that Drupal might depend on or that you might use in third party modules and really expands Drupal to be part of the wider PHP ecosystem. So when we produce a download of Drupal for you to use we have to do some work to make sure that that download is composed already. So we did that work earlier this year and then updated the pipeline itself to make that process easier to maintain and provide better support for doing security releases that involve these third party dependency management. For Drupal CI the testing system that makes sure that there's strong code quality going into Drupal. We've adjusted the way that that system works so that you can test whether that your contributed modules are ready for Drupal mine. So because of that on the day of Drupal mines launch something like most 60% 65% of the top 200 contributed modules were already compatible before the software had even come out. Since then we've had thousands more. So there's been a tremendous effort by the community thanks to these tools to get the whole software ecosystem for Drupal ready for Drupal mine. And I think never before in Drupal's release cycle has so much of the contributed module ecosystem been ready so soon. I'd also like to talk about the Drupal steward program. So we just announced that this program is launching together with our founding partners. This is a security service being offered by the Drupal Association in partnership with the Drupal security team to help protect sites from highly critical vulnerabilities that might occur in the software. So let me walk you through sort of how this program will work. The first step is that the security team might identify a vulnerability as a highly critical or mass exploitable vulnerability. So some examples of this. There's the very dry name as a core 2018 to also known as Drupal get into this is the kind of vulnerability that would have been protected by this program. The security team will then determine if this vulnerability can be protected on a network level with a web application firewall. Then the security team will release a PSA that says that this program will cover protection for this vulnerability. So in the background between the PSA there's usually about a two week period while the patch is being created so that Drupal can be updated to close the vulnerability. So in that gap, the security team and the Drupal Association and partners create these web application firewall rules that protect you from the vulnerability acting in layman's terms like a virtual patch that protects you even before the actual patch is available to be downloaded and applied to your site. So we'd review this virtual patch rule set in the network application. Check it to make sure that it doesn't have any false positives that might disrupt people sites and then enable it to protect sites in time for when the patch happens. The primary value of this is it means you no longer have to be on red alert when there's an upcoming vulnerability or an upcoming patch release because you're not in a race with the bad actors that are trying to reverse engineer what this vulnerability is. You no longer have to be up waiting for that patch to drop particularly for international teams or teams with large number of sites to manage. You can now schedule this update at your own pace with your own change management processes relying on this virtual patch layer created by Drupal steward to keep your site protected in the meantime. There are some limitations to be aware of so it can only apply right now to these highly critical mass exploitable types of vulnerabilities at the discretion of the security team. It may be applied to certain other vulnerabilities or vulnerabilities and certain contrived modules, but that'll be communicated in the public security announcements so you'll always be able to check the PSA to know if a particular issue is going to be covered or not. And it's also possible that certain kinds of vulnerabilities simply can't be protected by this kind of technique. So if that's the case it'll also be indicated. I want to thank the various partners who are going to be involved in the Drupal steward program. So firstly our founding platform partners aquia and pantheon have both provided seed funding that's making this program possible. So they're participating to protect their hosting platforms as a whole and also to provide the funding that allows us to create a community tier of Drupal steward to protect all of the sites out there small to large who might not be hosting on these platform partners. We're also going to be working closely with our agency partners who are supporting partners at various levels so that they can protect their clients as part of this program as well. So we're really excited about this and happy to talk with you about it more at the Drupal.org panel which I'll talk about in a little while. Finally, again for the developers out there issue forks and merge requests. If you have contributed to Drupal in the past well in the past almost 20 years. You've done so by providing a software patch patch file and frankly that's getting pretty old fashioned these days. Most code contributions come in the form of pull requests or merge requests as they're sometimes called. And we're really excited that these are now coming to Drupal.org and in fact already available for a number of first beta projects. So how does this work. We continue to have the original Drupal.org issues which are the place where the discussion about a software problem in Drupal takes place. In any issue you can generate a workspace and issue fork where you can make your changes and test out a solution to that problem and then open a merge request so that the maintainer can review your changes and merge it back in. Because of this change and the use of GitLab on the back end as the code repository and code contribution tools for Drupal.org these changes do not require you to have a local development environment. They don't require you to use the command line. You can actually do everything from your browser creating a clone of the software editing the code in a Web IDE and opening the merge request without ever having to open up a terminal window. So it should make it much easier for existing contributors and for people who are new to the community to contribute to Drupal. This is what you'll see in the sidebar of projects that have this feature enabled. We're still updating the user experience and trying to make sure that it's simple and clean so there'll be some changes as we go but we'll talk about that more at our session. And this is what a merge request would actually look like once it's been created with someone's change and this little demo merge request was created again entirely in browser. So I hope you'll join us to find out more information about all these initiatives for the Drupal.org engineering team that I've just spoken about and also several others that we didn't have time for in this presentation today. So the Drupal.org engineering team panel will be on Wednesday at 1015 Pacific time and you can check out the schedule for more. And with that I'm going to hand it back to our executive director Heather to talk about the Drupal Association Q&A and close us out. Yeah so if this robust overview leaves you with some additional questions or need for information we hope that you will join us on Wednesday as part of DrupalCon Global. We'll be doing a live Q&A. We'll be joined by some of our board member, our officers will be there as well. It's another opportunity to talk to Dries so if that's the draw then we're more than happy to have you there to ask Dries some additional questions from a governance perspective as well. And we hope that you'll also join us in the booth as Carrie mentioned. It's a great way to come by and have casual conversation and say hi. So just another thanks to you for participating, for being an attendee at this first ever groundbreaking DrupalCon Global all online event. Thanks again to this team and then Tim I'm going to have you put us all on the screen so we can say bye. Thanks everybody. Thank you this week.