 Let's get this going. I think we roll call already. While I was fiddling with my audio, but do we need to do a quick roll call or do we have the list of people? You got it Donna? I'm just going to put it in now. Okay. I can see Vessa. Give me a chat if you need names. Trace. Tiffany. Morton. Do we have, do we put our guests like Kieran's in there somewhere? Yes. So we usually, I think Angie usually breaks out board members from other attendees. And so Kieran's out there and then Rudy and Tatiana from the DA staff are also online. Oh, and Megan can't forget her. Hey Megan. Hey Tatiana. Hey Rudy. They're all muted. Put you in. You're keeping them well muted. We can't hear them scream. All right. Trace, Tiffany Morton. Who else? I'm me. Oh yeah. I'm here. Yeah. Missing right now is Angie. She won't make it at all. And Jeff is missing, but he would join us later probably in about 10 minutes. Okay. And then Samir is Samir here. I think Samir has a family issue. It's only about yesterday. Okay. So he's an apology. Yep. And, um, Matthew is probably an apology may hop on a little late and. I don't know. All right. Well, maybe she'll join us. All right. So I think we approved minutes of the last meeting. By email. And so many from. Yes, it's confirmed. They're all approved. Awesome. All right. Well, so, you know, this meeting, um, we'll start with an operational updates provided by Holly. And then we have updates from the different software working groups. And then, uh, we're going to brainstorm a little bit about the community election process. And there's two proposed changes that we would like to vote on. Um, we'll see a ghost. And then Holly has an update from the retreat with some action items. That we agreed upon. And then hopefully by then Jeff. And we'll ask to give an update on the CTO hiring process. So, um, I'm going to start Holly sounds good. Yep. So thanks everyone, um, for, For being here for listening in and participating. So, um, a few things from the trenches here, uh, down staff level. Um, the first bit of exciting news that we moved. And so we have a space where we don't pull up into each other. Um, but we're really excited just to, yeah, we're just really excited to be in a space that's our own and is not, um, um, and the bring you to triangle of Portland. Um, where you can actually go outside and get a cup of coffee or get something to eat, which is great. Um, but on top of the move, we got a lot of other good stuff done too. Um, and you know, February is usually, um, you know, we're pretty focused on getting geared up for Drupal cons. Um, and that's where most of the energy was, uh, for sure. But we also had a global training days, the first one of 2014. And, uh, our new staff member Lauren Shay did a really fantastic job of just, you know, really doing some good solid communications. Um, and actually, uh, was managed in this first day to, um, recruit more organizations to participate than we had, uh, budgeted or planned for for the whole year. So, uh, way to meet your annual goal in one go. That's some good work. Uh, yeah. Um, and then, uh, of course we've got, uh, uh, just want to put the reminder out there about the dashboard again that, um, we are continuing to work on that dashboard. So, uh, numbers are all updated for February. Um, and we actually have a, one of our planning Friday sessions in two weeks is going to be focused on, um, getting the metrics in the dashboard, um, aligning those with, um, you know, the actual cycles a little bit better so that when we see red, green, and yellow, it's, um, it's actually, I mean, a little more meaningful than it has been for the last couple of months. So that, that update will be coming to that. But right now, still those colors are a little bit misleading sometimes. So, um, yeah. So everyone was really busy over here doing lots of stuff. Um, and we continue to just really focus on making sure that we, um, hire quickly around here. So that, um, particularly on the tech team side, that's where a bunch of our focus is this year. Um, and want to bring people on so that we have the resources to take on all the projects that we have specced out for the year. Um, so continuing to really focus on hiring, um, some things we've done there. So we have, uh, in our project managing management space, um, we have a section related to hiring. So we built some systems in so that, you know, you have a job post is going to ask you all the right questions that you have to think about, uh, and then accuse a bunch of tasks to get it posted in the right place, et cetera. Um, we're documenting, you know, how all our tools work, how to write a job description, all that kind of stuff. So getting some good groundwork in place. Um, for that, um, as well as, you know, really just trying to, um, work with staff one-on-one and make sure they're able to get those hires done. Um, on the governance side, um, you know, that still continues to be a thing that can hold us back if we can't get the, um, if the governance groups aren't able to work well together and work quickly together. Um, and I think there's been actually a lot of progress in the last couple of months, just in terms of things like the software working group being able to being able to say, yes, do that project and hand it over to the staff and then the staff, you know, finding the contractor and pushing the, you know, pushing the ball forward or taking on the work and pushing the ball forward, uh, or, you know, working with volunteers to push the ball forward. So I feel like we're starting to make some progress in that arena, which is great. Um, we have a CTO hire, which should help, you know, continue the momentum because well, someone who's really focused on that in a, in a unique way. Um, and, um, we will have a couple of candidates for you guys to consider probably before the next board meeting via email, um, for the software working group so that we don't lose steam on that. Um, but I think the real big, uh, issue for us overall that we're trying to get a handle on is Drupal.org performance. So we have a number of goals for the year that we're definitely behind on. And, um, we have to continue to focus on that area. Um, so folks are doing a lot of good work. I think Rudy in particular, it's been, it's been a while God's done to have him on staff full time and, and focused on, um, site performance. So things are definitely happening there. Uh, the, we've got, um, we're working with a CDN to get that set up or testing it on, um, association or roll it over to, to the larger site. Um, that should help us improve page load speed, especially internationally. Um, the numbers go up pretty dramatically when you get outside of the US. So that'll help a lot. Um, and then, um, one other thing is that, um, we had on the books this year a part-time customer service hire for Drupal.org, someone to work in the queues and deal with the, mostly the non-technical things that come up in the queues, like help me reset my password kind of stuff. Uh, but also to, um, uh, act as a, um, a good, like a conduit between, you know, a person who has an issue and the tech team, uh, or, you know, or the working group that needs to address the issue. And, um, Liz Trudeau has been on staff for a while. Um, and she has, uh, in the last year, I've been working part-time and she comes back from having a kid of her own. Um, is ready to come back full time. Um, she really knows the community well because of her work in membership. And she really gets the queues as well. So she's been, um, starting to take on that work for us. And that should really also help free up. Infinite echo. There we go. That should also really help free up space for, um, you know, Tatiana and Drum to be focused in the right places as well. So we're doing our best. Like we keep working on Drupal.org performance. I think we're making steady progress. And if you look at the numbers month over month, they reflect that too. They are improving. Um, but we're still in the red for a lot of Drupal.org numbers. So we got a ways to go for sure. So those are, those are the big highlights. Um, I think if you look at the, the numbers themselves, um, you know, lots of things look really on track, especially in our main KPIs. Um, budget is looking, you know, good. Uh, the revenue is looking really strong. Um, we are meeting most of our community metrics. Uh, you know, membership revenues on track, um, all that good stuff. Um, we actually, um, we, um, we have, um, sorry. Refocused. Um, we have, uh, lots of people applying for scholarships and all that good stuff. Um, and so those overall KPIs look really, you know, the things that we can really control look really good. Um, the one red number in there is program participants. And again, that's really because, um, the numbers don't, the, the sort of year to date actuals we're measuring against here is just the annual goal divided by 12, but that's not how program works. Right. So that's the kind of thing we're going to fix to Fridays from now, um, and have updated in time for the branch dashboard. So, so KPIs look good. Um, the cons, um, I, I do want to highlight two things in the cons. Um, not because I want to be alarmist or that because we actually have a problem, but because we want to paint the potential. We want to paint the potential problem for you. Um, so that you're aware of it. And you know that we're thinking about it and we're trying to manage around it. Um, so with the triple cons, um, things look to be, you know, on track, um, site submissions or slides, um, session selections, training submissions, all that good stuff closed on Friday and we had really good strong numbers on par, um, with Portland, which was, you know, record breaking for us. Um, so lots of good community involvement in the cons. Um, and, you know, we're about to go ahead and make those session, um, selections and get the announcement out there about what's going to be on the agenda. So, uh, we also have a keynote secured, which for some reason Stephanie Alhage made a mystery to me. I'm still trying to warm it out of her. Um, I think because the things aren't final final, but we have a yes from someone that she's really excited about. Um, and, um, and so things look really good. Um, I do want to talk about some of the things that we are trying to make sure that we have a backup plan for. So a couple of things. Um, one, um, the sponsorship sales goal is 800 K. Um, we are, I think Megan said, I want to say we're like right at 695 right now. Uh, and we are, um, you know, really working to get to that 800 K goal. It seems, it seems really possible and absolutely within our reach. Um, and I know the sales team has been really refocused in the last week on this goal. Um, so they're all working towards it really hard. Um, and Megan's done a fantastic job of making sure that, you know, the sales people are, are, um, focused in the right place. Um, you know, there's some possibility that they don't quite make the goal. Um, and then right now, um, with registrations, we're, we're definitely a little bit behind where we want to be to hit 4,000, uh, according to our best calculations, right? So we take previous con registration data, look at that as a pattern, and I predict where we would need to be today to hit that 4,000 goal based on past performance. Um, and based on those Portland numbers we're behind by a bit to hit 4,000. Uh, and if we kept on this track, we would end up with numbers that are very Portland like right around 3,500. Um, so we just wanted to show you that, you know, if we, if, if sponsorship revenue fell short and if we came short, 500 guests, uh, the net loss would be about 24 K, uh, the net change I should say should be about 24 K. The con would definitely still be profitable, but it'd be about 24 K off, um, the budget for the year. Uh, so worst case scenario, we're still not, you know, even remotely. Um, we're not worrying about it, but we're planning for it. Let me put it that way. Any questions about that? Cause I know that's a big, big topic for everyone. I would just like to say, I think that, that about, um, people signing up for the last six or eight years, um, nothing happened before we had the sessions and nobody really pays. It gets tickets before that. So I don't think that it should even be on the guys right now before we got, uh, when we are out of sessions and we're out of the, um, early bird, I think then there might kind of be, then we can begin to look at the numbers up until then it's, it's just so whoever is really quick or those who have like, your head budgets, they'll pay buying tickets. I personally wouldn't even think about buying a ticket before, you know, after sessions and accidents and so forth. And I know that's not far as a number, but that just the usual thing you have seen over the years. So I wouldn't worry about that. That's right. So, um, in between like announcing the, um, sessions and the early bird deadline of April seven, that's our, that's our key week, right? That's where we need everything to go the way we want it to go. Uh, and after that, then we can really start to worry, but we just wanted to put the numbers on the table now so that we, we know what we might have to track against. Cause it's always good to know what your plan is before you need it. What's the date that we're, uh, that we're, um, um, announcing sessions again. I know I should know this, but it's not at my, my fingers. Um, I'm going to say number and someone's going to yell at me. Um, I, I want to say it's the 21st. Yeah. It's basically two weeks from now, 28th, maybe. Let me just see if I can get. March. Yeah. So the week of Monday, the 24th, that's, that's the week that you're going to see those hit. All right. And of course, and how many, oh, sorry. Go ahead. How many, how many, how many people have, uh, have, uh, submitted, uh, submission, submitted session proposals and, uh, um, how many people it just finally, um, came up after 20 minutes of trying to download that. How bad my internet connection is right now. So, so, um, uh, how many people, how many actual people, um, um, submitted sessions and how many of those are going to be accepted. So, um, the, uh, the exact number I'm not going to remember. Stephanie told us the other day and I, I cannot remember it's, uh, but essentially it's a ratio of like five to six to one in terms of like what gets accepted versus doesn't. So we say a great many, you know, because we end up with around a hundred sessions. So we probably have somewhere in the neighborhood of 600, 600 submissions. Something like that. Yeah. Okay. Well, buddy. And I was just saying that I remember the numbers from the top of my head. It's usually between four to six hundred sessions for the American contents about three to four hundred for the European contents. Yep. I want to say it was five, 81. That's the number that's coming into my head, but that could totally be a lie. Oh, uh, and I can see an IOC that that step is giving us five. Oh, good. And 130 sessions, give or take the last and 582 total seven. 584 submissions. I was so close. I was only three off. So that's like, that's like, uh, 450 people that we know are really interested in the con who aren't aren't going to do anything. And they may not even do early birds, but they're not going to do anything certainly before, before, before. Sessions are announced. Yeah. Yeah. So that kind of tightens up those numbers a little bit for you. For sure. We also have, you know, the hotel block is doing really well. And so we have like way more people who have registered for hotel rooms or reserved hotel rooms than have registered for the conference right now. So that's just another indicator that there's more stuff coming. Yeah. So, yeah, no, that's not like, a lot of people try to get their, like, they want to reserve a hotel room and then they go through the process of like trying to get the travel approved and all that good stuff before they can register. So. I agree with Morton. We shouldn't panic. Right. Maybe they're thinking like South by the hotel room, like you really have no choice. That's right, Denise. That's the first thing. Yeah. Yeah. So there's definitely no panic over here. And I, but I'm just, you know, like we're, we're really working hard to move towards, you know, being data driven and knowing where we're at, you know, and I just want to share these things with you. Yep. That's great. Okay. Anything else on that? Okay. So, Austin, Amsterdam, you know, we're, we're working on and that site is scheduled to go up in the next few weeks as well. So that'll be a very early launch. And I just want to say congratulations to the, the Stephanie is because they've really, you know, pushed this stuff forward in a very productive way and that's been much appreciated. So on the triple dot org side, again, like I said, there's lots of red when we look at these numbers. Part of that is, I don't think we always had the best numbers to go on when we were looking at what to model from. So that's something. But other things like actually just clearly need to get fixed and it's going to take some time. So for example the page response time but like I said, Rudy's really working on a plan there. It's going to be in December and January numbers for that they were pretty outrageous and now we're actually, you know, within a second of goal, which is, I know a second is a huge time, a huge amount of time in, in the standard of the web but is much better than where we were at. And then Jeremy has done a ton of work on test spots in the last couple of months. And so it's still above goal but I think if you recall from the last board packet this number was like 147 minutes of test. We're going to have to do some improvements there so hopefully we'll continue to see this come down. And we as staff continue to be really committed to trying to figure out how to help Jeremy. You know, this seems like a really, I know this is a really critical issue, especially for the core maintainers and so we feel extremely committed to, to figuring out how to solve this problem as quickly as possible. So there's that. And then one just big bright spot in the Drupal.org numbers the landing page traffic for Drupal eight continues to be incredibly strong. So, yeah, I mean it's still you know compared to overall Drupal.org numbers it's it's it's small but that that page is getting some significant traffic and so there's definitely interest out there you guys. Definitely interest. So, so on that side just a couple of quick things that the software working group helped spin up and we are working on. They got a developer tools team going which is really great. And we've got a few projects going because of that so we are working on. So we deployed the UX improvements to the issue page. We are working on version control to get ready for Drupal eight release and Marco right now is working on back linking commit messages those another thing it was really asked for. We have all of that work going on, as well as we just started working with Christopher Jervais and he's going to be doing leading discovery for that semantic versioning project so we've got a couple of folks that we're working without the community on a contractor basis there, which is great. And I think, you know Rudy said a lot of words about infrastructure. But yeah we've been replacing a lot of old equipment, still working on the open stack setup made some big strides in the last week in particular so think we're going to get really close to being able to help help volunteer spin up development environments. And that's it that's a huge part of that again that to prong strategy for getting improvements made this year. So you know moving faster and having budget and staff and contractors but also really empowering volunteers. And then global training days again I already told you it's been a really big amazing success. We had 34 training companies participate in the, in the first training day we have 41 companies over the entire year last year so it's a really good improvement by putting some focus on this. And we really hope this will turn into a really strong recruiting tool for the Drupal community. So we'll be getting some more summary up about that but we're really excited to see this, you know happen a little bit, a little bit bigger and a little bit more for the community so. I think the only other big highlight I want to make this year is just this time around is around revenue. So I think we've discussed in the revenue committee and maybe in the last. We've definitely discussed in the revenue committee that the ISP program that we've been working on is definitely sluggish. And so we're looking for ways to get around that whether we're sort of changing up our product mix so we can still hit revenue goals overall and focus on ISP as sort of like let's focus on lead gen instead of sales this year. But we're, we're working on on figuring that out that piece out. So otherwise, things, which is good. I think those are the big things of there are a lot more words in the update. Anyone see anything they want to ask about awesome. If not, I think we should move on to the. This is Karen, I just want to say I wish all my meetings were just well prepared. Thanks Karen. There's a comment in there, but you don't have to address it right now. Address it later. Okay. I'll reply to the comment. All right. Well, so let's get the updates from the different working groups then. I'm going to start with the software working group. Which I think that update is going to come from Tatiana. So right. Yeah, Tatiana and muted you see you should be good to go. Okay. Thanks. Hi everyone. So the political software working group. We are currently for people in the working group, which are Angie Melissa Neil and I, because Kim sadly decided to step down a few weeks ago and we're still working on getting new member on board. We're hoping to be done with this soon enough. So our annual plan. Next slide includes the following initiatives. First of all, appointing Drupal.org leadership teams responsible for different subsections on the website. Secondly, developing a vision high level vision for the site which will help us make software and future decisions. Development future plan for the developer and support tools together with the teams, which we are point for specific sections. Next one is vision and communication around community driven Drupal improvements, which is related to the work infrastructure teams doing on like better development environments and better process for developing for Drupal.org in general. And lastly, our last big initiative is bigger Drupal.org ideation process, which will be a basis for planning for 2015 and hopefully even 16. So what we did, what did we do last quarter. First of all, we appointed developer tools team and the team already started working and regular public meetings and seems to be doing pretty good. We also basically appointed community tools team. Public announcement should go out in the next few days. We are just finalizing the list of people. We also started to work on appointing communication tools team, which is currently under discussion with the content working group. And we also started working on appointing translation tools team, which will be all about a localized Drupal.org website. Current project status. So out of five section specific teams, we already appointed two. Two are still in progress and we haven't started on one yet, which is documentation tools team. And here we are just waiting for documentation working group to be officially appointed so we could coordinate with them on the team. Developer tools team started working on gap analysis for the current tools. This will be basis for future planning. The rest of the projects we had in our annual plan are scheduled to start later in the year. So we haven't started on them yet. We also have some projects which we authorized as a working group, but we are not actually working on them. First of all, developer tools team leads the work on the three quick win Drupal.org features which we identified last year during the ideation process. And to help with that, we hired, well, we as a Drupal association hired Marko Vilikas to implement one of them. The clinking can be some issues and that project is pretty close to be finished. Additionally, we approved a budget for discovery process, as Holly mentioned for supporting Drupal course semantic version of Drupal.org, and we already have. Hello. Okay, yeah, that was weird. Tatiana. Yeah, are you still there? I think those are Tatiana and I'll think. Okay. Just checking on Tatiana. She went offline it says. All right, we'll see if we get her back. There's only three more slides. I could probably say all the words. Do you guys want me to push forward while Tatiana tries to reconnect? Hello. Yeah, it's probably better to just skip ahead right in the meantime or I don't know. Yeah, let's not waste time. Okay. So do you want me to get do I'm going to walk you through the last three slides and then we can move on. Yeah, I think that would be fine. Yeah, great. So yeah, so as Tatiana was saying Christopher base working on course manic versioning and then the infrastructure work is leading this but it's obviously been in close collaboration with the software working group but the infrastructure work group has been leading primarily through ready to work on creating the full, full development and staging environments so working on that. So a couple of challenges to the work right now on. Obviously we need to appoint an additional member to the working group get that up to full speed. And we are always obviously, you know, limited by the amount of time that this volunteer group can can spend talking about issues, and you can unmute Tatiana. See if she's back. Thanks. Awesome. Yeah, carry on. So I have no idea why maybe if I decide to go down right in the middle. It's not like there's a revolution in your country or anything. So it's cool. Right. Yep. So, current challenges for our working group. I assume is for most of the working groups. First of all, is limited availability of members. If we just had some time could get so much more done. Secondly, we do have a lot of quiet time consuming tasks, which in the group needs to deal with at least for now until we appoint all the teams and have all the processes going. Also quite a big challenge is a lack of volunteers with knowledge and desire to be members of leadership teams which are pointing. So these results in a working group members taking some of the roles on and in ideal world, this would not be happening, but that's just what we have to do right now. And also, last challenges, changes in working group membership so we have to spend some time on boarding members and getting them up to speed and such. So what we need to be efficient were obviously more volunteers for the group of leadership teams, and we also need to hand more tactical tasks to the group association stuff to keep working group on a strategic level. And we did some steps in this direction, but we can probably do more of that. So here are plans for the next quarter. The following. First of all, we will finish appointing all the group of leadership teams. We will work with the group association CTO on the vision where the group of leadership is going. We will work on future plans for the development support tools based on the analysis performed by the teams. And lastly, maybe the most important we will prepare for the big community ideation process to plan for next year or two. Thanks. Questions for or about. I do actually. I was wondering if this has been put on the table for the governance committee to relook at software working groups charter once the CTO has been hired. Is that something we can do at the Portland retreat perhaps to make sure it's still relevant? Yeah, we haven't been in the church doing that, but I think that's a great idea and I would love to help. Yeah, I think we need to look at probably all three charters, but in particular software working group seems to me to be one that needs to be looked at in the lens of having a CTO. Yeah, I'd love to do that. The initial thinking was to obviously appoint the CTO as a member of the group, but more may be required. Yeah, the idea was for the CTO to actually be the chair of the group. Right. I agree. There's a lot of it's worth a discussion at least and maybe changes as well. Especially like what's, you know, maybe now have additional leadership teams within the software working group like developer tools leadership team. It sounded like in a community tools leadership team and a communication tools leadership team and a translation tools leadership team. So there's at least four other leadership teams. And now we'd be good to revisit that or to think about that in the context of the CTO and also like does that set us up to make decisions fast enough and all that stuff. I noted that for the retreat agenda. Great. And I'll reach out to the rest of the the governance committee and we set up a time for us to look through these things together. Awesome. Alrighty, no more questions. I thank you to Jenna. The next group that's on the list is the content working group but you know the chair is George. I don't know if George is on the call. Hi, I'm here. Can you hear me? Awesome. Yeah, we can. Are you going to walk us through George? So, yes, but I will need someone to advance the slides for me. I volunteer for that job. I'll give it to Holly. Thank you. Awesome. Thank you. I think it's Holly. Okay. Great. So, hi there. Welcome once again to Drupal.org content working group. Next slide. Just a reminder of who we are. Megan Tatiana, Jeff Hayden, Royce Colton and myself. Next slide. And, you know, again, this is recap. The major initiatives we're working on this year are doing all the foundational work that's necessary to conduct a full redesign in 2015. And what that includes is starting with user research and persona development so that we have a better understanding of who our existing audiences are, who our target audiences are, what motivates them so that we can serve them better. We know how to serve them better. Followed by audit and assessment of Drupal.org content combined with the development of a comprehensive and long-term content strategy for Drupal.org and the development of better metrics and reporting for progress and success. We have a lot of data right now about Drupal.org. What we would like to do is turn that into more actionable information. In addition to that, we have a number of ongoing duties and responsibilities assisting staff with landing pages, marketing initiatives, developing various policies and, you know, other triages as necessary. Next slide. What we did in the last quarter, we developed the draft RFQ for that user research and persona development project, which is that first stage of that foundational work for the redesign. We worked with Joe to review a copy for Site Builder and Drupal 8 landing pages. You know, in particular with the Drupal 8 pages took some of the language in there, tried to make it a little bit less developer centric for some of the different pages, tried to make it use a little less Drupal Insider jargon. We're working with the staff to identify personas for future landing pages. So we had the Site Builder page that launched at the end of last year. And then basically there are a number of other landing pages that staff is working on pushing out over the next quarter. It seems like we might have a consensus that the next one might be front-end developer, femur, someone in that kind of general audience. And we've also been working on various policies, including updated terms of service and privacy policy. So in the next slide, so our current status report, and this, I put this together last week, so this is actually a little bit out of date. The user research and persona RFQ actually was approved by the committee at our meeting this morning. We were a little behind schedule on getting this out due to a combination of factors, which I take full responsibility for, but it is in great shape. And in addition to the RFQ, there's also a blog post that kind of explains and provides some context for what this project is and why we're engaging in it at this point. So the idea is that that post will go up tomorrow on the ADO blog, be cross-posted to GDO and receive promotions. So the community is aware that this is going on, can kind of get out any questions, comments, feedback over the next few days, and then the RFQ will be released, I believe, early next week. And so those are both in the hands of the staff right now and will be published as soon as feasible. The policy draft specifically for the terms of service and privacy policy, I believe, are currently that we have a draft that is actually undergoing legal review. So I believe that our next meeting will be reviewing that and then providing feedback as our working group. And then, of course, the other landing pages and other content creation initiatives are pretty much pending, availability of staff to execute those. Next slide. Current challenges. And the first one is probably kind of a familiar strain across all the working groups. The limited availability of non-staff working group members. We have actually a great advantage in the content working group in that we have a lot of staff on our committee. And so they're always there, which is awesome. And for those of us who are community volunteers, we're not always able to put in the same level of hours that the staff folks are. However, we do have kind of a standard and expectation that for group participation across the board, and we are meeting that. So it's not a critical issue. And this is another kind of, the second item is always kind of a challenge, I think. We are working on a big long-term project. It's very forward-looking. And one of the challenges, of course, balancing that against taking care of things in the short term. And really, this comes down to a question of focus and time commitment. We don't want to spend so much time on the big project that's not going to have a payoff for another year or two. That we neglect some of the things that need to be taken care of in the short term. Conversely, we don't want to spend all of our time focusing on immediate triage and neglect the bigger long-term work that needs to be done. And then, finally, of course, making sure that the interests of the community are synchronized with association priorities. And where this really comes down, again, we have a fair number of staff in our working group, which is awesome. But they're, of course, very often seeing things through the lens of their metrics. And those of us who are the community volunteers don't always have those same metrics or priorities. So again, it's not a big issue. It's just something that we need to make sure that we are aware of and that we're talking about it in an open way. But in general, I'm actually pretty happy with how we've managed to balance that. Moving on to the next slide, what we need to do to be more efficient involving more members of the community in helping to execute our initiatives. So I've actually had the opportunity, Joe and Megan have introduced me to a couple of interested members of the community who have approached them and have expressed interest in helping out. So I think we've had folks from the community, obviously, helping out with the Drupal 8 pages, the site builder pages. I'm going to be having a call with another community member next week. And so really we're just, for those folks who care about this stuff, who care about Drupal.org and have the availability to lend a hand, we're always more than welcome to involve members of the community. And the more that we can add, it'll help make some of these other tasks a little bit easier to execute. So as part of the blog post that introduces the audience research and persona development project, we are reaching out to the community to help us participate in that. The exact nature of that community participation will be defined once we have the consultant in place. But we are anticipating that there will be the potential for in-person interviews at DrupalCon Austin as well as additional interviews conducted remotely because we want to make sure that we're speaking to folks that are representative of our entire global community. Moving on to the next slide. What are we working on next quarter? Audience research and persona development. The first step is obviously the vendor selection process. And that's being managed, I think Tatiana's PMing it. It's being managed by staff. And then getting our consultant kind of kicked off as soon as they're selected. Working with there are a few new staff members. We want to make sure that we're providing guidance, answering questions as needed on things like case studies, landing pages and other content. Once the proposed Drupal.org policies are back from the attorney and we've had a chance to review them, we'll be sharing those with the community to get their feedback and to validate that they're consistent with what our community needs and is looking for. And then the next phase is the content strategy project. We'll be developing that RFQ over the next quarter. We'd like to get that out this summer. And make sure that we have that timing early enough that we can complete the project within this year. But also make sure that it's informed by some of the direction we're seeing from the research and persona development. And then of course we will be having working sessions at DrupalCon Austin to kind of track where we're at and where we need to go. And that's all I have. Any questions? One of the big challenges we had as a community was how little people understood what a redesign for a website was and how the process would work for the one we did many years ago. And I'm just wondering if you thought of doing a webinar series to take Q&A and create an app set so that people who wanted to get involved in the redesign or wanted to comment on it could sort of get a baseline. And then another thing to think about is is there some way to sort of recognize members of the community who've put in effort to understand the process or offer them a badge or some sort of official participant thing where they've read the blog post, they understand the process, they understand the working group world. So it's less of complete nut or craziness and more of people who've shown an effort to work within a process and inform themselves. Yeah, so to answer that second question first, I have not actually given that a lot of thought. I think that's a really great idea. Obviously as we get further down the process and are involving more and more people, we're going to need to have some structure around how those volunteers are involved. And I think it absolutely makes sense to make sure that they're recognized in a very public way. In terms of your first question about sort of helping folks understand how this redesign process is going to work, I think that is, so the blog post takes kind of a, and we're in the kind of final stages of editing it right now, but it does take kind of a historical view of Drupal.org, understanding how the site has kind of organically grown and developed over time, how we've kind of gotten in this position, where we are today, what we were able to do with the redesign from 2008 to 2010, but also kind of what the limitations of that project were, and how we're going to this time be able to address some of the issues that we weren't able to address in that earlier redesign project. I think a webinar, once we have the user research consultant selected, I think a webinar to kind of introduce them to the community is not a bad idea, and love to see if that would be something they would be open to and interested in. Any other questions? Alright, thanks George, it was very helpful. Thank you. I think in general, recruiting seems to be an issue, so I like what Kieran said about maybe doing webinars or communicating more loudly how people get involved and stuff. It's probably something we can do for all of the working groups. But let's move on to the infrastructure working group. I'm not sure who's going to present these slides, actually. Yeah, I think Tatiana's going to grab that one too, for Gerhard. Alright, the floor is all yours, Tatiana. Let's make sure. Actually, Rudy is on the call, so he will do this presentation. Ah, sorry about that. I'm good at him. I am, you did him. Oh, can you guys hear me? Yep. Alright, hi everyone. Rudy, I'm a member of the Drupal.org infrastructure working group. In the group we have Neil Durham, myself, Gerhard, who's our chair, Narayan and Tatiana. In our plan this year, it's been a number of things. A lot of them are part of the security audit that we had this last year. So the first big item is to move to our own virtualization cluster to give us more control over dev and staging environments. So we can have a network separation between development and staging, separate ACLs for developers and staging and all that kind of built into the system. And we're continuing service isolation following up from the security incident. So new virtual lands in place for network isolation, planning on more firewalls and better intrusion protection systems and infrastructure. We're working on better automated monitoring and scheduling audits of things. So software like OSSEC to do automated kind of security monitoring in addition to things like Pingdom to do HTTP and transactional like web monitoring of infrastructure. And we're just in general continuing to work on security and performance improvements. We've been working on SE 1x support in our configuration management as well as CDN deployment for faster load times. Last quarter we created a plan to improve the Drupal.org monitoring. This included better Nagios monitoring and a plan for kind of managing our own monitoring system outside of a current data center providers system. We have been discussing what CDN to choose, how to implement and test that CDN and that process is underway for getting that in place. We're planning open stack development environments and kind of the requirements around that. So gathering all of the network bits and security things and how to integrate that in with our existing sort of dev and staging environment, how to do that, how it will fit in. We have a pretty good understanding of that now. And we're planning to simplify the infrastructure issue queue components. So right now the infrastructure issue queue has many different components to it. And we went through a list to kind of pick out what's actually required there and to make it just more general components in the queue. So it's easier for people with questions about IRC or just general web issues to just pick web server instead of having to go through Apache or MySQL or specifics like that. And this is slightly outdated. Open stack is now ready to deploy basic VMs. So that's making good progress. We've added three additional VLANs, one public, roundable VLAN for network and two private for dev and staging back in traffic. We have now ping to monitoring for Drupal.org and all of the subsites. We didn't have that before, so that's a good step. And that's shown to be pretty useful for the infrastructure team to notice when outages are happening that are too fast or aren't detected by our Nagio Spondering system. We also have a new database server deployed, which is offset a lot of the subsite traffic and helped improve performance on the subsites on Drupal.org. And we have an Edgecast CDN test account created that we're currently using kind of in the process of getting the SSL HTTPS support figured out with them. Current challenges, I think this goes for all the working groups. It's time and availability of the working group members. We have a decent amount of people in the group, but we're all pretty busy. It's tough to be able to get them in the same place at the same time. It's also hard to get good infrastructure volunteers right now just for like infrastructure team and how to get people behind kind of these bigger tasks like the open stack cluster. And then we've been making good progress here, I think, but the separation of strategic tasks from taskable tasks. Most of us are also on the infrastructure team, so it's sometimes very difficult to get around like the database server was down earlier or there's some actual tactical thing we've been working on to get the meetings more focused on strategy, how to make Drupal.org more performant, how to continue expansion of Drupal.org, use their base and keep servers happy and the site performing well. So to kind of get those tasks more in the forefront and less on the kind of tactical like our monitoring server didn't detect this thing. How do we fix it? And to be efficient, we really could use more kind of rockstar volunteers to help with the more advanced tasks. Getting people in the barrier to entry is pretty steep right now and part of the strategy for like open stack and these other kind of development environment things and moving to get and getting everything a little bit more open and out of the control of not the infrastructure team makes it easier for people to just jump in. You know, with open stack, we'll be able to give someone an account and give them a quota and let them work on what they need to work on or contribute without having to go through kind of a manual process like going to me or Neil Drum or Narayan to get access to the things they need. So we're working on less barriers to entry but there's still definitely many barriers there. And there's also been kind of a lack of focus on the infrastructure side, on the test spot infrastructure. The test spot team has been separate from sort of just regular infrastructure team tasks and things we're doing. So trying to get more focus on test spot infrastructure, how to improve that, how to get Jeremy Thorsen more involved with our team in the working group. And so next quarter, the biggest item is to get the CDN deployment moving along so to get the actual CDN in front of kind of the subsites first and then finally Drupal.org as we work out any kinks we come across. We're working on kind of how to better our internal monitoring systems so how to keep us alert if things are happening, if things are breaking, better like deeper MySQL checks and deeper web checks to know if things are breaking before they actually break to get that in place and to include Jeremy Thorsen in the working group meetings to improve the transparency with test spots. We've been more involved lately talking with Jeremy and working with Jeremy so to get his ideas out there and so we can kind of work more as a group and get more transparency there, I think is a good next step. And thanks. Many questions on items. Rudy, have you selected a CDN provider? We have selected Edgecast. Okay. As the working group, that was kind of a... Yeah, who do we select? You know, Narayan had done a bunch of research on CDNs and kind of nobody was against Edgecast so we went forward with them. We have a trial account with them right now and they're working on it. Oh, go ahead. What other CDN providers did you look at? That is a good question. Max CDN was definitely one. I think there was talk about bigger ones like Akamai but the expense was a little high for what we're doing and Edgecast came out as a good mid-range CDN for our needs. Are you looking at any application performance monitoring vendors? You're talking like New Relic or a system like that? Yeah. We had discussed that a bit. I'm not sure. The kind of the consensus was that the production effects of that, the working group does not want to run New Relic in production. So it hasn't really been discussed much. I could definitely bring it up in our next working group meeting and see where that's at. We do some Google Analytics monitoring of page reformers and stuff like that. Pingdom has a real user monitoring system that we now have with our Pingdom account. It's not enabled yet but we're kind of doing some testing with it to see if it gives us enough drill-down data so we don't have anything right now in the production space for New Relic or actual code performance. I think if we go into something like that, it would need to be something we could just use on dev and staging and how to do the performance testing there might be kind of up to the project or whatever we're working on if we need to get a load testing third party to come in and do the load testing if there's something like New Relic on that VM to see where the bottlenecks are. Thanks. We'll take a look at my comments offline. Okay. All right. Well, thank you, Rudy. In interest of time, I suggest we keep moving. The next section is the community elections. Hall, is that something you're going to present? I think Donna is going to talk about this. We still have Donna. Oh, I muted her. She had to come back online and she's muted. But here she is. Donna, you want to try one more time? Hello. Yes. Can you hear me? Yep. Okay. Holly, are you going to drive the slides? I sure will. I sure will. Awesome. Okay. I'm kind of getting over all of the slides. Okay. So community elections for 2014. At a high level, our goals moved on to our... At a high level, our goals are to increase the awareness and participation amongst the community in the election process that we have traditionally. So far, the participation has been pretty low. So whilst the aim is to represent the community, if the community is not involved, then the question is how representative are we actually being? Improve the user experience for voters. Provide better resources to candidates to assist with onboarding once they're elected. And this is something that's sort of been discussed, but we haven't really locked down is to shift to a two-year staggered term for community elected board members. Next slide. We've established that a year isn't really long enough to be effective and discussed that, you know, taking that community directorship to two years would probably help with that. And that it's really helpful for community tractors to be involved in the strategic planning. But they need to have... You need to balance being involved in that process with understanding a bit more of what goes on. So timing is an issue there. Next slide. So we're recommending that we modify the out large direct terms that we work in... to publicize the election cycle better. And that, you know, to help get those directors up to speed that we really work on that onboarding process. Next slide. Last year, Pedro and Tariana and Drum did a huge amount of work to get the voting software up onto D7. And it actually all worked pretty well. We had an offline vote counting thing using the software that we used. And that also worked a lot more smoothly than any of us kind of anticipated. That was great. And the hope is that this year, because we've got Brendan on board, he'll be able to actually manage the technical side of the election. So that's really great. And now because we do have, you know, extra firepower around marketing and communications, that we should be able to improve that outreach and really try to engage the community more effectively. Next slide. So this is sort of one of the big questions. I've just kind of listed out the timeline there that we ran to for last year. You know, should we be replicating something like that? But we also raised the idea around timing to shift the elections to February 2015 so that we can have our new board members in place by our American US Drupalcon retreat. As an opportunity to give them more time to get into what it's all about before we sort of get strategic to the end of the year. It gives them us time to do face-to-face sort of earlier on and all that kind of stuff. So that's what we're sort of looking at at the moment. Next slide. However, to change the terms, we will need to amend the bylaws so I'll let you read the current definition in your own pace. What we're suggesting is that we change this so that at-large directors shall reflect and represent the Drupal community at large. There shall be two at-large directors who are elected by the community and ratified by the rest of the board to serve staggered two-year terms. You can see there that the change is pretty minor and I've highlighted in blue from serve one-year terms to serve staggered two-year terms. This would also mean that we would elect one director per year for two years as opposed to electing two directors for one-year. And to transition into this, we propose the simplest way of doing this is to extend the term of the most recently elected director by one year should he be willing to be so extended. Matthew, we would like to convince you. Okay, so that's sort of where we're at and then for the next elections we would be electing only one member. That also simplifies the election process somewhat and we don't need to kind of juggle things to elect two from the same vote. So I think that's kind of its next slide. I think he's been on to a vote whether or not we want to... I'm going to go forward with that so I think it's probably worth having a bit of open discussion about this before we dive straight into a vote. Polly, anything you wanted to add to that? I'm hitting a jolly rancor. I'm going to finish that and then talk. Sorry. I don't even know what that is. I want faster. I guess just open floor if anyone has questions or comments on that general part. Donna, this is Karen. I'm wondering how much of it is... I'm wondering how much of this is... you need the time to figure everything out versus an enablement issue where if you went through a two-day intensive course or something like that or went through a big long list of learning materials that you could come up to speed faster. The reason I bring this up is certainly one of the challenges for community board members. I think it's also a pretty significant challenge for new board members as well as well as members of the community and staff and stuff like that and whether we're really getting at the heart of the problem. Which is just how much effort it takes to pick up speed. Yeah, I think that's a good question and I think part of it could definitely be helped by having some great materials or perhaps a course. Part of it is also the socialization of becoming part of... we effectively become a team on the board and I've sort of seen the difference of the meetings we've had, the more recent meetings where everyone actually knows each other and we're all kind of... we've all kind of... the group formation thing has happened and we have actually become more performant, I feel. So some of it is definitely just raw knowledge like how can you get the information in your head faster but some of it is just time and socialization and we don't meet frequently enough to really do that. So yes, I think some of it will be solved that way but not all of it. Being the newest member of the board and having quite a bit of experience, board experience prior to this on other boards, I would concur with those thoughts. I do think that there are ways that we can improve onboarding so new board members can become more effective, more quickly on the board of directors but one of the things that strikes me is that it takes three to four months to really even get a sense of the other people that you're working with and start to gel with those people and by that point, a quarter of your term is complete and so it really, I think, I think six months in you're feeling like you're getting your legs. One of the things that Holly said to me in Chicago was, wow, Matthew, it feels like you finally got your voice and that's true. That's exactly true and I believe that Morton, when he ran for his second term, you know, voiced the same concern. He didn't have enough time in one term to do the things that he felt he had committed to when he ran and got elected and I think that's all valid. I personally think that two-year terms is a very smart thing to give. I do think that we should improve our onboarding material as well but I think two-year terms is a good direction. Well, I can kind of back that up by being though I've been elected twice and of course that's all. One of the good things about having a one-year term is it's a pretty good test of where you stand and also people around you feel that you were completely screwing up. They would get a chance to get rid of you, you could say, but for me last year it felt very much that I had some things I knew I wanted to do and new steps I wanted to build and having 12 months to do that and the first two to three months is just figuring out who's doing what, why are we doing things in a certain way and especially if you don't come from an American background it gets even harder. So that was definitely a thing for me that took some time but there is also the other consideration that says by having a one-year election it's also a way for if a community doesn't feel that that they actually have a voice on the board they get a chance to clean up house each year. We of course still keep that by having a vote voting a new person in once a year but it's just one of the other opinions that I've heard when I've been told with the deal about changing it to a two-year term is well what if we elect somebody who is showing off trying to not be in what we thought and that's maybe a thing we should take into consideration. Part of that is the job of the board itself to police the other members and there are contingencies in the bylaws that allow removal of a board member and I think that if we were in a position where an elected member was really screwing up or was acting in a manner that was not appropriate or if community members approached members of the board to say hey this person really isn't doing what they ought to be doing there are mechanisms in place to take care of those kinds of... I don't see it as a big thing but it's at least a thing to have in the back of the head. Yeah, I think Angie has raised the concern too that the community election process can be a little bit of a wild card and if we were to get someone... You've got me twice. That's right Morton, you're the catching point. What do we do? I think I've certainly heard those concerns and I've seen a community elected member and I certainly felt that it was six months in before I really cropped exactly what was going on and then turn around and it's time's up so I definitely favour the extension but I do hear the other side of that argument and I think they're very valid concerns. On the other hand I don't think we should be afraid of our own community so it's not a thing... I don't see it as a big problem I just see it as a... it's not all shiny rainbows I think it's noted, right? We sort of go yeah that's an issue but it's not a big one. Do anyone else have other thoughts? Anyone else have thoughts they want to share on this? Go ahead. I was just going to say the things like we've got really good examples of being able to extend people and there's a really good mechanism when it's working well and if you do get a wild card really intense and hard to... I mean you can measure it but it's really hard to work on that dynamic if things are going well and having run some organizations and been part of organizations people often don't think they've put enough time into exit plans and that's why you have to time those or time limited to sort of force an exit plan if things aren't working well. Anyone else? I think that's a good point about exit plans for when it's not working. Although I would point out that I think that the board has the ability to make changes in personnel anytime they need to. I've been on boards where all board appointments were automatically founded by some short period of time like three months or six months just to make sure that both sides after they actually got in to see what the workload looked like people who got elected may not be able to start and like what is that people generally feel like they're in that asset. It's just all about that. If their term is if we're talking about a two year term if it takes six months to find your legs then maybe it's not fair to judge before then. But I don't know. And I will say that it does feel like it takes six months at least in this case it's taking me about six months to really really feel like I've got enough wherewithal to help with effective governance. This is Jeff. I just want to say to who made the point? I guess Matthew made the point about, or Donna maybe I can't remember now. Sorry it was Donna. We really are gelling a lot more as a board the composition. We have to find that balance. I think it's great to have a trial period or something which is are you sure you want to do this to make sure that people aren't slogging through and didn't really appropriately address the commitment. But I also think that anything that we can do including this measure to extend the time frame that would allow us to keep a composition of the board more intact and overlap for a period of time if the results are anything close to like what we've observed lately because I do think that every team goes through the forming norming storming craft and we've definitely been through that and come to a point where I think we're much more efficient and I think it's really helpful for everyone. I would support this if we think that that's an indication of why we're doing that. Thanks, Jeff. Anyway, I also want to have some thoughts to share. Yeah, to be clear, I want to chime in with Jeff. I think that it's a better solution to do, to stagger the elections and keep them around a little bit longer. Thanks, Denise. Alright, if there's no more feedback or concerns, maybe somebody should make a motion. I'll make a motion. Sorry, go ahead. I'll make a motion to amend our bylaws to reflect to your staggered terms for at-large board members. Second that. Second that. Great. So, do we want to do a roll call on this? I think it's important. This is our bylaws. Alright, let's go. Matt, he says I. Morton says I. Dree says I. Tiffany, I. Jeff, I. Did I miss one? I've got Matt, Morton, Dree, Tiffany, Denise, Jeff. They're yourself. Army, hi. Vesa. Vesa, I. Donna, I. I think that's it. One, two, three, four, five, six, seven, eight missing. Angie and three, yes. Hurrah! That's a unanimous accolation. I can't spell unanimous. Awesome, thanks everyone. Alright, so let's move on here. Thanks, guys. Thank you for leading the charge in this, Donna. Alright, follow up from the retreat. I believe that's back to Holly. Hi again. My candy. So so we met in January and talked about wanting to. Create a fill in some of the gaps that we have in terms of just sort of overall organization. Strategy and some of the pieces you need to make that happen. So we talked about vision statement, adjusting our mission statement. Values for the organization and then we also talked about what seems to be a problem that we run up against over and over again, which is that there's a real lack of clarity about sort of what should be the responsibility of association staff and what should be the responsibility of the community when it comes to Drupal.org, Drupal cons, all the community assets that we have to maintain together. So those were the things that we talked about. We had a lot of great discussions and wanted to share with you how we are thinking about operationalizing this plan and that's what this document is about. So I wanted to put in front of you some of the major milestones related to those different areas and if this looks good then we'll take it down to staff and you know we've got more detailed steps laid out that we can put into play on the staff side to work with the community to have discussions about all of this and move towards some sort of consensus about all of these items with the community. So the RACI chart, which is the way I've just sort of summed up that idea. We talked about RACI over and over again, the idea of figuring out who does what and how. So our goal there is to be able to talk about that and vote on it in August that we would have a draft for the board to the staff would work on a draft for the board to discuss on June and then take to the community in July. Vision and mission you guys have already discussed mission. We want to work on finalizing some of the discussion, have some community discussion around that this month and bring it to you at the next board meeting to vote and get that piece in place. I think that that piece is really important for the RACI discussion. Values are also really tied into this. We want to talk about it at the June Drupal Con retreat and have a discussion with the community after that be able to finalize those in July for the organization. And then board operations is another thing that we talked about just making sure that you guys are set up to support all of this work. So we are going to the plan would be to repeat the board survey that we did last year in the month of April discuss that in June and then that will require a further action plan based on whatever directions we see from that in my hope here is that we would be working really closely with the governance committee who would look at those survey results and make the recommendations to you about where to go next. So with all those pieces in place that gives us a really good framework here on staff to then complete a 2015 leadership plan and budget which would also include a look into 2016 and 17. We don't ever want to give you a plan without some sort of context for it that it's a little bit longer term. So this definitely would fall short of a strategic plan but we want to be able to flesh out a little bit what like 2016 and 2017 look like. So after the June, July, August time frame we have all those pieces to be able to finalize that and bring you as we did in our last cycle bring you a draft for the September Amsterdam retreat have community discussion around that after a board vote in November. So those are the main things and I think that what we need from the board to get that done we'd love to have some folks from the board who want to work on the vision and mission who want to work on sorry drafting some of the language around the vision in particular and have the board help us identify who are the key stakeholders in the community to help us have this conversation. We definitely will want some board volunteers to help draft that that Tracy chart and as I said the governance committee to be involved in the board operations piece of it. So trying to keep that short because it's been a long meeting but there's where we're at any discussion or concerns about that. It was pretty clear to me but no one. All right next and last item is an update on the CTO hire which I believe could be fairly quick. Yeah so I don't want to steal too much thunder from Holly so I'm gonna No you can steal away. No, I think this is yours I think you ought to I think you ought to own this one. All right well with the we call his thunder if you don't bring the thunder so all right I'll bring the thunder. Yeah I know with the great help of Jeff and a really really wonderful hiring committee it was a really great experience to work with all of those folks we are really excited to announce that we have made an offer and it's been accepted so we have a CTO. Yeah and yeah his name is Josh Mitchell he works at the Multnomah County so he's here in Portland and Multnomah County is big government Drupal shop he's run a lot of great projects both applications and websites for the county has a really great team builder has not been Josh himself you know not been a super huge contributor back to the project in terms of code but it's definitely been a participant come to Drupal con that sort of thing and it's just really really excited so excited that he's starting really quickly he'll be coming on board on March 31st. Yeah terrific news yeah and I just want to say you know Josh was our leading candidate so we got our first choice which was pretty cool and I think in addition to that he's he's probably he's probably the closest I think to the description that we laid out in the beginning so I think we'll be able to we'll be able to stick to our guns when people ask questions quite well which of course is always important in community management so we may have a few years less than we targeted initially of actual years of experience but you know I don't think anyone's going to be able to take issue with his his experience for a CTO role. Can we get some talking notes so we're all we're all pounding on the same drums so to speak definitely different when that's a really good idea actually you know Holly we might want to write up just from the notes that we have from all the interviews because we have really good we might want to write up some of the things that we liked best about him and that way you know when we send it out we can say hey you know one of the things we loved about Josh is he really understood the challenges of working in a technical community or yeah definitely that's that's already in the work so I mean we wanted to stay here at the board meeting but of course we're doing a larger public announcement a little bit later so Joe and we are working on that with Josh right now so before we post anything online which is when the flood of questions will come we'll make sure that you guys have those talking points. I appreciate it. Yeah I think we're looking at like Wednesday or Thursday next week for that. Alright well I think this wraps up the open session at least so thanks everyone or one little question back from the elections is Holly did we also need to convene a new election committee I just remember that was in the slides. Convene a committee oh I still have you on the committee let me follow up with you on that offline okay cool no worries alright any other questions alright well you know let's adjourn this part of the meeting and then move through the executive session so thanks everyone for attending and including like Kieran for your participation but you guys in a minute or two thanks everyone thanks everyone