 Andrew, you'll be taking notes, is that right? Or did we change that? I was going to ask. I can read this here today. I am, and I am taking notes. I just made a doc, and I don't know. Anyway, I don't know how to find you. All right, well, you guys sort that out. I guess we get started. As usual, we have an open session followed by the executive session. So for the open session, the agenda is in the board packet. But for those that do not have access, I'm going to talk about just an operational update as we do normally. And then you special agenda items today, a little talk about time management and our board meetings, or meetings in general. And then we're going to do updates from the different board committees. Very quick two minutes for each of the five committees. And then we get an update on the content strategy, as well as an update on the advertising strategy for Drupal.org. So with that, I'm going to give the floor to Holly for the operational update. Thank you, guys. So just a few notes about some of our key areas that we've been working in from the month of January. You'll learn that the whole board packet has turned over in terms of the metrics that we're reporting on. Just to start with, then I will just make the callable announcement that we're definitely going to be working on how those are presented throughout the year. So last year, we got in a habit of collecting data and trying to use that more to understand where what it says about our work and what kinds of tricks we need to make. And we present that in table format throughout the year in the board packet. And we are currently working on revisiting, having to present that data so that it has a little more meaning behind it for you. So you'll see those change from month to month as we implement some new systems. But I wanted to say a note about that. And if you have questions or feedback or thoughts, we definitely want to hear those. If there's something that does or does not work for you, definitely feel free to send me a note as we work out our dashboarding stuff. So the logistics aside, some of the highlights from January. Obviously, we're all starting to work around releasing Drupal 8 with the community. So the de-accelerate program kicked off strong in January. Huge thanks to the branch. Sorry. Holly, I'm finding it really difficult to actually hear you. I can hear that you're speaking and that it's just a bit fuzzy and indistinct. Can you get close to the mic or something? Yes. And or it's totally ignoring the mic. Oh, that's so much better. Thank you. That's so funny. We moved it like six inches. OK. Thank you. I'll also face the microphone. That also helps. Good deal. So we, as I was saying, we're working on a Drupal 8 accelerate that project a lot. And I wanted to send a huge thanks to the branch meetingers and Angie in particular for all their work to vet the proposals that come in and also get to give them things that they want to see funded. We've made nine grants so far. Lots of entity field work in those grants, but also a couple of events, including the Drupal Camp New Jersey Sprint where they did a lot of work on menus. And our next big sprint that's being funded through the program is a CI sprint that'll happen at the end of March. So Jeremy and Nick and actually Shyamalan, a number of people from the community will be here in Portland working with the Drupal.org team here to get that next set of testing issues tackled for the Drupal 8 team. So we're excited about that program. And we've definitely seen an uptick in community submitted applications lately, which is good. So hopefully we'll see more of that and more ideas from the community. On the roadmap side of things on Drupal.org, the team has really been working hard at the board and working group priorities, in particular, better account creation and log in. So I think we have the majority of the account creation improvements in place. And this has been huge in both making it easier for folks to sign up for an account in a meaningful way while also reducing the number of spam accounts that we have. And so the next focus on that side is on the user engagement path. And you'll see some notices go out to the community about some of the work that we've done there so that we can give our folks the right level of permissioning on the site as they engage with the community. Issue credits is another area on the roadmap that we're still working on. We've made an initial commit on that issue. But the progress has definitely been slowed down by a couple of things. One is a set of internal projects. We moved Drupal.con sites over to events.drupal.org. And that was a huge lift. But it will hopefully the ideas end up giving us more time or end up making sure that we spend less time launching each new site and also getting elections off the ground and improving on the experience that folks had last year. And also, I think that the other thing that really slows that work down is that we're excited because we've had a lot more community contributions to Drupal.org lately. But we're also then responding to those community contributions. So that definitely takes up a chunk of time. So it's going a little slower, but we're still working on that front. On the Drupal.con side of things, not technically in January, it happened technically in February. But Drupal.con Latin America, we did one. We had one. It was a big moment for us to actually get that done. And the event was really positive. And I just will have lots more details for you next month. And there's some more detail in the packet even. But I just want to send a huge thanks to Hyro and Camotek and all the folks who helped us pull that event off. Nixida, Leandro, really helped make that a wonderful space where I think we've really learned from each other through that process. So it was wonderful for that. Los Angeles is launched on events.drupal.org, as I just discussed, which is great. Reg should be opening up very shortly this week. We should see that open up, which will be great. And also, I just want to make sure that everyone is aware that we are getting ready now that Latin America is behind us for our next Drupal.con in another location. And we're planning Drupal.con Asia in India. So Megan and Rachel took a site visit in January. They visited a number of cities, really spent time with the community to understand what their needs were in general in India, as well as what each community looks like in those locations, which is pretty amazing. And I have to say that the most amazing part is just the reception that they got from the community. Everywhere they went, the community put together events specifically for them and really showed them the best of what's happening in India. So we really are excited about that event. Things could be really spectacular. That's the momentum on the Drupal.con side of things. And then the other big push right now is elections for the board, of course, the at-large seats. So we launched nominations in January. Right now we have 18 candidates who have nominated themselves and they represent 12 countries, which I'm really excited about. We have much more Drupal representation than we did in the past. Several folks from Latin America, several folks from Europe, someone from New Zealand, someone from China. So I think that those are all really good, positive steps. That's awesome. Yeah. And two women, so I'm gonna take it. Although I did tweet yesterday, where are my ladies at? Nomination closed on Friday and then meet the candidate sessions are next week. So I'm just scheduling people into those meet the candidate sessions now. And then just a reminder about the schedule. Voting opens on March 9th and we'll run through the 20th. And then we'll be able to, we'll ask the board to ratify the results via email and make the announcement publicly on March 25th. March 9th through 20th with voting and we'll announce it on March 25th. So I think those are the highlights. Any questions from the board packet? I think there's no questions. All right, well, I think we can keep moving then. Thanks, Holly. That was great. Some exciting updates, a quick item that I wanted to tackle real quick is that after the board retreat and after some of the last board meetings, a couple of us huddled about how we can do a better job of staying on time in some of our meetings. So we've, the last few meetings, we've kind of run over every single time. And so we all agreed. Those that were part of this conversation we should do a little bit more time management. And so as of today, we would like to try two things. One is time boxing, the conversations. And as you can see from the board packet, for each of the agenda items, we added how many minutes we want to talk about each of the topics. So that's a new addition. And so I'll try to help manage things towards that right now we're doing fine. We started actually five minutes late with the call. So we're actually right on time. The other thing that we would like to ask people to do is to save your questions to the end. After each topic, we can use the remaining minutes that we have to do Q&A, but not to ask questions during the actual presentations itself because chances are these questions will be answered later. So we're gonna start with these two things, you know, time boxing and saving the questions to the end. Hopefully that works. If it doesn't work, we'll try some other things. There's many other things we can do, but we figured we would just start with these two actions. Is there any questions on that? Yes. Angie asks if we should use the question box and go to meeting. That's right. So that's also a very good thing to do so that whoever the presenter is of a session or a topic they can look at the questions in the go-to meeting. And if we're limited on time, that person can pick maybe the most relevant or the best questions or whatever judgment he or she may want to use. And then if not all questions are answered, we can always answer them after the call or an email or some other means. Great question, Angie. Any other questions? Awesome. Well, in that case, I suggest we keep going to make up a little bit of lost time in the start. So let's move on to the board committees. So two minutes each, starting with the revenue committee. Sure, this is Megan Sanaki. I'll just make mine short, but January was looking really good for us this year with revenues and we are just keeping our eye on Drupal jobs. Carrie is going to give a presentation of where we are with our digital advertising in Drupal jobs. And we're also pulling together the Drupal 8 Accelerate Fundraising Campaign. And so that's something that we'll be kicking off publicly in the next couple of weeks. In the executive session, we'll be talking more about that and Jeff can give an update there of some of his initial efforts. And also, I just wanted to point out that one of the things we're doing to grow the revenue team is we are staffing up. We've already hired Rachel Rivera as our junior sales rep working on Drupal jobs and we have a position open. We're currently looking for someone to be our digital ad sales rep. We're already 33% of goal right now for the year. We had some great early wins. There's lots of room for growth and we're looking for the right person to help us accelerate revenue in that area. Awesome, that was it? Or was there more? That's it. All right, thanks Megan. Governance. Governance. We didn't meet this past month. However, we did make the changes that folks asked for the language for the bylaws and we're looking to get an email vote on that. Very good. Finance. So Finance Committee did not meet in person but we did review the October, November and December 2014 financials and notes by email and we'll be presenting those in executive session today for board approval. All right, thanks Tiffany. The executive committee, we didn't meet. We can go straight to marketing. All right, I am still working on finalizing commitments for members of the committee. So I hope to have our first meeting next week where we can build out more of an official plan and so hopefully the next time that we'll meet I'll be able to give you a list of who is on the full marketing committee. All right, great. So a reminder that that was Gina Montoya, marketing committee chair extraordinaire. Hello, hello, thank you. Yeah, thank you and you know, welcome. All right, is there any questions on the board committees? Just to disappoint the exact committee we did meet. Oh, we did meet, I'm sorry. Sorry. We talked about time-boxing meetings and things. That's right. We did meet about that. Direction in the minutes, please. As you see it. All right, any other questions? I have a feeling. All right, great. All right, so let's move on to the content strategy updates, please. All right, close that out and move this down right here. Yeah, just so you know, they can't see that on the screen, so you're fine. They can't see questions. Okay, perfect. All right, I'm going to kind of walk through this as quickly as possible here. So as most of you on the call though, we started the content strategy project earlier this year with the objectives to improve quality and findability for all of the content on Google.org to reframe the Drupal project around user roles and proficiencies, really taking a look at that user research that we've done in the past and using that to make all of our decisions or at least a large portion of our decisions, to develop a content governance plan for Drupal Edward to work on the quality of content on Drupal Edward and also to have a real focus on user engagement and helping to promote contributors that are giving back to the project. We've been working with Forum One and one of the things that we noticed in this project pretty early on is that it takes a while to get a new contractor up to speed on just kind of the scale and scope of Drupal.org. It's a huge site. I often throw around the numbers of 1.2 million nodes and 2.4 million comments and that's an awful lot of content. And so it just takes a long time to get people up to speed with a lot of the history, a lot of the background. I felt this myself when I was coming on board with the role of CTO. So to get them started, we gave them a whole bunch of background documents. We walked them through the content ecosystem, all of the subsites of Drupal.org. We showed them all the communication channels that we've documented and we know that we have. We did an initial content type inventory that shows content types over, content type counts over time so we can kind of see what content types are growing and shrinking on Drupal.org. We also did a user task to content type mapping and a current site map. This is a very high level site map but it's gonna be important in some of our ongoing work. One of the things that we were really trying to get out of this project was a messaging framework and part of that messaging framework is a series of what we call big ideas. These are, I've heard it described by some community members who reviewed this is very marketing in terms of the language being used and I would say that's absolutely correct. These are the big ideas that we used to really market what Drupal.org is, what Drupal the community is. So people need to know that Drupal.org offers the best Drupal resources on the web that is supported and maintained by a welcoming and cross-disciplinary community of Drupal practitioners. So that's one of the big ideas we wanna throw out there. Related to that, we want to inspire people by the wide and active global network of Drupal users and their passion for the software and we want that to come through in all of our messaging that we're using. Joe can talk to this a bit too but we're definitely collaborating between our marketing and communications teams and the Drupal.org team to make sure that we're kind of infusing everything we do with these messages. The next big idea is to get people inspired in order to get people inspired we need to confirm their opinions about Drupal by making it easy for them to find community conversations, user resources and the vast catalog of contributed projects, case studies and really show them opportunities to learn and build their proficiency around Drupal. One last big idea is to cause them to use Drupal, create a user account, post a question, attend an event, volunteer and contribute to the Drupal project. We don't actually expect that every single user will do all of these, but as many users as we can get to convert on all of these activities, the better. And these are some of our key measurements of engagement with users is that they're doing these types of activities. I keep popping back up the user research, reminding people that the real focus of our efforts is that transition from learner to skilled and that talks a little bit about getting people to build their proficiency so getting them out of the I'm learning about Drupal to I'm actually doing things with Drupal and ideally that they've moved into that area that they're making some part of their income in a Drupal related field. Project deliverables for the content strategy project, we have quite a few deliverables in here. The vision brief which has been shown to the board kind of outlines those big ideas. There's also some key messages and the objectives that we started with are all included in that vision brief. We have a content audit template in place and we're gonna be starting soon working on what our content audit strategy is going to be to make sure that we know what the majority of our content is. And we've already done one thing in this area that was really fascinating. We took and we looked at our books and we were able to calculate that of all of the book pages created on Drupal.org, 35, I'm sorry, I just saw that sound drop. Can you guys hear me okay? Yes. Okay. Okay. Sorry, Matthew, it was just you. So one of the stats that we found is we were really digging into the research is Drupal 7 having been released in January of 2011. If we look at everything prior to 2011, it gives us a really good litmus test of content created before Drupal 7. And book pages, 39% of our book pages were created prior to 2011. Of that 39%, 25% of all book pages from that timeframe, or I'm sorry, of all time have been updated. So basically we have this kind of sweet spot of about 24% of our content. You're right, Tiffany, those are different. I actually have a graphic up here that'll give me the correct number in just a second. But 25% of our content on book pages has not been updated since 2011, even though it was created prior to 2011. That's the stat I really want to get across. You have three minutes left. That's good, I've got like two minutes of content I can get through. We're also working on a site map, taking that high level site map that we currently have, updating it into the new one. We're working on a governance and community management plan. This is gonna be a really important deliverable. It's gonna take a lot of work with the working groups to make sure that we get something that we can share with the community that we think they're gonna buy into. But the idea is if we're gonna improve quality, we're gonna have to implement some workflow and content lifecycle into the content that we have. To address those things like the 25% of content that hasn't been updated, even though it was created in this case almost five years ago. On-going staff work, we continue to map our message to our audience and our audience to our channels. So we have a full map of when we communicate with different user types and what messages we approach them. We're also doing some work to do some rewriting of key content. We're working on communications editorial calendar. And we're trying to define the role of community manager and what that looks like. We certainly have community managers in the community right now. A perfect example would be like Angie, that's her title with Aquia. But as it relates to Drupal.org content and onboarding new people as they're coming on board, we wanna make this a little bit more formal and we think that there's a need to staff up in that area as well. That's certainly one of the recommendations that's coming from forum one. And here's that stat I was talking about. 55% of Drupal.org book pages were created before Drupal.7. 32% have been updated since this launch, which gives us that 20. One. 23. 23% of all book content. See, I should have had that before I used that stat, sorry. 23% of all book content is essentially out of date and has not been touched since Drupal.7 released. Rollout planning, we have a lot to do. I'm actually in the process of meeting with the documentation working group, the content working group. We have our all working groups meeting next week to kind of reiterate much of the progress that we're making. I will say that this presentation here is almost out of date already because we have a content model that we're gonna be putting in front of the working groups for feedback starting this week. So there's some really exciting work in this and I think we're kind of, we keep stumbling across new things that are just showing us just how vast our content library is from our community generated content. And we're coming up with some great ways to kind of restructure it and make it a lot better quality, which I think is gonna help Drupal in the long run. Joe, is there anything you have to... No, I think you can come with it. Okay, cool. All right. Did I make it on time? You made it just on time, excellent. I'm actually, I don't actually don't know if the time includes time for Q and A. I actually also don't know if there are questions. I don't think I can see the chat. The ones that popped up, Tiffany pointed out that the stats were different on what I was quoting there. I should have had the number in front of me before mentioning it, but the 55% of all book content being created before Drupal 7 was the real thing that we wanted to kind of throw out there is that we've got a lot of content that is years and years old. But that was the only question, Dries, so. All right, good. Yeah, I don't think, I think only the presenter can see the questions, maybe. Yes, I will look, work on next time I get the mouse back, I'll see if I can let you see the questions. All right, yeah, no worries, or it can help me manage the questions. There's no question. Then, Josh, I think is very helpful. And then the last part of the open session is the advertising, and we have 20 minutes for that, so. All right, and that includes time for questions as well. So hopefully I can, my primary focus is gonna be on our advertising strategy for this year, but if time permits, I'm gonna give a brief update on jobs and then open everything up for questions. So just a quick update of our goals and your today revenue so far. I just wanna pause you and say, welcome to Carrie Wessina. Hi. Hi. I don't think you guys have heard from before, but I wanna make sure you know who's talking. Carrie. Welcome. Thank you. Another voice to memorize. Yeah, exactly. So our goals for Drupal.org web ads, as we're now calling it internally, digital advertising is $250,000 for the year. And as Megan mentioned, we're pretty strong there. Year to date, we're at 34% already. So there's a lot of room for growth there, but we are making good progress so far. And then Drupal jobs, the budget is 216,000. It's a little bit soft right now. It's only at about 5%. We should be closer to nine or 10, but I'll be talking about some new marketing initiatives that we're working on to try and remedy them. So since I started here in October, I've been doing a lot of research and trying to address some of the challenges regarding our new initiatives and our existing advertising opportunities. So I've been doing a lot of interviews with the Drupal Association and a lot of the board members, community members and then various Drupal businesses, both large and small, just to get a good scope of what our marketers are looking for and what the community will support on Drupal.org. One of the challenges that we need to address is that while there are banner ads on the site right now, there's a relatively low amount of pages on those pages. So one of our initiatives is to continue to grow that traffic and grow those opportunities directly on the site. Something that we need to be aware of is that as an industry standard, larger, more intrusive ads are becoming the norm. So it's not necessarily the direction that we're gonna go in, but it's just something to keep in mind as we're trying to compete with, I guess, other potential publishers. And on that same note, there are a lot of concerns over the user experience and the community impact of these new initiatives. And we're trying to be respectful towards the Drupal Association's engineering team. They've got a really big roadmap this year, a ton to do, and while we're gonna need their help, we're trying to be completely disruptive. We're also working towards addressing the shift of programmatic advertising. What that is is data-driven, real-time, automated buying and selling of digital media. So if you take a look at this chart over on the right, this shows total US ad spend in the programmatic category. This year, 55% of all digital advertising spend is expected to be programmatic, and that's gonna jump to 63% in 2016. So in addition to ramping up our direct sales force, there's a really keen focus on some programmatic efforts as well. One way to do that is to introduce ad networks and exchanges on your site, but that does pose some risk. Ad quality is really hard to monitor and maintain as is the ad's relevance to the Drupal community. And there are relatively low prices just because of all the middlemen involved. It's definitely a volume game. So when you think of kind of the risk reward, it's not necessarily worth it at this stage in the game to introduce that risk to our site. And here's an example of what... Sorry. What a typical publisher portfolio looks like in the advertising realm. Many publishers are employing this barbell strategy where on one side of the spectrum, there's a premium direct sold side, and on the other side, there's this programmatic automated side of things. Their inventory could include display advertising, which are basically banner ads on a desktop site or mobile or in a newsletter, email marketing. So for example, renting out a list for dedicated mailers and the various custom programs, which is basically a way to describe anything that's not a standard banner ad. So it's more out of the box or outside of the box. And then some sort of indirect or programmatic efforts, which could include ad networks, open exchanges, and then private marketplaces. And just to help visualize and explain the difference between programmatic and manual and direct and indirect, this graph up here shows you on the manual side and the direct side, so the bottom right, that would include a direct sales team. So they're calling people and taking people to lunch and sending, you know, insertion orders and sending creative back and propagand. It's very manual. A lot of the shift is trying to address some of that waste and making sure that things get a little bit easier with a more automatic process. And that's where we get to the programmatic side. So in the indirect programmatic side is a real-time bidding platform. So that would be something like Google AdWords or Google AdExchange where people are bidding in real time on available inventory using data to inform their ad decisions. And then programmatic directs. So that's a situation where you might create some sort of automated platform, but there's a wall, so you would have to invite advertisers to participate in it, which is good for the publisher because it keeps the level of quality and control and it does also require some direct sales force. So the biggest takeaways and guidelines from all of this research is that our new product should appeal, not only appeal to advertisers, but also support our users and or our mission. When possible, we wanna monetize users to our logged out and not contributing. We're gonna be handling that in a few different ways, but one way is to avoid the issue queue altogether, but places like the home page is okay because it's not necessarily where people are coming to work. We don't wanna clutter the site or interfere with navigation or disrupt visitors, especially contributors. One of the biggest takeaways that I came across, especially when talking to Drupal businesses, is that these products need to be inclusive, so we really need to focus on offering some low-cost options so that smaller players can take part in them as well as the larger players. Create, we wanna create more high-impact opportunities for our partners and then address this large shift to programmatic advertising. So we get together as a team. Everybody came with a huge list of advertising product ideas and we ranked them against certain objectives like user experience and ROI scale and our ability to execute. And we came up with about six new products. So this is just general category view of what our product portfolio is gonna look like for 2015. So we'll have onsite and newsletter display banners, a dedicated email program, a couple custom integrated programs, and then a programmatic marketplace. And I'll delve into each one of these individually. Onsite newsletter display banners are pretty straightforward. I'm sure you've heard a lot about the content that we're curating, like Josh mentioned in his presentation, that the marketing team has been working on these resource guides and content by industry and eventually blog posts that are not only really useful to our users and there's a big need for it, but it's also a good opportunity to increase our banner inventory onsite and allow advertisers a really targeted advertising opportunity. We're gonna be rolling out an ISV marketplace program. So this is gonna be very similar to what we're doing right now with the hosting listings in the marketplace where a supporting technology partner can bid on a placement here. The ISVs are definitely a market that we're trying to go after more. We're gonna do this pricey model on more of a performance basis just so we can entice them to try advertising on Drupal.org and hopefully expand those opportunities. We are creating an opt-in third-party dedicated mail-air list. So when a user creates a new account on Drupal.org, they have the option to opt-in to special offers from our supporting partners. This is gonna take some time to implement. We started to work the opt-in placements on existing profiles, but it'll take probably at least through Q2 and Q3 to build up this list in a meaningful way. So it's not available yet, but we hope to be able to start sending them in Q4. And these are, I anticipate, being really high in demand. Dedicated mailers usually work really, really well for the partner. It's a win, especially if they can offer something special and unique to the users who sign up for it. So again, it's something that's good for the advertiser, but also benefits the user who partakes in it. This tried Drupal program is one of the first kind of more custom integrations that we're doing. This is a brainchild of Josh. So we've been working on kind of the ins and outs and the details of it. Essentially, it's a lead generation program where a prospective user can try Drupal in a free dev environment. We're gonna be showcasing different hosting partners, but there are gonna be certain tests in place just to make sure that it's a really positive experience for the user. So for example, you have to be able to set up a free account and create a site in under 20 minutes. So it's really a consult though. We're gonna be working really closely with these partners just to make sure while it is a revenue opportunity, it's also a really good, it fills the need of a feature that doesn't really exist on Drupal at all right now. And then the last product that I'm gonna go into in more depth is what we're calling audience extension. It's similar to a private marketplace except that it's all occurring off of the site. It's a secure, anonymous and non-interruptive way to advertise to Drupal.org visitors. And it's essentially allowing advertisers to programmatically reach visitors of Drupal.org while they're on other websites through ad networks and exchanges. So anonymous visitors are tagged with a cookie and then when they leave the site, the cookie follows them and then allows advertisers of our choosing to serve them ads across the web. There are a lot of questions that come up with this often just because it's really different and unique for my thing that we've done so far. So here's just kind of a list of some answers to our most frequently asked questions. It is anonymous. No personally identifiable information is gathered and no data is sold or exchanged. All this is doing is allowing, we're plugging into this larger platform and allowing advertisers of our choosing to bid on a potential ad impression. We're not actually giving anybody or exchanging data. The way we implemented this in a very careful way so that we're supporting do not track browser requests and we're just completely excluding logged in users and any traffic from the issue queue. It also does not conflict with EU privacy rulings. The partner that we're working with to do this perfect audience does not allow you to bid on European traffic and that's how they kind of avoid that. My biggest, the reason I'm such a proponent of this particular product is that it's really inclusive. It's affordable for small businesses. It doesn't cost anybody to join a program. It's a lot like Google AdWords, it's self-serving. You can sign up for free. You don't have to have a minimum spend so if you wanted to test it out for a hundred bucks or less, you could do so. And it's a huge plus that we can monetize the site without flooding it with ads and disrupting user experience. Even though the ads will appear off of Drupal.org, we're still working with perfect audience to vet the potential advertisers and make sure that it's only high quality and relevant advertisers that are able to participate. So this program, it does have the potential to generate a significant amount of revenue as we continue to roll it out and invite more advertisers to come on board and it requires very few resources from the association. The implementation was pretty quick on the engineering team and instead of our sales force we're working with the perfect audience sales force which is much larger, about 15 people plus and rely on them to kind of do the heavy lifting in the selling. This is a general picture of the timeline for when all of these products are gonna be released. It's a little bit hard to read but basically the gist is we're trying to space it out a little bit so we're not completely taxing the engineering team. But we're trying to front load it with some of the more higher revenue generating products just so we've got a nice little cushion that if some of the smaller products have to fall off the schedule we're still really prepared revenue budget wise to do that. That's all I have for advertising so I'm just gonna do some quick jobs, updates and then if people have questions at the end we can answer those. You have about four minutes right away. Oh, okay. Or maybe a little bit more, five minutes. Okay, thank you. So we launched a homepage redesign. I think you're probably familiar with this already. We just cleaned it up a little bit, created some new more specific calls to action for an employer versus a job seeker. We added this featured company block up on the right side as an added benefit to anybody who purchases a Drupal job subscription. So not only would you get unlimited postings for a year but you also get regular rotation in this really high profile placement. And starting yesterday we actually just launched the ability for a job seeker to save a job search and then receive regular job notification email updates on it. So it's really good, good user experience. You know, some of you doesn't necessarily feel like they have to hit the site every day just to be abreast of new jobs and it's good for new job postings because you know that relevant candidates are gonna be aware of your posting as soon as it's up. We simplified the job store. We used to have five products. We narrowed it down to three. We've got a single job posting, a featured standalone job posting and then the Drupal job subscription which is still the same which now includes this added branding of the homepage promo as well as exposure in those daily email notifications that just went out. We were a little bit hesitant to flood the site with a lot of traffic before some of these changes went into place. Our customer service ticket to purchase ratio was a little bit high in the beginning. We just had a couple things that we needed to fine tune. It was around 25% and now since these changes have been in place, it's dropped significantly which is really good. So we're down closer to the 10, 15% range and that can always be improved upon but now we can go ahead with some of these larger initiatives to drive lots of traffic and feel confident that we won't get flooded with customer service complaints. So we're working on some integrated placements on Drupal.org including a jobs link up in the top and abs and then rolling out a more integrated block down in the bottom. And we're continuing to run banner ads across Drupal.org. We're doing a lot more in terms of testing trying to create campaigns that are catered towards job seekers versus employers just so we can drill down and do better targeting on Drupal.org so we can make those a little bit more efficient. But we also realize that we need to reach beyond Drupal.org. We're working with EVQ which is a marketing lead gen firm that we've been working on for some other initiatives and we've recently tasked them to help us identify and reach out to some recruiters and end users and make sure that they're aware of Drupal jobs. This month we're gonna be rolling out targeted email campaigns both for existing customers who've purchased and who want them to come back as well as leads who've come to the site and posted a job for free but haven't been converted to a purchaser. And then continuing our presence in the newsletter the Drupal Association newsletter and then dedicated mailers to accompany our banner ad campaigns to our Drupal business list. It might not happen anytime soon but we are talking about developing an affiliate program for Drupal jobs so partner sites or newsletters can promote Drupal jobs and then we can give them a rev share and any sales that come of it which is just a really good way to expand our reach without necessarily having to invest in an ad budget and then continuing to have some kind of presence at upcoming Drupal cons. Awesome, thank you. We have one or two minutes for questions. There's any? Kieran had some questions and it is, oh Kieran wants to know on the ad revenue is it 33% or 33% of bookings or 33% of earned revenue at this point? Bookings, yeah. And let's see, will we invite only new accounts to opt in and I assume Kieran that you here are referring, oops, I assume Kieran that you are referring here to the email list, I'm guessing. Right now the only opt-in has actually has been added to existing accounts so you can actually go in your account and then opt-in and then we will shortly be rolling out the feature for new members but obviously we wanna roll this out to as many existing members that we have so. Well the field is added to a new account creation as well. Oh it is, okay yeah, so on both fronts the opt-in is available and we'll probably work with the marketing team to try and make sure that there's some more awareness around that. Yeah, and then Matthew wants to know what we're using for the email newsletter. We as of this week actually, Friday I think it was, we made the last push to move our newsletters over onto MailChimp. They're one of our premium technology supporters and they're actually doing a very generous donation to get us kinda off the ground being able to move our entire list over to that. So the Drupal Association newsletter was already there but this is gonna move Maintainer News, the Drupal newsletter. Eventually we haven't moved security or we haven't moved security or maintainer yet but we've moved all the other newsletters over to MailChimp, so. Now is it. Awesome, all righty, I think that concludes the public part of the board meeting. Yeah. Thanks everybody and then we are the board members and Holly and Meg and I believe we're gonna regroup for the executive session. We'll see you over there. All right, thank you.