 All right, I think we're good to go. Well, thanks again everyone for joining us during my morning at least. I'm not sure where it is where you are or what time it is where you are, but thanks for joining us today for our fourth quarter of Supporters Call. Again, my name is Holly Ross, I'm the Executive Director here at the Drupal Association and we are just really thrilled to be able to do these and share so much great news about what's happening at the Association and what you've helped make happen. So again, welcome. And if you are listening from your computer today, you've got the mic and speaker audio option. If you could wear a headset, I would really appreciate that, that helps keep the noise at a minimum. And we've got a Q&A window set up. So we definitely want you to ask questions while we share today. So feel free to jump in with whatever it is that you wanna know about. I'm gonna be trying to check that out and looking for folks that have questions so that I can make sure the presenters ask those. So I think we're not using the chat, but there is a raise hand feature. There's also a Q&A window, you can pop things in there. And if you learned something new or fun that you wanna share, our Twitter handle is at Drupal ASOS and you can use that to share far and wide. So that's the housekeeping for today. And I see Ray that you have a question. So I'm just gonna unmute you. At least you have your hand raised. And I inadvertently pressed that button, Holly. Thank you. All right, carry on Ray. How are you today? There's my question. Brilliant, I'm great, I'm great. All right, we're gonna go back to business here. And we are just a couple of, one more quick note that again, we answered a little bit before, but we will record the session today and make the slides available to you as well. So keep an eye out for those later on today. Okay, and just a reminder about a few of the things that are coming up at the Drupal Association, we're always working on something. And we have a few exciting DrupalCon events that are in the works. So in February, we'll launch our first DrupalCon Latin America in Bogota, which we're really excited about and should be a really interesting con to be at both content-wise with a great mix of speakers from around Latin America and the rest of the world. But also just an interesting one, it's the first time we'll get the chance to try and use translation services at a con so that we can make content available both in English and Spanish. So we'll learn a lot from that experience while we have a great time learning about Drupal. And then after that in May is DrupalCon Los Angeles. That show is gonna obviously is coming up soon and in January is when we're gonna be launching call for papers for DrupalCon Los Angeles. So you definitely wanna keep an eye out for that and get your session submissions in for consideration. And after that in the fall, we'll be headed to Barcelona for in September and that'll be DrupalCon Europe in Barcelona. And so materials for that call for paper, all of that will open up later on in the spring of 2015. So three big cons coming up and then also our quarterly global training days. We just finished our last global training days of 2014. So the next one is getting on the calendar for 2015 and we definitely invite all of you to help grow the Drupal community by participating in that and helping us bring new Drupal developers into the community, get them all trained up and ready to go. So keep an eye out for more on that as well. Those are just a few events that are coming up. Today we're gonna be looking at 2015 and what's on the docket. So we'll talk a lot about some Drupal.org improvements that have been made in 2014 and what's on the plans for 2015, how we're gonna market Drupal in 2015, especially as we anticipate a big Drupal 8 release. We'll be talking about advertising on Drupal.org to help fund more of the work that we're doing and Drupal jobs, which launched this year. So that's what we're gonna talk about today. And of course, I just wanna say thank you again to all of you who are on the call. You're here because you are a supporter of the Drupal Association and the work that we're doing. So everything that we're talking about here today is only really possible because of the support that you give to the Association. So just thank you so much for all the ways that you contribute both financially and with your time and with your good energy and all your good vibes. So I really appreciate it. So what I'm gonna do now is find Josh on this list. Here he is and unmute him and Josh, are you there? I am here. Excellent. You hear me okay? Yep. Excellent. Well, I'll go ahead and dive right into this then. So before we jumped into 2015, I wanna do a recap of 2014. Very much a year of going from zero to 60 very quickly. My first day with the Association was actually March 31st. And we immediately began building up an engineering team. We are now fully staffed on our engineering team. We have 11 and a half FTE that are dedicated to improving Drupal.org and the Drupal ecosystem, which is really exciting because it's let's do a whole bunch of incredibly effective things for the community. First, the infrastructure improvements have been big. We've had bigger, faster test spots on Amazon Web Services that we've been rolling out for major sprints and at the cons. Those have been a lot more successful than our previous test spot architecture because we were able to put a lot more power at the test spots for a short period of time, get through the sprints and then dial them back down again and that's been awesome. We've removed a ton of technical debts. The history of 13 years worth of buildup that we are now organizing in a more enterprise sort of way, which is really exciting because it's gonna give us a whole lot of flexibility going forward. We've improved our monitoring and uptime. We've done performance improvements with the CDN. We have new database servers that are going on. Well, actually, they went online last night around five o'clock and you shouldn't be seeing some very noticeable performance improvements on page load speeds and particularly how quickly a page renders now because the query should be happening orders of magnitude faster. We're gonna be doing some metrics on that over the week and figuring out just how much of a gain it gave us but our early estimates were that it should give us two or three times the speed on some pages that are particularly heavy on the queries. Another thing that we did this year is we implemented change notifications. So if you're interested in hearing about what's coming next on Drupal.org or we can advance, you can sign up for the change notifications. There's information about the change notifications at drupal.org slash roadmap. All of our kind of links off to our various initiatives are on that page. Holly, go ahead and pop the next slide up. Some of the things from 2014 that are more on the software side of things, we've been working really closely with the working groups on project prioritization. We did user research workshops with them in Austin and then finalized some user personas that we rolled out around the Amsterdam timeframe and we've been doing some blog posts about different types of personas that are using our site. Been really focused on trying to move people off the ladder, going from newcomers to learners of Drupal to what we would consider somebody skilled in Drupal and then moving them on up to experts and then masters of the craft. And we're really excited about the work that the user research highlighted and it dovetailed really well with the prioritization work with the working groups. We also launched an API this year which was very exciting. It's already allowed a couple of the services that are using Drupal.org to shift from scraping the site to actually calling the API and getting the data directly from that. And that also is a performance improvement. We've moved several Drupal 8 blockers including making a semantic versioning possible so we now can do Drupal 8.0.0 instead of just 8.0. We've also been trying to set the upgrade path for localize.drupal.org by removing blockers from the community team that is working on that right now and I'm really excited to see that move along because localize is such an important part of making Drupal available in multiple languages. We've published a roadmap which is no small feat because it takes a lot of time and effort from all the members of the working group and our advisors who all got in and helped us do a ton of prioritization and strategizing around what should be the next thing, what is the most important thing. One of the things that came out of that is the Drupal.org responsive redesign or if you prefer to just call it redesign in general because we're kind of taking a whole look at re-envisioning the entire Drupal.org site over the next year or so. We kicked that off with the content strategy work that we started with one of our supporting partners, Forum One, they won the RFP to work with us on this content strategy and so far it's been a really positive experience. We're identifying some gaps that we have in the content types on Drupal.org, trying to fill those in and I think there's gonna be some really exciting things that come out of that particularly for supporters and for long-time users of Drupal that need ways of communicating a little bit more effectively with community. When we were doing the prioritization, everything broke down into basically four areas and these are roughly scaled to the size of effort that they represent for us. We are taking efforts to fund Drupal.org so making sure that we have multiple ways of bringing in revenue for the association that helps us put that revenue back into Drupal.org. We've been looking at sustaining support and maintenance on the site so that's a lot of those performance improvements and getting rid of the technical that I was talking about. We have our community initiatives and these are initiatives where I can't put a staff member full-time on it but I can remove blockers that may be stopping community volunteers from being able to do what they need to do to get something out the door. So we're really excited to work with community members if they have an idea that they're passionate about and they're driving an initiative forward. We can dedicate some resources to giving them infrastructure support or deployment support or perhaps testing support. Those are the types of things that we can jump in and help with. And then we have our board and working group priorities and I wanna go into those in a little bit more detail. And congratulations to Holly to catching the fact that that large pause was I wanna go to the next page because I didn't think to say, next slide. So first of all, the roadmap when we took the board and working group priorities we said we can't do everything so what are the things that we can focus on first and we're gonna be focusing on better account creation and log in, we've got some exciting work coming there. We're gonna be changing the way a newcomer is seen on Drupal.org so that if an account is in its first 90 days, people can actually see that and what we're hoping is it'll trigger a more friendly reaction to the posts that they may put on the site and kind of work them up the ladder towards being learners and then skilled users in our community. We're also doing some things to fight spammers which is kind of something that you don't think about doing until you're being attacked and we're trying to be a little bit more proactive about this by being able to identify those humans that we want to engage and work up the path which will make it easier to defy spammers and get their accounts blocked more quickly and keep our community clean and neat. We're also doing some great work on organization and user profiles. A lot of this stems from the presentation that Drees gave in Amsterdam that talks all about engaging the community and tending the common good that we represent with Drupal.org and so what we're really looking at is ways to highlight organizations that have contributed, being able to pull that information into their profiles and then after we have all that information in the profiles, figuring out ways to give benefits to those who contribute the most by showing their content in a slightly different way so that it gives them that recognition for being heavy contributors and this is a huge shift for Drupal.org but it's one that we're all really excited about because I think it's gonna encourage more contribution and it's also gonna help keep around the great contributors that we have both on the organizations that give a lot in terms of the time of their employees and directly in terms of financial support of the Drupal Association but also those individual contributors who do it just for the passion and being able to highlight them and show just how much they've given to the community and that's something that we're excited about. I mentioned the redesign of Drupal.org we're definitely going responsive with this. We're planning to support all the way down to mobile devices, all the way out to very large screens that our developers are often using Drupal.org with but it's more than just the visual appearance of Drupal.org, it's really about reimagining the content of Drupal.org and designing around that. We're going to be doing some exciting things with issue work spaces and if you missed any of the earlier presentations we've done on this get-in-issue workflow improvement I highly recommend that you track one of those down and kind of go through it. We are just now kicking off that work. We're very excited about it and we think over the next six months you're gonna see some really transformative ways in terms of how we manage our work on Drupal.org so that we can be a more efficient open source project and that's gonna be really exciting. Yeah, next two both make Drupal.org search usable and also improve tools to find and select projects. This was something that came out over and over again in the user research. Really what we've heard from folks is they need to be able to find the solutions that help them build great Drupal sites and so we're excited to be working on those two things in the next few months. And then one of our biggest sites that is still sitting on Drupal.6 that we need to get upgraded so that it's in the proper upgrade path is Drupal groups and we're doing some pre-work on that starting in the February timeframe in terms of planning and figuring out what kind of the next steps for Drupal groups is going to be. How about if you wanna go ahead and pop to the next slide there. I wanted to go over a couple of recent improvements that were directly related to those initiatives. Go ahead and hit the next slide. If you have a, oh, that's in a different order than I expected but that's okay, I can talk about this one first. No, it's okay. So the first thing I'll talk about that we just released in November is this new commit credit message. It auto-generates the commit credit message. This was something that was previously done through an extension on your browser called Redditor and it would kind of readrupal.org and it would create this message but it wasn't a complete message because it didn't follow kind of the collection of all the people who had contributed in a particular issue allowing you to see the people who had uploaded a patch in the form of a file or image in the form of a file or had commented on an image or on an issue and being able to pull all that together in a commit message and this is an important first step in that contribution credit concept that we're talking about. Right now this is just focusing on the users. The next version of this is actually going to also include the organizations that supported that user in doing that contribution and so this particular UI is going to change a little bit but what it really comes down to is it gives us a really great way to see just how much conversation has gone on in any given issue, what that turned into in terms of a commit to the Drupal code base and so it's kind of an exciting first step along that path and it actually is pretty easy to interpret and read through as well so we're excited about its use by the maintainers of both core and also of contributed modules. The other thing that I wanted to highlight, if you have a profile, this is what it looked like a year ago. It was very basic, we did call out if you were a supporting partner, which is awesome. Using here one of my developers profiles just because he happened to have the screenshot of it and he contributed a lot and you can kind of see that and he has some mentors but it's very basic and plain. About six months ago we implemented user profile pics, we started improving what the profile looked like in terms of little bits that we moved around here and there. If you were to look at it as recently as last week, you'll see that we continue to move it towards this a little bit better organized profile so we've been taking these incremental steps of getting old technical depth in the form bold profile fields, migrate them into a more standard way of listing them and then showing those on the profile. What we're hoping to get to in the next, really in the next month to a month and a half is gonna be what the next slide represents. And for those of you who've been following along, Danny Norton did some great work in this area but basically highlighting out projects maintained, highlighting out the community involvement at a very high level, organizing things, giving some areas of expertise that we can highlight on people's profiles. We're really excited about the changes that are coming with the profile. So stay tuned, more to come there, they're gonna continue getting better and thank you again for the support that makes that possible. So a couple more things to think about in terms of improving the experience because that's what we're working on right now. The things that we're doing for new users is that user role progression that I was talking about where we're really trying to engage users, engaging those new users in their first 90 days of creating an account on Drupal.org and then using community members to help us identify new contributors. This is something that we kind of do with the very highest level administrators of the site. People have been around the community for upwards of eight to 10 years who got so involved that they have some level of administrator access on Drupal.org but we're looking to extend this out and grow this a little bit so that more community members can help us identify those contributors and kind of grow that base that makes us a strong community. And then for our long-time contributors, the user experience improvements that we've been doing there have been really about performance. As we were doing some of these migrations, we actually found a performance improvement on the project pages and user dashboards that equated to a 200% improvement of load time on those pages. And so having dedicated people who are continuously looking at these things that are looking at the monitoring that are actually looking at the measurements of how things are loading and how quickly, this has been huge because it's enabled us to identify the quick wins that make Drupal.org better. So again, I say this every time I get a chance whenever we're talking to your supporters, thank you for your support because you're directly making Drupal.org better by giving us the time to dedicate that resource to it. That's what this slide was about. Sorry, I got ahead of myself, Holly. That's all right. Thanks, Josh. Excellent. I don't see any questions in the question queue. So I'm going to assume that made sense to everyone but just a reminder that there's a Q&A feature. So if you do have a question, go ahead and pop it in there and I'm happy to work backwards. If you think of it later, think of something later that you want to ask Josh. And you know, Holly, I should put another plug in Drupal.org slash roadmap. It highlights all the things that are in the initiatives, the stuff that we're focused on right now. You can click through and directly see the work that we're focused on in that area as well. Brilliant. Yep. Drupal.org slash roadmap. Excellent. Well, thanks, Josh. I know you guys have been busy. It's nice to see that all here in a nice summary. So one other thing that we want to talk about that's upcoming for 2015 is a new program that the board and staff have been working on along with the branch maintainers for Drupal 8 and that's the Drupal 8 Accelerate program which we just launched last week. And this is something that I think we're all concerned about which is, you know, when will we see Drupal 8 out in the world as a real product in and we want to help make that happen as quickly as we can for the community. So there've been a lot of discussions throughout the years as I understand it about how the association can help fund Drupal projects development. We definitely have a strict mandate not to be engaged in the actual development itself, not to influence the core code. And we take that very seriously, but we do want to help the community get to releases as quickly as they can. And there's lots of ways that we can do that through the tools that we develop on Drupal.org and Josh's team has done a lot of great work there. There's lots of ways we can influence that through the Drupal cons and training people and getting them engaged, working with sprint mentors and getting new folks to come to the development process and start contributing to core at the Drupal cons, right? So there's lots of things that we've been able to do in a soft way, but we haven't really been able to show a direct correlation between that work and increasing the speed or velocity as Josh likes to say of making a Drupal 8 launch happen. And the community has struggled to figure out how to fund this in a long-term way. You've seen Dries talk about getting more companies to fund core developers, Alex Pott's chapter three and the Acquia funds several folks and we've got lots of other core committers who are funded full or part-time by other companies. Chex is funded by MongoDB, right? So it's an interesting ecosystem, but it doesn't take care of everything. We have definitely had conversations about the association paying people directly or hiring core developers, but that seems to maybe cross that line of the Drupal association not influencing core development. So we decided that rather than try to sit back and think of the perfect way to answer this question, what we would do is we would develop an experiment and see how it goes. And that's what the Drupal 8 Accelerate Program is. Our goal is to make sure that we positively impact the release date of Drupal 8. That's gonna be a little tough since we don't actually have a real finish line. We can't say that right now we definitely come out on November 27th in 2015 if no funding were made, but we think we can track some, we think we were hoping that what we can see is that through this project, we can see folks reducing criticals at a rate faster than they were being reduced prior to our assistance, for example. And what it is basically is just $125,000 fund that will be modeled very much after the community cultivation grants that the association already gives out. So the community cultivation grants are requested by the community. So someone can write in and say, I'm gonna do a camp for the first time in Uzbekistan or in Mali. And I need some assistance to get that camp going. Or someone can write in and say, I'm gonna start a training program in the Philippines. I need some assistance to get that program going. And what we have is a group of community volunteers who work together to review and vet those requests. They make, they agree to make certain grants. And then the association acts as the bank and a bit of logistics support. And that's something that we do all over the community. So we will wire the money to the folks who receive the grant and then we'll provide them with a little bit of support to help them get going. And that's very much what we imagine here in the Drupalate Accelerate program. The difference here is we're gonna have two kinds of requests that can be made. The community can still certainly request all kinds of things, but we're also gonna have requests that come directly from the branch maintainers. So the folks who are most responsible for the core product, they'll be able to say, I see a really huge need here. Here's a way that we can move it forward and they can make a request themselves. Now, in this instance, for the Drupalate Accelerate Fund, it is the branch maintainers who will be making the decisions. So they will fund it themselves, which is a bit of a thing, but given everyone's time constraints and whatnot, we thought this makes the most sense. The branch maintainers have to all agree to make the funding. So if there are a set of folks who don't believe that's the best next step, it doesn't get funded. So there's a bit of a check there for that. So branch maintainers can make a request. The community can make a request. We chose this approach for a very specific reason. We wanted to make sure that while the branch maintainers certainly have the most inside knowledge about what is critical to the project and what needs to get addressed, and while our overall goal is just to knock out all of those things as quickly as possible to get the release out, one of the other things that we really wanna be able to do is to encourage more people to get involved in core contribution in a bigger way. And that's what the community requests are really about. So I think you all know we've had significant success with Drupalate in terms of getting people engaged. There've been over 2,400 contributors so far, which is amazing, but it does follow that sort of typical long tail of a few people with a ton of commits and then a very long tail of people who each have one commit. I fall into that very long tail. It's really difficult to get folks to move from their first commit to their second commit to their fifth commit to their 10th commit, right? So we wanna find those folks who are in that sort of sweet spot of like I have five to 10 commits and we wanna get them to a hundred. And we were hoping that the Drupalate Accelerate Community Fund is a way that that can happen. So things that we're specifically looking for from the community are things like I am hosting a camp, we're gonna do a sprint focused on Drupalate's criticals. I need a branch maintainer there who can make commits, right? Because we all know it's demoralizing to do the work and then not be able to get it into core quickly or at all. So we also know that there are a lot of tools that are maintained by the community that relate to how quickly we're able to work on Drupalate. So if you're working on automated testing or something on localized or some of the other related tools to a good product release for Drupalate, community members can request funds to make those tools improvements. And then we're just really looking for whatever ideas out there that the community might have, whether it's, you know, I wanna figure out how to organize a 24 hour sprint around the world or I have a user group and we wanna do a weekly sprint on X topic and we need support for, you know, whatever it is, the branch maintainers and the association are really excited to see what kinds of innovative and interesting ideas the community can come up with. So we hope that you folks will help spread the word and think of things that you guys can do in your communities and request funds to help make that happen. And obviously we all hope that this means that we get Drupalate sooner and faster and better than we would have before. So just a little news about the Drupalate Accelerate program and once again, you can find all the details on our site. So at asos.drupal.org or slash Drupal D8 Accelerate. So that's a little bit of news from my end of things. And just to say that we did put one sprint in working order before we got the program going. We just had eight folks in Ghent, that's in Belgium this last week and they were all really excited about the progress they got about, you know, being together, right? So this wasn't sort of your normal contribution sprint. They went in with a very specific plan to tackle very particular things, which is what we would want to see for these Drupalate Accelerate grants. And they were really thrilled because they were able to get the number of critical issues for a D8 release down to under 100. And lots of folks who were there described it as getting three months of work done in five days because it was very concentrated. And everyone involved really felt like this did have a positive impact on the release. So hopefully we'll be able to get more of that done and get it out the door. So that's it on that program. And speaking of Drupalate anticipation, Joe, my colleague Joe from the association, I'm gonna unmute you. Why don't you tell us a little bit about how you're gonna get the rest of the community into a D8 frenzy? Yeah, so I thought this was a good slide to start with here kind of segue from the Drupalate stuff. This is a chart from a recently conducted community survey. And so this is kind of a sneak peek at this particular chart. The question was, which best describes your organization's adoption of Drupalate? And as you can see, the vast majority, around 82%, either answered, eventually we will likely build Drupalate sites or migrate to Drupalate or we are eager to start working with it as soon as it is released. So that's fantastic. And I was curious to see how end user respondents answered that versus the design and dev shops. And you can see the breakdown there on the right, 74% of the end user respondents or site owners, whatever you wanna call them said that they answered in one of those two ways and then 87% of design dev shops say they will move to Drupalate. So some pretty exciting momentum there for Drupalate and obviously a lot of anticipation. We'll be publishing the full results of the community survey early next year and there's all kinds of juicy data points and tidbits like this. So keep an eye out for that. Okay, Holly. And I just wanted to take a moment to recognize the migration of the Weather Channel to Drupal. That is, as far as anyone can tell, is the largest Drupal site in the world with more than 100 million unique visitors per month, more than 20 million pages of content. It's a top 20 US site according to ComScore. Lots and lots of attention for that when it happened earlier this month. I think there were over 100 retweets from the Drupal Twitter handle and I've never seen that many retweets from the Drupal Twitter handle. So tons of social media activity, just lots and lots of attention. So that was a really awesome launch and congrats to Media Current and Acquia for getting that launch. There is a case study on Drupal.org. If you're interested in looking at that and I can actually drop a link in that queue to that case study, but it is in the case studies section on Drupal.org if you wanna check that out. I did wanna also mention the recent SQL injection vulnerability that you probably have seen on October 15th, the security team sent an advisory on the SQL injection vulnerability for Drupal 7 that you probably heard about and it received some coverage in the press. It got some attention and then later in the month on October 29th, they sent out a public service announcement that had some very urgent language in it that, hey, if you haven't gone out and patched or upgraded, you really need to do that right now. And they also gave essentially a time to vulnerability window from the time the vulnerability was disclosed until you should no longer consider your site safe and that was only about seven hours. So that public service announcement got a lot of coverage. It was pretty tough coverage. A lot of it was negative. Some of it was fair. There were a couple of incorrect data points in some of the coverage. I worked with the security team to put together a follow-up post that is linked there and actually if you go to drupal.org on the homepage down in the lower right in the news section, you'll see the follow-up and you can link to that. In that follow-up blog post from the security team, you can see there's some talking points addressing some of the incorrect coverage. And also just about software in general and the fact that all software has vulnerabilities. And also there are some hints at some potential new security processes and policies. And a lot of the negative coverage was around the process and policy. So when and if those processes and policies are updated will certainly help to amplify that out into the market. If you wanna advance there. Also wanted to touch on a few highlights from the 2015 plans. We plan to exhibit drupal at some European tech and marketing events. And in 2015 we're focusing on Europe. The reason for that is if you look at the breakdown of DrupalCon attendees, in Europe it's a much more developer heavy conference. There is not the evaluator audience that there is in the United States or North America when we look at the breakdown of that show. So in North America there's more engineering management, IT management, marketing folks. Some were the evaluator types. So we wanted to in 2015 take this to Europe and the events that we're going to exhibit at that is still in process. We're still working on exactly which events we're going to hit. As well as how we're going to fund the effort as well. But we will be hitting at least a couple of events in Europe exhibiting Drupal. Also we're going to be introducing some curated technical marketing content. We're going to be introducing or reintroducing a Drupal email newsletter. Believe it or not there actually has been a Drupal email newsletter in the past. I believe the last email newsletter was sent in 2008 at some point. So we're going to start that back up. And you can expect to see that in 2015. We're also planning to introduce a Drupal blog on Drupal.org that will be curated content as well. And we're in the process of introducing some resource guides along a given set of topics. And we're looking at things like Google searches and other kinds of data to try to understand where do we really need resource guides. But essentially what these are are curated groupings of high quality content around a given topic. So there's one on CRM that's in the works. There's one on media that's been published and there are a few others. So we'll be continuing to publish those on Drupal.org in 2015. Also case studies, there are a number of great case studies on Drupal.org. A lot of them are very technical in nature which is a great thing. Most of them are from I would say brands that the average person would not immediately recognize. So what we want to do is also create some case studies from some of the larger brands that people would immediately recognize. And they may not be quite as technical in nature. They may focus more on a business problem that was solved, a marketing problem that was solved, those types of things. So we're going to be introducing those in 2015. And then of course the Drupal 8 launch. Whenever that happens, we have a plan in place to get lots of great coverage. We're working on a webinar series. So there's going to be a lot of activity there. We just need to help get that out the door as Holly mentioned. And that's it for me. So I'll turn it over to Carrie unless there are any questions. Thanks, Joe. I think we're still on the clear question-wise. And let me just make sure Carrie, you should be able to speak now as well. All right, hi everyone. I'm Carrie Lasina. I'm the digital advertising and monetization product manager, which is kind of a mouthful. I had to shorten it for my business cards. I came out in October to help expand the digital advertising opportunities on Drupal.org. Our goal is to generate more revenue support for the project with products that really speak to our supporters' needs and goals. So I've been conducting a lot of interviews with our supporters. I know I've probably chatted with many of you as well as members that represent the larger community just to gain some insight in what makes sense for Drupal.org. Some of the biggest guidelines and takeaways are that products should not only appeal to our supporters, but they should also be helpful to our users and support our mission to grow Drupal. We also want these products to be inclusive. So not only do we wanna create more and more opportunities for you, but we also wanna offer some lower cost options and tier pricing when possible. And we're also trying to create some more high impact opportunities, but we wanna do so in a way that it doesn't clutter the site or disrupt our visitors, especially contributors. So some of the products you can expect to see from us in 2015 are the ongoing creation of curated content that Joe is just talking about with sponsored banner opportunities. So we're gonna be developing these resource guides, content by industry, for example, Drupal for government or Drupal for pharmaceutical, and then blog posts that will have banner opportunities within them. We're also looking to add banners on more high profile pages like the homepage, the marketplace, case studies, and then search results. All placements that won't offend the majority, but add a lot of volume to what we can offer you in terms of banner inventory. We're also exploring this new idea called Audience Extension, which would allow advertisers to programmatically reach the Drupal.org audience while they're on other websites through ad exchanges and networks. This is pretty new, and it's something that we're still exploring and hope to make available after we've had some time to run it past a few more people within the community. One product that kept on coming up when I was chatting with many of our supporters was this desire for dedicated or solo mailers. So we are working on creating an opt-in dedicated mailer product, which is where we would send out a dedicated email with a special offer on behalf of a supporter within a Drupal.org branded wrapper. This one's gonna take a little bit more time to get going. We're gonna be using probably the first half of the year to actually develop and generate that list that we can send to, and we hope to have it available and up and running by Q4. And then lastly, we're gonna be building some custom opportunities that make it easier for prospective users to try and test out Drupal. In terms of the timeline, we're trying to roll things out as quickly as possible. We're working on talking to the community about the best way to message these new initiatives to the community, and we're also trying to work with the engineering team's roadmap and just weaving these products into their roadmap without being too disruptive to all these other initiatives that you heard Josh talk about earlier. As soon as these products are ready to go as they're supporting partners, you're gonna be the first to know about them, just so you get the first crack at them. And Don or Johanna will be in touch with more info when those are up and running. And then moving on to Drupal jobs. We have been making some tweaks to the site that are either already live or about to launch. We're improving the user experience and flow a bit, so creating clearer calls to action on the homepage for seekers and employers with fewer steps to access the store and just hopefully making things easier as you move around the site. We also eliminated, we simplified in the store by eliminating a couple of products. So we eliminated the five pack of jobs and the standalone branded company profile page. We did rename the super bundle. We're calling it the Drupal jobs subscription. It's essentially the same. It's unlimited postings for a year as well as a company profile page with some added promotional benefits that I'll get to in a second. The last change in the store is that the featured listing will no longer be an add-on to a single posting but a standalone product with a goal of it being a little bit more user-friendly when you purchase it. Holly, if you don't mind clicking on that link, I've got a screenshot of the updated homepage for Drupal jobs. So you can see there's very clear calls to action whether you're an employer or a job seeker, making it easy to find your way around whether you're new to the site or an existing user. Also over on the right side, we've implemented this featured job company block. So if you have a job subscription and you do have that company profile page, you'll get very regular rotation in this very high profile block on the homepage. And could you just go back to the last slide? Thanks. We're doing the daily email that will update the job seeker with new postings that match their search criteria. The goal is to improve the seeker's experience and keep them engaged with the site. So if you're an employer and you post a new job, you don't have to wait for them to find their way back to the site. They'll get a notification through this daily alert. But the plus side is there will also be some more branding opportunities hopefully within it that are similar to what you saw on the new homepage. In terms of our traffic strategy, we're continuing to include promotion on Drupal.org through banners and some new integrated placements down the road. We're gonna be including messaging in our newsletters, developing some targeted email marketing campaigns, and then just doing some regular social media presence to keep it top of mind. And so far, so good. We have over 600 job seeker profiles so far. I think that's up from about 100 or 150 from the last supporter call that I saw. And then just please let us know if there's anything else that you think we can do to improve the experience, either as an employer or even as a job seeker. I mean, feel free to ping us here in the Q&A window or just shoot us a message after our call. We'd appreciate the feedback. And that's it. Thanks, Carrie. Next slide. So that was not a little amount of stuff that we're working on. And I think that's certainly not everything that's in the plans for 2015. Sounds like I have an echo. Hang on one second. Okay, so hopefully the echo is gone and Rachel can confirm that for me, but I don't hear it anymore. I think it is. But yeah, there is a lot of stuff going on for 2015 and this is certainly not all of it and not even all of it that we'll see from Josh and Joe and Carrie this year, there's a lot going on. But we're really excited to get to this work and to, I think, really grow more fully into the mission that the association has. And we're just so thankful that you have been such a huge part of it. And again, just thank you for the financial support for all the ways that you support the Drupal Projects through time and effort and energy. And also just thanks to you personally. I know we talk to a lot of you one-on-one throughout our work every day. And you guys provide a lot of just great moral support as well, which really is also very important. So we couldn't do this work without you. And I just would like to say one more special thank you to Megan in particular, but also Joe and Josh and Carrie for your great work this year in making all of the great accomplishments of 2014 happen. And we're really excited about what's gonna happen in 2015. So thanks everyone again and have a great holiday season and we will talk to you again in the new year. Show you some of the progress.