 Okay. Megan, your screen's cut off. Yeah, how's that? Do you see that? Yep. Great. Okay. So again, thanks everyone. We're clearly having some technical issues, but I'm really glad that we can give you our quarterly update on the various things that we're doing here at the Groupal Association. It's always a pleasure to be able to let our supporters have a little more insight into what we're focusing on, what we're moving forward on your behalf as a business that's supporting Groupal, and how we're helping the community come together as well. So just a few things. If you can just stay needed during the call, that way we don't record everyone typing. If you have questions, you can use the chat window. And, you know, you can always tweet anything you hear. By all means, share what you're learning, and you can use our handle at Groupal Association. And so if you want to listen to this later, we are reporting it. We're going to email it to all supporters as well. Today, we'll just go over some top news items here at the Groupal Association, and then Carrie is going to talk about some changes to the supporter program. And then we are going to just give some highlights on DrupalCon, and Tim will then talk about Drupal.org. But of course, we want to first just thank all of our supporters starting with the signature supporters, and our premium supporting partners, as well as the supporting partners, and those are the Drupal agencies that are coming together to support us. But we also have technology and hosting companies, in addition to the ones you saw on the signature slide. These are the premium levels that are supporting the program and recognizing that they are also benefiting from Drupal and wanting to give back, and those that are at the supporter level. And of course, all the funding goes to improvingdrupal.org, which is the home of the project, and allows us to bring everyone together to build the software and providing the tools that everybody needs, as well as doing the initial work we've started to do, which is promoting the software, with some of the redesign we've done on the home page, as well as the recent industry pages. So just a little update on some Drupal Association news, as you may know, there's been a lot of community discussions over the last couple months about how we can improve community health, and that starts with remodeling governance, how we make decisions by and for the community of how we decide how we want to operate together and move forward together as a community. And so we, as the association, want to support this effort that the community wants to own, but they do need some support, and so we have hired Whitney Hess to run community discussions. They are mediated discussions that started at Drupalcon Baltimore, and then they happened virtually online at different times, so people all around the world would have the opportunity to join and share their thoughts, their needs in terms of community governance, and that has concluded, and now Whitney is preparing a summary of everything that she's heard, where there's agreement on how to move forward, and some proposed next steps that she was hearing from the community. So you'll be hearing from her soon, we'll put out a blog post, but some really great things. I think you can hear some more in a recent podcast that she and I just did with Lullabot. The good thing that I think I heard coming from her was people don't feel that community governance needs to be thrown out the door, that there's a lot of good things we just need to build off of what we have today and just evolve it. So the other bit of news is that Drupalcon Vienna is happening in September and registration has opened as well as call for papers. So we certainly encourage you to participate and get involved. This is another great community event where we kind of break down those international barriers and let people come together, share ideas, and learn and grow as a community. So we'll hope you'll participate in that. And I'm sure there'll be some more news that you can just follow by reading our newsletters that go out monthly. So let me hand this over to Carrie and she is going to talk a little bit about the supporter program and how we're evolving it to create more value for you as a business. Thanks again. So I'm talking about some new and improved benefits that we brought to the program last month. So as I'm sure most of you know, funding from the partner program helps build the successful Drupal ecosystem. And all funding from these partner programs goes directly to support Drupal.org and our engineering team. So some recent D.do improvements include Drupal CI functional testing, project application process revamp that helps open up Drupal contribution to a wider audience, as well as a Drupal.org homepage revamp that helps show evaluators why Drupal is the right choice for them. Next slide. So some supporting partner benefits were going unused because our partners weren't seeing the value in them. Now that Drupal 8 is out, we want to direct more attention to promoting Drupal adoption within our channels, including Drupal.org. We want to better align our supporter benefits with our mission as well as with what supporters value the most. So we've been talking to our supporters to see what they do find valuable. Some things that kept in coming up were leads, brand visibility as well as thought leadership. So these new benefits provide this kind of value. And they include contribution credits for signature and premium level supporters. It includes case study promotion on the front page, as well as a feature Drupal.org news post. That's great. If I could just ask a quick question in terms of those benefits, how do they help with the value that supporters are looking for? Sure. If you scroll to the next slide I'd kind of go into some of the details. So contribution credits is our way of acknowledging that there are many ways to contribute to the project. We often say it's time, talent, and treasure. So organizations that are supporters will get a range of contribution credits depending on their supporter level. And then as you may know, contribution credits help your ranking within the marketplace. So credits are tied to your org partner badge and your profile. So if you're currently a supporter and you have that badge, you already have these contribution credits associated to your organization. And then on the next slide, a lot of the new benefits include homepage visibility. So the homepage sees 350,000 visits a month. That's our highest traffic page on the site. And 50% of the visitors are new to Drupal.org. About Drupal, try Drupal and case studies generally have high engagement rates. So we've made certain assumptions about this audience. They're primarily technical evaluators that are coming to learn more about Drupal. So the featured news stories and case studies will help turn the homepage into a Drupal marketing tool and provide visibility and needs for supporters. So along with organic news, the homepage news feed will amplify your content that's compelling to the technical evaluator. And then featured news cities will just make sure it's fresh and compelling brand names are out on the homepage on a more regular basis. Benefits that we're eliminating are the run-of-sight banner ads, the association newsletter article and blog post, as well as the promotion of a prerecorded webcast and the DNA newsletter ad. And I'll go into a little bit about the why. Some companies just didn't take advantage of the run-of-sight ads. It's really low volume in general. And the ads are pretty deep in white, so it's reaching more Drupal developers rather than their target audience of evaluators. And same with the newsletter and blog post. It generally reaches other Drupal businesses, but not necessarily technical evaluators. And then lastly, we're eliminating the prerecorded webinar, which was just quite frankly pretty difficult for people to support and produce. And then I just want to say a quick thank you for your support. Your account manager should have already been in touch about these new benefits. And if you have unused visibility benefits that we're eliminating, you'll have the opportunity to keep them until your agreement runs out or transition to the new benefits. So if you have additional questions, you can reach out to Delana Lang or Mark Branstetter for more questions. That's great. And we're always listening to our supporters and what their needs are. So this is just an example of how we've gone through an exercise to get feedback from the different supporters to find out how we can make this more valuable. Because we really, it really matters that you're contributing to fund Drupal.org improvements. There's so much more we need to be doing and can be doing. So we want to make sure that we keep you as a supporter. You find value in this. And hopefully we'll be attracting even more supporters. There's a lot more companies out there benefiting from Drupal and we want them to see the value in giving back as well and how that ultimately comes back and has returns for them. So with all that said, please know that we are listening. If you have other ideas of how we can create value for supporters, please let us know. We're always looking for new ideas. So thank you. And thanks, Carrie. So let's just talk a little bit about DrupalCon. One of the things we want to do for our community is creating value through the two channels that we manage, which is DrupalCon as well as Drupal.org. And as it relates to DrupalCon, we want to grow attendance, but we also want to lean into more of that adoption journey. DrupalCon definitely supports our contribution journey and helps those come together to work on the project. We have sprints and we have core conversations for people to talk about what to do next with this but we also want to use this event to make sure we're talking to people that are using Drupal and get them to fall back in love with it and learn how to do more with the software. We also want to get evaluators in so that they go to the exhibit hall and find partners to work with and that they also fall in love with DrupalCon and make the choice to go with the software for their organization. So we have some more work to do to really understand the purchasing process basically within the end user and who we really need to be bringing into the event and curating content for. It's a big effort because we are evolving the focus of this event here in DrupalCon North America. But we have definitely started taking our steps in that direction. I think by having the event in Baltimore, which is on the coast for the first time in years, just really helped us get into a whole new audience of people pulling from Philly to D.C., etc. up and down that 95 corridor. And it resulted in us having our second highest attendance ever for DrupalCon. Which was really wonderful. I think one of the things that I found really encouraging was that Drupal training kept selling out, especially mastering Drupal8. It sold out, expanded it, sold out again. It's just things like that that are showing that there's some uptick in Drupal8 adoption. I'm starting to look at how we can see DrupalCon as a leading indicator for DrupalAdoption and DrupalHealth. Anyhow, there's some other things that I thought were pretty notable. On Monday we also have industry summits. And this is one of the ways we're leading into that adoption journey. We're doing industry-specific summits provides peer-to-peer networking sharing knowledge within that industry through case studies and people can talk in a safe space about their common pain points and how they can address them. We're finding it's really successful. We did it for nonprofit and government, higher-ed and media publishing. We were able to expand that. It was really successful. The nonprofit summit 100% of the attendees said they were satisfied to very satisfied. We just know that we are really focusing in the right area here. A lot of these came from industry-specific buffs birds of a feather and then grew into these summits. We're looking to see how it could nurture other summits in the markets that we know are going for triples, such as healthcare or finance. We definitely want to see what we can do to start growing some interest there as well in the conference. Another thing that's really important to bake into the DNA of any conference, especially tech and especially open-source conferences is diversity. GitHub just put out a survey that showed that in open-source diversity is really low. What we're showing is about 3% of conference attendees of one of the underrepresented groups. We are very fortunate that Drupal has much more diversity and focus on inclusion, something I'm very proud of. We worked with many people in the community and the track chairs to lean into that even more for this Drupal con. One of the things we did was we reached out to underrepresented groups and even provided some funding to help people that had great content to share and help them come to the event to share their content. We were able to measure what our diversity levels were in terms of speakers and attendees. We have a good benchmark now that we want to grow from. But I think the numbers really show that their efforts paid off with 29% of the session submissions from speakers had self-identified as coming from the underrepresented groups. So something we're very proud of and will continue to work on. We also in terms of we're kind of still going through all the session feedback. We usually find out what were the top 10 most popular and most attended sessions. But one that we do know is that for those that are sponsoring Drupal con even though it's a paid session versus a community selected session they're still highly attended. And actually FASLA which is one of our supporters and sponsors of the event had one of the top 10 highest rated sessions. And so I think we have been doing a good job kind of coaching the business community on how to really create content that sells at a session. And by sell I mean we're coaching you not to sell but to educate just to be more specific there. And then also as we were talking with our sponsors and looking at the survey we're finding that that people felt there were more leads coming in. There was more interest from evaluators. So we're hearing some good feedback so it seems that as we're leaning into this adoption journey and trying to get the right content and acquire the right attendees for businesses that you know we're moving in the right direction we know we still have work to do and actually I'll be flying out to Portland tomorrow no today a few hours to go meet with the teams so that we can think about how we can do even more to unleash our marketing abilities to to attract in more attendees at Drupalcon. So just want to let you know some of the ways that we're investing in this conference and keeping you and your business in mind. Another thing that we announced at Drupalcon Baltimore is that we have a new brand and for anyone who didn't get to hear that message I just wanted to share it with you. In the past every Drupalcon had its own brand and you can see the nice assortment here. They're beautiful at the end of the day as we're trying to promote Drupal and Drupalcon beyond the DrupalSphere we need to have a brand identity that really resonates and is consistent and so we went through an effort to find an agency that would work with us on creating a consistent brand and in the end this is through the whole process what was created and it is designed to represent that Drupal is both a blend of human element as well as that technology element and they come together in Drupalcon to create this amazing environment of learning and building upon each other's knowledge and kind of coming together as a community as well and so we're excited to be able to show this new brand identity starting with Drupalcon Nashville as you know sponsorships have already launched so you might have seen some of the graphics there with the splash page that's out there but the whole idea is that we will be promoting Drupalcon first not the city which is what we were doing before but we'll still have images that highlight the city that we're in and we'll still be doing special iconic branding that captures the spirit of the city that we're going into so you can see what we've done with Nashville and the guitar so there's still a lot of fun and play that we can have with the branding but at the end of the day what we're really trying to achieve is that consistent brand that resonates beyond the Drupal walls because ultimately we are trying to reach beyond our own community to invite people to come in the other thing too is that this just saves us a ton of time and even allows us to shift our resources to do more for the community rather than reinventing and re-skinning our sites every Drupalcon so there's some other benefits going on too so let me shift this over to Tim now who can tell you a little bit more that's happening in our other channel which is Drupal.org yeah I'd be very happy to so there's quite a lot that's happened over the course of the well since our last quarterly update and the first topic you might have heard about if you attended Baltimore but I'll reiterate it here it's a really really big change for the community so just to give some background history for pretty much the entire history of the project the in order to contribute a new module or a new theme to Drupal.org you first had to go through a project application process and back in the day this was for historical reasons about how we managed how the code got into the repositories but it's become a kind of legacy burden on new contribution and speaking with a number of supporters whether they're shops or technology supporters who may have their own tools that they want to integrate with Drupal it's been a big barrier to people to be able to say hey you know I'm building the site for a client we need to integrate with this awesome new service that's out there but I can't contribute that back or I can't do it in an easy way so what we've done is completely open to the project application gate process you can now create full projects on Drupal.org without having to go through a manual review and instead of that we are now putting new signals about project quality on the pages to try and make sure that we still give evaluators all of the information they need to know which projects are right for their Drupal sites so a few events to the next slide so one of the sets of signals it relates to security coverage because this is one of the biggest concerns we heard when working with the community to figure out how to make this change previously the way that you knew that a module had received security advisories in the event of the disclosed vulnerability was if it had a stable release and a full project on Drupal.org and that was pretty much the only way to know and it was kind of insider knowledge to make this something that's more useful to the community at large we're now putting signals directly on the projects so you will see these shield icons and indications of which projects will get security advisory coverage from the security team and just as a reminder that doesn't mean they're going through and trying to make these modules secure it's just a responsible disclosure policy if any security issues were to be discovered and that will help our evaluators understand which modules to use if you go to the next slide this is what some of the signals look like if a project is not yet covered so we have to provide that information to let people incorporate that as part of their decision-making process again when evaluating modules and this is what you'll see by default now the security coverage process that is still something of an opt-in so if you want to be able to get those green badges and shield icons there's a process for that that you can look at when you're going through your project submissions and then finally let's see here oh yeah this is what that process looks like so you get this opt-in option on the project pages and you get warnings but when you're making releases to say hey maybe you want to have security advisory coverage before you release the full version of your module and then if we continue to the next slide the other thing that we're doing around project quality signals is that we're working on ways to not just provide security signals but provide signals about why you might want to use a particular module for other reasons so the most basic one that's already out there is just starred modules so you can see someone who's trying to discover modules can now actually see which ones are the most popular which is a great signal most widely used we already have information about how much usage the various modules have and we wait those into search so you can get the most popular, most widely used modules and be looking at those when you're looking for something to use and then we're looking at adding additional signals related to code quality based on some automatic tooling that comes with Jupyter CI that we could then expose on project pages to say this is fully following coding standards this has got all the polish and shine to be used in a production environment so that's what we're doing or that's what we did with the project application process and we're still doing a little follow up work here and there but I think it's one of the biggest changes for Drupal.org in really years and one of the biggest changes for the project that will really open up contribution so if we continue to the next topic I'd also like to talk about the developer tools evaluation which is a big kind of long term initiative for the project and again I talked about this a little bit at Baltimore and so you can get a little more detail if you go and look up our D.O.Panel in the Baltimore sessions but basically we're evaluating whether to continue down the road of custom building our contribution tools using Drupal on Drupal.org or finding ways to integrate with major open source tooling providers like GitLab or Git Hub and you've seen a series of blog posts posted to Drupal.org about this process but let me just give you an update about where we are in the evaluation so if you go to the next slide the process started with an initial evaluation and then a deep dive with the staff with the technical advisory committee which is a group of advisors consisting of a couple community members and one member of the board and then we made some initial recommendations at the board level about what we thought we should pursue further and we communicated out this shortlist that that was those three options of Drupal.org, Git Hub or GitLab that you saw on the previous slide and there's a blog post about some of our initial evaluation there and now we're moving into this phase of trying to prototype what the different options could look like doing sort of alpha work to see what those integrations are and look out for gotchas or look out for workflow issues so that we can kind of preserve that those positive and unique elements of the Drupal workflow while still modernizing the tooling so that's the phase we're in right now and continuing to work on that and there'll be more updates either in blog form or as part of these updates or at the next Drupal con as time goes on let's see here and if we continue so yeah the next steps like I said we're going to learn by doing what we're exploring a prototype we want to see if we can pilot these tools probably with an initial contrib project and then we want to at some point we want to have this in a place where the community can actually like use these things a little bit and help us do some kind of final gap analysis help us see what we missed so and then I have one more topic for today that I'd love to update everybody on so let's go to the next slide so this is my favorite gift on the entire internet I use it to represent the Drupal.org infrastructure it's quite the Rube Goldberg machine of moving parts and pieces and we put out in March a RFP to find a vendor to help us manage infrastructure services so that our internal engineering team can focus on feature development primarily and not so much on maintenance provisioning of machines so if you go to the next slide these next two slides because it's too long to fit on one page is kind of a diagram of what the existing infrastructure looks like so you can see that from end user back to the back to the basic infrastructure we go through our Fastly CDN layer we then have a series of VM hosts where we run instances that provide all of the different services for Drupal.org whether that's our get services solar for research our development environments all sorts of things like that if you go to the next slide you can see where we keep some bare metal servers for the like really the services that we need truly high performance like our database service and some of our media serving and then we also have a portion of our infrastructure that happens in the cloud primarily Drupal CI dynamically scaling AWS spot instances so this is kind of the scope of everything that we're trying to manage and really find someone to help us manage so that we can focus on features and not just on this architecture so if you go to the next slide so the by finding this partner it'll help us internally keep focused on the mission so if we're successful we get to focus on feature development on on the sites themselves and the services that directly serve the mission of association on project improvements and then the partner can manage underlying infrastructure for us so to talk about where we are in the process on the next slide I've laid out something of the timeline but basically we started with posting an RFI to see who might be interested we received all those letters of interest by the 24th of March and had actually quite a lot of interest in potential participation in the program and sent out the full RFP those proposals were due towards the end of April and since once we received all the proposals we've been reviewing them internally and scheduling interviews with leading vendors and we are now in kind of the home stretch to make a decision so you can look out for more information about that in the coming weeks when we announce the decision and how we're moving forward but we're really excited about it as a way to help refocus our own limited resources on that core mission work that we really want to do sounds great lots of work happening so thank you for that overview I just wanted to see are there any questions from the group I'm going to just stop sharing and if you have questions you could use either the chat or the Q&A function in the toolbar at the bottom of the zoom window alright I see we have some comments already in here yeah one existing question was just whether or not would the existing con sites change to the new branding model all the existing sites will retain their current designs it will only be moving forward that the new brand is implemented alright well if there's no other questions feel free to email us at any time if something comes to mind we're always here and eager to hear from you and to work with you so just reach out you can probably have your account manager's email but you can also reach out to me directly at Megan at association.druple.org just don't tweet that email out please and anyhow just thank you so much for funding this work that we just shared with you and there's so much more we didn't have time to get to we just wanted to give you the highlights but we will certainly keep you abreast of other news and our monthly updates and we'll talk to you again next quarterly webinar so thanks for your time and have a great day thank you everyone bye thanks