 I think we're all set, Dries. All right. Are you recording? Yep. All right. Thanks, everybody. Thanks for joining. Sorry for the late starts. As you can see, we have an agenda for today. Sorry, I just got a message from Angie. She's on her way and she'd be here shortly in the next minute or two. So we're going to do the typical operational update provided by Holly. Holly, I'm going to limit up to 10 minutes, and then we're going to do a quick discussion from the board's committee updates, then an update on Drupal 8 accelerates, also presented by Holly, and then an update on the strategic range, also presented by Holly. Hi. It's Holly's show. I'll give the floor to Holly. All right. I'll talk for the rest of the hour, everyone. How's that sound? Great. Okay. So just a note from the operational update, and I'll just run through the sort of the highlights of things we're watching in the lowlights from the month of June. So a couple of big highlights for us. One in particular is that we were able to launch Drupal CI. Initially, it was just launched on for core, core testing. We just, like moments ago, though, we were able to launch it for Contrib, which is great, and it's still running concurrently with our old system, but so far it's been working pretty well, and it was a precondition for Drupal 8 release, because the CI improvements mean that we're able to test against more versions of PHP and different kinds of environments, which is a nice upgrade for sure, but the best part is that patches are going to get tested a lot faster. These Drupal is set up to auto scale. So with our old test bot system, we had a finite number of servers running at any given moment, and if a camp started to sprint in Eastern Europe at 3 a.m. Pacific time, and the sprint bots, the test bot started to get backed up, it was often hard to get someone to turn on more machines to create more capacity. So Drupal CI auto scales, we get that elasticity of the cloud, and the second that, you know, capacity for the existing servers is reached, more servers are spun up, so although the test times for a particular patch aren't necessarily faster with Drupal CI, the patches themselves are getting out of the queue much more quickly, so that should save our Drupal developers a lot of heartache in the future. Super excited about that. And then just a couple of the things that I think really are indicative of, you know, how excited the world is to see Drupal 8 get out there. I know it's been a slog and it can feel kind of, you know, lots of folks in the community are, there's some angst around getting Drupal 8 out the door, but I think when it does come out we're really excited about how people are feeling about it. We've had some white papers that we've done in the last month or so with the last couple of months around Drupal 8, and year to date we've had over 33,000 downloads or views of those Drupal 8 related content pieces, so we're excited about the moments in there and what that's going to mean when we're able to get a candidate, get Drupal 8 released. And the association also has really been growing its ability to reach members of the Drupal community, so we've had a ton of, you know, about a quarter of a million touch points with the community this year through social media, newsletters, people coming to Drupal cons, webinars, you know, all the ways camps that are sponsored, right, like all the ways that we are getting Drupal messaging out there or providing a service to the community. So we're really excited about that number, just that that sort of raw number is really big and exciting for us, and we'll talk about the strategic frame later, but it'll be even better when we're able to put some context to those touch points and show that we're really actually helping the community to achieve something. So there's some highlights there I wanted to point out. The thing that we're watching right now is Barcelona net income. We had solid early bird registration numbers, which was a big relief, but the registration has definitely been soft in this regular registration period so far, and sponsorship has been down this year from plan. So, you know, Rachel does a really fantastic job of managing the budget and managing to the budget so that we can, you know, we can meet our net goals, but that's definitely going to be a challenge this time around for Barcelona. But that shouldn't be super surprising news, but it is what it is. And then, of course, the low light for the month of June, we put a blog post out in the community and the board was obviously informed, but we went through a retrenchment process in June. We started that in June and we have, you know, we've shared that with staff. All of the immediate adjustments have been made and we're putting our plans in place to monitor where we're at and we'll share some of that, some of the financial bits of that with you when we get into executive session. So, those are the big talking points. Any questions about any of those items? Holly, how is the response from the community been publicly? I mean, if you could summarize, you know, sort of general reaction, it was pretty light, right? Or did you get a lot? No, I definitely did not get a ton of feedback from folks, although when I have one-on-one conversations with folks going forward, it definitely comes up. We talk about it with people. But I think the things that I've heard publicly is just they're grateful that we shared so openly, which is that feels good. You know, and I think a lot from the business community, I had a lot of business owners reach out actually and say like, you know, you guys did what you had to do, right? So, I definitely suspect there's some unspoken concern. But, you know, we just try to keep showing folks that it was a tough thing to go through and it feels and sounds terrible, but overall the picture is still really good. You know, the association is still growing. Thank you for any other questions? You have any other updates? Holly? I don't think so. Am I missing something? You think I should be saying? No, no, no. I'm just wondering if we can move on to the next section or not. I believe we can. All right, awesome. So community updates are next. They are in the board package. They're still being filled out. It looks like neither the finance or sorry, I can say they're still typing. Maybe what we should do is go over them real quick. Yeah, I think make sure we capture them. I don't know. Let's let folks have a minute in there. I know governments put their notes in and they do they do have an item they want to raise for discussion. If that's okay. Can we go last? Yeah. There's nothing else to review really right now. Okay, so we'll go first. So governments met and basically we were meeting around around board session for the next term. The short bit is that Donna and Spear both expressed doesn't understand the board for another cycle. That'll be brought into the discussions as we talk about who gets appointed and so forth. Angie expressed a desire to take a break, which I think isn't a surprise to folks. And so I think that also needs to be factored into our discussions. I think the biggest thing that we want to talk about is what appears to be a little bit of a change in process and how we navigate that. And that is that it looks like the government's committee is doing some of the stuff that the nominating committee has done in the past, which is totally fine and appropriate and good. But I think it would make sense for us to talk about how nominating committee and government committee ought to work together moving forward over the next three, four months until we've got a full slate identified, selected, and voted on. So discuss. Hey guys, have a proposal on how you want to work together? Well, Samir is sort of straddles both committees. And it seems like there's probably some good overlap there that'll help us. I think the biggest challenge is that in the past, and maybe I'm wrong about this, but it seems like in the past a lot of the discussions around individuals have been private to the nominating committee. And given the fact that Samir is also up for reappointment, this coming cycle, and he's on the nominating committee, we probably need to figure out exactly how that's going to play out. We do have a few ideas about some names, and we're more than happy to share those. But I think part of this discussion is figuring out, A, who really is on the nominating committee any longer? Because it seems like Denise maybe isn't any longer based on the committee's board packet listing. So we've got Samir, Christoph, and George. And that means that on the nominating committee, we only have one board member, and that board member is up for renomination. Right. I mean, Samir went on the, or Denise came off the nominating committee when she was up for her seat. So I would suggest that probably Samir comes off for this cycle and then can go back on if he wants. So have you had a conversation with Denise about whether she'd take on the nominating committees? Typically, we've had people who were outside of the community or off the board beyond the nominating committee, because the board, we obviously get to vote on the slate individually, and or the community-elected members. So Addy, previously Donna was on it, so I would suggest Denise and or Addy and or you would be good members of the nominating committee. But I don't think that, you know, I think that any suggestion you have come as like a board member to them rather than from the governance committee to the nominating committee, if that makes sense. That totally makes sense. Yeah, I haven't had a chance to talk to Denise. She wasn't able to make it to our governance meeting, but I'll reach out to her one-on-one and see what her feelings that are on that. My guess is that she'd be very interested in taking part in that, given our conversation at DrupalCon. And for the record, I'm totally game to be on the nomination committee as well. I mean, at the very least, I think we're going to need, you know, several people in terms of being able to talk to people and sort of doing the interviews and managing all that stuff. So I'm more than willing to help out whether or not Denise steps into that. Yeah, this is Sameer. So a couple of things that came up. One is you know, the workflow that goes from the governance committee to the nominations committee is relatively new. Because of the past, that's not what we did. And then the second is that if I have accused myself of the process, which I will, the nominations committee gets thin. And in the past, just sort of the logistics of managing interviews and talking to people and all that stuff is difficult with people living in different time zones. And then if you have a thin committee with, you know, like two of the people, it becomes even harder to do this. So I don't know if there should be a combined effort, or should be coordinated effort between governance and nomination. But that's something that came up in our competitions. I guess I don't understand why there would be. Can you clarify why there needs to be coordination? Because governance, as I understand it, just is dealing with, you know, how we function as an organization and nominating has typically been responsible for open board seats and filling that pipeline. So part of the overlap was where governance could indicate what are the things missing on the board or what is it that we need to move forward and sustain momentum in skill sets and backgrounds and so on. So something will just happen, or discussion and the nomination could take it on from there. That's one of the reasons you are thinking about becoming part of this. Tiffany, if you heard that, can you resummarize? We couldn't hear that very well. I was going to ask the same. It's very hard to hear you sing here. I'm not sure if you're far aware from the mic or not. So can you hear me now? Oh yeah, much better. Okay, sorry. So yeah, what I was saying was, so in the past, we've not had a workflow of governance to nominations. And one of the issues is that governance can provide feedback on the kinds of people we need on the board, the skill sets, their backgrounds, and, you know, the strengths they bring to the table to sustain the process of what the board is doing. And so that was one of the reasons why we thought there would be an overlap between governance and nomination. Does that make sense? And that was actually something that we were specifically asked, we were asked to do. And, you know, Holly requested that we spend some time thinking about that. I reached out to Drees, got some feedback from Drees, and we've formed a rough document at this point that has some of that thinking into it and also has some suggestions, some thinking around some people that might could possibly be considered, although nobody on the governance committee has reached out to any of these individuals at this point. Plus, there was a document that Holly started, I think in 2013 or 2014, where we indicated our strengths and so forth, and it had the board terms, and it also had a tab for suggested potential board members in the future. So all of this is sort of coming together in a way that I think is good. But I think that it makes sense for us to formalize some way to engage in a handoff from this work, from governance to nominating that is seamless as possible. And it would be somewhat good to have some overlap. And I think that with Addie throwing her hat in the ring and or Denise being involved in those conversations, that'll work fine. And then my feeling is that they should run with that ball and get us to a place where we've got a slate to vote on. Does that all make sense? That does make sense. I guess we need to, as you said, I think we need to get the right people on the nominating committee so that that committee is working well. Right. And it sounds like we have a couple of candidates. So I don't know how urgent this is. If we, maybe the next board meeting, we vote for these people to join the nominating committee? I think that's fine. My understanding is that it's taken two months in the past to go through conversations with potential candidates for the board and getting it to a place where we're ready to vote on a slate. And we've got roughly four months right now, a four-month window. So it's probably okay if we vote on the committee in the next board meeting. Right. Well, it sounds like Addie is a candidate and she just expressed that she would be happy to help. But Denise, we need to talk to her. She's not on the call. And I can reach out to Denise. That's not a problem. Right. If it's more urgent, we can always do a vote over email. Okay. Well, I think we've got a direction here and I can run with the ball. Go ahead. Just for the record, I'm putting in his apology because where it all is going to, she's actually scheduled to speak in half an hour. Oh, okay. Yeah. Okay. And then I guess as another question, is Samir, are you the chair of the nomination committee or do we need to identify a chair as well? He's currently the chair, but since he's up for nomination, I don't think he can be. So we'll need to replace him as chair, at least in time. Right. So in addition to, I guess in addition to bringing on new people, we also need to identify who wants to be the new chair. Is that part of the thinking? Yes. Sounds like it. Awesome. I think I've got enough to go on, to finish this work up. So unless there's any other comments or questions. I have one comment. I really like, it's resonating really well for me that our community elected, that our community elected positions are involved in the nominating process. That kind of, that just has a bell for me that I quite like. I just wanted to say that. So thanks Addy for stepping up and Massey. Thanks for all the work that you've been doing in this space. You're welcome. The only thing I'll add maybe is I know you guys emailed me asking for some some ideas of what I think would be good DNA, I guess for lack of a better word. To add to the board and I gave my feedback in doing so I try to represent others, including Holly, based on conversations that I've had with some of you. But I would definitely encourage the team to reach out directly to other people as well. Like I definitely don't want to be the only person giving feedback and input. Definitely. Thanks, Drew. Okay. Are there any other questions about that or any other things we would like to discuss from any of the committees? It doesn't look or sound like it. So I think we can move on to the next topic, which is the Drupalate Accelerate topic. Okay. Thank you. I don't have any slides for this because it's pretty straight forward, but I just want to make sure that we are on the same page. So to date, the D8 Accelerate campaign has raised about $222,000 of its $250,000 goal. So we're definitely in the home stretch. We're looking at the last 10% of the campaign that's come from over 400 donations of all sizes, which is pretty exciting. And just recently in the last week, the Indian community has been rallying around the campaign. They've donated about $2,500 from shops in India in the last week or so, which is pretty cool. And they're definitely the first sort of country I've seen come together like that and do an organized effort. So that's been great. So much more importantly, we've spent $127,000 of that money so far on 43 grants. And I think some really significant work has gotten done because of that. I lost track trying to count up the number of issues that have actually been addressed, but suffice it to say that it's a lot and really good work that's been getting done. So the plan from here on out is to let the committee continue to make grants. We're still open for community grants as well. And if we get to a release before we have spent all the funds, we will talk with the core maintainers at that point to talk about what's going to be significant for the release after that so that we can spend down the funds in the right way. So looking forward to crossing that bridge when we get there. But that's where we're at. So with the last bit of time to go, or the last bit of fundraising to go, if we are, I know folks have still been working on some larger donations from corporate entities that you are engaged with. It'd be awesome to have those lined up within the next couple of weeks. So we have a sense of how close we will be to the finish line by the time we get to Barcelona. If we are approaching Barcelona and we still have so many funds to round out the campaign, we'll be doing some work at Barcelona and on Drupal.org, et cetera, around the Barcelona timeframe to try to finish out the fund. So that's the plan right? Holly, I would love to see us push and just make that our deadline so we could plan a huge announcement there. It would be really cool. I think we can do it with 25K left. I think we can do it, but I don't know. I don't want to be in Barcelona trying to raise money still. Thoughts and opinions on this, Holly, that we can probably dig into a little bit this afternoon when we meet. But one idea in the crowdfunding level is perhaps we could do a relaunch for the finish. One of the things that we've lacked is a really solid end date, a gold date. I think that a little bit of a relaunch campaign around this is the deadline for doing this is something we should think about. I mean, we did set that as our deadline. And I think we've done, we said by September. I mean, I don't know, I guess to me that always meant before Barcelona, but we can't control, we can't control. I think we've all pushed pretty hard and we've done a really good job. I just really wanted to be able to announce at Barcelona that we had achieved this goal. I think it would give a much needed sense of just accomplishment to this effort. So this is Angie. A couple of things about that. One is that we might legitimately run into a problem where this would be a great problem to have. But let's just say we could run into a problem where Drupal 8 gets to zero release blockers before we run out of money because we've got about 100k left and we could possibly be as low as nine this week. So a nine release blockers. So one thing that might help with the last bit of a push is if the board had a plan for how we want to spend any overage money. So for example, I could very easily see us transitioning funds that we don't spend in the run-up to getting Drupal 8 launched, but instead repurposing the grant to now be about key contributed modules or something like that. If we had a really solid like if we raise too much money then we're going to spend it porting making sure media and panels and blah blah blah are ported. Then I think we not only save face in the event that the committee can't spend money fast enough to make a difference, but we also provide a really strong incentive for continuing to give because a lot of people might just look at that and see like well if you got a hundred thousand dollars left why do you in nine issues why do you need me to pay you anything? Yeah, I would agree, but I think the flip side that I think is really positive to this Angie is that our original goal was 125,000 dollars right. We kind of did a stretch to say let's make it a quarter of a mill and you guys have spent 127 so that was kind of right and I think that can be part of the story that's part of a relaunch to get to the end and having what we're going to spend the rest of the money on as part of that would work really well. Sorry Jeff. No, that's okay. I'm going back to look at and I certainly in the original documents you drafted I don't I'm not actually positive if we did say this but we were prepared for that contingency Angie and that we said we were supposed to say at least I think we did I'm just trying to find the place where you said it publicly. I think we were we were going to say you know essentially yeah if we go through this money we are going to keep rolling in terms of squashing bugs now that might not all be criticals per se but you know rest assured there'll be plenty of bug squashing and post you know post launch issue or post release issues that we could use this money for but we didn't I don't recall explicitly saying that we would then dip into contrib per se but I mean it seems like a pretty easy modification of the original policy to do that we never said we'd refund money let's put it that way. There's a number of things we do like we could save the money for future criticals because there's only maybe nine left but there's going to be many dozens of criticals including security bugs that will be identified over the next year right. We can also focus on majors right there's major bugs which are going to be they're not release blocking but they're still some of them are still painful so to speak we can we can look at those or per Angie's suggestion we can look at contributed modules so there is a number of different options and you know we can do combination of those options or any of these I think we should figure out who's going to be the right team that comes back with a proposal I think. Plus trace. So on the who from the is that something Holly you would like to own? Yeah let's just yeah I'd love to talk to you guys and just sort of figure out how you want to how you want to frame it and you know it's tough to put solid plans in place to your questions and concerns Donna and Jeff right now because we just don't know where we're going to be so we're trying to be flexible and know that we're going to we're going to try to own that space but we're not quite sure what the message is at this point right. Yeah I think I think I think that's that yeah another way to look at is at Angie's point is just you know we want to raise the last 25,000 we ought to do it fast anyway I mean regardless because I would just take it as a challenge to go ahead and get it done and then and then that's not even an issue because I would agree like I think if we're you know we're sitting at 230,000 dollars and then we announced that we've reached you know in our release candidate then yeah people are like yeah why should I be the guy why should I be the guy that throws the last dollar in the pile you know what I mean it does start to eat away at our incentives so I think you know doing a final push before Barcelona both for morale purposes for practical purposes of actually getting the money before you know there's this incentive to have it and also just you know not having to even spend our time worried about what we would do if we if we raised it all after you know if we if we didn't need it anymore it'd be just great if we just knock it out but pays yours have been done I don't know yeah I'm gonna say that without um some additional uh you know higher dollar donations from uh you know some from from some of the more board driven donations you know I I don't think we're gonna get all the way to that last $27,000 um but it also sounds like you know we're gonna get to a place where we have a release candidate um and you know I also feel like it's fine to declare victory somewhat shy of $250,000 we got to the release candidate with that money right so but let me let me uh I'll I will try to set up some time to chat more with like maybe Angie you and catch about what direction we want to go to we want to go forward with can you guys still hear me got weirdly silent gonna say no probably move on to the next one yeah okay just trying to keep us on time on track here I don't know if she's back yeah I know that's fine I just want to make sure someone could hear me oh there's Holly Holly's talking to somebody else that was weird the mic the mic totally dropped out I heard Dree start talking and I thought it was because he heard me but he didn't no I was I was just saying that we lost you and then when you come back we should move on to the next topic to to keep ourselves on track here because we're uh we're running a little bit behind sounds good because we started late so sounds good and I'll uh I'll reach out to Angie um and probably catch to try to have that conversation about the direction okay sounds good let's move on to the strategic frame then yep so I just want to give you guys an an update uh we have been working on this internally um the association had a number of goals that they've been that we've been working under for the last few years and we've been working on refining that um started in January with the board retreat uh and have been working um with the staff for the last uh bit of time to update this um and for some staff this will be um the first view of it arranged like this uh but we'll be talking about it in great detail great detail at our staff meeting our all-hand staff meeting next week so um just to remind folks our strategic frame starts with our vision and mission and hopefully got those those have not changed um and part of what's driving us uh overall is an overall org strategy here of building our authority as the as the voice of Drupal in the community um so uh you know we are we want to do that in a very collaborative way obviously it's our voice all together um but we're still working on really where is the association's role in a lot of places and figuring out what that authority is not authority over people but authority with people that's going to be really key to any of our success um in the future so as we have been um as we've been thinking about what is it overall that the organization is trying to do you know our our real strategy is figuring out um is trying to do everything in a way that helps us helps cement our role in in the community um we have a number of tools that we can use in deploying our strategy um that give us sort of an unfair advantage over other players in the space one of those really important ones is the fame wand we can draw attention to people because we have lots of channels to do that and really celebrate the community um we have Drupal.org and that's something that we help manage with the community um and because of that position it's something that we can use to highlight things um highlight various initiatives uh etc that need attention um the trademark while still owned by Dries is something that you know we get to use in a privileged way um so that's that's something that's useful for us as an organization and the fact that we are vendor agnostic gives us a position in the community that allows us to do some things that are unique and useful uh for the project as well so these are things that we think about in executing um in executing our strategic frame and I think we do have a couple of constraints in terms of what we're able to say that we're going to achieve over the next 12 to 18 months so I just want to put those on the table obviously we don't have cash reserves right now to invest in new programs or services so anything that we do has to be able to pay for itself really immediately um and it's also clear to us that our the structure the way that we're organized the work that you know really is been designed to support the work that we do and so if we decide that we're going to do radically different work it's just going to it would take time to shift that right so I just want to be clear that we um you know we were an organization that worked on Drupal cons and then and then an organization that does Drupal cons and supports Drupal.org and if we make changes that are you know affect that it takes time to execute so with that in mind what's in our strategic frame just to remind you um the strategic frame is about getting where we want to go but how do we achieve our mission um or how to get to Cleveland I'm going to go fast over this because you guys have seen this a lot um the board part of this is really focused on the mission and the goals um and the staff are really focused on the tactics and the objectives and we overlap in a strategy area we talk about that a lot together. You guys helped us identify in January uh our three to five year goals so developing sufficient professionals leading the community in development of Drupal ensuring the sustainability of the project and the community and increasing Drupal adoption along with increasing the strength and resiliency of the association itself. So what has ended up being in our plan so developing sufficient professionals to meet global demand for Drupal we've uh recognizing our constraints again there were lots of things we could do um but what we have on the docker right now is a single strategy of educating and training individuals and we have two objectives for the next 12 to 18 months the first is around defining an engagement plan specifically for Drupal.org to map what it means to go from learner to skilled so creating creating those skilled developers and then we will be focusing on Drupal cons and other programs that can help create actual training opportunities for individuals and our first objective here is just to understand like how many training opportunities we can create um and we'll get into uh sort of the qualitative nature what is the you know are we actually moving people from one one you know from learner to skilled um and subsequently. So again that's for the short term uh that 12 to 18 month period um as we're able to add resources uh to the to this objective our future strategies will be building and directing the network partnering with tech training programs so things like um I forgot here in Portland what they're called already but training programs who are creating Drupal developers universities right and recruiting people into the Drupal network directly those are all strategies that we could entertain at some point in the future once we move on from those two objectives and we're able to get them out the door we will uh add that strategy of building and directing the network um and then work on getting working with the training opportunities that already exist in the ecosystem um helping to make them more visible and get people engaged in in those um and that will let us um sorry have anything went ahead that will let us then um get to a place where we can start to measure that qualitative output how many skilled developers are we actually creating our second goal is leading the community and focused efficient effective development of Drupal we have three strategies we're using right now establish model and maintain positive community values partner with product teams coordinate communicate the priorities and incentivize development uh the first one should be pretty self-explanatory that's we're going to do our work in a way that reflects community values um the positive community values we have out there the second partner with product team to coordinate and communicate priorities the product team here is the Drupal product team so probably the core maintainers is what we're talking about um and I want to emphasize that this is something kind of new um the association hasn't had a clear and real relationship with the um core maintainers in the past nothing formal um but if we are going to help uh lead the you know efficient and effective development of Drupal we have to know what it is that is coming up what's going to be important to to Drupal development um and that's going to allow us to understand what it is that we should be highlighting and directing the network to go do so uh that's that's a really important strategy I think uh for this goal and some and some others um and then incentivizing development itself like how do we use Drupal dot org and the other fame wand you know our other assets to help um create a reason for people to to get engaged in the development of Drupal so our first step is going to figure out what it is we want from orgs to you know what we want those orgs to do and that does require conversation with those core maintainers that you know various points of the release cycle what it is what is it that we need uh companies to provide um you know do we need them to give us a developer for a day a week or a developer full time for three months or is it you know uh is there are there specific contrib pieces that have to be focused on those are the kinds of questions that we need to understand um for the various stages of product release uh cycles product development cycles um and then once we know what that is um we can create the list of incentives to implement in the future we'd like to have a strategy added in there around market research so that we can actually talk to Drupal customers and understand the demand and opportunities for Drupal um that will be useful to share with the folks who are actually working on the product and making sure that you know they're developing things that people actually want um and once we complete that initial set of objectives um we will also be working on uh getting the Drupal.org roadmap initiatives um project managed through the new initiative framework as part of the content um strategy that gets implemented on Drupal.org and we'll be looking to um we'll be looking at the issues for core uh understanding how long on average it takes to close an issue in core um and working with the community to find ways that help us resolve issues faster because I think um one thing we hear again and again is that most of time people don't at a certain point people don't care if the answer is yes let's do it or no let's not it's the part where you put an issue out there and it sits for ever and ever and ever uh and no decision is made that's the part that's painful right so let's do looking to resolve issues uh on ensuring the sustainability of the Drupal projects we are looking to provide capacity support um board at one point this said capacity and funding support but we're not sure that's the right strategy going forward we need to have more conversations about that but we definitely want to provide capacity sort uh support organizing that capacity of the community to align with project priorities um this again is this is tied to working with those core maintainers and understanding what's really important for the project right now um and then incentivizing development is also a key strategy here so uh this is a little less intense we don't have to quite understand what the entire like product development cycle looks like and what's needed when but we do want to open up that relationship of core maintainers and understand in the next three months these are the kinds of skill sets that are going to be really important because we're going to be addressing these kinds of issues and how do we use um Drupal.org the newsletters um you know social media et cetera to really highlight what that is and drive people to those very specific focused things um uh and those can be core things but those can also be contrib or other areas of the site right um and then get those things up and highlighted on Drupal.org um and then the last um the last objective here is getting Drupal.org profiles uh to earn the community role um that just shows a minimum level of engagement and if we're constantly growing the number of people who have the community role um we are that's the pipeline right for that engaged community member who's going to go on to become at some point uh you know a skilled or expert developer who's contributing back to the project um so that's about growing that funnel of folks who can continue to work on the project. One other strategy that we want to employ in the future but don't really have capacity for right now sharing the tribal knowledge of our key leaders so this is um really making sure that camp leaders are talking to camp leaders um that folks who are working on you know various initiatives within the project you know are connected to other people doing similar work uh future objectives um creating training opportunities for community leaders um actually after I talked to Donna and they might be able to move that into the current plan um we also we talked about this in Los Angeles helping to helping core maintenance recruit new developers for key topic areas um and also the same thing for camps and there's some discussion about whether or not that was really needed so we're going to go back and do some research with the community about how much that's actually needed um like that that bench building for the project how useful that will actually be. Uh we had a goal about increasing a Drupal adoption in target markets um you said define target market um and for the moment we're going to go ahead and say that we're going to focus on enterprise customers but we're not going to try to use tactics that align with um the the business community that's already focused on this this customer base so um you know the the enterprise is you know those are the customers that have you know been identified as the thing that's really key to the success of the project so we felt like that's the best place we can spend our time right now um we have a few different strategies here um curating and disseminating vendor agnostic information we'll get in alliance with one of our key differentiators um working with Drupal shops to get them to build the conditions for more Drupal adoption and then partnering with ISVs to increase the product value proposition so you know you are a company that works with specific kinds of marketing software for example you know knowing that you can um use Drupal with that software helps make that more valuable to you so a few of the things that we're working on here from an objective point of view um getting the wide Drupal section up on the site um that's focused on evaluators and specifically enterprise evaluators um we will um be creating Drupal marketing materials uh you know obviously aligned especially with the with the with the DA release um we will have worked with 12 ISVs and our partner connect program to engage them in the community and make sure that their integrations and you know integrations are solid and and doing good stuff um and we will be looking into this year um the possibility of doing a co-funded market research study for for Drupal uh as well that's something that would help both in the enterprise um and it would help in the efficient development of Drupal so we think that's a good thing to pursue if we can if we can fund that uh future strategies um working with strategic agencies um to get them to adopt Drupal um and then conducting market research uh to understand the demand and opportunities for Drupal so we're gonna we have an objective here that will help us understand if that's a strategy we can employ uh and future objectives um you know building a list of agencies to target and then uh another key piece here is defining personas for those CMS evaluators and decision makers so that we can uh further hone in the materials that we're preparing and last bit is focused on the association in particular um and and our health overall so uh our strategies right now are really just trying to use our current staff and resources to the best of our abilities uh we're focused on improving process and finding efficiencies where we can um and we're using systems and software um and you know in a cost effective way for us um our two main objectives right now are finding the future the long term sustainable funding model for the association like where is our growth um we know that the the board um and lots of community members will like to see a step into more roles um we can't do that unless we grow um and then we also have a goal of restoring the operating reserve to a monthly minimum of $200,000 and then in the future you know we'll be setting objectives to grow that so the imperative for us in this plan is the strength and resilience section that's what we've got to be focused on in the short term um while we um you know go through this next 12 to 18 months that's what we're all going to be focused on here um and that won't come at the expense of doing other work um and as a mission-based organization we're always going to try to make sure that our financial health is you know aligned with our mission uh for sure but this is definitely what we're going to need to focus so the next steps for us right now is just to present this with the all staff meeting next week um the objectives area um is the launching pad for the staff to go back and look at the work that they're doing um in the next 12 to 18 months and figure out how it aligns with those objectives so where does the Drupal Con team see their role in helping to um align community resources around the uh the the work that needs to get done in Drupal right now right um because there's lots of opportunities to do that uh we're putting on a Drupal Con anyway so we might as well do it with some purpose right uh so so that's the kind of thing that they're going to be doing uh starting next week um and then they will set goals that feed into those objectives um and those will form their their team dashboards um so that's what'll happen uh next um then we get to measure stuff so we're going to update the org dashboard uh set the objectives as the kpis and for some of these objectives uh like there's still blank spots there because it's something we've never measured before and one of the things that's been really is like tough emotionally is to set a goal for something we've never measured before uh only to realize that that was a crazy goal so um we might spend some time just sort of understanding what the baseline is and you'll get you know we will report what the numbers are but we won't say it's like you know it's 20% of goal or anything like that uh for some time um we'll be doing some baseline setting but the the kpis um are going to be those objectives from the strategic plan and then the team goals that feed into those will also be on our dashboard so you'll be able to see sort of what's driving those kpis and that's going to be the thing that lets us also understand that tactic's working but that tactic is not right so we'll update the org dashboard and the packet as well for the board so it'll be oriented around the strategic frame uh going forward and i'll be bringing you guys a draft of that and i'd like to see us be able to shift over after the september board meeting into a new format and that'll mean no more operational updates we're just going to be focused on those strategic objectives and the work that we're doing that supports those so i'm going to stop there those are all my words great awesome thanks holly um so i think um what i what you know i think what is best is that we maybe don't discuss this here in case there is discussion but that we do allow people to ask some questions if there's questions uh clarifying question that holly can clarify uh if you have concerns about this or ideas on how we can tweak it improve it maybe that we should table and either we can talk about it in the next session the executive session or we can find some time separately to do it but i do want to make sure people can ask questions to help them get things clarified that sounds good so is there any any questions what's our operating reserve monthly minimum right now what are we what are we sitting at i cannot answer that question okay matt's on the call but um i'm matt's on the call but i do not know at the top of my head maybe matt will message me something magical not enough yeah i'm just interested in in how far we have to have to pull that ball down the down the field gotcha well we do have um so you know our general policy around financials is to review those in executive session and once they've been approved to um publish those out to the public and we do have that on the executive session um docket so we'll be able to see those for sure i'll shut up then any other questions other questions um okay is there is there any other questions about the meeting in general versus the specifics okay anything anything you want to share or say if not i think we move to executive session you can come back to this topic um if you'd like um if not i suggest we do the normal uh the normal agenda for for the executive session thanks all right see you guys there thanks all right actually was not here