 Um, could you just run down who's not here again? You did that at the beginning, but I was getting the meeting minutes kind of ready and I missed it. No Vessa, no Samir, no Denise. I'm here. But there's a dog. Is Vessa still on the board? Yes. He is. When do those terms expire? This month. Uh, yeah, that's why we have that on exec session. We do. Yes. And I know that because I copied and pasted it, but didn't read it. But now I've read it. All right. Sweet. All right. All right. Um, welcome everybody on the agenda today. I mean, I think you all have the minutes or the board packet rather in front of you. We're going to do the typical operational update and Q&A and then we're going to do reports from the different committees that will be very quick to manage each. And then we're going to talk about the licensing working group charter. And then we're going to move on to the executive session. And we have quite a few things in executive session. So hopefully we can get through the first part quite fast. Holly, the floor is yours. Yep. Um, I will go fast. Um, thanks, Dries. So I just want to highlight a few things from the packet this time. Uh, and I'll start with the Drupal cons. Um, sorry for making you seasick while I scroll. I'll get there. Uh, so for Drupal cons, um, obviously we're in our first month after, um, Amsterdam and as many of you already know, we had record attendance for a European comm at Amsterdam. Um, there were 2,300 folks there, which is really fantastic. Um, that was a bit of a surprise. We had a, uh, leading up to the last couple of weeks before the con. We felt like we were behind and then we had a real surge of last minute tickets, um, mostly from Amsterdamians. I don't know how you say that. Amsterdamers. Amsterdamers. Of course, of course they're Amsterdamers. Um, so, so that was great. Um, we have also been pulling through all of the numbers from the financials to the, um, session evaluations to the overall conference survey. We'll have a lot of, you know, more about that in next month's recap of the Amsterdam con, uh, spoiler alert. Uh, nobody liked the food. Uh, so we'll be sharing some more about that and things that we're doing at future cons to address some of the issues that did come up. Um, in other con news, Latin America is now live. The site is live. It took us a while to sort out, um, how to do payment processing, um, in Spanish and in English and in Colombian pesos. Um, but I want to send a huge thank you to our community volunteer, Aldebir, for helping us sort that out with pay you vendor we're using there. And, um, also if you get the chance, definitely register if only for the fact that it makes you feel like a millionaire to register in Colombian pesos because the a lot of pesos to the dollar is all I'm saying. Um, and then Los Angeles, I just, uh, I just saw the final comps for the, the art. I just want to say it's spectacular. I'm so excited. Uh, but, uh, the big news in Los Angeles is that the session submissions for Los Angeles start in January. Uh, so look out for those. Um, and just on, um, on our side of things, we've been working towards, um, you know, new unified Drupal con sites to make a con launch a lot easier, um, for us internally and Jacob and Emily and, um, Stephanie Alhage working a lot on that. So we're really looking forward to seeing some of that work, um, which most end users won't really see the benefit of, but you'll see some new things on the con sites starting in Los Angeles, um, uh, on the back end and, and also a few things on the front end too. So we're excited about that. So that's the Drupal con news. Any questions about that? Okay. Um, on Drupal.org on the Drupal.org side, um, the big news coming out of Amsterdam was that we released the roadmap for the 2015 plans and you can see those at, sorry, you can see those at, um, Drupal.org slash roadmap. Um, and all the plans are laid out there. We've had really good feedback just to the idea of even publishing the roadmap. Um, and now, um, as Josh puts it, we've published lots of this kind of thing before on the site. So now the trick is to actually do it, uh, so they're working on that. Um, but we're, we're, we're pleased to have that up there. We also in the last month released the terms of service and privacy policy updates. Um, which is really, um, you know, did our best to take what was some really, there was some really great constructive feedback from the community and we tried to really make the tone, um, and spirit of those documents align with, uh, you know, what we feel are the community values and the association values. Um, and we think it's a much better document. We're still keeping a list of things that, uh, folks have questions about that we might want to update in future versions, but right now we have over 15,000 folks who have accepted the new terms of service, um, logging into the site. So that's great. Um, and the team, sorry guys, the team also, um, uh, in the last month launched a new commit message interface on the site. Uh, we also have over 400 automated tests now. So when we build something, we actually can test it on staging before we push it to live, uh, which is, you know, the right thing to do. Um, so those are two big, huge things that happened in the last bit of time. Um, and especially on the testing, I just, you know, I know that, uh, Melissa and Sam did a ton of initial work on those BDD tests. Um, and I just want to thank them for doing that and Ryan and our team for picking them up and then also actually getting a lot more continued support from Melissa Anderson in, uh, in getting those tests back up and running on the site. It's been a, it's been a really great thing to have. I think the last bit of news on the Drupal dot org site is that the team is fully hired out. At this point, we brought on our last, um, engineering team person, um, Tim Landon just joined us as a project manager, um, and that has been fantastic for the tech team, um, and also for, uh, community members and for, uh, particularly for our staff who, um, you know, now feel like they have a great resource to go to in terms of, you know, identifying the things that we need to get done on Drupal dot org and, you know, figuring out how to get them done and when they can get done and all that good stuff. So awesome. Yeah. And of course, oh, I should also just mention we continue to work on updating the profiles on Drupal dot org and that's the first big technical step and towards, you know, realizing some of what Dries talked about in his Amsterdam keynote, um, and we'll have more to talk about that, you know, in the coming month. So any questions about Drupal dot org? Okay. Very briefly on the community program side, we did have a global training days last Friday and, uh, last Friday and Saturday, uh, there were 82 participating organizations, which is fantastic. Um, and we were thrilled to have events on every continent, but Antarctica, which clearly means that, um, George, I'll work on that. Yeah, somebody needs to work on that for the next time of trip for global training days. I'll make a note of it. Yeah, it's time for us to go back. Okay, good. Only the baby needs to go. Yeah, that's the tricky bit. Um, and then on the marketing communication side, um, you know, Joe spent some time working with the security team as we released the, um, the core security advisory, uh, that went out last month. Um, and then we spent some follow up time working with that team to develop a strategy, um, to respond to the new cycle, um, as a follow up to the PSA that, that followed up that security advisory. Um, and so, uh, basically those guys are working together now. Um, the general gist of it is to, um, let the discussions continue and let the cycle die down. Um, and they are working on materials related to, you know, addressing lessons learned from the, um, from that, uh, announcement, um, and, uh, some more, you know, sort of proactive, uh, here's what you can do in the future and here's how we've changed our systems, uh, you know, to, uh, to address some of those issues. And so, uh, I think starting, um, December, January, we'll start to see some of that content get out into, uh, out into the, out into the ether. So I think those are the, um, the big highlights to talk about from the October through the member timeframe. Any questions about anything else that you guys might have seen in the packet? There's no, well, there's no questions. We can move on to the board committee. Um, so let's follow the order that's in the doc, which is revenue and the governance, finance, executive marketing. So revenue. This is Megan. Um, so we are doing pretty well. I mean, Holly talked about people on Amsterdam finishing a lot, um, stronger than we anticipated, which really helps us out on the sales team who's responsible for sponsorships and the supporter program, web ads, um, the other non-con revenue. Um, they are at 97% of their annual goal and so they're using the next couple weeks to really push hard to get that to 100%. Um, and, um, so overall income is looking pretty strong. Uh, if you look down at the different product lines, you'll see that Drupal Jobs is off. Uh, it's been compensated by going over on the sponsorship side. Um, and that's what made up for that. So I just want to kind of point out those types of things. Um, but what's important to note is that, um, our 2015 revenue plan, um, has a big emphasis on like Drupal Jobs and Drupal.org web advertising. So this fall, actually while we were at Amsterdam, we, uh, brought Carrie Lesina on board as our product manager and strategist for creating, um, web advertising products and improving Drupal Jobs and really getting those numbers up. And she's done a great job interviewing people throughout the community, uh, potential customers, um, working with staff and she's coming together with a great list of products and a prioritization plan to, to roll these out. And so, um, I feel like we're really well positioned to move into 2015 and I'll have more on that, uh, shortly. And then also just working with the revenue committee to prepare for 2015, two areas that we're focusing on are the, um, is the co-marketing campaign. So it's been great, uh, just to recap, uh, at the last retreat we talked about two marketing events, uh, in Europe, um, and we want to find two industry events where Drupal could be the sponsor. We'd go in with some companies to demonstrate the power of Drupal in different industries. And, um, it's been great working with VESA and, and the others to kind of get that research going and so we'll be working more on that as a revenue committee. Um, and then also starting to think through the steps for the fundraising campaign that's associated with, uh, the Drupal Aid Accelerate Program. And, um, so those are the things that we're focusing on right now. Awesome. There's no questions. We can move on to the governance, uh, committee. So the governance committee, um, uh, convened, uh, in just recently to talk through all of the, uh, all of the, uh, um, election change, uh, stuff that, uh, that we had, uh, discussed in our previous board meeting, um, and we've come up with some, some recommendations. Um, I'll, uh, uh, you all have, uh, have, uh, have been shared, uh, on the, uh, on the, on the notes. They're pretty messy, but I'll put together sort of, uh, a clean bullet point, uh, set of recommendations that we came up for, came up with for, perhaps the next, uh, the, the next, uh, board meeting, uh, if we can get it on the agenda. Uh, great. Uh, finance. So finance committee, um, has been meeting and, and working with Holly to review the, um, proposed budget, um, that we'll be talking about in executive session. So I'm not going into any, any more on that. And then obviously, um, we've been, um, reviewing and approving the Q3 financials, which we'll also be looking at in executive session, but we, everything looks good. So that's a good thing. Um, the executive, um, committee, we did not meet, because there was nothing to meet about. Um, so I think we can move on to marketing. Yep. And let me just, I assume that Joe is there with Josh and by unmute this mic. Hey. Hey. I've been here for room. Yeah. Can you hear me? Yeah. Yeah. So the, um, as I mentioned in Amsterdam, the primary activity right now for the marketing committee is to try to identify a new chair. Um, as I mentioned in Amsterdam, we put up a call for a new chair, both online through our channels as well as some one-to-one outreach. Um, and we, we did have one person who self-nominated. The good news is that, uh, she has great credentials and, uh, I think she's fantastic. Her name is Chiquina Montabuea. She's from Bullet Reaction. Um, I spoke with her length, uh, about her background at credentials and I think she's great. Um, so next month, uh, for the December board meeting, I'll be including some information about her. Uh, as far as her background and credentials and, uh, we'll have a agenda item to go ahead and approve her as the, uh, chair. All right. Um, unless there's questions on the board's committees, I think we should jump to the, uh, licensing, uh, licensing working group charter. There's a separate presentation. If I could just tie, if I could just hijack the meeting for one second. I don't know. Josh, are you still there? I'm still here. Yeah. Do you, um, can you turn your camera on? Yeah. You know, you know that it's, uh, already been. Oh, yeah. Okay. Just making sure. All right. We just wanted to say, um, happy birthday, Dries. We got. Oh, and we already ate some of it. Oh, very cool. Wow. Show that again. Show that again. I need to take a little screen grab. I'd love to get a photo of that. Yeah. We do. Thank you. I'm tweeting it right now. I'll be sure to copy you. That picture is the full cake without the. Yeah. I wish I could blow out some candles over the internet, but we're still working on that module. You are such a dag, Dries. I love it. All right. Thanks, Josh. Thank you. It's very kind. Sorry, we didn't actually get to meet on your actual birthday. I'm sure you're not. The gift of abort meeting. Yeah. Too funny. All right. So should we go to the licensing working group charter? I think we should. All right. We were going to sing at everything, but I got sick. I'm in my pajamas. I don't know. So like I was up for that. All right. So as you folks may recall a couple of months ago, we came to you. There had been escalating number of questions regarding how licensing issues get handled on Drupal.org and a number of community members reached out to me. We met a couple of times and we came to you with a proposal to form a licensing working group. So that's the overview. This is the group that I had a conversation with in July. And we had, you know, a few problems that need to get fixed. We have an increasing number of issues that get posted. They are all tagged inconsistently. Additionally, they go into the webmasters queue. And so, you know, those those folks that regularly monitor the webmasters queue, they're not trained in licensing. They don't really know what to do with all those issues. And even the people that have some experience with it don't have any, you know, don't feel that they have any authority to make decisions like yes, you can include that or no, you can't or we're going to add this to the whitelist. So, you know, there's a few players involved. Obviously the association is one of the stakeholders because we are legally responsible if things aren't carried out properly. But we also want to serve the project contributors through the working group because they have lots of questions and right now they're just not getting those questions answered and it's one of the reasons why it just makes sense to, you know, maybe host your code somewhere else and not on Drupal.org because, you know, you don't have to that kind of ambiguity is taken away. And then the security team has some small investment in this as well because if there are any vulnerabilities in any whitelisted libraries, right, we're going to have to address those. So there's just a team that we want to stay in touch with. We do this work. So again, we came to you with a proposal to create a licensing team which we moved to calling the licensing working group. And we sort of put three models in front of you and you said to us go back and talk about how this would be for and to come to us with a charter. So we did that. We created a draft charter. The language was finalized at a Boff in Amsterdam and we had about a month of time that it's been up on the site for public discussion. There are a few points. They think are already addressed in the charter and everyone that participated in those original discussions felt like the charter was in good shape to go ahead and and signed off on it. So they all feel like it's a really good shape. Couple of the highlights of the charter sort of the key points. It'll be a working group of four to five folks. We went with the option that they're all appointed by the board because the association is legally responsible. The scope of the working group is limited just to the licensing code and other assets on D dot oh not on other sites. So if we get reports of licensing issues on other sites you know myself I'll probably end up chasing some of those down but the working group here is not responsible for those and just to be clear the working group is also not in charge of determining which license is used for the product. So the decision of moving away from DPL v2 for some reason right that's not under the working groups purview that's still Dries's purview with this charter. I think one of the other key issues is that the group responds to issues is not policing for issues. So if an issue is spotted and it's raised the group deals with it but what the group is not going to do is a you know a code review of all code that's checked in at Drupal dot org and the group will also maintain the whitelist of allowable assets that can be included in your code. So those are some of the key points from the charter. And then to get them started that we need a queue for licensing issues which the Drupal dot org team is you know ready to help set up and then we will get some training set up for the working group members. You know probably a briefing and then Q&A with the law firm that we work with here in Portland and then working group members will also need get access to remove projects that are in violation of and don't respond to requests from the team. Holly is that that draft up somewhere? I mean it must be if people are working on it it's publicly available somewhere at the moment or yeah it was posted up in the legal working group on GDO so okay just it and yeah all spelled out here so it's pretty short. Ta Ta I'm going to yeah thank you yeah other questions so far so so the next steps assuming that the board is ready to accept the charter once the charter is established then we need to recruit team members and identify a chair. We can do that with posts and a self-nomination process just to get some names in the door and then bring a a list to the board for approval hopefully at the December meeting might run into January with holidays and whatnot we need to establish a license in Q and then obviously set up time with the legal team to get everyone trained following that. So that's the update and where we're at and what we're asking for is to approve the charter today. I'll make a motion that we approve the charter by second. Not sure we set that but who seconded? Hello? Who seconded? It was Rob. Hey Rob. All right, awesome. So those who are in favor say aye and those who are opposed say no. Aye. Aye. Aye. I'm abstaining because I haven't actually read it yet. Okay. And we're missing some votes still. I was starting to get off mute but it's an aye. All right. Have we lost people, Holly? Can you tell or not? Let me see. I don't know where Tiffany went. Let's see. Jeff's still there. Are you there still? There's Tiffany, yeah. She Tiffany wrote up here. Yeah. There are B-R-B so I'm not sure she should pop back in a second. But I think Tiffany is the only one we didn't hear from as I watched the voices go around Tiffany and Angie. Maybe let's start over and hopefully by roll call that will make it a little bit easier. So sorry about that. So say your name and then say yes or no if possible. Oh Angie says she can't talk but aye. Just so you know she texted that in. Can you guys hear me? Yes. We can now I think. So this is Matthew. Aye. Chris, yes. This is Jeff. Can you guys hear me? Yes. We can. I had some kind of audio problem there for a little bit. Sorry. I am. Did we all blink? It was just me. I couldn't hear for like three minutes there. Yeah, something happened. So we're redoing the vote. Okay. So it's Mike here and I Rob. And Angie was I through IRC. I think or I am and then Tiffany. You don't know what Tiffany. This is Donna. I've now read the charter and I I I thank you for that glitch, which means I can now not abstain but vote. Yay. All right. So where we Angie, are you thinking what are we missing? Is it just that's everyone that's here. Dries. Okay. So I think that means it's approved. Excellent. Thanks guys. So I think that's the end of the public stuff. That's right. So quick. Who owns the the flip point to go find people to fill this group? Are you going to do that? Or is that something you need someone to volunteer to do? No, I have a draft ready to set something up. And I was just going to send it out to the same sort of advisory group of people. So. We'll post it. If I do the writing, Larry's happy to do the posting, which is helpful. All right. Any more comments or questions from anyone? There is nothing. I think we can officially adjourn and then regroup on the other call. Details are in the calendar. Invite.