 I'm going to take us through the first couple of items, and then turn it over to Tim and others who will update us on financials and a few other things. So here we go with the regular presentation, and I'll go ahead and keep going, Adam. Yeah, exactly. That'd be great. So as you can see, we've got a number of updated items. The first thing I want to do is we've got two new board members, so I'm really excited about that. I'm not sure if Annie's on yet, but I want to thank Annie and the rest of the nominations committee. This is one of those things that you think is sort of a couple of phone calls and you round people up and you're done, and it's one of those things where the board actually has a pretty rigorous process in terms of thinking about, you know, what are the criteria that we're looking for, who might fit that criteria, a series of conversations with folks, and obviously people need to decide that, you know, Drupal is a place where they want to spend part of their time as active community volunteers giving back. So this is a significant process in my experience, and I'm just really pleased. We've got two new board members, Luma and Vishal, and I saw Vishal's name, and I can't remember if I saw Luma's name on, but maybe if the two of you could just say hello, and just tell just a minute about yourselves, you know, sort of your introduction to the Drupal universe, I think that would be great. Awesome. Luma, why don't you go first? Good morning. I'm delighted to join you guys at 7am on a brisk Wednesday morning here in San Francisco. I got introduced to Drupal when we were looking at replacing our homegrown content management system and, you know, given how intricate our internal environment was, quite frankly, Drupal was the only one that was flexible enough to really meet our needs. And it did not take long for us to be able to swing a fair amount of very strong opinions across the organization that going open source was going to be the way to go moving forward. And I'm happy to report that as a result, we've actually paved the way for a lot more of the technologies within Schwab to go open source as well. So we did some, what do you call it, yes, there you go, there you go. But I've been in the financial services industry for quite some time for over 20 years. 18 years, 18 of those years have been in the digital space specifically within content management of all of our prospect experiences. And so I'm delighted to be able to join you guys now and really just learn from you because you've brought this movement a long way in the same amount of time and I'm excited to be a part of it. So thank you. Okay, Vishal, are you there? Yeah, I'm there. Good morning to all of you if you are able to hear me out. Yep. Okay. So my name is Vishal. I got introduced to Drupal around six years ago when I took the open source as the group within data consultancy services, one of the system integrators in the world. And ever since it has kind of excited me and also intrigued me with the kind of community that Drupal has. So we have been working a lot around Drupal both internally as well as externally. But more than that, I'm excited to be there as a part of this particular team and see how or what two cents I can contribute to the cause of Drupal, so to speak. All right. Well, again, yeah, thank you very much and you know, I'm really excited that you all are on the board. And again, you know, Annie and the nominating committee, it's largely thankless behind the scenes work and it is incredibly time-consuming and I just want to express my appreciation again to the folks on the nominating committee for just doing a fantastic job identifying Luma and Vishal and bringing them on the board. Okay. Next. Yes. Yay. A couple extra members. Yeah, but June was recently, recently born to Annie Miller and has joined the family and we just wanted to say a brief public congratulations. I know that Annie may not actually be able to join right at the moment to acknowledge that and say that that's just wonderful news and we're very pleased to see June in the world. And just one more, the Drupal Association Director of Revenue, Carrie Lasina, just had her baby on Saturday, Lila just joined the world, new Drupalers. We're going to get them indoctrinated into the community as soon as we can send those Drupal onesies over and get them to join us. So after that brief insertion, I'll hand it back over to you, Adam. Okay. So I want to give everybody an update, as you all know, towards the end of September, Megan who is our longtime executive director and had really grown up inside of Drupal professionally left us to continue working on open source but at Google. As you all probably are aware, as part of our succession plan, Tim was set to be our interim executive director and he's doing a great job. The team has continued to do a great job and I'm just really pleased with where we are. Obviously we do need to conduct a search to find a replacement and so what has taken place over the last 30 days or so, or 60 days I guess it is, wow, time has flown by. But at any rate, the board met and formed a search committee, it's customary for whoever the board chair is, which happens to be me, to also chair a search committee for an executive director so I've agreed to do that. And obviously we wanted a nice cross-section of the board and we also wanted representation from the staff so it made sense to ask Tim to sit on the search committee as well. And no mention of Tiffany Ferris. She is a longtime board member, a longtime contributor to Drupal and I think is a function of her sense of history and sort of executive presence and sensibility. There was a general sentiment that it would be good to have somebody who is not on the board but who has a wide range of experience and Tiffany certainly fits that bill. So that's the search committee that the board has appointed. We also went out and interviewed a number of firms and selected layman associates, Jan Lehmann who is the principal of the firm, is directing our search and she was the unanimous first choice of the search committee so that's great when that happens. And so I think we're all feeling really good about, in terms of, so right now they are working on a profile which the board will have an opportunity to talk about and then once that profile is up which we anticipate will be the next week or two then people can actually start to apply and obviously the search firm will also go out and solicit people who they think will be a good fit. We're not quite sure how long the search is going to take. It could take three months, it could take nine months. So we're asking for everybody's patience in the meantime. Obviously we want to find a great candidate rather than move as quickly as we possibly can. So while I think we will move along, again we want to make sure that we find somebody great. Obviously we will publish as broadly as we possibly can the criteria and how people can apply so that folks who may be interested can do so. So that's kind of where we are right now in terms of in terms of the search process. I think Tim the rest of the agenda is yours or others, right? Yeah, so I just want to run through quickly the committee updates and some of the procedural items that are sort of typical for our board meetings really quickly and give the chairs just a brief opportunity if they want to add additional comments before running into the association staff updates. So just going through this as quickly as we can. The governance committee met a few times since our last meeting focusing on assembling canonical lists of local and regional leaders to move forward the initiative to create local associations that can work in concert with the DA as the global association and is continuing to organize local country slash wards and create governance around that with the intent to bring the global slash wards events to Drupal con Seattle. Michelle, do you want to add any quick commentary or should I keep running through? I know we're relatively short on time. Michelle may not be on yet. I'm not sure. I heard he was caught. I do see him on the participant list. He may not be able to speak where he is. So I'll just go ahead and keep going. Okay, yeah, here I am. Okay. The usual for Michelle not to have a comment. Let me put it that way. Yeah, yeah. I just have a quick update. Well, the good thing is in the Netherlands, we just the local association hired a market here this year to do a lot of marketing and PR for Drupal. And this is now being copied by Belgium as well. So Belgium is going to hire a market here in 2019 to set up local marketing, a local marketing initiative. So this is good. This is moving forward. If we can copy this to other countries, that will be great. This is basically the roadmap we've set aside for us. Awesome. Thank you, Michelle. And I know that that work is together with the promote Drupal work in general is trying to create a sort of global coordination around the marketing efforts for Drupal. And I think that's really valuable. We'll have more to say a little bit later in the presentation on the promote Drupal effort for the finance committee, which is chaired by Jacob Redding. This committee meets monthly to review financial statements. So again, they've met several times. We've got some great feedback on some operational improvements and improvements in finances. We'll have an update from Angie Saban, a director of operations, a little bit later. And so this committee focused their time on reviewing some new formats for financial statements in our dashboard proposed budget in 2019, dashboard recently. So there's a lot of good material there. Jacob, if there's anything you want to add, feel free. No, I don't think at this time there's anything to add. Which we get to the finances. I think the one thing I'll add is we're very happy to have Angie on board. And she's done some extremely great work. So we love the new formats. It's been tremendous to have Angie on the team. And I think everyone will see that as we go into her update in a moment. So awesome. Quick update from Revenue Committee, which is chaired by Ingo. This committee did not meet since the last meeting, but has been in communication regarding the launch of an upcoming program. We'll be talking about that a little bit more in the executive session, because it's not quite ready to take public yet. But there's some interesting news there and a few other things that have been developing in the meantime. So we'll look forward to those updates in the future. Ingo, there's probably not anything to add, but if you do want to drop in anything else, please do feel free. No, nothing to add. Thank you. Thank you, Ingo. For the nominating committee, this is chaired by Annie Miller. Annie is possibly listening in by phone, but she did let me know she wasn't able to immediately join the call. So I'll run through this update quickly. So obviously, the committee concluded their work on the last round of candidates. And again, we're thrilled to have Vishal and Luma joining us on the board. It's wonderful to have more experience both from a system integrator perspective and from an end user organization perspective and people who are just sort of tied into the open source world. There was the potential for one additional seat. The decision was made not to fill that seat until the next round of nominations. So there's one available seat that can be included in the next one. And then we also want to just put out the call that your suggestions for the next round of nominations that will take place next year, next summer and fall, are still welcome and needed even starting now. The process for vetting candidates can easily take six months to a year. So it's a process that's always moving, even though we're just welcoming new members. We're always in the process of looking for more. So Annie has requested that if you have thoughts or people you'd like to nominate for potential consideration to join the board, please email the members of the nominating committee. And the board packet has the names of who those are, or you can reach out to me if you need the contact. So those are our committee updates. The other thing is, as part of our standard procedural operations, we do need to approve the minutes from the last meeting. So we have our public board meeting minutes from Drupal Europe. And if anyone would like to. I think it's my job to say I need a motion to approve the minutes. And Audra, I'm assuming you're hanging out there taking minutes this time, right? I'll make a motion to approve the minutes. OK. Thank you. I think that was George. And I need a second. This is Jacob. I'll second the motion. OK. All those in favor say aye or put up your thumb. Any opposed? All right, the motion passes. I discharged my responsibility. Thank you, Adam. All right, so we're going to roll into Drupal Association financial updates. And I'm actually going to invite Angie, who we just mentioned earlier before, to speak a little bit about this. So I'll go ahead and switch over to the first slide, Angie. And you just let me know when you want me to keep moving. Hi, everybody. I'm Angie. And I've been with the organization since the beginning of September. So I've got a background just quickly a little bit about myself. I have a background in nonprofit finance and HR. And I've been in this field for about 15 years. So I'm coming with some experience from several different types of 501C structures. So I'm very happy to be here. Tim, if you want to go to the first slide. So this is our new dashboard report. The first slide of our new dashboard report that I created for the organization that hopefully will give a little bit of a narrative visually about where we're at as an organization. So this first slide is all about cash. And I'll talk a little bit about each of these and keep us moving along here. But this first shows our cash position at the end of October. And in the blue, you see our unrestricted cash. Both our total and then what our goal was for this. Actually, at any given time in the year, our goal is 15% of the budgeted gross revenue is unrestricted. So we're really close to meeting that goal, which is good. And actually, you'll see in the next slide that we're continuing to see growth in that through the through your end. And then this top part on the first slide, first chart is our restricted cash that we have on hand. And to the right, you can also see how that restricted cash breaks down. So a good chunk of that is money that is for next year's DrupalCon in Seattle. So sponsorships and ticket sales that have come in and currently are sitting as prepaid cash on our balance sheet. We've got a new restricted classification called Promote Drupal. So you can see that broken out in hopefully, you can see the different shade of red there. And then we still have so many from our different camps that we act as fiscal sponsor for. So that's how that breaks out. And then available funds for general operations in blue. And moving forward. So as I said, for cash, you can see the green line here is our 2018 cash and it's trending upward. And part of that is simply due to opening registration for Seattle a bit earlier than we have in previous year. So that gives us a bit of a bump up. And we've also had some really great activity by the revenue team on sponsorships as well. So that's contributed to an increase in our cash trend line. This next chart is our actual cash projected balances, which is really just based on timing of when we think inflows and outflows of cash will happen. So it can vary a bit the actual projected there. But generally, it's looking quite good. And then our projection of what the restricted balance will be as well as there in red. So that takes us to the end of December. And next month, we'll see this continuing on into 2019. And then you can move forward. And then this last slide, I believe it's our last slide, just shows our ratio of revenue, how much of it came from Drupalcon 2018 versus all other types of income. So you can see the ratio there is skewed slightly toward a little more than 55% of our revenue for the year came from the Drupalcon 2018. And then in our very last chart here, you can see the very first column shows net income of October. The second one shows our original budget. The third one shows what we've re-forecasted for. And then the last one is our projected net. So we're coming in significantly better than what we had originally budgeted. Maybe not quite as high as we'd hoped after a re-forecast, but we have a few one-time expenses at the end of the year that is part of why it's slightly less than what we had re-forecasted. But we're very pleased with where we're landing for the year. So that's really good news. And I think that might be the last chart. I think it is, yeah. Thank you. Yeah, thanks very much. So I'll move into updates about Drupalcon and where some things are at there. Firstly, Seattle is obviously coming up in April. It's the next big event in North America. The accepted sessions have been announced. And the actual schedule of sessions will be coming on December 14. This is something we're really excited about. Of course, there'll be lots of messaging and promotion to promote the event and get it moving. We also, just last week, traveled to Vienna to meet with Keowney Congress, who are our partners to operate Drupalcon Amsterdam in 2019. And here's a photo from that event where you can see Drupal Association staff, Keowney staff, and community members of the advisory committee who all came together to spend a two-day deep dive on the scope of the event, on some possible adjustments and changes to formats and ways to bring in new audiences to European events. It was a really great conversation. It was a great two-day experience, I think. Keowney had already previously attended both Drupalcon Nashville and Drupal Europe. So they're already getting well tied into what the feel of the events is like, what the programming format is like, and what the culture of the community is like. So I think it was very, very positive. And if you saw some of the tweets from DeBoer, for example, I think the feeling is really good right now. So we'll be continuing to meet with them on a regular basis to coordinate what's going on to help do their integration when they are ready to begin things like their own call for papers and ticket sales. And so there'll be more news as that develops. Finally, just a reminder, at last Drupalcon, we also announced that in 2020, the North American Drupalcon would be happening in Minneapolis. There's not much news to say yet, but I just wanted to put out that reminder again to know that that's coming up. I'm really excited about it. Next, I'd like to run into some promote Drupal updates, just a few items to touch on with more to come. I think the first thing to say is that Rebecca and the volunteer team have been meeting quite frequently to discuss the game plan and outline for promote Drupal. As was an overview was given at Drupal Europe of the current state of things and the collaboration tools that were put together to create some global collaboration. And there's some key materials that are being assembled to really make this work. So one of the first initiatives was to create a brand book for Drupal. And this is brand and logo guidelines. There's a public draft already available and there's first revision already planned. This is basically a set of guidelines so that we can unify the look and feel of promotional materials across agencies who might wanna use these resources, across local communities, across local associations in different countries. It's a great selection of material that helps us create a consistent brand message for Drupal across all of the channels and all of the regions in which we'll be talking about it. So that draft is certainly something that you can take a look at and there's some really good material there. The next revision is gonna include a vision statement for Drupal's market position that's been based on a series of interviews that took place in September and October and that'll be integrated soon to further update that brand book. In addition, so on top of kind of creating materials, we also have to create a place for materials to live. And so there's a wider effort to enhance the community portal on Drupal.org, Drupal.org slash community and provide new ways to move through the user journey and identify who you are, what you wanna participate in and how to get there, how to get in touch with the right people. So there's this find your place kind of menu that has a variety of options. There's more than just what you can see here. This is just what we'll get on the slide to help new members of the community orient themselves and how to get oriented to the community. And for example, each one of these expands and has some options for diving deeper into, in this case, for example, looking for regional groups or looking for communication channels. And yeah, there was this UI was inspired by at the splash awards in Drupal Europe. There was a similar UI by one of the splash award winners. And it was very inspirational and that opportunity to see and share great case studies is really helpful for us and everyone in the community to find new ways to move forward with these things. I wanna jump into some Drupal.org updates next. So first, the GitLab update. So right now we are furiously in the process of running and rerunning migration tests in the staging environment. We actually behind the scenes we have the, we've hooked up in production, the version control GitLab API, which is the kind of backend bones of how Drupal.org will interact with GitLab and begun the process of user syncing and things like that. So these are all part of the phase one process. Integration points are really promising and we've had great help from the GitLab team. They've been wonderful partners resolving issues as we found them, typically things like needing some additions to their API and things like that. So our commitment to complete phase one was Q4 of 2018. We're sort of halfway there. We have some elements of what was in phase one in production. We may slip that by about a week for some of the public facing things like the code facing stuff because we don't necessarily want to deploy over the winter holidays, but at the very least, we'll have it at the beginning of January. And there's a detailed update in this issue if you want to see all the activity that's been going on. And then there's some really powerful stuff in there. Finally, I wanted to slip in some preliminary PHP version telemetry based on an October data sample. So we actually recently discovered that because Drupal 8 uses Guzzle as part of its installation process and update process and things like that, it actually collects some data that we didn't know we had. So for example, it has PHP version information. So we're actually in the middle of building out some more detailed reporting mechanisms, but we did a quick example just from the October data set to just see for all the sites that contacted us and for all the sites that contacted us in October about update information, what versions of PHP are they running? And this is all the Drupal 8 sites. And what we find is it's surprising to me at least, it's only about 20% of Drupal 8 sites that are still in a PHP 5 environment. So as we talk about deprecating, as we talk about deprecating PHP 5 in upcoming versions of Drupal, we have maybe not an insignificant audience that we need to communicate to, but I think I suspect we're actually doing rather well compared to other PHP-based CMSs. It seems like a surprising amount that these sites are actually already ahead of the curve and have moved into PHP 7. Good question. Is this Drupal 8 or Drupal 7 included? This is 8 only. 8 only. All right, thank you. Cheers. Okay. And then our next update, we're looking at reimagining the tri-Drupal program. This has been an area where the initial program has been actually very successful for the Drupal Association and for the end users who it targets. It's been an opportunity to find a way to tri-Drupal to work with a couple of partners who can create a good demo experience, but its kind of scope was limited. The original experience was a bit minimalistic. It was mostly focused on sort of three placements that were more or less ad placements for doing different trials. And each of the demo experiences of the different partners has been different. So there's some inconsistencies and some things that we really think could be improved. So we've put together concepts for the next generation of the tri-Drupal experience that I want to cover really briefly. We're gonna reuse some of that same awesome new UI for identifying what kind of user people are. So you'll be able to choose the appropriate experience for the type of audience. So those audiences are basically our three main personas, the marketers and team leaders, people who want to get their hands dirty like the developers, or people who kind of already made a decision and just need to get in touch with a partner. So what these sorts of things will look like is an option to opt in to watch a demo video, which we'll be creating to show off some of the great features like Layout Builder and the Omami demo. We feel that a video is just more appropriate for some audiences than jumping them right into a full demo experience, although there are some audiences for whom that demo experience is really powerful as well. And so what we'd like to do is create a unified demo experience that people opt into, gives them an opportunity to play around and then still integrates those partners but integrates those partners into the demo experience so that they can move on from the demo having had that consistent introduction and then take it into the partner that they may want to work with. So we're excited about this. There's definitely implementation work to do. It's not something we turn around and do in a day but we've been talking to partners and we think that this is gonna be a great way forward. All right, finally, just some board notices, things that are under discussion. We won't be doing the formal discussion of these items here in the public session but there are things that we want the community in general to be aware of and to be aware that the board is aware of. So first, the community working group put forward a proposal for their change in charter. That's something that we've been looking at and talking about offline and other informal conversations and something that we hope to have additional news from the board soon in terms of considering that proposal, possibly shortly after this meeting. And then also the governance task force put out their recommendations. These were basically 13 recommendations for how to further evolve community governance for Drupal. I've linked both the original proposal and Dries's blog post thanking the task force and outlining the elements of that proposal and addressing some comments there. This is something that is in sort of a 30-day comment period after having been first released. So we've been sitting back, seeing how the community responds to all of these proposals and there's quite a mix of proposals. Some of these proposals are things that we are either sort of partly acting on already or can act on in the near term. Some of them are medium term and some of them are long-term initiatives that would require some significant funding. And the task force was very transparent when they put forward these proposals that some of them were wish list items and some of them are things that we can move on quickly. So we wanna thank them very much for their tremendous work. It was more than a year's work really to put all of that together. And it's just really helpful to have that consolidation of everything that people are looking for. Yeah, Tim, I just wanna add my own thanks to the governance task force and obviously the trees as well for organizing it and asking that they go forward and work on this. And as you said, I think there are a number of really good ideas in there and also a number of sort of wish list items that are gonna be a little bit harder to figure out how to implement. But it was clearly work that was needed and they put in a ton of time to give us a very thoughtful set of ideas to consider and themes that they uncovered as they were talking to people in the community. So I just wanna add my own thanks to that. Yeah, I totally agree. And I think just the level of compassion and care that's clear in everybody's interaction in this process has been really tremendous. And it's something about that community that I think at times we take for granted but we have one of the most committed communities that's out there. Yeah, I would like to echo that as well. This task force has been working on this weekly that provided weekly updates and they've had multiple phone calls with them as well. We're currently in a 30 day feedback period which is about to end actually. So I would recommend everybody on the board actually to go look at the documents and to read up on each of the recommendations and to also read up on all of the feedback on the recommendations because for each of the 13 recommendations there is an issue on Drupal.org linked from my blog post. And I recommend we look at it because it actually often impacts the Drupal Association. And so it's really useful to actually take a look at that in my opinion. And I think it would be good and respectful to actually come back with a sort of a plan of which of those 13 we feel we can move the needle on and sort of what timeline we think we can do that. So I do think we need to probably huddle with a smaller group and figure out what our official response is gonna be sort of a plan to a plan kind of response I think would be good. Yeah, and we do have some time set aside in our private session after this portion of the session to do some of that initial discussion of those items. So we'll do that as well a little bit today. Let's see here. So now is typically the opportunity for community Q&A. Now, typically with most of these meetings we find that most people join, well, most people view the recording rather than join live and especially in a December meeting I'm not sure that we have any questions. And yeah, it looks like we haven't had any come in. So what I'm gonna do is go ahead and we'll go ahead and close public session here. Thank you all for attending. Thank all of you who have watched this recording at a later date. The minutes and the board packet information will be posted publicly on the board section of the Drupal Association website. So you'll be able to review all of that. If you have additional questions you can certainly reach out to me and I can appropriately forward any questions to the board as necessary or answer them myself. And we really thank you for your participation and your interest in board activities. And with that, we will go ahead and switch over. Thank you very much everybody.