 We're going to kick it off with operational updates provided by Holly, we're going to talk about DrupalCon Latin America, we're going to get an update from our new CTO, I think this is his first board meeting, and then we're going to talk about the community elections process, and then we're going to switch the executive session for previewing and getting an update on the cash flow and revenue updates. Any other topics which we should add? No? Alright, then I'll give it to Holly. Thanks, Rhys. So welcome to the month of May, in which we will discuss the month of April. So lots of stuff going on, not the least of which is our new logo, which you can see on the new board packet. We're very excited to have. It looks really awesome, reversed out of things, so we're excited to have that. But that is just a small update. We had lots of stuff going on this last month, and I think one of the most important things coming out of April is that we got the managers together here, so Josh, the CTO, Megan, the associate director, Stephanie who runs community programs, Joe who runs marketing and Chris who oversees operations together for a long week of meetings as we start to get ready for 2015 and beyond. So lots of planning is going on right now to set the stage for next year and the years after, which we're really excited to start doing. And to compliment some of that work, you may remember that we talked at the end of January about one of the key questions that keeps plaguing the association is what is the role of the association, be the community, and all of the work that we undertake. And we formed a small committee of board and staff to help try to tackle that question with the community. And they've done a number of one-on-one stakeholder interviews about that very question. And we have developed a survey that is based on the racing model, but a little bit simplified, that we're about to launch out to the community to get some feedback about where those lines should be. So we're continuing to work towards a clearer answer there, and that'll definitely help us with our long-term planning as well. So that work has been happening for sure. And then I think one of the key areas that we continue to focus on here, it continues to be a risk, it's just being able to hire fast enough. We're really thrilled that Oliver Davies just joined on May 5th as a second developer for the association. And he's already got a couple of commits under his belt, which is awesome. And that will hopefully help us continue to accelerate the work of the tech team. We also were able to make an offer out for a DevOps role. So we're fingers crossed that that comes back positively, and we're able to announce a hire there very shortly. And that's really going to help because so much of our work this year is just getting our infrastructure set up to improve the performance of Drupal.org and to align with the security recommendations that we got back from the consultant last spring. So Rudy's definitely done a tremendous amount to move us forward there, but there's a ton more to do. And building out that infrastructure to make those improvements is really key. And then of course, because we are thinking about 2015, 2016 and 2017 already, those guys are going to have to then turn around and really make sure all that infrastructure is optimized for where we're going to grow. So we want to get those people on board. So that's good progress. And then we have a number of other positions that are up. And so if you go to association.drupal.org slash jobs, you can see all the listings that are posted there. The strategy that we have employed is just to put out all of the openings we might have on a tech team and see where we get really good candidates. And one area where we have a number of leads is in the UX role. And so that's good because we have a number of leads. But the hiring overall still is kind of slow. And we're just really working to flush that team out as quickly as we can. So that's one big risk that continues to be out there. And we're just pulling as hard as we can to get that done. So I want to highlight that area. So that's sort of general stuff. We've been focused on the future, really around the race and values work that we talked about back in January and hiring. And then if we dive down into some of the programs a bit, I'm just going to look at, I'm going to skip down to the DrupalCon updates. So Austin's on track. We're managing that budget really well. So I think there's nothing there that should be super surprising for folks. But I did want to touch on Amsterdam. When we were able to launch Amsterdam, we definitely had some issues related to commerce and the commerce configuration. And at the time that we wrote the packet, they still existed. Josh and the tech team and Steph were able to work those issues out. Things are working well now. But I just want to highlight that because I think one of the key things this organization is going to have to do is figure out how to make a DrupalCon site and store rollout much simpler. This is an incredibly heavy lift every time we do it. So we're going to be strategizing ways to maybe have add DrupalCon site. And things like one commerce store where all of your commerce experiences related to the association happen so that we don't have to repeat these things every time. And thankfully with some tech leadership, I think we're in a place to address those things. And that would help us avoid these kinds of issues in the future. So that's something on the consign to point out and you'll hear a little bit more about Latin America later. So we'll get into that. And then if we look at some of the Drupal.org statistics here, one thing that I want to point out is a nice highlight is that we do have a metric around responsiveness and the issue cues, making sure that when people post something, it is responded to in 48 business hours so that they don't feel like they're shouting in the wind. And you'll recall a couple of months ago, we were able to, well, about a month ago, we were able to employ part of Liz's hours here. So she was ready to come back to work full time. So we used her other 50% capacity to work on the issue cues. And we're really excited because we just saw a huge jump in the responsiveness having Liz on board. So we're able to meet that goal now, which is really wonderful. So hopefully the community really feels that investment too. She's just really great at what she does there. Will that be a continued portion of her job description? I don't know if it will continue to be a portion of her job description, but we will continue to have this role filled, if that makes sense. That's great. Going into 2015, we might shuffle the deck a little bit, but this is a role that will continue to be filled. So hopefully the community feels that way. Can I ask a really stupid question there? Is Liz just getting in there and saying, yeah, I heard you're awesome, we'll do something about that? Or is she bringing attention to things? It's probably too much in the weeds. You can ignore it. I'll talk to you about it later. No, it's good. I think she is definitely looking for those trends and things that need to get escalated to the tech team to actually address. So there's a bit of an escalation path. And also, I think she's been about to meet with the tech team and basically say there's some trends that we're seeing in the queues each week. Yeah, each week. Great. So they're getting sort of that metadata look at the queues, which is important for the tech folks, right? Because they're so focused on one issue at a time. Yeah. And then there's things that she can actually respond to. I will help you reset your password or whatever it is. And she does respond directly to a number of things as well. Cool. Awesome. So there's that issue responsiveness. Excited to see that number in the grain. We continue to see numbers around engagement numbers like commits and comments down in the red. And our theory there is still that we're waiting for a triple eight release. We set some goals thinking that triple eight would be out at some point and that these numbers are definitely tied to that release. So we'll see what happens there. And then we we talked about page response time in the last meeting just to let you know, like it continues to go down, which is great, although it started so high, the number still in the red for the year. But we're just a couple of weeks away probably from standing up the CDN in front of Drupal.org itself. And we think that we'll just accelerate the responsiveness even further. And then I think just one other note on the on the tech team to highlight is just, you know, also in April, as I think I joked somewhere that we have to stop indoctrinating our employees in this way. But just after Josh started, we had the Heartbleed security incident. So just want to point out they spent a fair amount of time responding to that, that as well. And did a really great job handling that quickly and professionally. And definitely got a lot of kudos from the community for dealing with that well. So we're excited to be beyond that for sure. So those are some of the highlights in the tech area. Any questions about the tech team and Drupal.org? Okay, and then I'm going to move on to some revenue updates, because community stuff just all looks good. And there's words on the page that you can read. So revenue, as you are aware, we are working on increasing our revenue opportunities or diversifying our revenue streams so that we're not all about the cons. And Megan Steem has done a really good job of selling established programs like the supporting partner program and growing those, which has been really wonderful. And we have a couple of new things coming online this year as well, including the job board. The minimum viable product should be out by Austin. And the it's looking really wonderful, which I'm very excited about. Cheeky Muggy's been really great to work with. And so we will have that out there. And you'll start to see that revenue hit this summer into our, into our P&L. And then I think the really key thing on the revenue side is, you know, we also know that there's a lot of potential for advertising on Drupal.org. And I want to be careful here and say, you know, again, we don't when we say there's a lot of potential for advertising, we don't mean there's a lot of potential to put an ad on every page of Drupal.org. But we think there's a ton of potential to deliver advertising in, you know, a contextual way in certain parts of the site, like never the issue queues, right? We get that. And we've experimented with that this year, right? We're expanding the scope of the hosting listings and shaking up the strategy a little bit there. And Megan's team has done a great job thinking that through and executing. And that's definitely increasing the revenue from hosting listings, which is going to be fantastic. And then on the advertising side, what we introduced this year were ads on a couple of the landing pages. So we've got the Drupal 8 landing page and a site builder landing page. And we have a couple of sort of cornerstone folks who have purchased ads on those landing pages, which is great. And we think there's a ton of potential there, but we have to push up the SEO and, you know, amount of site traffic on those pages, which we're poised to do when we hire a content manager that will go a long way. But we think there's some more. And in 2015, to really continue to do the work that we want to do, we have to grow revenue even more. And we're going to talk about this at the retreat, but I just want to say that we're definitely thinking that we're going to have to push harder now to get more expertise on board to really grow that part of our program out, the advertising part of our program out the right way to make the big numbers. So we can feel the potential is there. We don't have advertising expertise, you know, people who deliver those services in-house. We're working on getting all the information we need, but we're definitely going to have to do a bit of a hard pivot and probably focus on that a lot for the rest of the year to really be able to generate the kind of revenue we want to for 2015. Questions about that? Do we have a sense of what the percentage of revenue from advertising that we want for the association? You know, I haven't thought about it in those terms, but if I could do some math, let's call it 1.5 divided by 7, whatever that is, it's that percentage, because I don't have a calculator handy. It's tiny. Um, yeah, 20 percent. No, that's 20 percent. Okay, okay. Yeah, I think 20 to 25 percent sounds about right. And that's super back of the envelope, so don't, you know, I would not consider that number final. Other thoughts on that? Okay, then the last thing that I just want to... Oh, good, Angie's found it. Another thing that we need to fix. But the last thing I wanted to highlight, sorry, was just to point out a couple of other bright spots. Just Joe's work with the marketing folks, all of our social and email metrics are really good, like just really solid. And, you know, we're going to be doubling a bunch of numbers this year. So I think the reach of the association is growing very quickly. And that's great news. And I really like to see that we're going to be able to talk to more people about what we're doing and what's going on. And that can only be good stuff for the community. I was excited about those things. And those are all the highlights I have. Did you guys have questions about anything else in the packet? You know, it's very clear. Alrighty. So I think we can move on to the next topic, which I believe was the DrupalCon Latin America. Is that going to be presented by Stephanie or you, Holly? Yeah, Stephanie's going to present that. So, Steph, you should be online now. Hello. Excellent. Can you hear me? Yeah. Okay, good. So, yeah, Latin America, DrupalCon is moving right along. We have a strong team in Bogota that is very excited and engaged. And so I just thought I'd kind of go through and talk to you a little bit about what we're doing. We're going to be in Bogota, as I just mentioned. February 10 through 12, what we're looking at is a two-day con with one day of sprints, so three days total, no training, no CXO, just the sessions two days for two days and a sprint. We're expecting approximately 400 participants. And the team is working to do a lot of outreach to all of the countries in the area to see, you know, to really try to maximize participation. We're also talking about creating a little video, like what is the difference between DrupalCon and a camp, because evidently they're saying that folks aren't really clear about the difference. So, we want to give them some materials to use. And I think we'll just do a webinar and then record it. So, that's one of the ideas we're looking at. Okay, next slide. The project team, so myself and Lauren, Lauren has stepped up. It's not her normal, it won't be her normal role, but she will be doing the coordination for Bogota for us. And she's doing a great job of rallying the team. We also have, we have Carlos Ospina in Houston, who is from Bogota, and then Aldebert, working, we're working very closely with them. And we have some other folks too that I'll mention in a little bit. So, this just gives an overview of the program. So, there will be two keynotes, so Dries, you, and then one other keynote, 40 sessions over the two days, and then one day of sprinting. Okay, next slide. Lauren is looking at managing, she's managing, you know, kind of coordinating with the content team. She'll be in charge of BOFs. She's the design lead and then website constant editor. Of course, all of this, she's never done. So, we're mentoring closely and working with her to get all of this done. Diana, we're bringing in just for pre-planning. So, she won't be on site, but she will be assisting. She'll be going on the site visit, and she'll be assisting with all of the logistical pre-planning, including how to manage registration and those kinds of issues. Okay, next slide. This breaks out who's doing what on the local team. So, Carlos is the community lead. AldoBear is, oops, AldoBear is the content lead. And Donna, and thank you, and Pedro have both agreed to assist. And in terms of assist, we mean just help identify those speakers outside of the area, of the local area, that the community, that the Latin American community wants to bring in, so that we make sure we're keeping this that it has the quality of a con and not just a local camp, you know. So, we're going to be looking at who we can invite to play and to present content. Fernando is the sprint lead. Ivan, the volunteer lead, and Hiro, Julian, Nick, and Leandro are all on the planning committee. So, we're bringing in Sao Paulo, Brazil, and Hiro has been very instrumental in working out the sponsorship packages with Megan. So, he and Megan have been working on pulling that piece together. This is just a kind of a list of where we are, what's happening. The designer is Felipe Rios, and he has the front-end designer, Harnan. The two of them are kind of the design team, and the visuals are very pretty that they're coming up with. So, Josh, on our end, is working with them. We're all working to make sure that the timelines are being met and that they understand exactly what that workload is to have the site build as well as the other design content. Content team is in the process of being put together, and all of the track chairs are being selected. Some have been identified, others have not yet. Splash page, I'll show you at the end. We have a copy of it. It's beautiful. Volunteers. Lauren's engaging a lot of folks. The additional keynote ideas are being generated, and Dries will be talking to you about that, what they would like to do there. And then venue options. We have three venues that we're going to be seeing on the site visit, and then we'll be landing on the site. That site visit is scheduled for right after early July, July 3rd, actually. We'll be going to Bogota. So, the risk and mitigation, you know, the challenges of this third con clearly is budget, I would say, is the first major risk or consideration. The challenges are that we have low sponsor revenue opportunities lower than we're used to, and we need to keep the ticket price low because of the area. So, we're really looking at every angle we can to end at a break even for this event, and it's going to be challenging, but that's the goal, is to break even. The site build and getting content on the site. This is a con that internally that we were really trying to manage for the first time, you know, without Steph Alhage's assistance, and she's of course mentoring Lauren, but we have, we just have some challenges of how to get the site up, and that's, we're working those bugs out, and Josh has been great at helping work through those issues. And then the other kind of challenges that it's a different con than we're used to putting on, right, because it's kind of in between how a camp organizes with the community and then how we do Drupalcon. So, we're finding those places that we can really engage the community and have them take ownership of big pieces that we usually have ownership of and making that work. So, it's more grassroots, and we want to make sure that there's the sophistication of a Drupalcon with the event, and I have no doubt we're going to achieve it. It feels a little bit like it's like the early days of Drupalcon, like when we were in Barcelona and so forth, right? Yes, yeah, I think so. And, you know, this kind of continues to bring up the question of what differentiates a Drupalcon from a camp, you know, as an example. It sounds a little bit to me here like we're not going for a camp, we're going for a glorified Drupalcon, Drupalcamp, not for Drupalcon. No, we're definitely going for a Drupalcon. But we're doing that with, you know, it sounds like we're not even turned on the engines. I'm not sure what you mean. Yeah, Martin, can you be specific please? Okay, I believe so. It seems like normally if we go into a Drupalcon, we have spins before and after, we have full staff on. It seems like here that we're going in with people who are, as you said, we're not going in with the Northern people doing Drupalcons in both Europe and the States. So we're doing a smaller event. We're still calling it a Drupalcon. This goes back to my... Martin, take your Northern Hemisphere imperialism and put it somewhere else. This is about developing an emerging market. Sydney was the same deal, data. Honestly, I think this is very, very disrespectful. It is, but it's also like we have to start somewhere. Public board meeting I'd like to remind everybody, please. Sorry. Yeah, I think that was a little bit too disrespectful. What is how come that we go and we say we're going to do a Drupalcon, and we're not going in full loan? But we are going in full loan, Martin. I'm not sure what you mean. What we have determined with these third cons is that they are different in that they're going to be a different size. We have to gauge the size based on the community. We have internal resources that we have to manage, and we don't have the capacity for specifically Stephanie, who works on the other two bigger cons. She doesn't have capacity to take on the third cons. Yeah, that's exactly what it is. We're going in with a voice that says, hey, we're going to do a Drupalcon, but what we're actually ending up is doing a Drupalcon that could just as well be done by locals, and then we would support them instead. So it would give another idea of what it is that we're doing. So people outside who doesn't know the difference will say, oh, we're going to go to this Drupalcon, and instead of it being like bells and whistles, it's going to be a camp with a little bit on top of it. So they're going to end up being disappointed and say, hey, this wasn't what we were expecting. Well, it seems like it's more than a camp to me, and the way I look at it is, yes, it's going to be, maybe it's going to be a little bit like a camp for the first time, but we're sort of, it's the first time we do it. We're going to use a Drupalcon brand. It's not going to be like a Drupalcon in North America, but it's going to get us there, and hopefully the Drupalcon brands will attract people from all around South America versus just one country or a few people from other countries. And I think that's something that the Drupalcon name will do. I'm just going to chop it and grow it. And so that's going to take a while, and I think we use, you know, we adjust the budget based on where it is. So I don't know, I'm still excited. Personally, I'm just afraid that, no, we did mistakes two years ago, that did set a lot of things back, and it's just me being worried. Yeah, I can appreciate you being worried, and I think that's worth listening to. And I think it would be helpful for me to get some more, like really clear specifics. And, you know, maybe it would help for us to talk in more detail than, then, you know, we would normally present at a board meeting. So I'm totally happy. Yeah, I know, that's why I'm only charging on the top of it, and trying to keep it as top level as possible. And there's just, there's just things around it that I'm new, but like, hey, there's, we can talk about that later on, I can try to be more specific. Yeah, let's schedule a follow-up, so we can just hear, like specifically, are you worried that, you know, specifically what you're worried about, so we can figure out. Yeah, basically, I'm simply worried that we're not gonna make enough punch, and we're gonna create another failure in South America, and now I would hate that. Yeah, we would also hate that. We sure would. And that's why I'm speaking out now, instead of waiting, it'll fall months. I feel, though, like this is being approached in a much more methodical and sensitive way than the previous foray, and you know, that's coming from being a guy that watched the previous attempt from the outside. Well, one of the things I'm worried about is that, and I've been looking down to meeting minutes, and I missed the meeting back in February, and I never remember us voting for this venue, or for this being in Bogota, and I'm kind of like, how did that come around? I'm not saying that it was a wrong decision, I'm just saying that that was one of the things that we saw two years ago, that suddenly there has been a decision of a place. Well, Morten, I can assure you that it wasn't sudden. This time we had a number of conversations face-to-face and online with the community, so... Okay, let's take it offline, because I feel like... Let's do that, totally, totally. Yeah, I'm good with that. Great, yeah, and we have every intention to create a successful DrupalCon in Bogota, I assure you, and we will make sure that that happens. Next slide, Holly. Thank you, and I just wanted to show you, this is the Splash page. We're just adding the year on here, but... Good point. Yeah, yeah, I thought that might be helpful, but Felipe is just really doing some beautiful work, so yeah, we're full steam ahead, we're putting a lot of attention on this, Morten, and we're figuring out what those pitfalls are, and how to work through them, so... I'm glad to hear that. Yeah, yeah, so that's the update. Great, looks like we're agiving a little bit. I like it. I really love it. Thanks, Stephanie, for the time you put into this. You bet. I think just to finish the topic, I think one other thing which sets this apart from DrupalCamp is the fact that I think a number of us, including myself, are really committed to this, and we're going to go there as well, and hopefully that will help bootstrap DrupalCon as well. With that said, let's move on to the next topic, which is an update from our new CTO. Do you guys see what I mean about how good this logo looks? Reversed out, I'm just going to say. Holly, are you going to be angry at me if I say, if you put a red and white behind it, it looks directly as if it's an egg and logo? All right, we're going to have a comment. All right, so for those of you who haven't met him yet, here's Josh. Hi everybody, I'm Josh, Josh Mitchell. A little bit about me. My previous role was with Multnomah County here in Portland, Oregon. I'm doing IT applications management for our enterprise web and library services. Really large-scale Drupal sites that we've been in place at the county, and I'm getting much better as Holly likes to point out at not saying we when referring to Multnomah County, because now I say we when referring to the Drupal Association, which is important. There's a little bit of my contact information on here as well, but mostly I wanted to give you guys an opportunity. If I haven't had a chance to talk to you yet, let's please do try to connect and have an extended conversation about the direction that we're looking to take things. Speaking of the direction that we're looking to take things, I'm about six weeks, seven weeks into the position now, and I'm beginning to get an opportunity to see what we have and what we need to move towards. So these are a few of the things that I want to put out to you and get your feedback on as well. But first of all, we're shifting the thinking of our tech team from what's the next thing I can tackle in the issue queue, because there's a lot of noise that occurs in the issue queue, and it's often a case where you get pulled in one direction and then you get pulled in another direction. And what we want to really shift our thinking to is small projects that have the prioritized issues attached to that project. So basically a little bit more planned out work rather than always approaching it from what's the next fire burning that we're going to turn our attention to. And that gets a little bit easier as we hire up and we've been talking about the hiring. And I think that's going to be a big portion of this is to get some full time staff on board that can participate in that way. What that will allow us to do is start running Drupal.org a little bit more like a product and less like a contributed open source project. And what I mean by that is in no way is this meaning to say that the community is not so going to be contributing to Drupal.org. But what it does mean is that we will be a little bit more intentional about these are the strategy that has been set based on the priorities that were set by the board and by the working groups. And then we'll be able to execute on that with a little bit more intention. The big piece here is while we're doing that we still have to make sure that we're not excluding any volunteers and giving them a respectful way to contribute with structured opportunities. They can make a bigger difference than the kind of haphazard way that we sometimes approach projects right now. To achieve that I think we're getting partway there this year with the hiring that we have planned but we're very much focused on infrastructure this year if you look at the hiring plan. We are planning on adding a little bit of UX but going into 2015 what we really want to get to the point of being able to do is that every project that we're assigning we have a developer a UX person. It could be a front-end designer. It could be a theme or depending on the skills of the developer and UX person. And a key that are on every single project. And I think project management is going to be an important piece of this because it tends to be something that isn't a it's not a core skill that we tend to get out of volunteers at the moment. It tends to be a skill that people want to work on or that they're interested in helping with. And I think having those project management skills built into the association staff is really going to help push things forward a little bit better. That doesn't mean a chem would necessarily have just one project but they would be assigned a developer and UX person for maybe multiple projects that they were helping to shepherd through. And then why this is important. What I've heard so far is that we really want the Drupal.org tech team with the help of the volunteers to support the entire Drupal ecosystem. I'm big about documenting what it is I'm taking on. And so one of the first one of the first things I needed to do was actually go through and create a visual representation of everything that we actually have right now that's started at Drupal.org. As you can see it's pretty vast. We're talking about 35 to 40 active sites that are being maintained plus several key services that really serve as a foundation for other sites to do what they need to do. Updates.drupal.org isn't really a website but it's a core structure that we have to have in order to have updates, status updates show up on Drupal dashboards for our users across the world. So I say all that and I show this picture in part to say whenever I ask for more people and as we look for more ways to do revenues so that we can hire more people this is why. We have a really big infrastructure to support and we have a large number of sites to support. I think this is also why if we look at things like the DrupalCon sites even maybe DrupalCamps we're going to be trying to look at a way to make that one site that can pick up the theme from whatever that project is but not necessarily a completely separate installation because that does take a lot of time for us to spin up each and every time and it really kind of divides our focus whenever we start going down that path. But we're also going to add some sites where it makes sense. Things like jobs.drupal.org we're looking at making that standalone for a couple different reasons but in part because we don't want to create confusion around Drupal Association jobs we really want it to be Drupal jobs so that we can really highlight that for the community and store.drupal.org which gives us an opportunity to have one star that truly runs all of our commerce associated with the Drupal Association and you can kind of see a rough timeline that we're looking at there in terms of moving from starting with just selling some gear next year starting to do registrations maybe by the end of the year doing membership and by 2016 basically anything that we were going to run commerce for we could do it through Drupal Store. So the last slide we have there is the staffing. These are the types of positions that we're really going to try to bring into the team but these are just the positions that we have posted for this year. I don't have any project management positions posted for this year that's definitely going to be something that we have to address in 2015 but what we are really trying to knock out is another solid DevOps engineer hire a security and architecture engineer that can really help us harden our Drupal environments and help us create the great architecture that allows for good integration between all these systems and then there's three positions up here the product manager, the user experience engineer and web designer. I've posted all three with the plans that we're going to get the best candidate out of all the applications to those three jobs and try to see where they fit into what we need for the coming year. Lastly the QA engineer I think this has been a key thing that we need to come up with which is a better way to do our deployments and to test our deployments along the way someone who can write both the automated tests but also can help us really structure our testing plans and help facilitate the community helping us test things on our staging environments. So those are the key things I kind of wanted to walk through a little bit of what I see the direction being that we can take a little bit of showing you this is kind of what we see that we have to support and the structures that are already existing that we need to keep going forward with and a little bit about the staffing that we're going into for 2014 and some plans for 2015. Any questions? I have two arms in the air right now like a skull to go. I'm just habituated to this. Any other? Any questions? Well that was not a question from Martin. That was a quick notice. That was actually a comment. It was me being very happy but like yes. Any other questions? Nope just gratitude. Josh thanks for coming on board. Well thank you. This makes me happy. Yeah nice job Josh. This is a good briefing good first steps and I'm very happy to have you as well. Yeah he's a rock star you guys. Thank you. We may not hire fast Holly but we do looks like we're hiring well. We did well yeah. He's a grammar nerd which I love. All right well let's switch to the next item which is the community election process. Great yeah thanks again Josh. Good so just as a reminder we have and I think two reasons I wanted to put this on the agenda one is just to make sure that it's out in the community and we'll write more about it but also I want to get get some volunteer help from the board please. So if you will recall we had a discussion started that started in Prague and we've already fixed all of the mechanics around how we re-engineered the elections to like one candidate to a two-year term staggered every year. And the other thing that we decided to do was to go ahead and push the community elections out into the spring so that we could align them with a Drupal con so that the new community board member could experience a face-to-face meeting very quickly after their after their election. And it's really just not possible to do this in a fall time frame because August is a month that apparently does not exist anywhere except for the United States. And if we were going to do a fall fall election we just we you know we were going to run into you know having to do candidate recruitment and meet the candidates in August and voting in August I mean we just couldn't do those things. So that was why we made this move and so I just wanted to let you know that we've got a timeline here we've got a project plan in place the team has met to sort of understand what that project is and this is what it looks like. So we'll be doing technical setup in December and January and that's just getting the election module up and configured and hopefully also prettier this time which is my way of saying UI and UX improvements. And then we'll do self-nominations the first part of February so give everyone a chance to you know get over the New Year panic. Do nominations do some meet the candidates voting and then we have a March currently we have a March 25 board meeting scheduled because I made that date very specific. So ratify the vote and get that communicated out to the community just a few days after the voting. So that's the timeline we're working with and just to give you a it's just a review some of the things that we're going to be doing on our end. We had a Drupal 7 upgrade which meant we had to use different election. We had you know new staff and board members getting engaged so we had to build all the elections in 2013 from scratch again which totally worked and I really want to give say hats off to Donna and Pedro for doing the incredible amount of heavy lifting they did to just make it run but it meant that it meant that although we were able to pull it off and it worked we weren't able to really improve the process the last time around except for the fact that the board didn't have to do all of the work. So in you know this time around we should be able to make some of those improvements because we've been through it once before as a staff with the same tools. We're going to be lengthening the time of the meet the candidate space and improving the interface for that so that hopefully we have more interaction during that period and the issue that we really want to work on this year is diversity of candidates so making sure that we have a nice representation both you know in all the ways that you can define diversity but I think particularly you know globally and then turnout so if you recall from 2013 we had turnout that was on par with 2011 it wasn't high 100,000 votes we need to improve that so those are the two things in particular that we need to really work on this year and those things I would really love to be able to have some that's where I want to have the board focus so in the past the board had spent a lot of time on these sort of logistical mechanics right like I will schedule a meeting and run a meeting for meet the candidates we've got staff that can do that this year and so I really want to put the board brain trust on these more strategic questions of diversity and turnout which I just said all those things on that slide so we need some folks to work on the election committee which is a subcommittee of governance to provide feedback throughout the process really focus on those two issues and then you know I'll be in charge of PM in this this thing with the board and staff and I just need a couple of folks who can really engage at those key times to make sure that we have you know improved our voter turnout and have some really good interesting candidates so that's my summary I would love to help with that is that Matthew? yeah great I would say as I was elated last time and that I'm moving for a one-year period I don't yet if I'm going to run next year I'm going to figure that out or it depends so I would say right now I don't think I could help out I can well it could create some strange issues if I did true so I should if people want to have my opinion go ahead and ask I still need to figure out with myself I want to if I want to run again now that I wasn't I'll only put it on a one-year term compared to the two-year term so I need to figure that out first okay the only thing that would be weird Wharton is if you decide you are going to run again if you run this video as well that would be anything that's weird but if you decide that you're not running again you'd actually be an ideal person to be on the committee yeah I know it all depends on where we end on this year so it's kind of I'm kind of like on one part I really want to want to help out on the other part I still have issues or things not an issue things I want to work on so it's kind of like politics needs perhaps county can I be kind of like an emeritus on the committee I would really like to not be doing the elections this year having been involved in the past three in one way or another I think if you have done it twice you don't have to do it again but get off get off do you have free time but I sort of say the emeritus I'm like totally I probably have some helpful stuff to input so Massey maybe if you want to you know ping me every now have a regular ping about it or something or you know like have me but I don't know just put that out there yeah I think it's gonna be great to just make sure you're at the couple of you know whatever conversations we have around diversity and voter turnout yeah I mean it sounds like you know you guys are gonna be doing the heavy lifting anyway so I'm you know I'm quite happy to be involved great great but by when do we need to committee assembled I'm not gonna call a meeting till the fall so I think you know in the October November timeframe is when we're gonna do a kickoff to specifically around these issues so that we can work them into the more full plan are you looking for do we need to be having the conversation with the community about having moved the date so are we just kind of gonna do it and hope no one notices no we definitely do need to have that conversation so I need to put it out there's a bullet here on the timeline that for a community discussion in May so I have a blog post half drafted that I'll get out there just to tell everyone here's the bullet I think put it out and also we're gonna put it out on the community summit and we're open around and say here we're moving the dates because we have changed these things and this is how it is and if somebody thinks it's a catastrophe and the world is going on to this talk about that I don't think that's gonna be an issue honestly it's a technology that we're moving the date and that's how it is done yep yeah I think that if we if we if we have had had larger percentages of voter turnout in past years it might generate some buzz my guess is that most people don't even remember when the elections are because because you know just just in terms of how how how it's gone gone down in the past and something I want to table but not discuss now Matthew for the governance and for elections in general I don't know where it came up again recently but whether or not that we should be looking at increasing the number of community elected positions going forward I can't remember the source but someone else raised this again recently so I just wanted to say that out loud it's been a talk that's been on a couple of times that and especially been a talk that's been like on why isn't the whole board elected and so forth and as I see there's reasons that the whole board is not elected to make it work but definitely the other part of us figuring out should more be elected on the board is definitely a discussion that's worth because it's it does do set some question marks around this that's okay how democratic is this actually and then you can always go back like well this is also about being work and so forth and blah blah blah that's a good topic for the governance committee I think for sure I'm not sure if that's been tabled for their agenda or not but that's certainly the right place to talk about it yeah yeah we're planning on we're planning on the governance committee is planning on discussing terms and we can certainly bring into into that conversation what the what the composition might what might be optimal but that's probably that's probably like Donna said it's probably something to be tabled for the time being I'm gonna jot it down in our I have the sort of 2014 master calendar I'm gonna pop it into one of the months so that it doesn't drop off sweet yeah I'm gonna randomly pick a month for now but we'll figure out where it goes well good Matthew and Morton and I think Donna I think you're just a you know advising capacity would be really really helpful so I think I think I'm good excellent any other questions on this any other questions for the open board session if not I think we can adjourn thanks everyone for participating today and for the board members and Holly you know we'll see you in the executive session so let's switch to that thanks everyone thank you thank you