 Having said that, let's get this going. I'll try to keep this on time. The agenda for today is pretty straightforward. We'll have the regular operational updates. We'll have the discussions from the board committee. And then we're going to present the results from Drupal calling Los Angeles. And then we're going to talk about Drupal.org. And then after that we'll have our executive session. With that, I'll give the floor to Holly. And I believe, well, we definitely have quorum. Yeah. Yeah. I don't want to state it at all. We'll get there. Excellent. So again, just apologies for the late packet this time around. But July, lots of stuff to talk about. But as promised, we're sort of trying to convince those things. I'm going to talk a little bit about a couple of the highlights. And I snuck one in. It's actually an August highlight, but I decided it had to go in the packet now. It was a Drupal Con Barcelona ticket sales. Had been looking sluggish for a bit. But we just closed out the regular registration period and learned that we are on pace for our budgeted numbers, which is about 2,000 folks for the show, which is great. That's fewer folks than we had at Amsterdam. We had about 2,300 people in Amsterdam. But if you'll recall, Amsterdam was kind of a surprise to everyone. So we don't think that we'll see that bump again, right? But it does put us slightly ahead of Prague, which was about 1,800 or 1,850 folks. So it's good to see ticket sales are right in the pocket for Barcelona. We're very happy about that. Drupal Jobs was also a highlight in July. It was the third month in a row of revenue growth for Drupal Jobs and $10,000 revenue for Drupal Jobs. And that's the first time that we've had that kind of consistency out of the platform. So we're excited to see that happening. But we are working on a rethink. We won't call it a relaunch, I guess, but a rethinking of Drupal Jobs to help make that growth happen a little bit faster. So we've got a team here internally that's working on that. We're currently focused on sort of a customer discovery process using the Lean Canvas methodology. So we've been interviewing folks. We'll have to be talking after this meeting about what we discovered. So that's good stuff. And the other really cool news about Drupal Jobs is that Matt Holford, who is the CTO of DoSomething.org, which is an amazing nonprofit based in New York. They do awesome work connecting young people to volunteerism and activism. And they are a huge, huge Drupal shop. They get a one-month sabbatical there after a certain period of time. And as long as they volunteer with their sabbatical time. And he's spending his volunteer sabbatical with us working on Drupal Jobs. So yeah, it's really rad. And we decided not to put him on features because we weren't really sure what features to focus on since we're going through customer discovery right now. So he is building and focused on reporting right now so that we can better track what's happening on the site as we do roll out some of the changes that we anticipate. So that's really cool. And the things to watch, categories are sort of performance to our mid-year adjustment. So we put the retrenchment plan in place. We have a monthly update of the forecast. And as of right now, we've made really good progress on expense reduction. Revenue is still sluggish, not dangerously sluggish right now with Drupal Con Barcelona ticket sales coming in strong at the end of regular registration that did a lot for us. But because the cons are such a big chunk of change on the revenue and expense side, they can cause a lot of swing in our forecast. So things will get a lot clearer after we close out Barcelona. But we're in an okay place right now, just not spectacular. And we're trying to be really conservative with those forecasts so that we're prepared for the worst, basically. And then low lights, although we're pleased with the Barcelona ticket sales, the sponsorship income is definitely offering about 80% of goal for that. So that's something that the sales team has been struggling with. And I think it's just a reinforcement of the idea that sponsorship in Europe is really tough to grow because we see so many actors who shop primarily who are only working with, you know, seeking client work within their country. So the opportunities are just a lot less than they are in the North American con for sponsorship there. So 80% of goal does represent it is lower than the 2014 Amsterdam con. And again, I think Amsterdam has this centrality that we're able to capitalize on a little bit better. But it is not, you know, a hugely significant reduction. So just to give that context. So those are the key things I wanted to share. And any, you know, any questions from us? With the sponsorship being down in full Barcelona, I just wondered if there was any kind of common theme coming back to the sales team about what people are saying. Is it primarily around, as you said, the lack of local, you know, that people really have a local focus so they're not interested in sponsoring. You know, if they're in Germany, they're not interested in sponsoring something in Spain. Is that really the main driver? Were there any other themes that we should be aware of? Yeah. Megan, Ashley, do you want to address any other issues? Sure. Yeah. I mean, we've always known that when we go to countries that Drupal shops don't sell into, that they are less eager to step up and sponsor. And also when we go into countries that don't have a large Drupal shop base, we lose a lot of the silver sponsorships, like that lower tier. So we saw that. But we also did a big push to ISVs. And whether it was timing or, I think some of it was a bit of timing. Some of it's regional issues. A lot of them are saying they're putting their money into North America. They weren't looking to fund Europe. And so we're kind of assessing out, like, is it DevTools, is it business apps that are making specific decisions that way so we can understand that currently right now I'm reaching out to DevOps tools that talk with Nginx and Atlassian and Docker and I think New Relic. And let them know that we're thinking about a more developer conference in Europe next year with a focus on a DevOps summit. And there was more interest there. If I can show, really demonstrate that we have a DevOps audience. These people are more interested. So we're definitely digging into the feedback we got this year. That's really interesting. Thanks, Megan. Anything else that you guys want to talk about? Or other parts of the packet that I didn't really address here? No more questions. I guess we can then move on to the board committee updates. Which I think we don't have anything typed in because I keep forgetting to email. I did email. No, I did email this time. But I didn't get anything back. Maybe we can go around the room then. Follow the list. I'll go first. All right, Holly. Okay. So we didn't meet. So we don't have an update. We didn't meet this month. And even though it was for this month, you should just know we're just focusing on, we're doing the long-term strategy and getting feedback. Governance. We didn't meet. However, we have completed a draft handoff for the nominations committee and that's been shared with the entire governance committee and Holly at this point. So I think the next step there is to decide whether it's Addy or Denise who becomes chair for this cycle because Samir is up for reappointment. We also had conversations with the various board members that are up for reappointment about their intention. I find it hard to hear you, Denise. Sorry, I'm as close as I can get. Oh, I know why you can't hear me. How about now? Much better. Is that better? What I said was we also had conversations with the board members that are up for reappointment about their intention. Yeah. And that hasn't changed from the last meeting. I don't think unless there have been additional, additional information. Yeah, I got a new email from one of them. Okay. Thank you. Anything else from governance? If not, let's move on to finance. So the finance committee met yesterday to review the financial statements in the 990 will be presenting those in executive session and recommending approval. All right. Thank you. The exact committee we did not meet. And then the marketing committee. They did meet, but it was while I was on vacation and I haven't followed up with G&A. So I'm not sure what to discuss. So I don't have an update this morning. All right then. All right. Next. If there's any questions on that. All right. Let's move on to Drupalcon, Barcelona. LA. Thank you. Okay. So we are going to be talking about Drupalcon, Los Angeles. And this one. Thank you. I can't do it. Okay. So we ended up at 3,186 people. We were down slightly from Austin, but it was really only about 5% of a decrease. And we were up about pretty noticeably in the business summit. And we launched a new higher ed summit, which was extremely popular. We ended up releasing additional tickets after the original allotment. And had a couple summit crashers that we had to keep an eye on actually on site. So that was exciting to see that people responded well to that. And we had 357 people attend our trainings. So I'm going to kind of, I have a lot of data in here and we will be posting a blog post, I think probably next week or the week after with all of the information from the slides and kind of diving into a bit more of the numbers, but I'll just kind of cruise through some of these things here. Basically, overall we saw an increase in beginner and intermediate and a slight decrease in advanced skill sets. And developers definitely are number one audience at 27%. And then the industry that were represented, it was really neat to see this year we didn't limit people to picking one industry. So we can't really compare easily year over year, but we saw quite a big presence in education and technology and nonprofit, which is not particularly surprising. And then just kind of diving into the financials. Here's a quick summary of where we ended up. So the goal is what we built our budget off of. The actual is where we ended up and the differential kind of shows you how we balanced against that goal. And I'll get into the line ends on the next one. But the moral of the story is that we did a pretty good job of maintaining our net income margins, even with slightly lower ticket sales and what we were anticipating. So as far as ticket sales go, the conference tickets came in about 200 under what we had anticipated. And we came in a little bit over on free tickets. So tickets that go to sponsors or volunteers or speakers, that type of thing. We also were down a little bit on training. We had 450 training attendees in Austin and we only had about 350 in LA. So that took a little bit of income down. But the higher ed and business summit both outperformed what we had budgeted. So that was exciting. And then this is our summary of our expenses. And as you can see, there are quite a few numbers there. One of the most exciting things, if you look at the conference facility costs and furnishings, one of the things that people may not be aware of is we actually got the entire convention center for about $5,000. And the reason why we were able to get that rental fee was due to the hotel nights that were booked by the people attending our conference. So the local tourism board calculated a rebate for us that was essentially $130,000 based on the- Wow. Yeah, yeah. So- That's awesome. Yeah, it comes out to about $40 per attendee. So that's pretty significant when we kind of calculate that in into what those ticket prices go to fund. And again, that wasn't money that came directly to us, but it kind of does by default. We get that incentive back. And then on top of that, a rebate at the convention center, we also got about a $12,000 rebate from the host hotel to fund the Coder lounge. So that was really another great way to save money there. Okay, so we obviously we missed our goals slightly, but we found a lot of kind of interesting nuggets along the way. But a few things that we heard kind of anecdotally was there wasn't quite that drive of coming to learn the new things about D8 because we weren't quite there yet. So for some people that had maybe come to trainings in the past, they may have been wanting to wait until D8 is released and there's a new training to come and attend. I think LA was also perceived as an expensive destination, particularly for freelancers. And then some kind of secondary things that we heard were the West Coast location was kind of prohibited for people coming from Europe. You know, it's an extra distance to travel. So no more time away from home. And then also we did have a shorter registration period with this con. We did launch a whole new events website platform. And so that for the slightly kind schedule there. We did try and do some concerted marketing efforts to boost ticket attendance when we were looking a little bit, we were lagging a little bit more behind the goal. We did two targeted email campaigns. One towards the people who had attended a previous North American con and one to people that had already registered asking them if they would like to invite a friend. And those were both pretty well received. We had really great open rates and we got about 15 tickets out of that. So some opportunities for continued improvement is really working on building on our forecasting capabilities. We have a whole new infrastructure on our registration site. So we have kind of a new layer of data to kind of process. So we can kind of do what we can to reconcile that against our previous years, but really starting fresh going forward with the data and the kind of the nomenclature on what what constitutes a registered sale versus a completed sale, that kind of thing. We also are going to be taking another look at our site selection calculator that we use to make sure that we have some of those secondary needs in there. So for instance, West Coast may not be as accessible for people coming from Europe. And then marketing. So we have a four pronged approach, advertising, paid advertising, content marketing, and email campaigns. We also utilize social media and word of mouth. So content marketing, this really is designed to support all of our efforts. So this is where we often drive our other calls to action too. And we use it a lot to communicate information to the masses. And then emails. Ironically, we've had our highest opened email and our lowest open email sent on the same day. To two different audiences. I got the second one and they were like, didn't I already get an email from you? They registered for DrupalCon. We do have a really great open rate, which is wonderful. And then the lowest open rate was sent to people that clicked that they were interested in DrupalCon. What's a good open rate then? Yeah, it's very, very high. It's much above the industry standard. And then as far as social results go, we saw the highest engagement on things that were directly called to action. So things that were purely informational. So that was kind of interesting to us to see how people were really choosing to interact with the social media in a more of a formative way rather than a push way. I just want to highlight your last point right there. Oh yeah. Huge, huge thank you to Paul Johnson and Alec, I'm going to butcher his last name. So I'm going to say Alex. They were unbelievable volunteers and really did a great job of helping us stay on top of all of the inbound and outbound messaging for social media throughout the lead-up to the event and then onsite as well. Alex Laughlin taught me how to find Giffy's. So you have him to thank. Yes. So as far as marketing goes, we had quite a few lessons learned. Things that we just kind of build upon from previous years, but also just kind of reinforcing that we really want to focus on using our targeted marketing channels, the email and paid ads to reach targeted audiences for specific actions and using that content marketing on social media and events to kind of provide the information and add that extra value to the community. Okay, so getting into the details of the actual content itself, our highest attended session was Better Tools for Content Creators. Aha. Cycling. The top ranked session was Creating a Culture of Empowerment. That's a good session. Yeah, yeah, and you know, it's kind of reinforcing the popularity we've seen of things that are kind of broader overarching topics rather than Drupal-specific. Okay, so as far as what we heard back about sessions and content, one thing I want to also mention is we had fewer session evaluations filled out than in the past, but what we did find here from the people that filled us out was that the speakers were really engaging in their delivery. They found it really helpful when they had easy... It was easy to follow along when they had organized presentation decks. And there were some sessions that really inspired people to continue learning and looking back at projects with new eyes, taking a new approach to things. The things that we've heard for next year is that we need some extra work on essentially like coaching the speakers or making sure the sessions are at the quality and also making sure that we're conveying the right expectations with the titles and descriptions, making sure that those are particularly accurate. And for the generalized topics, they do want to hear more Drupal-specific examples. All right. One thing I don't know, in Los Angeles, did Emma Jane do her speaker training again for those presenters? Yeah, it's something that people can seek out, but it wasn't. But does she do it live for them? Yeah, she does it live. And I think that's a really good thing that people can use to see the recording. In those evaluations, what was really exciting is 89% said yes, they did learn something in the session they can use in real life. So that's really wonderful news. We had, again, less unique evaluations, and one of the things we want to do is to continue to reach out to speakers to include that push to evaluate the session at the end of their slide deck. For those that use our... our designed... in there, but for people that are using their own deck, we want to make sure to encourage them to encourage people to follow up. As a note, that might be a good thing too. Why is the... Track Chair's up about... so when they're doing reviews with speakers in the lead-up, they can reinforce that message. Yeah, that's a great note. Okay, so jumping into some more... Oops, I'm missing the slide. Go ahead. Okay, so talking about sprints, we had 442 people show up on Friday. We had a lot of great feedback from them, and I noticed... I know we had Standing Room Only in the first time Sprinter Workshop, which was really, really exciting. We also received a lot of really great feedback about the extended sprint location. I don't know, we had two different locations, one on each weekend, but both of them managed to have absolutely fabulous views of the city. It was pretty cool. Yeah. Okay, so jumping into our 10D survey, so not the session survey, but the survey on the event itself. The top three things that met expectations were session content, building Drupal skills, and business networking. So the nice thing here is that we are meeting expectations pretty much across the board. There are some things that we want to work on as far as it's interesting to see that both too higher and to find a job are on the far right-hand side of the chart. Then go to the next slide. Okay, so as far as things that, these are items that people said met or most exceeded expectations. And the top three were again, session content, building Drupal skills, and then rather than personal networking, which it was in Austin, it was business networking for Los Angeles. So something compared favorably, something not? Yeah. I'd like to see the content and speakers as well. Yeah, good. And then as far as activities go, it's again ranked left to right as far as usefulness goes. And sessions, boss, and networking were all high. Okay, so as far as people that indicated things that were very useful, the things that we noticed a major improvement in were Drupal training, contribution sprints, and summits. I think it's really exciting that improvements went up so noticeably. I think it's about 15%. The things that we saw some declines in were the value of sessions and keynotes. Okay, so our net promoter score is 33, which is down from last year's score in Austin. We have a few things that we think contributed to that, which we'll go into in the next couple slides. So overall, we definitely heard that people mainly came here sessions. So they came to grow their skills and meet a lot of new people. And we were meeting and exceeding expectations, but they want higher quality in all aspects. So we have a very discerning group. There were some really great feedback that we were collected as far as the actual sessions themselves. And there are some things that we're working as an internal team and then also with the program teams to make sure that we are doing what we can to support our speakers and ensure that they have what they need to provide content that everyone's excited about. We also got some really great feedback as far as our on-site experience. So people enjoyed the signage and found that it was really helpful and made it easy to navigate the conference. And that was well received as well as the registration area. So some internal things that we're working on implementing for many for Barcelona, if not New Orleans is creating some really clear policies on refunds and free tickets. So as I mentioned, we went a bit over on what we had anticipated for free tickets. So we're trying to find some good meeting grounds so that we can make sure that the people that need those tickets are able to attend. We also had some issues with our website that came up as the launch of a first site for the first event on the new platform could be expected, but we have already implemented a lot of things that will make it easier for our crew on site to execute the registration process and to do some reporting. We also found that we had some issues with the check-in process for the summits and trainings because the summits have grown so much and so quickly we were a little bit unprepared for all the people that showed up on site without registering that still believed they should attend their way to the summit. So we've got some stuff in place to help ease that pain point for future homes. And internally we also decided to come up with a better procedure for launching sponsorships after the initial sponsor perspective goes out. That's kind of an internal operations thing. And along those lines we want to make sure that we find some new sponsorship opportunities for sponsors that are looking for a different kind of engagement with the audience. Rachel, I've got some ideas on that based on an event I went to here in Australia. So let's make a time to chat. Yeah, that's great. Back, we removed barriers for first-time attendees and we found ways to expand that further. So we launched the first-time attendee social and that was really great. It was well received and we heard we want more. So we are looking at ways to expand that to a full day and maybe involving possibly an early first-time sprinter workshop in the weeks that people can sprint throughout the week. We also need to focus more on the basics by the holistic con experience. So making sure that things are just kind of right up and presented with the right and we also want to make sure that we do a better job of communicating the value of a con. So making sure that people are clear on their expectations and what they're getting when they come and finding ways to present the con to each individual audience. We're blessed with having a very diverse group that attends but because of that everybody has different expectations on what they're going to see and what they're going to experience. We also did a great job of fulfilling volunteer requests. We extended sprint space, sprint supplies things like that so we want to continue to do that in the future. Our signage again was something that we heard really great feedback on as far as being helpful, easy to read. So going forward again we're going to work on that programming revamp, working with the speakers making sure that the tracks are things that are continuing to be really relevant. Creating that holistic conference experience so one thing that we've been talking about is creating some recommended track for session paths for people of different experience levels or different job backgrounds. We heard loud and clear that people would like something either in the form of an official Drupal con app or an easy to use mobile version of the site so we're looking at our options there. And we want to continue to develop our outreach to those that are new to the Drupal universe. One of the exciting things is our beginner and our advanced numbers did go up so we're seeing some of those new people come into the Drupal sphere and we want them to come back and keep coming. And another thing is we just internally we need to stay nimble. So operationally as DA is hopefully close to becoming a very real and realized and released product we need to be nimble in the fact that that may have an immediate impact for 2016 cons or 2017 cons. So being adaptable and ready to scale based on the demands of the community. And now it's on to New Orleans. Any questions? What was our net promoter score the last time we took that pulse? It was 53 in Austin. That's a big drop. It is although I think it was pretty similar to what we saw in Amsterdam last year. It's interesting is when you look at some of the charts don't have a seizure while I back through slides quickly. When you look at when you look at some of these charts there are places where LA meets Austin and places where Austin meets LA. So you have basically on the whole I can get rated about the same across a bunch of these areas. So it's interesting to me that the net promoter score was so significantly different and my gut would be a lot of that was honestly the distance between the hotel and the conference center. Yeah and I think also we had a higher number of surveys filled out last year and my experience is that the more you have the more you have and the people that I think tend to drop off are the ones that had a good experience. So that could be too. Do we incentivize evaluations in any way? At this point. We could look at doing some sort of drawing one of the people who filled out evaluations. In Austin, they had a drawing to win a three ticket. Oh, we even agreed to get drawing for LA. Okay, maybe that was part of it. Bring it back. See what happens. One thing what I've seen people do effectively is during the conference itself they just take two minutes while everybody's sitting in their chair and with a mobile app or a mobile website and ask them to do the evaluation right there. Yeah, we definitely mentioned it in the closing session but it would be helpful to have them do it there while we're... Mostly here while you finish your survey. And then we'll tell you the city. Now we're going to play a song you finish your survey and then we'll tell you where the next con is. Well, it works. People do it. Yeah, I think it's brilliant. Matt just said too we'll wait until we get to a certain completion rate before we do it. That may lower or no net promoter score though. Any other questions? All right. Flores for Joshua. I think to talk about the Drupaloric. It is. Yes. All right. You want me to control your own? Sure. Just hand it off a keyboard here. So I want to walk through real quickly the Drupaloric prioritization process that we just... This is the first time we've repeated the process so we initially introduced the idea of prioritization last year over the course of the summer. We came out with our first roadmap as right around the time of Amsterdam and started sharing that out. One of the things that we noticed though is that because as the year goes on the process probably needed to happen a little bit more frequently and so this was what I'm going to call the first of our quarterly updates to our prioritization. The nice thing about this is it allows us to have a little bit more focus. When we did the 2014 process we added work along the way and the result of that is that it essentially made it so that we were able to work on a lot of different things and move a lot of things forward just a little bit but we weren't able to get as much movement on any one thing as we really needed and so I think this new process is definitely it's going to allow us to have a little bit more focus from quarter to quarter particularly in quarters leading up to a con when we really want to be able to show something to the community and reveal something to the community associated with those big events. So one of the things that we kind of took a step back and said I had a quick question. Yes. Sorry, what was the color coding on the slide so I'm not sure I followed that the green and the red and the black. So the black those were the original items that we prioritized. The red were things that were pretty significantly based on the size and scope of the content strategy work and then the green were things that were kind of added in. They weren't part of the planned items that we were going to do in prioritization when we originally did prioritization we had like we basically had a list of seven things these are the seven things we're going to do and then because there wasn't a way to kind of regularly update that roadmap the other things were added as we went along because they would have prioritized out highly we just didn't necessarily have a process to communicate that. As we approached the prioritization process again one of the things that I felt was really important is that it actually aligned with the strategic framework that set the goals and set the really that mission for the organization we have to be filling that through the work that we choose to focus and so you're all very familiar with the goals that we've set over the last couple of board retreats in addition to those goals we had two immediate priorities that we factored into how we did the prioritization in our last meeting. Everybody knows right now that the biggest most important thing we could do is make sure that Drupal 8 is on track and so we wanted to have something in our prioritization process that gave a lot of extra weight to any infrastructure issues that we needed to resolve in order to allow Drupal 8 to happen so if there was a critical issue blocking release we were going to prioritize that higher naturally. And the other thing and this is obvious based on kind of where we're at right now as an organization and looking at our total expenses and how revenue is coming in, if there was an opportunity for a particular feature that would also drive mission driven revenue that was going to be something that would also get a pretty significant bump from the working groups. In the end we came up with the following prioritization matrix and I'll describe it really quickly because I don't want to get down to the specifics of how the numbers are assigned but with the working groups we came up with the scale. Everything is weighted on a 0 to 10 point scale you'll notice that Drupal 8 and revenue got tens so they gave a lot of extra weight. You multiply that times the score that's given whether that's a 9, 3 or a 1 or a 0 you can actually give a 0 for this as well and you'll notice that we basically just took all of the board goals and gave them a relative weight based on this point in time. This will be the thing that changes from prioritization to prioritization because we will change those weights according to what's needed at the time based on the conversation with the working group members and it was really cool too because the working group prioritization process we had all the working groups represented including the technical working group all of the priorities were also reviewed by at least one member of documentation working group had representation there as well and then all of the Drupal.org working groups content working group, software working group and infrastructure working group. Really good representation it helped us get to kind of a strong list of these really are the most important things. Those little letters that you see under the goals represent the parts of our skills acquisition triangle so an s equals skilled an e equals expert and so what we were basically prioritizing there is the idea of this particular goal particularly speaks to the skill to expert transition or the expert to master transition and they're kind of weighted accordingly. Out of that process our top four priorities, sorry I'm changing the wrong screen our top four priorities are very much focused on Drupal 8 followed by things that are probably the most pressing at this very moment on Drupal 8 itself to hit all the goals. So localize.drupal.org I don't know how many know this but last week week before last time goes by very quickly we upgraded localize.drupal.org to Drupal 7 which was a blocker to us finishing one last thing that allows for localization to work with Drupal 8 core. That one last thing is on the plate of a couple of people we've got one community member helping with one issue and one staff member also helping push that last issue across the finish line. Drupal CI is the other thing that we spent a lot of time on. We now have a meeting every other week with core maintainers to just make sure that we're knocking off the last few issues related to that that would prevent Drupal 8 from being properly tested. We are very close at this point. Drupal CI is working to test across I believe it's six different environments which is a combination of a version of PHP plus a particular database version. An example would be PHP 5 plus MySQL 5.5 and that suite of tests just to give people a sense of what Drupal CI is doing these days that suite of tests tests over 94,000 assertions every time somebody submits a patch to Drupal core and that gets checked and the entire Drupal CI framework actually scales up down so what we actually see in practice is it's really fascinating here is we have certain times of the day where the number of tests being run drops to zero that's about 2 a.m. to 4 a.m. pacific time is right around that time and then we also see times of the day where that will spike up to 35 to 50 simultaneous test spots running to plow through all the tests that are being submitted. That auto scaling is going to be really important to the long term sustainability of the cost associated to Drupal CI it's also something like that 94,000 tests the sheer scope and scale of that is something that very few other open source projects can point to our test coverage is pretty phenomenal in fact with the recent test bots that were created for testing PHP 7 which isn't even fully released we've actually been helping them find some bugs every time that test run it actually uncovers like new seg faults that then get reported back to PHP 7 and we actually had an incident where we pushed a couple changes and then they retested and they fixed PHP 7 as a result of the rather extensive and very powerful testing that we do for Drupal so kind of a cool win we're hoping the PHP community move forward yay that's really cool so obviously that one has been a big priority it continues to be we're on track right now that we for sure will be all the blockers will be out of the way for Drupal 8 for Barcelona we also have kind of a secondary goal related to that that we want to turn off the old test bot infrastructure by Barcelona it costs us about $2,000 a month and it is not variable pricing so it's something that we very much want to be able to use that infrastructure budget towards other things the next two items that are on the list are ones that they scored out really well search being something that just frankly should work on Drupal.org but it's never really gotten the attention it needs we have a very nice execution plan that we think we can put in place for Barcelona so that if somebody searches for some pretty common search phrases on Drupal.org they will get what they expect which sounds simple but it's something that as I said it's not been given a lot of attention and now we're going to give it some and then the documentation section which particularly as we're rolling into Drupal 8 launching we felt like this was an area that needs to be really strong and needs to be set up to be successful from the start of Drupal 8 so as Drupal 8 is released and all that documentation starts getting created it will be a much better experience a lot of the features that get added to the documentation section will actually help across Drupal.org as a whole for instance we're talking about implementing comment notify so that the comments made on a piece of documentation can give notification back to the creators and maintainers of that piece of documentation we'll be able to use the same comment notify techniques across all the content types on Drupal.org so that communication is just a little bit easier to have right now the only communication that has good notification tied to it is really the issue queue if we get to it now our next prioritization process is going to be in Barcelona but if we can get those four priorities that we've set for Q3 knocked out before Barcelona the next things that we will jump on to in order of priority our proper project application improvements trying to make it easier for people to submit new modules and themes to Drupal.org working with the technical working group on some implementation features that they want to do there to improve project tools to make it easier to find all those modules the Y Drupal section which previously we were working on and actually the Y Drupal section I don't think is going to be blocked as soon as we've released the basic tools for documentation section our marketing team will be able to continue building the content for the Y Drupal section so that should be pretty much ready to go right around the time of Barcelona as well other things that we are going to be focusing on are build with Drupal section there's the desire to do a Drupal 8 user guide and that would be guide.drupal.org a better contribution section and we still have on our our long-term plan addressing the issue workspaces and kind of getting that pull request type functionality into particularly the core issue queue as a better way to work in our community so next steps face-to-face meetings with all the working group members in Barcelona that prioritization process will happen again and we'll shift the numbers according to the status of Drupal 8 and also the kind of where the goals rank in terms of importance in that moment and then we would also like to look at adding perhaps a couple core maintainers to that quarterly prioritization process to make sure that we're keeping the development of Drupal in line with where it needs to be the last thing I would ask is what do you feel would make this process better? I've got one for you Josh if you're going to add a couple of core maintainers I think it would be really good to see if you could find people who are big in the contributed module space and not necessarily core because I think there's a lot more people who are working in that space who we don't necessarily hear their pain points and also a site builder representative if you can find one that's actually we do want to add a site builder to our software working group at least one site builder and I know that that's a priority to begin looking for that person around the Barcelona time frame cool I think that's kind of missing in the mix at the moment great some more thoughts or there are other things that the board would like to weigh on that could be better about the process and the prioritization? It all looks good to me for me I guess I know this is kind of a bad question but like how is there things that we can do to create more velocity is there anything that blocking you or that's kind of hurdles that make things slower? Well velocity is my favorite word trees as everyone in this room was snickering a little bit when you said velocity because I use the word velocity all the time We have a quote up on the wall in here from Josh I only wear velocity style t-shirts so I actually think we're beginning to get faster and that's kind of hard to that's hard to see at the moment though I will say that the team has been working together now our last member of our product and engineering team on the Drupal Association staff was hired in November of last year so we're just past the six month mark where this group has been working together for a while I think certainly there have been some distracting factors this summer but the nice thing about them working together long enough is they're beginning to get some kind of economies of scale that come from knowing what your teammate needs and being able to deliver a piece of code that you know is going to quickly kind of make it up the chain and so that is getting faster I do think there is still a lot of room for improvement around how we can accept community contributions and how we can get them working with us in ways that will also keep the velocity moving One of the things we saw with Drupal DTI for instance is that project in order to get to production required a little bit of shift in thinking from what's possible to what will remove the D8 blocker and how do we get this thing launched and I think that kind of pragmatism that comes from a core team that's continuously working on something will lead to velocity it's just it takes time a lot of the stuff we're working on are big and complex Drupal CTI is a way way bigger project than I imagined a year ago I just want to go on record and say Josh says that the team can move faster than I believe you the team can go faster but I also feel like I don't probably said this but I'll say it again I don't really think it's fair to say that the team is not going fast enough I think the team has done a tremendous amount of work but there are two issues one is that not all of that work has been highly visible work a lot of that has been dealing with the craft of Drupal.org and that work is unappreciated and unseen and the other bit for me that I think is really important to note is that if you go back to Josh's slide about the priorities that they've been working with for the last year we started out with five and ended up with eleven and that's that's disruptive and a lot of those priorities came up at the very, you know, in sort of heightened this is a crisis ways and got added to the list and I don't and there's nothing wrong with that I feel like that's a normal part of this process where not only is Josh's team scoring but the idea that we have a team of engineers that can work on Drupal.org is new and so having people to call on is new so that's just all part of the process of the community leaders, you know, getting getting used to what's possible as well but I just, you know, I don't like to say that they're not going fast enough I still don't really think that's fair it's interesting if we look at just to be clear one quick correction I didn't say they were slow well fair enough I was just wondering if there's ways we can go faster even, you know and I understand there's a lot of forming of the team that have to happen and understand there's a lot of legacy crust if you will that needed to be cleaned up so I was wondering if there was blockers, things that we can help with to, you know make them able to run faster and the reason I ask is because there's a lot of things to do and while we're chipping away at these things that's great but you know you know I think we have a great team obviously there's 10 of us that are doing this as Drupal Association staff now that's not a huge team for the number of things that we're working on but I really do think that we're beginning to get a lot of the technical blockers out of the way that made us that made it difficult to implement new code on Drupal.org we have a new set of GitStruff servers in place we have new database servers in place or delivering through the CDN I mean they all seem like infrastructural things that well why wasn't that already the case and I agree with that except I also look at it as well it was not already in place because you know prior to the beginning of 2013 we had 2014 we had two people working full time on Drupal.org and the priorities so now that we've actually got a few more people that are continuously focused on it and I will be honest this is some of the most committed people I have ever worked with it is not uncommon to see startup culture like hours of work weekends days off there are crazy committed group of people and it's just getting to that point that we can really get the blockers out of the way that are technical hurdles and really begin developing new features and we're close to that it's taken a while to get here but we're very close that's great to hear I do believe Kieran wants to ask a question you may have to be unmuted I don't know yep sorry I can move your left top list I can see the whole screen Kieran wants to understand the Kieran says I'd like to understand the investment and revenue from IT versus the investment and providing services to the community so let me see if I can open the control panel and actually unmute Kieran because I don't understand fully there you go Kieran I can't unmute you because your phone somehow muted because of the phone connection and you're not connected to the computer audio actually so I don't quite understand your question Kieran unfortunately but if you want to talk to me about an offline or shoot me an email I'd be happy to try to follow up okay is there any other questions is anyone reading questions Kieran yeah Donnie you had one other question you put in here it's more of a comment I think it might be good to follow up on that technical debt that we've been paying down it might make a good story cause Drupal.org itself is a complex Drupal site and there might be some learnings there that could be shared might be a nice way to also let the community know that this unseen unheard and un-fanked work is happening but in a useful way yeah so the team does put up every month what's happened on Drupal.org posts I know but I mean more from a communications kind of a thing rather than the highly developer centric story that is told that way I'm thinking more do you know what I mean yeah like an episode of dirty jobs do you know what I'm talking about I was just thinking I need Ryan cause Ryan is my metaphor provider he would come up with a metaphor that would describe our technical debt right now but yeah it looks like Kieran I can unmute you I do agree with that though can you hear me now thank you okay so I guess what I'm saying is we saw a long list of IT projects and I don't know if you can go back and show them you know you said it went from 5 to 11 the question I have is when you look at your portfolio you know 10 headcount you look at your portfolio of investments that you're making a lot of them are very focused on how do we provide services how do we deal with technical debt how do we deal with maintenance how do we deal with new crisis as they emerge and so the question as we're looking at all these projects are any of these specific to specific to revenue generation you know let me add a little bit of context so you know we're in a bit of a startup boom again and many organizations see increasingly their IT dollars are being reallocated to marketing to drive lead generation and to fill the funnel to drive sales so we see the marketing organization is increasingly owning more IT dollars and deploying marketing and sales technologies to drive revenue and that's kind of the standard in the industry at least on the commercial side in the world and I think the non-profit side will shortly follow where it hasn't so just if you could reflect then you feel free to answer now and take it off to the executive session or get back to me at a later time but I think it would be useful to understand where the IT dollars are towards revenue generation versus where they are on the community services I think in the 2014 process revenue wasn't even a consideration really we had some projects that we were doing like triple events that snuck in right and then and triple jobs but it wasn't part of the prioritization process revenue consideration so that's something new for this new quarterly process that that is in fact considered and we are taking on work that we think will either strengthen and provide new revenue opportunities I would say the balance of the work because we have such a huge backlog of ideas and features that have been requested over the years the balance of the work being requested is definitely features for the community to improve how they interact and engage features to better communicate the value of Drupal by allowing the community to build things on Drupal.org that's definitely the balance of the work but I reiterate what Holly is saying we are looking for ways to do mission driven revenue and ways that one of the cool things about that is if we can find a thing that helps us drive revenue it may actually help fund a position that helps us provide more mission and so we are always kind of looking at that from a what is the sustainable way for us to grow going forward Joe one thing I would add on that trend here too is a lot of the marketing dollars that are spent are on SaaS products marketing automation and so forth and I think a lot of that trend is driven because the marketers wanted to get around IT so you know a lot of those investments are made outside the IT department but I think for us we definitely see Drupal.org as our best revenue opportunity but as Josh said to stress mission based revenue opportunity finding those places where we can create revenue but do something that also serves the project so yeah because the community is not going to say hey we need a feature so we can make more money off Drupal.org that's not something the community is ever going to stand up in demand let me know if you want to follow up on that awesome well is there any other questions if not I suggest we move to the executive session thanks so much everybody I appreciate the feedback I'd like to say thanks to Josh and Rachel for great presentations to us this session thank you nice work can I in between switching sessions I'm going to grab a coffee ok see you with you