 Okay, can you hear me still? Yep. Awesome. All right, well, as Holly mentioned, we have a very active agenda, so we better get going. Open session, followed by executive session, as far as the open session is concerned. We're going to do the regular operational updates provided by Holly, then more, you know, other people in the staff, we're going to get an update on community programs. We're going to talk about marketing committee charter and how to evolve that, hopefully followed by votes. There's an update on some, you know, branding changes on the logo and the different badges that we want to talk about today. We want to vote on the procurement policy, which has been acted for a while and, you know, needs to be approved formally. If you all are in work with that, and last but not least, we're going to talk some more about extending the at-large director term by a year. So, and that's just it for the open session, and we have an even longer list of things for the executive session, and you can see the report back. So let's get started with the operational update. Great. So, in honor of our very large agenda, I'll just try to keep it super short. And say that March was super huge for the association. We just really started putting so much great stuff out into the community. So we have that big long laundry list, but, you know, just able to celebrate a million sites for Drupal and starting that we implemented our first actual positive proactive change on Drupal.org since starting the D7 upgrade, which I know is long overdue, but still deeply celebrated here internally. You know, we had a huge global training days starting a user research RFQ, our new CTO started. We started working on a job, the job board, DrupalCon Latin America was announced, right? And we've been working on some branding changes. So lots of stuff from the staff out into the community this month, this last month. So it's been really wonderful to start to see all that momentum build and really start to put, you know, much more out there than than just the cons in a very real and tangible way. And I really owe a huge debt of gratitude to, you know, obviously the great staff here, but also the, in particular, the working groups have really been starting to hit their stride and get lots of good things out into the world. So it's been really great to see that start to take off. And I'm really thrilled that Josh Mitchell, the new CTO is on board and can really take that to an even better place. So that is good. The other quick thing I'll just mention is that we did manage to update the dashboard a little bit with some better year to date goals. So we did do a sprint together as staff to figure out, you know, what should more actually look like, not just take the annual goal and divide by 12. So there's some changes there and the numbers are a lot more relevant now, which is great. And so we'll see those. We sort of skip through some of the numbers in a minute. And as you look through the rest of the packet, you know, I think that the themes for us are just trying to keep up this pace is going to be a challenge and requires that we get all the right staff on board, particularly around Drupal.org. We're starting to build that momentum, but we have to sustain it. That hiring is going to be key. And Josh and Rudy and I have spent a long time talking about that as most of the hires on the tech side are focused on infrastructure this year. So we're keeping that up. Working groups, like I said, are really starting to make some good stuff happen, but we have to produce even more, even faster to meet all the plans that were laid out for this year. And I think, particularly coming out of the software working group, there was a lot of budget there to do things and move stuff forward. And we are starting to do that, but we need to pick up the pace there. And that's really leads to this third sort of risk, which is that Drupal.org performance is still behind where we want it to be for the year. So when we look at those numbers, you'll see they're behind. The caveat is that they really are accelerating out of the red. They just haven't gotten out of the red yet because we had such a slow start coming out of the end of 2013. So those are the things we're sort of concerned about on a meta level. But if we look at our main KPIs, things look really good overall. The one red number, not the one. One of the red numbers is the net income, but this one is still key towards financials that are reporting all of the revenue for the cons in June for often Drupal gone in particular. So we'll see that even as we get closer to the cons. There's just nothing to worry about yet. It's just the way we have that pegged right now in the dashboard. And then average membership spend still continues to be below what we want it to be. But the number of memberships has been really great. So even though the average membership spend is down, the revenue has been on. So we're not missing our revenue number there. We continue to monkey with that one, figure it out. And the other red item is just Drupal is a percent of the web. That's something, there's a target there that we want to hit for the year and we're behind. And obviously a lot of that is going to be tied to Drupal 8. And the earlier that kicks out, the more momentum we can build on this number. So, you know, we set a goal with the optimistic assumption about a long shape there. It's also when we actually don't have much control over. Oh, exactly. Right. So the main KPIs look good. Like I said, I don't think there's a ton of things to report except to stop and save for Drupal cons themselves. The numbers are reported through March. But our early bird date was in early April. And so I do want to stress that they're all green here, but they're like even better than green. If there was a green or green, I would put it if you added in their early bird date, I just want everyone to know that we hit our early bird goal just a little bit better than what we needed to be to hit 4,000 for Drupal con Austin. So that's on track and sponsorship revenue is just over a hundred percent of goal now as well. So everything looks really good to have a very big and another biggest Drupal con ever. Yeah. So Drupal con is looking great. The area that we're still continuing to put a lot of focus on is Drupal.org. That's the area where you'll see the most sort of red and yellow numbers. So around, you know, site traffic, number of commits, comments, those sorts of things. And to degree, we don't have a ton of control, but we know that if we can make Drupal.org an easier tool to use, we can increase the number of comments, the number of commits by, you know, making it be a friendly place that people want to work in. So we know we have some work to do there. In particular, this chunk here in the middle, page response time and test spots. Those are infrastructure related things that we're really focused on right now. As I mentioned, that's where the majority of our hiring left for the year is going to happen. All of those numbers were so far in the red coming into January, that they're going to stay in the red for a little while longer, but we're getting close to getting out. In particular, page response time is getting much, much better. And as we get a CDN stood up around the site, I think we'll see that get very near goal very shortly. But the average was so high in January and going into February, that's going to take us a while to bring it down into the green for the year. Test spots. I just want to point out that Jeremy and Ricardo Amaro spent a lot of time in Zegged doing work on the test spots, and that and some changes to core mean that the average for, the average test time in the month of March was just 47 minutes. You can see there's a big difference between March of 47 and the year to date actual, which is an average of the all three months, which is still 136 minutes. So we should get down to that 70 over the next couple of months. So the average will come down, but that was amazing work. So yeah, and we should then, with that test time down, be able to test as many patches as folks want to throw at us. So hopefully Drupalcon Afton is a huge sprint and we're able to get a bunch more core patches tested at that event. So those are the numbers. The last bit chunk of these landing page traffic homepage bounce rate. These are things that the user RFQ are really focused on helping us to address these are content working group issues. And we'll have to, you know, continue to work on these throughout the year. They're, they're definitely in the red, but it's not crazy terrible industry average kinds of numbers, but they're not where we want them to be. So that's another area of focus. Then there are a lot more words, but they're all good and easy words, unless you have any questions because I know I just want to keep it keep it moving along for today. No questions. Good and easy words. One other milestone we hit in the last month is that Holly Ross has her first patch in core. So that's pretty cool. All right. I saw a tweet about that. If you're pushing pushing commit quickly into call have a couple we need to talk about. Yeah. Last night when I got stuck in Salt Lake City on my way home from New York, I couldn't sleep. So I was scanning the, the queue for beginner documentation patches. So watch out. That's awesome. Yes. Only three more to beat Neil drum. Awesome. Section where there's all these words. I just wanted to make a note which I've mentioned to, I think Megan is the next global training day is like, while all of us are meeting in Austin for our retreat and immediately before Austin. Just wanted to flag that. I think the timing of the global training days needs a bit of attention and love. Cause I think that's going to be tricky for a lot of people. Anyway, I'm done. Okay. Yeah. No, thanks for that. I talked about that with the team and. Yeah, go for it Megan. Oh yeah. So we talked about as the team and you know, it's definitely something we can look at in the future just to watch competing dates. We get so much participation from around the world. Triple Con Austin is going to be pulling so many people from the states. So the rest of the world will continue to, you know, we're still seeing great signups and interest around the world. So it will impact a little bit on the, you know, in the North American companies, but it won't impact our overall goal by any means. It could actually be a plus for, you know, the rest of the world who can't participate in Austin to sort of maybe have some acknowledgement that, hey, you know, this is part of the whole Drupal community. Well, North America meets over here. All of you are doing these great, these great training. Yeah, just thanks Megan. It's cool. Awesome. All right. Well, I suggest that we move on. And that's again to the community outreach. Section of the meeting presented by Stephanie. Yes. And let me just queue that up for you, Stephanie. Thank you. It's just scrolling on the tiny little thing. Well, hi everyone. I just, you know, we, we realized that we had brought on a new community outreach coordinator and had not really told you what was happening. So we thought it would be nice to let, let you in on what's happening because it's very exciting. Lauren Shea has been brought on. And for the express reason of looking, when we look at the vision from our 2014 leadership plan, the second point is that the Drupal association is the heart of a strong Drupal community. And we want to grow community leadership globally. So that's really what we're focused on with this position. And a few things. So the community outreach coordinator is going to, is in the process of identifying community leaders, understanding how these leaders motivate and drive the community, understanding why they volunteer their time and energy to propel and support the Drupal project and evaluating, she's going to be evaluating and making suggestions for programs and growth opportunities. Okay. Thanks. And, you know, we can really assist the growth of the adoption by continuing to build a healthy community. So that's, that's what this position is all about. So Lauren, you may have seen some blogs of her. She's already blogging. She's tweeting. She's getting out there and meeting a bunch of people. She's going to be in Stanford this weekend at the camp. But she is responsible for global training days for webinars and other camps kind of overview and looking at ways we can continue to support them. She's the liaison for the DA to the community working with the leaders in Europe to assess their needs. And kind of an add-on for this year is she's going to be the project lead for Drupalcon Bogota because of resource we're kind of, we've reallocated her a little bit for that role. We've already met with the Latin American community for the first time to get that ball rolling. And it's a big deal. It's a big project. She's going to be also looking at program development and making some recommendations. There's a survey that's just gone out. So that's going to be, she'll be evaluating the results of that survey and making some recommendations that we'll be bringing up to the board. And she's tweaking and blogging. So that's kind of an overview of her. Just kind of a quick view of where we are. Our first global training days in February brought in 34 training companies, which is huge. And our goal for the entire year is 40 unique companies. And Lauren's already let me know that she has probably six or seven brand new companies already for the May 30th. So I think, I mean the, yeah, the May 30th. So we're already, I think we might already be at goal or very close to it. I think you actually transposed those from 34 to 43. We've reported 43 for the last couple of months. Oh, yeah. 43? Not 34. Yeah. Oh, I'm sorry. So our goal is for 40. Our goal is 40. We hit 43. Yes. Ah, okay. Yep. Well, there we go. So we're almost there. Yeah. All righty there. Cool. So that's global training days. And then if you can hit it. Community grants to give you an update there. We have a goal of 21 grants. We want 21 grants applied for for 2014. And right now we've awarded 11 grants. We have a totaling 16,006. And we have 23 for left for the year to award. So the grants that have been given, you'll see the list below of who we've supported so far. They're between $5,000 and $500. So a wide range of grants and all of those folks are doing really wonderful things. So we're pretty excited. Okay. Thank you. Drupal camp kits and AV kits. We had a goal to send 14 of these out in 2014. And so far we've sent six Drupal camp kits and three AV kits. The fiscal sponsorship. We're going to be doing a webinar in July to, you know, let people know more of what that program is all about for them. So what we're looking at is improving this program by really reaching out to the camps, finding out what would be super helpful. And then adding more substance, kind of more marketing swag to the camp kits for 2015. We're going to get that into the budget so that we can actually embellish those kits. Webinars, we have a goal of 1,000 attendees in 2014. Right now we've had 107. But we have a ton of webinars coming up so that number will rise quickly. We have a community, the global training days community webinar just happened yesterday. We're going to get the video out on that. And then we have, these are the ones we have coming up, how to hire great Drupal talent and getting more out of Drupal.org. And then we also have a bunch of supporting partners and tech supporter webinars coming up as well. And then Joe is leading the charge on the Drupal 8 series that will happen whenever we can do it. Whenever it's appropriate to do those. But that's in the works as well. So right now we have seven webinars scheduled from April between April and June. And then just to give you an overview of the leadership survey just went out to approximately 150 global leaders identified by our staff. And that was sent last week. The purpose of the survey is to find out who are our leaders, identify the roadblocks and successes in the community, and then how we can assist and support their efforts. So as soon as that results will be reported in May, they're coming in now. I think she said she has over 70 responses so far. So it's pretty good response rate for 150 being sent out. And we'll get back to you with the results of that. Yep. And that's the update. Yeah. So you can see this person. So Lauren's really focused on community in the, you know, global camp sense and not the Drupal.org sense of community. I just want to make that clear. What? Donna, you sounded like a tired move with Stella. I'm a delirious. I just thought you were an owl hanging out with a toddler. That's what I thought. Yeah. Any questions coming out of that or thoughts to share? Thank you so much for the update and congrats to Lauren for hitting the ground running. This is just great. Yeah. Agreed. We have a whole ton of data from. From. I'm just cheering with the bill. We're talking about now some of the stuff we actually did at the community summit. The day before. You can't. Finally, I'll get time to, to move on. So I would say from, from community perspective, it's really, really nice to see that we're putting, putting. People on staff to help us up with this because it's, it's a lot of things we need to fix. Yeah. Great. She's great too. She's really go get her. Awesome. Exciting. All right. Next up is the marketing committee charter updates. I don't know who's going to present this. Is that going to be Joe or something? Actually, we're able to unmute her. Yeah. So Betsy, I just unmuted you. And if you look like your, you have muted your microphones. If you unmute yourself, you can type up. Okay. Perfect. Awesome. Can everybody hear me? Yeah. Okay. Great. Okay. Great. So yes, this was one of the first tasks. So I rotated in in January and prior to that, I believe you guys had spent some time developing a process for selection and approval of the chair position. So we are just proposing to revise the committee charter. And then we're going to do a selection and approval process for committee members. And as the summary says, this just is limited to the composition and selection section, which is listed below in its current form, followed by the proposed form. And we have established a term length of one year. And a rotation of incoming chair or committee members in order to kind of to continue to have continuity between the committee members and not having everybody rotate in at once. The other big changes that we're proposing to provide the size of the committee down from 15 to just five members. And to start to leverage the power of more volunteer contributors to accomplish the committee goals. And we have also dropped the requirement since the committee will be a lot smaller to just include one board member or an advisory board member. The previous requirement was that there was one of each on the committee. And then the other one was just removing the provision for the meetings to be open to all Drupal Association members, but that they are open to all Drupal Association staff. So I guess, does anybody have any questions or concerns at this point? Um, could you, could you repeat the, the last thing that you said that it used to be that it would be open to all Drupal Association members. And now we're talking about Drupal Association staff. Yes. Can you talk about that just for a second? Yeah, I mean, I guess that was, so one of the goals of the committee is just to be very focused on moving actual items forward. We didn't, I, I don't, if that's like a big sticking point, I think we can definitely add it back in, but we were just thinking that for the sake of efficiency that we would just kind of keep the committee meetings focused and provide follow-up as to what we're doing in the committee. Has there been a lot of, a lot of noise coming from their community as a whole? No. There's been, I would say that lack of involvement has been one of the problems for this committee. This is Joe Saylor. I'll just add the last bullet point there is meant to accommodate, for instance, myself being able to join the meetings without needing to take an actual spot, one of the five spots of the committee. Right, right, I get that, I get that. It seems like if you're, we were talking about, and when we talked about Drupal Association members prior to that, are we talking, what do we mean by that at this point? Well, I think, I guess it would be anybody who is an active Drupal Association member. So we're going to, we're going to, we're going to, so I guess what I'm trying to figure out is if we're, if we're trying to, if we're reducing the possible number of people that could, that could come to one of these committee meetings, is that the goal? I think, so I think the goal, the overall goal is that what we saw with the previous committee is that there were a lot of people that were opting in to be on the committee, but not fully participating. So in an effort to re-energize the committee this year, we're looking at having a smaller committee that's really focused on taking leadership roles in different areas, and then leveraging a larger like volunteer community to kind of help with the actual execution of those initiatives. Okay, I get that. Sorry, I'll go ahead. Sorry, I guess I'm caught up on the sentence, committee meetings shall be open to Drupal Association staff. Okay. So that, that, that, that to me, that to me yells, I, we don't want people to, to, to be involved. And, and, and, and it reads to me, it reads to me personally as, as, as something that's reducing transparency. And that troubles me. Okay. So it's possible to use wording along the lines of what you just said, like, you know, the committee should be open to anybody who's willing to basically do something. Yeah, I mean, I, I, you know, this is, like I said, this is just a proposed draft. So yeah, I mean, any of that language can be changed. So, but like, I think that would help get it to, because yeah, I agree with Matthew. I think if, especially if the diff or whatever is, is, is like supplied on this, the community is going to reach the wrong assumption here, which is that we're closing off marketing to community participation and making it a DA thing only, which is actually the opposite of what you're trying to do. What you're trying to do is involve community participation, but just have a smaller group kind of calling the shots. So you guys can actually make decisions and do things. Right. So, okay. So I mean, if we drop the line about it being open to the Drupal Association staff, I'm assuming that doesn't prevent Drupal Association staff members from actually attending the meetings. I don't think it does. So I think, yeah. So, and I don't actually have edit rights on this document, I believe. So, Holly, if you want to just go ahead and delete that, that's, I mean, I think that it sounds like everybody's in agreement on that. Yeah. Personally, I was fine with the sentence. I didn't, I mean, I guess it was, it could be interpreted, but in my mind, it was not a negative sentence. Alarm bells went off for me personally. And I believe you. Okay. So what if we juxtaposition that you were removing, removing provision for all of these people and adding provision for just staff. I think it was actually the proximity of those two things seemed like it's reducing. So I think the, the line could stay because it has clarity that staff are welcome and staff are part of this process, but it probably just needs somewhere else for it to have that broader, that sense that, you know, all are welcome, blah, blah, blah, but we need to get on the things. Well, so in the, in the previous sentence, it says the committee may choose to organize itself in the subcommittees to facilitate the accomplishment of its work. And I mean, could we just add like comma and any Drupal association member in good standing is, you know, encouraged to participate in these subcommittees. That's a volunteer capacity. I think that sounds great. And, and, and is the, is the assumption that, that because it's all community members in good standing is the assumption that we have some association staff that aren't in good standing. And that's the reason that they need to have a special, a special status because it seems to me that if we, if it's open to anybody in the community, then it's open to anybody in the community. So the language is actually Drupal association members. So there's a, there's actually a payment involved there. So the good standing part of the means if they are in arrears on their fees, totally, totally get that, totally get that. I'm still caught. I'm still getting caught up on that last sentence. If we're talking about leaving it in because then, then the, the sentence implies that, that, that folks in who are on the Drupal association staff may not be Drupal, Drupal association members themselves in good standing. Anyway, I'm, I'm going to leave it at that. I personally think just blitzing the sentence does the same thing. I think we should blitz the sentence. I think it should be gone. Unless, unless Joe was that put in there because people were talking about it. I mean, I don't think any staff is not welcome because that doesn't make any sense to me. Not at all. Just trying to put it in black and white. That the staff would not be taking any slots on one of those five slots. Yeah. Yeah. And that's cool. Then we should say that. I think what I would propose is that, that that sentence be revised to say. Drupal association staff are also available to participate in committee meetings. So, I think it's also eligible or available or whatever. Cause it sounds like that's the clarification that you want to provide. Yeah. I think if we just leave it there, then it's, it's, it accomplishes what everybody's trying to get at. Plus one. So edited. Great. Looks good to me now. Are you okay with that? Yeah. No, that sounds good to me. Okay. Any other comments or marks, questions? Thank you for doing this. I appreciate it. Yeah. No worries. I agree. We'll be. We'll be good. If we can sort of. Re-start or like get some more momentum. For the marketing committee. So if people like this. Maybe somebody can. I'll move that we accept the proposed language for the marketing committee revised charter. Second. Great. All. Maybe all those in favor say. Hi. Hi. Oh. We get a second. Yeah. There was a second. Yeah. Yes. Yeah. All right. Let's try it again. All those. Yeah. Hi. Hi. Hi. No one seems to be opposed. Right. Yeah. Is anyone opposed? If you are saying. All right. That's approved. Thanks you guys. Thank you. Great job. Thanks. All right. Next up. The branding updates. Yeah. So this is Joe again. Yeah. Yeah. So this is Joe again. And one of the things that I've noted inside. I've been here for about a year. Probably if you want to go to the first slide there is. That we have some. Visual identities that are. You know, perhaps outdated in some cases or other cases, there is no visual identity for a, you know, a given program. And one of the. Most. Acute issues I think we can all agree with the badges. There have been a number of attempts. To update the badges over the last couple of years. And a few months back, decent volunteer to create us. Some new badges. So we've actually rolled these. I may have seen some communication on. On these new badges. And we now have not just a member badges for individuals and organizations, but we have badges for. Partners. And board members as well. We really like these. We've gotten great feedback on them. And we thought that it actually was a good opportunity to take a look at these badges and. Think about. The overall visual identity of the association. And. One of those things is the Drupal Association brand itself. You see it there on the top. That, that logo, if you will, it's not really a logo, but it was created. It's actually created. Along with several other treatments, Drupal groups, for example, as a way to give a consistent visual identity to the Drupal dot org subdomains. So it wasn't developed with it being a logo. In mind. So what we've done is we've taken this. This badge design. Try to try to. Try to take it a step further into. Why is this? Go side to side, not up and down. There we go. Into a new logo for the association. So you'll note that the icon mark there on the left. Is taken directly from the center. Drop from the badges. And then it uses the Drupal wordmark. And instead of the association being out to the side in an in line format, it brings the association wording down underneath the Drupal wordmark. And then what we hope to do is take this look and actually extend it into a visual system that we can use on other things as well. So global training days, for example. And grants. Scholarships. And other things that, you know, part of the goal here is also to create some consistency. So people know when they see something like global training days, they understand that that's a Drupal association program because we know that there is a lot of confusion about the programs that we provide today. And I think part of that is due to the inconsistent visual branding that we have. So a couple of notes about that logo. It uses a flat design, very simple design that, as you probably know, is very much in style these days. And I think Apple is really taking the lead on the flat and simple design. And now everyone seems to be adopting it. And so it is very much in style right now. Again, the drop shape is taken directly from the new badges. And again, we do hope to extend that look into a visual system. Not sure exactly what that will look like yet, but it will no doubt continue to use that drop within the blue circle and apply it where we need it. And also with our existing brand with the Drupal and Association out to the right, it's a very long and thin implementation that we have a lot of difficulty placing in spaces that call for a more square or a tall image. So we'll have a lot more flexibility around that. So next steps is, I hope to work with a designer to extend this visual system a little bit to things like global training gaze and community grants and things like that to try to create some consistency. And we hope to roll out this new logo probably in the next month. I actually need to come up with a plan and a timeline for rolling this out and communicating it to the community. But my hope would be that it would be out there by next month. And then the visual system with other things like global training days, et cetera, would be probably more toward the end of next month or possibly in June. So any questions, thoughts, concerns? Joe, this is awesome. I'm very happy to see this. I have some design proposals or ideas to it, but we can take that. I'll find no reason to use people's time here. I have a ton of ideas. I'm not a designer, but I think it's a massive improvement. Yeah, I think they're gorgeous. Thank you so much, Joe. I'm one of those people who have been tracking it. Oh, my God, can we get our badges changed already? And it's so nice to finally see it done. Thank you so much for bringing this home. It's great. I would love to see these as stickers at DrupalCon in Austin to see that stuff on people's laptop. I think that would be a pretty badass thing. I know that I've been carrying on a small little Drupal Association sticker on my old phone. And kind of the amount of people who asked me into that sticker was pretty high. I've got one to manage. That's actually a great idea. That's a wonderful idea. Have little individual member stickers or whatever on your laptop. That's amazing. I do think they've bought me what we should have like a crown on top of it. I don't even know if we need to announce this to the community versus just like just changing. I would like to see us just changing it and then work. I would love to see the, you know, as the staff moves forward, you know, designs. When you put that into a design manual, space is for non-profit organizations like us, it gives sense to have a design manual, but you don't want to lock yourself down. So, you know, when we're working with designers, we find new ideas and new things they could improve. We didn't lock ourselves in. That was kind of what we did with the old design also. We had to be there. I do think as general direction, this is a wonderful starting place. I would love just to see us begin to use it as quickly as possible. Agreed. I don't think the idea is to do a big press release and everything, right? But when we do the changeover, we probably put a post up on our blog that says... Yeah, we did an update with the new badges. Just, you know, hey, here are the new badges. We hope you like them. I think we should be updating the logo. And so my thought was just like another blog post saying, you know, hey, as a follow-up to the previous blog post, here's the new logo. And that's pretty much it. Yeah, I'm not sure about it. Versus going through a feedback cycle. Oh, yeah. Yeah, no. Honestly, I think we should just move forward. The old logos is a complete miss. And if we first open up this bike shit, I could sit here and use a couple of hours and find about the college terms and stuff. But I mean, let's just move forward. I agree. Let's not backshed it. Yeah. All right. Great. Even though I hate the gray and the dual association logo. Sorry. Sorry I came out. I couldn't keep it back. Yeah, let's start. Let's try. Let's try more. Great clean move on. Great clean move on, too. I will hold my hand over my mouth. There we go. We're on to a new topic. Look at that. Great job, Joe. Let's start with procurement policies. Okay. So that's me. So this is work sort of started out of actually the, for me, started out of our conversation last January and January of, or February of 2013. It's my first board retreat. One of the things we started talking about is the financial policies and procedures. At least they did that with Tiffany. And I had a few side conversations with folks about the need for some kind of policy to govern how and why we pay people versus ask them to volunteer. And so we need some guidelines in place. We put a draft together earlier this year. Put it up on GDO and the ADO blog asked for feedback. Got some good feedback and incorporated it. And I know we didn't hear from everyone in the community, but we did hear some good feedback. And so with that drafted this policy, which I sent over to you guys a little bit earlier last month, I think. So you've had it for a little bit of time. But the basics lays out two things. One, how do we know when we want to pay someone versus ask for them to volunteer? And we've designed this so that it's not, there are no hard and fast rules. But these are the kinds of considerations we would take into account and would lead us to say we think it is, you know, paid versus volunteer. So for example, if it's something that needs to be fixed by tomorrow, we might not want to spend the next 24 hours finding a volunteer if there isn't one that's super self evident, right? We would spend that time instead maybe paying someone to take care of it. Maybe paying someone, even if they're maybe paying the person who might volunteer because we're going to interrupt their whole schedule to get it done by tomorrow, right? So responsiveness and urgency is mission critical. If the thing is something that impedes core development, for example, that might lead us to think about, is the project discrete? So is it something that, you know, ends? Like you do it and you can walk away? Or is it something that goes on and on forever? Discrete projects are better suited towards volunteers, but of course we do have a long history of volunteers like Jeremy and Narayan who have been engaged in sort of never ending sagas forever. You know, we also have a long history of being extremely tired, occasionally grumpy, right? So we don't want to burn those guys out. So that's a consideration. If it's a unique skill set, so you know, if it's something that is particular to just a few people in the community, I think an example here in particular is there aren't a ton of people that really know their way around project module, for example. That's a consideration. I think it's something that volunteers to work. So if it's something that actually creates an improvement to the Drupal.org contribution process, it might be worth paying someone to do that work to get it out there faster to increase the participation velocity of more volunteers. And then of course, is there a volunteer there who's just ready and willing? Because sometimes there is and it's a framework, but not a, you know, these conditions are not mandatory, right? And of course, all of these would still be governed by our contract rules. So if we decided to go the contractor route, we would then be bound by our competitive bidding policy. So anything over $25,000 we would bid out. And then the other section in here is in kind trades. And the concept here is that we have companies that want to provide us with services in exchange for promotion or sponsorship opportunities, things like that. And so getting a policy in place allows us to take, make use of those trades when they're available to us. And again, we set up some bullet points that we would consider a framework for it. So I think the two most important things, we actually have, we do have lots of folks that come to us and have ideas and want to fuse their product, but we don't really need it right now. And sometimes they want to, they want to offer up things that we probably do need, but we really don't have the staff or capacity to use it, right? So we're not going to make trades for stuff just because it would be nice to have those things when we can't actually make use of them and get the value out of it. So if someone was offering us a service of, you know, $25,000 or more, we wouldn't just take the first offer that came along. We would actually say, hey, we need this thing and we're willing to entertain and entertain in-kind trades for it. Anyone who's interested in bidding, here's what you can do in his process we go through. And of course, to keep it all legal, all goods and services as part of an in-kind trade will be provided on our books so that they are nice and clear for the auditors, but also nice and public for the community. That way everyone knows what we're up to. So those are the two pieces. Questions and comments about that? Very quiet. I think that it's clear, makes sense is it makes very clear how we want to behave and exactly what a policy ought to do. At least the spirit of the language that's in here I think is really good. Might need a little bit of forward smithing, but by and large I think that the spirit of the language in here is really good. I did forget the one rule that I really remember from English class, which is the word very stupid and you should never use it. For me it was also very clear that my English isn't good enough to do word smithing. I'd be happy to help word smithing if you want. I told the same connoisseurs that my English isn't way not good enough to do word smithing on their own. I'm hoping that we can adopt it today. I'm not sure if we want to do that and then word smith it. We certainly don't want to adopt it and then word smithing because we'll need to. What word smithing, sir? I just, you know, it's very it doesn't read like a policy to me. Which I actually see as a benefit. I actually like it the way it's written. So I'm actually supportive of moving forward with the policy as I think it's very easy to understand for a lay person. It's consistent with the tone of the policies that we've been turning out. So I'd rather not delay. I think it's had enough review and I'd like to see it put in place. I think we need it. Yeah, I second that. I think let's just get it done. I don't think it needs to be perfect. And the perfect is the enemy of the good. And this is good. Let's get it done. All right. If anybody want to hammer holes in it, yeah, let's rather get moving. I mean, that's the change in being proactive, right? So we don't use all our time on small details. So I actually would move to approve it as is. Second. All right. All right. So let's everybody that's in favor say hi and people not in favor say no. Hi. Hi. Hi. Hi. All right. Were there any nays in there? No, we're not. I didn't hear any notes. Awesome. Thank you. That is also approved. Thanks for all the work in this. And the feedback from the community is awesome. Not only thank you to Holly and the staff, but to everyone that helped. Yeah. Thank you guys. One more vote. And the next vote. Is extending the at-large director term. My one. Holly, do you want to explain this? Yeah, sure. So in our last board meeting, we don't have prepared a proposal and we voted to approve a proposal. Not we, you voted to approve a proposal. To change up how we do elections so that we're. At-large director terms are now two years and one director is elected every other year so that their terms are staggered. And we, we got that part all approved. The thing that we forgot to do, although we discussed it, we didn't formally vote on it. The thing we forgot to do was formally extend Matthew's term by one year so that he would be our first two year term director since Morton in effect has done that by being elected a second time. So, so, so we need to vote to do that for. Matthew's term. Matthew also needs to agree before we do that. Yeah, I've already, I've already spoken with Holly. I'm happy to, I'm happy to do it. Cool. So I, I, I move that we extend the current, the most recently elected at-large director's term being Matthew Saunders by one year so that we can move to two year staggered terms. I will second that. Any objections? Can I reword the vote as do we move to, you know, do we accept Matthew's term to be extended until, what's the date? Would it be February of 2015? 15. 2016. Now his term would run to February 2015 automatically. That's his year plus a couple of months. We voted this year? We voted last year. Matthew would have started in officially on the first of November in 2013. Okay. Start of Matthew's term. So we're doing two things. I mean, it would have been from the first of November 2013 to the 31st of October 2014. So we're wanting to extend out to 2015 for the reasons that we discussed last time. And then so Matthew's term would be through till February 2016. February 2016. Okay. Great. Sorry, I just want to be precise because I, what I didn't attend the last board meeting and I just want to make sure what I write down is factual. So the vote is do we, do we extend, do we agree to extend Matthew Saunders term until Saunders' term until February of 2016? Excellent. Correct? Yep. I move that. All right. Yes. Seconds. Anyone second that? Oh, more than you did, didn't you? Three seconds. Oh yeah. As a printable, I think that that makes sense that. So yes. Any objections from anyone? I'm good. I'm going to abstain from the vote. That's a good idea. I think it would be a wonderful way to start. I believe yourself in. Yeah. We do politics right. All right. Well, nobody objects. So I think we can also approve this. Yes. I assume it will be stuck as a little longer. I'm all right with that. You're good. You're a good lot. So much voting. Right. Any, any final comments or remarks from anyone? Before we move to executive session. Well, thank you everyone for meeting. I think we're on track probably to, to finish on time. We're going to adjourn and then switch to the other conference bridge. Thanks guys. See you later. Thank you everyone.