 Good morning everybody. My name is Adam Goodman. I chair the board of the Drupal Association. It's nice to welcome you to this board meeting. I would observe that attendance is down apparently when we don't feed people lunch at the same time. And that's perfectly fine. I'm calling us to order. I can't see the slides. Are we going straight to the minutes approval? Yes. By the way, is Ryan here? So Ryan had agreed to take minutes for this meeting. So Suzanne is, thank you for stepping in Suzanne. Where is Ryan? He's going to get trolled. I don't know. I've got to figure it out since he's a major sponsor. Anyway, all right. I do need a motion to approve the minutes from our last public board meeting, which was on April 10th. I motion that we approve the last board meetings from April 10th. Is there a second? All right. No second. Any discussion? All those in favor say aye. Opposed? Okay. So that was the scintillating part of the board meeting because I think it's the only vote we take. I do want to, more importantly, I do want to give a couple of updates from the board retreat that we had this past weekend. This is something that we do twice a year, usually in line with each of the cons here and in the US. First and foremost, I know everybody has been great about welcoming Heather as our new executive director. Heather's been with us now about four months. This was actually Heather's first meeting with the board. So it was absolutely notable for that. I know I speak from my colleagues when we just had a great set of new interactions. Heather's going to bring, I think, a fresh perspective and a new sensibility to the opportunities and potential for the Triple Association and where we could be headed. I think the board is ready to go in that direction and to think about how do we build from the very strong history and foundation that we have to where do we want to go next. We just feel great about your leadership and where you're going to take us and some of your thoughts and we know it's not going to be perfect. We know that we want that forward motion. We want that experimentation and the risk and the change and the growth. We characterize our discussion over the weekend as vigorous and engaged and certainly went longer than was in the time budget, but everybody was great about hanging in there. Just a few topics in terms of what we covered to give people a sense of that. The first is that we did talk, as Dries talked about in the Dries note, and as Heather and Michael Amp talked about, we talked about the Community Recognition Committee and basically went from idea to how do we want to operationalize it in terms of giving a charge to that committee and we asked Mike Lamp who is stepping off of the board to chair that committee for us. I think he's going to do a great job. They're going to come back to us with their thoughts and recommendations. Certainly our hope is that we have something that we can share and help fine tune with people when we all meet in Minneapolis. So we've given them, I think, an ambitious set of work between now and Minneapolis. I would characterize it as this is really about the health and sustainability of the project and the DA and the debts where we want them to be focused. The board certainly is a part of the charter, wants whatever that CRC output is to be fairly easy and simple. We wanted to have really clear benefits for people who are contributing to the community, who are contributing to Drupal, and obviously in terms of helping to sustain the Drupal Association as well. So there needs to be benefits all the way around. Just a few other thoughts from the retreat. We did agree to have a deeper conversation and I think just part of it is about Heather's arrival as well and really doing a review of our strategy and what we want to go next and having a much more in-depth conversation about that. We're going to work on dates before getting together to have that conversation. We also talked about not surprisingly unrelated to the strategy, reorganizing some of the committees and board members you should now have in an email asking you to indicate which trainees you might be most interested in. So I'm going to take a poll to see who's responded. I'm ready. You guys get both. You get extra spotter professor, you get extra credit for your grade. We also talked a little about the importance of reaching outside of the Drupal community. Obviously we don't believe that the work inside of the Drupal community is done. There's always more that we could do. But we have a voice and we really want to make sure that we're using that voice as part of the association to talk about what's going on. By the way, when I talked about the community recognition committee, I verbally didn't point out there is a link for how you can learn more and how you can identify if this is something that you would like a process that you would like to participate in. We obviously are going to put together the committee from people who nominate themselves or who are nominated by others and that's key to this process. Lastly, there are a number of welcomes and thank yous. Let me do the welcomes first if I have it in the right order. We go where you go. All right. It's good to be the chair. All right. So I want to start by welcoming our newest members. First is Grace Francisco and you can read a little bit more about Grace. We also have four and a half new board members. I'll get to the half in just a second. I also want to welcome Leslie Flynn who is here. Leslie is one of our two community elected board members. And many of you may remember Leslie from the just extraordinary recognition for extraordinary service that she received in terms of earning the Erin Lynn board award last year. So I was just so thrilled that the community self fit to appoint you. We're really excited to have you. Now I've lost track of my order. Leslie was with us this weekend but was not able to stay for the con and again her background is up there. I think she's going to be really bring us along with Grace just to really some additional outside perspective. And that's one of the balance points that we absolutely want to have on the board. Switching to some folks with sort of more of an internal perspective is Owen Lansbury. So Owen's over here. And as you all know Owen and his team have been just huge contributors to the project over the years. He also brings a voice from a different continent and speak the same language sometimes. It's all about the accent. Exactly. So we want to welcome Owen and sort of the half partly because he's not here so I'm giving him a clue. Ryan who was the community elected board member. It's not sort of an automatic or you know even typical thing but Ryan and I think everybody knows Ryan again. Just the extraordinary contributions that he and his firm has made to Drupal over the years. It just kind of made sense I think as a part of that voice to have him continue on the board. But shift from being a community elected person to a board appointed person. So those are the welcomes. There are three really important thank yous. This is and I think that we certainly said that over the weekend and I think we all feel it as a part of the board. In addition to Heather's arrival and the arrival of the new board members this really is a transition point for us as a board in a very positive way. Again solid foundation to be headed. And three people are stepping off of the board after just extraordinary service. The first is Mike Lamb. Many of you again know Mike. He's with Pfizer and again he's going to join. So we didn't let him go exactly. Yes he's off the board but he's chairing this very important committee for us. It was our board secretary for many years and just was a calm, cool and collected and broad thinking presence. And I will certainly miss seeing him in the room. Any bill led our nominating committee. And it's one of those things that takes and it's one of parts of the process. Take an extraordinary amount of time and thoughtfulness and board nominations is one of those. We have a good problem and that there are a lot of people who would like to be on our board. And thinking about sort of the current composition and where we want the board to go and how we bring in those outside voices. And how we continue to raise the profile of the people who were appointing and all of those things. It just takes a lot of thoughtfulness and a lot of time and frankly a lot of meeting with people. And he contributed that. The other thing that she really did was a wreck when she came on the board was a sort of voice of the customer exercise for us. Which again gave us some new input and some new data in terms of thinking about who have we historically been listening to and who are we not listening to. And how do we hear those new voices and I want to thank any for that. And last is Jacob Redding. So Jacob many of you know was a volunteer with Drupal beginning in I think it was 1898. And then about 1906 or 1907 was on the staff of the Drupal Association. Then he wisely went away for a few years and we even more wisely brought him back as a board member. And so when we think about sort of massive transitions certainly Jacob stepping off the board is one of those pieces. He was our treasurer certainly from my tenure. It was after Tiffany, right? You picked it up from Tiffany Harris. Yeah, I think that's right. And those of you who know me know that financial argument is not my strength area. It never will be. So I called Jacob and said it'd be great if you could be the treasurer. You need to know that I operate on a very simple green, green, yellow red light system. And if you could just keep an eye on that. And we were still digging out and trying to improve the financial condition. And Jacob, your work and the work of that committee with Badi and others has really got us to the much healthier position that we're in today. And I know that's just your recent contribution but I really want to call that out. Because it's again from a foundation perspective has set us up very nicely to where we want to go next. So that's my updates. I'm now going to turn it over to you Heather. I'll say thank you Jacob. And Heather the floor is yours. So Jacob when I got to make a brief stop at Seattle Drupal Con as part of the executive search process gave me the insiders tour of Seattle. And so we spent what I think was a couple hours walking around Seattle and getting the lay of the land. And so it was a combo learn everything about Drupal that's in his head, which I think would take two years. But also just you made it a very, very fun welcome into the Drupal community for me along with everyone else on the board. So thank you and Jacob you'll be much missed. Okay, so what are we up to and what am I thinking? So this is the one slide version of that. Hopefully what we've got our eye on in the coming year is not too dissimilar from what's important to you as well. We do try to align those things, but some of this will resonate what Adam already talked about. And some of these things are what we're working on internally at the D18. One of the things I heard very clearly coming in is that we do a very good job speaking to each other in the channels where we already exist. And where there's a huge need is for the rest of the world to know about Drupal and to embrace Drupal and to see it as an important part of technology. So we're really thinking through where should we be where we can have that voice show thought leadership and help everyone else know the magic of Drupal that we know. So that's a huge focus area from us. It's going to be heavily leaning on the marketing side. So we have hired a new marketing director. She came in a couple months ago and a lot of what that vision is is setting up a strategic plan around how we make that happen. So you'll be hearing a lot more of that in the coming months. Really focusing on relationship building in particular with our supporting partners and our key stakeholders had a great supporting partner session yesterday. And what really came up and some of you were in there is, you know, we really have a need to align closely with a lot of communities, but that end user community is one of them. So how do we support our supporting partners, right? Many of whom are agencies and that's a key focus area for us. And we came up with some good things out of our session yesterday that we're going to put into action. But I think it's even more aligning the people that drive Drupal and the Drupal Association and how we can better work together so that we're all meeting those goals. Adam already spoke to this, but what was on our list from the very beginning was, you know, those mechanisms to recognize and reward volunteers. And so while there will be the mechanical component of capturing contributions, there's also a marketing and communications component of highlighting those that work within the project. So what's really important to me is that we're making very visible, whether it is through social media or blogs or however we can do it, highlight those of you, the people behind Drupal and the power of it. So individuals, companies, anything we can do to better showcase all of you. Another session we had yesterday was around local associations and they have a huge need as they are growing to be able to look at scaling, recruiting volunteers and how all of that can align with the Drupal Association. So we're working on what the structures look like for us to be able to provide from a kind of a shared services model. There are things that are critical for local associations and events to do in their administration. Right and where we want to put the power of volunteers are in the things that we're not on the ground to be able to do. So what we're working together to do is make sure that we let you do what you do best and then we better find where we can support from the DA angle. Membership, so thank you to everyone. Raise your hand if your member sticker is on. Yes. Yay. Okay. So you may have noticed some increased activity at our DA booth here at Drupal Con Europe where we're really pushing the power of DA membership. And so we're committed not only to bringing you into the membership family but also creating meaningful membership programs. Right. So right now it is thank you for being a member. You're funding our work. We also want to find out what are meaningful benefits that we can bring to you as members and layer those into your membership program as individuals and as organizations. So that's another big initiative that we're working on this year into next year. I already talked a little bit about local camps and associations. It really is looking at how do we lay the groundwork so all of that happens a little bit easier. And then we we launched the diversity and inclusion conversation heavily in Seattle. We continue to look at that and fold it into what we do. But what we don't have at the DA that we're working on now is a real strategic plan behind what that means. So where are those focus areas? What are the focus areas within diversity and inclusion that are meaningful from a Drupal perspective? And how do we start to not only talk about it more and recognize it more but actually start to move the needle? So I'd be remiss if I don't take every opportunity under the sun to recognize my team. Some of whom are here. So Tim, Ryan and Neil were brave enough to join us today. I think everyone else has been put to work at our booth, which is why they're not here today. But this this is a really special team of people that are putting all this together. And when you have that moment of why can't they do the 18,000 things on the list and why are they only doing the 100? Just keep this number in mind and understand that we we're working to scale as well. We are we're walking the walk when it comes to getting outside of the Drupal bubble to an at least outside of our DA bubble. So I got to attend my first Drupal camp a few months ago at Drupal Camp Atlanta. And so we're also committed to how can we get to spend more time with you from a local perspective and not just at Drupalcon. So if you've got a local event happening, make sure it's on Drupal.com so that we know it. And if there's something special happening, you need some special content from us or anything like that, reach out and let us know. Outside the Drupal bubble, Tim and I were attended by invitation to the Google CMS Leadership Summit. Google did pay for us to attend. So thank you, Google. So we got to spend some time with CMS leaders in general. But I think the most meaningful conversation we had and Tim agree is we got to have an open source roundtable with our peers. And what was probably not what's surprising and not surprising at the same time as when we talked about what are our biggest issues, they're all the same in general, right? So we're all facing the same challenges. What was clear to me is I need to do a good job of connecting and collaborating with my peers in open source so that we can better learn from each other. So they see Drupal as a leader in many, many ways. So there was a lot of pride in the room when Tim and I were there because we got to talk about what we do great. But there are things we can all learn from and this contribution recognition piece is huge. So I think what will likely happen is the next time we land at the summit, once we've run through the initiative that we're talking about, is open source is going to be looking at us to be a leader in this. And when we talk about opportunities for thought leadership, I think this is one of those we should take advantage of. We've also gone to some other events. One in particular was a Portland Partners in Diversity event. So we're also trying to go to non-technology events where Drupal can be part of the conversation. You'll see some of the people in the room that are also at this table, so Midwest Drupal Summit. We also had a presence at Drupal GovCon and we actually hosted a smaller version of our executive summit at that event. So that was another way for us to not only connect with developers and marketers, but also to connect with those end user executives that I know everybody's interested in getting hold of. Speaking of membership, hopefully on social media, you saw our membership campaign. This is going to be an ongoing campaign. So if you'd like to participate, you can reach out to us and we'll feature you on social media. You can see some of the summaries of things where people said I'm a Drupal member because. So we are thrilled about our community. We want to highlight you more and this is just one way we can do that. So I mentioned the Drupal Executive Summit we did at GovCon. We've actually have done three so far. We're doing a fourth in Minneapolis. So if this is something that's interesting to you, please reach out. This is a way we're reaching into CTO, CIO, CMO audiences as well. I mentioned it pre-dries note, but one thing that was really exciting was launching the official charter for the event organizers working group. I think this is going to do a lot for us in organizing local events so that we are sharing best practices, learning from each other, not recreating the wheel because there are great things happening across the globe when it comes to local events. And we need to make sure we talk to each other and share all of that great expertise. These are the camps that were represented on the organizers working group and wanted to highlight that there was global participation so that we had various input. So DrupalCon Amsterdam, we are here. So this is just a quick overview of who's attending DrupalCon Amsterdam. The last number I heard was just under 1,500 people. So that is that's good turnout for resurrecting DrupalCon Europe. As you can see, these are the top 10 countries represented. Fingers brag accordingly. And then you can look at, yes, Germany and Netherlands are up there. But it's nice. It's definitely important that we have a presence in Europe and thank you Europe for giving us a little bit of time to figure it out. And we're thrilled to have been able to implement this new version. I'm wondering why Belgium is not at the top of the list. Can you comment on this? My country is letting me down. And that's the snippet on Twitter. It's funny that you say this because for many years I would say Belgium was ahead of the Netherlands. And it was always kind of like, you know, the fun. Wait this for a couple of minutes and we win. That is true. You can massage the data and make it work. So because it is a new format and we're all learning things in conjunction with our event partnership with Quoney, I wanted to make sure one that you were able to give feedback on individual sessions, which you can do through the app. There is a debrief bot this afternoon here at Drupal Khan so that you can have some live discussion around your feedback. And if you're not able to make it to that event, you can participate in our online survey. We would very much like to get your feedback. We're taking our notes. We need your notes so that we can get this even better for next time. And I know we have not officially announced a session yet, but we are feverishly working toward being able to do that. And we're committed to making this work in Drupal Khan Europe again. So we do have, if you don't want to wait a year to come hang out with us, you can visit us at Drupal Khan in Minneapolis. Just a quick quick look at what the week of events looks like. It is a full five days with that fifth day being the contribution opportunities. One thing I wanted to point out. So what we always, you know, we always try to learn lessons and make every Drupal Khan better. And one thing that we're doing in Minneapolis is increasing our community involvement. So we opened up the training call for proposals as an open call instead of invitation only, which it has been in the past. So that's giving a nice diverse pool of training sessions. Our program committee has traditionally been about 20 people. And this year we very purposely reached out in the community and it's around 70 members of the community that are participating in the program committee for Minneapolis, which I think is just a great improvement. And that's going to lead to even better thought leadership and even more perspectives on what that content looks like. And if you are thinking to yourself right now, gee, I really want to be involved because that looks fun. You can. So we have a link here. If you don't have a chance to take a picture to use later, you can find us at the DA booth, but we will find ways to get you involved. We still need speaker and session team members. We still need leaders for various tracks. And of course we need speakers. So speaker call for proposals is still open. So there's still an opportunity for you to get your content in as well. When does that close? December. December 10th. Yeah. So we hope to see some of you in Minneapolis. And at this time I'd like to bring Tim to the stage. To talk about Drupal.org. Yeah, so as you all know, a large part of the mission of the Drupal Association, of course, is uniting the community to build, promote and secure Drupal. So on that build note, our small but mighty team of engineers focuses on creating all those tools that let you hear build Drupal itself. So I just want to talk a little bit about some of the work that we've been doing and the work that we do in general. One of the just things I'd like to highlight really quickly, and you may have seen this slide briefly go by in the preamble to the Drees note as well, is that Drupal.org is increasingly part of the service infrastructure that supports Drupal as a product. So, you know, many years ago, 10 years ago, Drupal was something that you could sort of use by itself. It wasn't dependent on kind of web-driven services, but now every year a new bubble goes up on this list of something that Drupal.org provides that direct integration back to the product, whether it was updates at the beginning, things like security advisories, the composer endpoint, the localization services. And we expect more year over year, and Drupal.org will continue to be sort of an essential part of Drupal as the software, not just as a support infrastructure. And I think that's something we'd love for everybody to keep in mind and help collaborate with us on as we work to make Drupal even better going forward. Quick comments, yeah, I was going to say. So, you know, we're in my project. I will say that the collaboration between the Drupal project and the core committers and the Drupal association is all time high. Like it's never been this good. Like all the things you mentioned, they're happening, we're seeing, we're getting the support from the Drupal association to make things better. You mentioned all of the initiatives, but it's obviously a big thank you and huge credit to you, Tim, and Ryan, and Neil, and hiding there at least for me. And I'm sure other people as well, but thanks for all the hard work. It's been night and day actually compared to just a couple of years ago. Awesome. And so another of the initiatives that I think everybody was hopefully thrilled to see during the, during the Drees Now. When they finally saw it. Yeah. Once the video began playing was this collaboration with the European Commission to work on this automatic updates initiative. And that's an example of those services where the process of packaging, the update packages, assigning them securely, delivering them to Drupal sites is all infrastructure that takes place on Drupal.org So this initiative was kind of a dual experiment and a successful one on two fronts in that it's a new way for us to collaborate and support Drupal as software. But it was also a new and very significant collaboration with the European Commission as, you know, a large governmental organization here in Europe recognizing the value of Drupal. And, you know, they use it internally on almost all of the EU sites and properties. Right. It's important to them. But the fact that we've been able to reach out and get them involved and have them become good citizens and participants in our community is tremendous. And we want to look for those opportunities in other places to multiply the impact that our small team can have on the Drupal project. So we are seeking more sponsors for more phasers of that initiative. So I'm going to give that shout out again because I'd love to get more people involved for more organizations, whether you're supporting partners, whether you're end users, whether you have connections to other government organizations that are heavily reliant on Drupal, hint hint Australian government. And maybe you want to have some participation in this. So those are just some quick updates. I think we can move to sort of a Q&A session. We've got about 15-14 minutes for questions for the board at large or for us as the engineering team. You can line up with the microphone please so that we can get everything on the recording. Alternately, we can pass it around if the board members have any comments that you'd like to add. Great first one. So where's the big blue group lead gone? No, the inflatable has a puncture, I'm afraid. But we'll certainly get that arranged. Tim at the last group, can you talk about pull requests? Oh, yes. Yeah, so I should talk about that a little bit more. So Neil has been working quite a bit on the next sort of elements of GitLab integration and sort of prototyping what it's going to take to turn that on. We're hoping to do that actually very soon. So we had some dependencies on the GitLab team itself that I mentioned at previous events. I probably shouldn't get too technical, but they did full clones of every repository every time you made a fork. That meant that if we had a fork open for every core issue, it would be 200 terabytes of disk space just for core. So we needed them to fix that and do object deduplication. And they released that in their 12.0.0 release just a month or two ago. So since then we've been getting that ready and right now we're just in the process of integrating it into the UI. So Neil has a development site that we're working on that actually has the full, there's a button to create the fork and you can kind of see that. So we're going to put that together and then probably pass it around a bit for UX review to make sure that that's going to work well for everybody's workflow. It should be coming soon. Next six months. I hope less, yeah. Can I have it? It's only really quick on that. Can you grab the mic? So for those people who don't know, I work for Accenture review really quick. We have 500,000 employees worldwide, very big organization. And recently I was talking with our head of DevOps who was working on certain things and no joke in like a big Slack channel that we have. He was asking other sort of leaders like, does anybody know of a large migration to GitLab? It's something like maybe 10,000 branches. That's not very many. So he needs some examples for like our enterprise clients, but we're way beyond that. Yeah, 40,000 projects by a lot of branches. So yeah, we're doing things way above what they're doing. More questions for the board or perhaps for me? So I know that one of the reasons that we left Europe for a year was really a financial decision. I'm super interested in knowing how this shift to using a vendor that we're using has affected that bottom line. Yeah. So the good news is the way that we've structured the partnership is dramatically different than what we've ever done before. And quite frankly different than we do in North America. So the upside is there was we did not own the financial risk of the expense side of running the event. So it's more structured like a license agreement. What that does is allow us to do the things we do well. The community pieces get everybody together, but it doesn't have such an impact on our financials that we had to not do it. So Adam, I don't know if you want to say anything else about it, the reason that we're committed to getting your feedback and getting this just right from a partnership perspective is not only does it allow us to keep coming back to Europe and not have the financial risk. The idea ultimately is that we scale. So there are other parts of the world we need to be in and this is the only partnership construct that will allow us to do that effectively. That's what I was going to add is our hope is that this experiment turns into something that we can scale to other geographies around the world and figure out how to make work. I think we're all aware, certainly as a board, we want to be more present in more places and in an in-person way, not just in a virtual way. Because we know that we need the two to really have a very healthy community. So yes, we need to figure out how to do this right and part of doing it right to your point is how do we scale it in a way that we can do over and over again, not just in the same geography, but in different geographies. And part of that is we know that what a conference would look like here is obviously going to be different than what a conference would look like in India, for example. And we want to be able to account for that as well. So it's not just let's figure out a cookie cutter. It's let's figure out a model that works, but still allow for the authenticity and the flexibility of the community and the voice in that. And therefore, wherever that conference would attract. For what it's worth, I think that this experiment worked pretty well. That's great feedback. Just to speak on the global scaling piece, one of the reasons that Quoney ended up being the partner of choice is that they have a global present. Global presence with local teams. So all of all of these places that we want to go, they have the ability already built into their system to accommodate that. So we're not taking a local team and trying to grow at the same time. We've got we've got somebody who's got that structure in place. Are there any, can you talk a little bit more about your plans to collaborate with other open source projects to communicate the value of open source? So I don't know that it's anything specific right now other than we need to do it. As about as far as the plan has gotten, but I think part of that means while it's important to have me at Drupal events, it's just as important to have me in non Drupal events. And we need to make sure that that is that's in the schedule and in the planning and in the budget. And when I think about it, we think about how do we scale that effort? So it's not just does the staff need to be places, but we even talked about board as Drupal leaders being in other places. Ambassadors of the Drupal community being in other places so that we can truly scale that effort. So we're building out the plan of kind of what that looks like and where their strategic collaborations. But some of that we won't know until we get there and have conversations and see who wants to who wants to come hang out with us too. But I think the first step is we've got to go and we got to meet him and we've got to have the conversations. And I think it's everything from your typical open source communities to we had a conversation yesterday with Facebook open source. Right. So we've got to be thinking about all the different ways that we work together. And in almost every conversation there is something that we have in common that we want to collaborate on. So so far so far it's been a good experiment. We just need the time and bandwidth and scaling mechanism to do more of it. So if you're interested in being part of this Drupal community that helps us get out and about and evangelize Drupal in some non-traditional areas please let me know. Easily our biggest constraint is not on anything that we do whether it's inside or outside of the community is frankly just time and financial resources. And we have just enough funding to do exactly what we are doing right now. So any new activity that we take on and there's a long list of things that we as a board really want to be able to do. We have to figure out sort of in a nice way how are we going to pay for it in terms of the staff or volunteers and helping those volunteers stay organized or other financial commitments that are required in order to make that happen. And as I think about Drupal we've got big ambitions. We've got big goals and we want to do it all. We really do. We just got to figure out how do we how do we support it in a way that is sustainable. And Maria and George are fighting over the chance to go to the mine. I was surprised by the pricing for Minneapolis tickets. I know we've done some experiments in the last few years and has a long time in Drupal that pays his own way because I'm an independent contractor. The pricing now is egregious. I had an e-mail exchange with hoping that you can consider ways to make it more affordable for people that aren't being sponsored, aren't being paid by big corporations. We've gone from three days to two days or four days to three days however you calculate it. So the price per day has gone up a bit. Can we speak to it? We did a pricing study a couple of years ago and looked at, and I don't have the specifics off the top of my head, but what we looked at was basically where are our peers at and where are we at. And to say that we were below the mean would be an understatement. And I know when we changed pricing, I'm not even sure we hit the mean but I could be wrong. We got closer? Yeah, we got closer to it. And the other piece of this, and I'm sensitive to your comment, is we do have a scholarship program because we still want to obviously be open and accessible and create opportunity, but we also wanted to recognize frankly the reality that, and I appreciate what you said. But we also know the vast majority of our attendees are people who are sponsored by a company or an organization that has the resources. And I really want to tie this back to my previous comment, which is we are committed to being open. We are committed to being diverse. We are committed to offering more benefits and more opportunities for people to participate in the Drupal community. And all of that takes resources. And that's important. We've got to find a way, and it's not sort of how do we max, we don't sit in the room and think, how can we squeeze every penny out of somebody so we can get their money. That's not what the conversation is about, and I want to be very clear about that. We really are trying to think about how do we, how can we do the things that we as a community know we want to be able to do. And to help grow and sustain Drupal. Again, people point to us, as Heather said, with, you know, wow, it's incredible that you guys are doing this, this, this, and this. And at the same time as people inside the community, we think to ourselves, yeah, but we still want to do this, this, this and this. The scholarships are really good. Like, that's a super, super, super program to have available. The scholarships are terrific, and I'm really super-weighted to get folks who are, you know, less able to attend the events, to be able to attend the events. I would imagine though, and I'm going to pick on Doug here for a second, a fellow who's at his point in his career probably would say, I'm not going to, I'm not going to apply for a scholarship. There's somebody else who needs it way more than I do, and I totally hear what he's saying is being an independent contractor and still being really expensive. Sure. And so I'm going to put on, I don't want to have a long dialogue on this, but I'm going to put on my, I'm a professor hat for just a moment, because this is something that we absolutely see in higher ed, where people will say, there's somebody more deserving than me, so I'm not going to even bother or apply. That's where the mistake happens. In the nicest possible way, that's not that student's or your decision, and you never apply. Ask the worst thing that happens is you get, you know, a no, and I think we can figure out, we'd rather have you be there and figure out how to make that happen. Can I add to this? So as a board member, so the discussion has been a lot about contribution credits, as an example, and the DEA today gives sponsored, so partners, 10% discount, if you are a partner of the Triple Association of the Prizes, and I think that we have an opportunity, especially in this case, and what you're mentioning, to actually use a contribution system if that would be reflecting on the contributions to actually do some kind of a discount system out of it. Just saying that as a board member, that I think that that's to be something that we should be looking at. So I would love to see that maybe happening. Well, and I think that feeds into what I mentioned with looking at membership, not just organizationally, but individual. Those are the things that we're trying to tackle. So I've been collaborating with the last group of cons of it on the program, and I feel like we are making good progress, especially also with the collaboration with Gwani, but like every year I have the feeling like we're starting from scratch again, so somehow all the knowledge gets lost, and all the good learnings that we have kind of dropped, and then we start like really late, and then kind of, yeah, I'm wondering if it's maybe the kind of collaboration tools that are a bit dated. I see a lot of good progress being made on triple.org, but overall I'm not yet convinced if we really solve all of our collaboration problems fast enough to be like effectively collaborating as the community that we're growing. Yeah, I think a particular area of collaboration tools that needs more attention. We have a lot of good tools for individual issue collaboration, documentation collaboration. We lack a lot around the formal tooling for initiative collaboration. There's sort of like landing pages for it, and then people set up their Slack channels and things like that, but those are the kinds of like project management oriented things that we're still missing, and that could apply to cons to volunteer opportunities, but also to the software. Yeah, so I want to add to this, thank you so much for being part of the advisory board, and I feel it because Imra and you and we were doing this. So one of the things that I want to actually say and give compliments to the DA staff, because you actually stepped in really well in the last months to help us to get things done, and there were issues like recording. That was not part of the original deal with Gwani, and we just somehow missed that. So what happened there is that the German Drupal Association came and said, we are going to take care of the live streaming, so they sent a person here, from the left over from the budget from last year, to come and do the live streaming of Drees Note, and also Pantheon sent Kenneth Dahl here to actually develop the recording that we are having here. So also like we should thank them for stepping up and actually taking care of that, but you're totally right, we should have figured this out many months ago, and solved it earlier and not be in less minutes there. I would say that we should do a retrospective of this together with the DA, maybe after two weeks or tomorrow. So with that, we are a little bit over our time, so we will wrap it up. Adam, I'll let you officially close out the meeting. Thank you all for coming. Do we do a motion to adjourn? We're going to do a motion to adjourn just in case we need to. So is there a motion to adjourn the meeting? Did we approve the meeting minutes? Yes, we did. If you show up on time, you know all of the things you're doing. It was just a long time ago. Is there a motion to adjourn? Second. Okay, we are adjourned. Thank you all very much.