 Everybody's here. Two board members are not in person. Tiffany is on the phone, though, and Sameer is on the phone as well. Everybody here can see the agenda, but there's a few other people on the phone. I'm not sure they can see it, but basically we're going to do a quick operational update with some Q&A. We're going to do questions from the board committee reports, and we're going to talk about DrupalConAsia. We're going to get a vote on the infrastructure working group chair, and then we're going to get an update on the Drupal8 Accelerators program. Are there any candidates from the last election to see a letter? Good job, you guys. We're in coordinate. So many of you guys are so engaged, so looking forward to the next election. The first one is that our sales team is now here, and we have a sales person. It's definitely a challenge for that sales team to function the way that it should, but we have everyone here at the con as well, and I think we have some really great folks on the team who are really good fit for the community and the work that we're doing, so if you get a chance to meet Jenner, Mark, not Mark. What this role does is after you have achieved a certain number of interactions on Drupal.org, and that can be comments or commits or group posts, other kinds of activities, you then can be a community, you can get this community role. Recognition for folks who are giving so much to the community. Real human is doing great stuff at Drupal, but people with a community role also get to wave a magic wand and bring other people into the community by confirming them on Drupal.org. So once they are confirmed users, you can leave comments on issue queues, et cetera, et cetera. So they're able to help be ambassadors and bring other people into the community. So we're really excited about that chain of events that's happening on the user role side of things towards that overall roadmap. Highlight for us in the last month is that we launched the Try Drupal program, which is pretty new, and we love this program because it does two things that are fantastic. What it does for us is, first of all, it helps us towards our mission of promoting adoption of Drupal. On the page, you can choose from several partners, and the list will continue to expand where you can start go, and without having to pay for it, start at least a 30-day demo of Drupal. So if you're evaluating Drupal, you can come in and get a fully functioning demo site and start to see how Drupal works for you and your organization. So we're excited about that from an adoption site, and it's had a really great update. Three-day demo. Is it live? I don't see it live. Well, the program has different words on it now. Start a whole digital demo. Just hang on. We have a minimum monthly guarantee with the CPA on top. If there's more traffic, the more traffic we provide to them beyond the threshold, then we all make money together. So at 700, what we're hearing is that 700 is a higher conversion rate than we anticipated coming out of the gates. So strong beginnings. What just three days? It depends on who the partner is, how long they actually make available. Some of our partners have Office for free accounts, so technically it lasts as long as they want to keep it. But for our partners that don't have that sort of structure of a place, we wanted to give them a way so that they could be a part of the program, do a demo that would highlight the best of Drupal, and hopefully it would be a team for them as well. Something like SimplyTestMe, it's 30 minutes, so we felt like three, compared to more of a developer-focused group like SimplyTestMe. And we're still looking at a couple of partners. Our work to watch list is revenue overall. So we went into 2015 with an investment this year is in the sales team so that we can build strong revenue lines and continue to do programs like slightly lower sponsorship numbers than budgeted, and slightly lower ticket sales than budgeted. Mostly on the expense side, thanks to Rachel who's amazing and we love her. We see a net income effect from that, but you know, the real issue has been on the non-con revenue, so advertising and other programs. We have some things that are totally firing and some things that are not, so we're going to continue to really tweak around the revenue lines throughout the year. The bigger picture is that we have to really rethink our overall revenue model, not just some separate revenue lines, and we're going to start to bring that thinking to the board in June. So we'll have some executive sessions around that, because we'll be sharing some financials that you don't do publicly until they're approved, and then we'll be bringing that out. Our two lowlights are revenue-related. Dennis, the supporting partner program, got off to a slow start with a very distracted and overworked salesperson. One remaining salesperson we had. The general supporting partner program was really good for that. We do have the hosting partner program, which that's the salesperson that retired, right? We just got that person back on board, so we're hopefully can catch up some of that revenue, but some of it just may already be lost for the year. So that was a little night, and then I mentioned con revenue coming a little low. Those two things are, you know, the not-win. I think the next topic was the board committee updates, right? So they're in the pitch. Yep, I don't know if governance or exact. If you guys have anything you want to add? Wrong, but I guess this is... Yeah, it is me. Same thing for the exact. Is there any questions on that? I have one. Sameer, you're on the line, yeah? Do you have time for a governance call while Matthew and I are in a room together still? Sure. Okay, cool. Let's try to schedule something for... We'll do it in mail. I'm sorry, we should have talked about it on the weekend, but thanks. Other questions? Alright, let's move on to Drupalcon Asia. Well, I'm really excited to announce that we are going to have a Drupalcon Asia. We went from SES, which city was the best one, and I'll go into a little bit more information, but I am not revealing where the location is. We're going to have to come to the closing session to hear that big news. So... Did you just say our condom thing? I'm not done with my presentation! Stood out because it is an IT hub, and most of our Drupal.org traffic comes from there. So we wanted to see what we could do to make that work and bring more people into the project there in Bangalore. We went to New Delhi. We were hosted there, and there was even a camp for us. That was pretty exciting. And there is a really strong Drupal community. It's one of the older communities, long-standing communities in India. It's also the government hub for the country. And then we went to Mumbai where they also have a strong Drupal community that's been growing over the years. And they have a strong business hub. So those are the three cities we evaluated. And when we were there, there was a couple things that we were looking at just to make sure we were mitigating our risk. Whenever we go into a new... what's that? That's a giant point. I know, I just like the picture. We're going to a new country. We don't know really what we're going to be dealing with. We've been doing these events in North America and Europe for quite a long time. So we know what to expect. So we really had to pick a city and a location to help reduce our risk. So these are just a few of the things that we had to consider when we were evaluating. So one, we had to make sure we had a strong Drupal community so we could make sure that people will show up for sure for our event. We wanted to make sure it's attractive and easy so people throughout India could come, but also people from beyond, even for us in North America, we have to make it easy for us to get into that city. And of course we want to make sure it's exciting for sponsors to invest because we really are going to need a strong sponsor base. We know that it's going to attract a pretty large crowd. I think a thousand is modest for a goal. So we want to make sure also that Venue has a good brand experience. There's always that can't be too fancy, can't be too much like being in a basement. So that's kind of the right one. And of course the most important thing is that the venue, the catering, the internet, everything has to fit within our budget. So these are some pictures from our tour to all these cities and I just, like I mentioned before, the community really came out in full force and showed us such a warm welcome and really rolled out the red carpet to help us really understand these cities and the community. So a special thank you to everyone who made it so special for us. And when we were there we talked about goals and strategies. So we did a lot of work with the community in India to decide what we really wanted to achieve if we bring Drupal Khan Asia to India. Some of the things we talked about was that we want to unite the Indian community. Right now they have camps and meetups all over but they never get together as one large community within their country. And then of course we want to connect them with the world for knowledge sharing. We have been seeing a strong contribution culture that's been growing in India. We want to accelerate that. There's so many Drupalers that we just really want to bring them in the path to have them be part of our community giving back to the code. So that's going to be a big focus for this event. And then of course with all these developers that are out there we want to make sure we're growing their skill level so that they are really contributing to the project in very meaningful ways and making obviously great websites. And then there's always the need to connect these developers with employers. And so we feel this here in North America very much that we need to have more talent. They feel the same way in India. They have a lot of initiatives going on to grow their talent pools right now. And then in terms of strategy we're going to use this event to attract Drupal developers to our community and just further grow them into this contributing community. That is the strategy for this event in a nutshell. So like I said when we go into a new country we don't necessarily know who's going to show up. So we have to work with the community to get a good sense. And this is what we are anticipating is that it would be 80% Indians coming from the country 20% from outside the country. We feel that we're calling it Drupalcon Asia to make sure people from whether it's from Saudi Arabia, whether it's from Vietnam, all throughout even China make sure they know this is for them too. And just even talking about this event here at Drupalcon Los Angeles we are already hearing so many Americans say yeah we are going to this one. So we'll see how that goes. It's going to be very much a developer event. We see that with the camps in India as well. That's who they're catering to and that's who we should expect. And so we'll also probably see some site builders. And of course we'll have the CXOs from all the Drupal shops there in India and in the surrounding area. And we might see some CIOs coming to evaluate Drupal. This is definitely not a big marketing event to get more businesses to adopt Drupal in India. So that's not a goal but we might see some people that will show up expressing interest. Every time we go into a new country we have to understand what works for their culture and for India what they recommended is that we have the event starting on a Thursday where we'd have trainings, a business summit, and a community summit. We worked with the community on the price points for training, what's typical price points for them. And then Friday and Saturday would be the keynote and sessions. And again we worked with the community on what's the right price point. So it would start at $50 for Early Bird and go up to $100. And then Sunday would be the sprint. And so since the big focus to get everyone to learn how to contribute is the theme within the content that we provide and sprint mentors and just really end with a strong sprint at the end. And so just kind of in a nutshell, just like to be really clear this event is for primarily developers we also will be seeing site builders, the Drupal shop owners, and the community organizers. We really want to also level up all the community organizer skills and programs so that when we leave they can still work within the community to keep it strong and growing. Things that we're going to evaluate along the way. There's a big interest in having a government summit. Drupal is really big in the Indian government so we want to see what we can do to bring people together kind of like the higher ed summit we had here, see if we can do that in India. And saying, well that's government. So same concept for government, something similar for higher ed. The business community did say they might want to pull funds and do their own PR. So when juries went to the camps in 2011 the community did a PR campaign had some good press. So they're looking to do some of that again. And also right now students who cannot pay, right now we do need to have people paying to come because it's an expensive venture for sure. We're trying to find ways to help students come in and bridge the gap since they won't have the funds so we're coming up with maybe we could subsidize some tickets and some companies might want to step up in that area. Right Mike? Yeah. Okay, so as you can see we started working on the budget and just like with DrupalCon Latin America when we go into a new region, a new country, we are willing to run a deficit on the event because this is our investment in the community. We know that over time as things grow that just like in North America and Europe it will pay off and it will become neutral to profitable over time. But that's not our goal. Our goal is to make this happen. And so we are willing to run a deficit. One thing I do want to point out again ticket revenue because the ticket price in India is so low we are really going to be leaning on sponsors to help make this event happen. So I'm really happy that we have a committee forming that we can go out to the Indian provinces, the SIs. That works going to happen the next three weeks. And of course anyone outside of India who wants to sponsor we would welcome that. So tell you where it's going to be. Racheet is on stage today. Racheet and I have been leading Drupal community in Mumbai for the last five years. I've seen it growing from five percent the first meetup that we did was five percent and you know I was just literally thinking that how we can grow it and now it's like more than 650. Last camp that we did Drupal camp in Mumbai. Mike was the keynote in that. We had participation of more than 650. That was awesome and people are so empty about the whole Drupal thing that's happening. And with the Drupal call coming to India they are really excited and we are really going to rock it. Go ahead Ani. Hi I'm Ani. So I'm Racheet from Bombay. I actually started my Drupal journey a long time ago for the Haramchala project. I was an organizer in Delhi and I moved to Bombay and I found it to be a much better city. Yeah so we are extremely excited. I'm actually looking forward to the government thing so I've been working with people because in India there's a massive push for open source and it was great visiting Australia and Donna's great camp over there. It was fantastic to learn about what Australia is doing and how the Gulf Sea mess is working out really well. So we want to kind of use that to maybe provide policy advisory to the government. We use that knowledge to build a base around Drupal. That and Racheet has actually started a Drupal Campus Ambassador program so the student initiative is underway. It's really exciting and the Drupal Con is definitely going to help. Reasons visited 2011 was a watershed. This is going to be the second one. So when Reasons visited Bombay I think that was the point when Drupal can be started great. And after 4 years and he's visiting again it was a good con. It has to feel good. Let's go. Thank you. Okay who else? I don't want to miss anyone. Sundar. Not professor. I think Reasons visited I had to go on the first stop. So he's been instrumental in helping us understand what's happening in higher education and attended the higher ed summit and hopefully we can take that knowledge and repeat the program. We hope to have one day of higher ed and gov together. Let's see if we can bring up some people from the government as well as other institutions. Thank you. Thanks for all your help. And we have Chakrapani who's from Bangalore. Hello everyone. I'm Chakrapani. I'm from Bangalore. I started my Drupal journey in 2009. I was part of the Drupal camp in Hejabar when Reasons visited Hejabar. And I moved on to Bangalore and I was involved with the Drupal community in Bangalore. I've been organizing a lot of events, sports events in Bangalore. And we are going to have the first Drupal camp in Bangalore in July. Really excited to go to India. That's right. It's exciting. Thanks for all your help. Who's planning on going? Ever we do is going to have the right bandwidth in the venue that we have. We'll have people on the ground to make sure that... It's all kinds of different things in different countries. You need generators. And in how there's so much more logistics. He's an expert. Wherever we end up he's going to advise us. He'll travel to that place. Any other questions? Alright so the next item is the Drupal.org infrastructure working group board chair confirmation. Sure. Since I prepared this nice long speech. So we recently had the chair of the infrastructure working group set down. It was his recommendation that we promote up on Ryan Newton who has been on the infrastructure working group since founding to be the chair. And I say I wholeheartedly agree with this and so I close it to the board that we take that forward to a vote. Doran is a rock within our community in terms of keeping our infrastructure up in performance. Helping us get serious really tough transitions. So I think this is a very appropriate transition to make. I would like to put forward a motion to accept Ryan Newton as the chair of the infrastructure working group. You're unmuted if you're talking. I'm unmuted Tiffany. Try now Tiffany. Oh I said I. Thank you for all your hard work. How do we help move Drupal 8 development forward. We did an experiment at the end of last year where we funded a bunch of core again. I want to thank Wondercraft for hosting them while they were there again. Those developers met together for a week and knocked off some digits worth of criticals from that time and we thought okay this could definitely work. The board got together and helped raise 125,000 dollars from some anchor donors including many of the companies represented on the board to basically serve as a match to the community. So the challenge was to the community was can you match this 125,000 to help us get to 200,000. So we launched the actual public campaign we started funding things in January because we knew we had a base to work with but we launched the fundraising campaign in March. So right now as you can see we're at 194,897 dollars not to be too exact about it. If I refresh $50,000 goals we've only got about $55,000 left. So in just two and a half months that means from the community we've raised $50,000. And that includes the gift that we just got this meet from time of $25,000. So if you divide that amount by our $273 the average gift has been $260 but if you take time out it's $168.15. The donation hasn't really you know that doesn't matter right the fact that so many people are giving and one of the fun things we've actually been doing is if you go get your Drupal t-shirt or your Drupal hoodie or your Drupal dog sweatshirt clearly I'll sold out. I need more. You can't get those anymore but if you go to the Drupal store and you get that t-shirt you are able to round up your purchase and put that to AAA Accelerate. So almost at $300 $0.25 at the time right? So now with people that do round up it was $120 by transactions of $130. So wow. I want to find those 11 people who didn't. She did. I got an email and another one today. Another one today? It's really reflective of our community right? People are giving what they can give whether it's big or small and it's all adding up and it's something that's pretty huge. So I just I love it as a metaphor for our community. So do you want me to talk a little bit about what we're spending on now? If I could just ruin that perfect transition though for one second and just say one thing too just for people to appreciate and understand is that when we got we first talked about this and we had our meeting we were talking about raising $100,000 right? We were going to go for it at $100,000 and credit to Kieran who kind of challenged us and said you know if we're going to do this I think we're going way too low right? And so here we are double that and you know so just I think it's worth recognizing that this is a bigger accomplishment than maybe we set out to achieve too. Yeah and so it's exciting that we've raised so much money. We've got a ways to go but we gave ourselves a deadline. But it's the story isn't how much money we've raised it's the impact that that money is having and I don't think that it is a coincidence that people have looked like this since we started funding and that's definitely been affirmed by the folks who are closest to it and do publish all of the grants that are made and the issues that they address and I think you know this list is pretty impressive so Angie you want to talk a little bit more detail about some of the things that have been funded? Yeah I mean the reports are good you can go ahead and read them but they are kind of Greek to people who don't say like I do which I don't understand why you don't but you know so in that big list are things like performance improvements we're doing a lot of really awesome stuff in Drupal 8 to make performance fast by default which is making really poorly done benchmarks makes us look really good because we're like out to here and everyone else is down here. We're also doing things like playing around with rendering caching so we're doing things like Facebook big pipe where we can chuck the initial version of the page out really quickly and then let the dynamic bits filter in as they have time that's going to really improve the perceived speed of Drupal especially mobile devices and we're also doing things to just fix really bad performance regression so we're really aiming for Drupal 8 to be not only fast by default but fast for both anonymous and authenticated users and a ton of work is going into that to make Drupal 8 really really great in that area we're also finding security fixes because nobody wants an insecure Drupal 8 so that's an important thing that we're doing. Just pat it on the back and tell it it's doing a great job. You're doing a great job. Everybody's like stay married and stay married. Yeah so security fixes we're also funding in addition to just like fixing broken stuff in the Drupal 8. If you're curious of what's left and what we might be finding ahead of talking about yesterday but we're also finding some really great community features like the Drupal CI project which is going to be the next generation test bot that is all based on sort of a standard DevOps stack that we can use to do things like test Drupal 8 in multiple environments so we'll know if we commit a patch that breaks PHP 7. For example we can get that all working across any of our supported PHP or database versions and the cool thing about the way that's being architected is we can expand it later to do things like automated coding standards reviews or behavior development testing or all kinds of other cool expansions that we want to get into. We're trying to really be strategic in how we spend this money, not only big impactful things for Drupal itself but also things that help the wider community as well and really forward. That's my field. So I'll just add my just a gigantic thank you to everyone who has contributed to the campaign so far. I know people have been doing that work because it's a lot of hard work so close. The traceability on that page is awesome. I love the connection between the ticket number, the person, and the funds. It's really really cool. It's very transparent and it just makes people realize that this goes to something. Yeah, so on our staff also just to recognize Elise who's been working with Cork Minners to make all this stuff go. She's brought your work on that. Elise is awesome because she does things that we don't know how to do like write checks and all these ideas. We're just like things need to happen and she takes care of it. It's awesome. Where's my hug? Oh, here's your hug. It's exactly twice as much as we've earned. That's how we roll. Something around 87,000. That's what we've spent. I know if you should talk like a little sprints. Outside that is a small amount. Yeah, it looks like there's lots. It's all there. It's the biggest. Nothing smaller than $500 to $12,000. This is several multiple grants that are large numbers, so $3,000 and $6,000. Let's go forward and we can talk about to change the way how we keep the money out because you said like you spent eight hours to fund somebody for five hours. Yeah, I did say that. How did that change? That's a great question. The last public board meeting we talked about, the way that the grant is set up right now is people come to us and they say I would like a certain amount of money to fix this issue. We always start the grants at $500. We can kind of make sure everyone is a wonderful people, but some people do better with deadline based development than others. We want these things to accelerate and not get $500 and eventually fix something. We were doing a thing where we would get these grants or we would go out and find people and say can you work on this for $500 with some of that happening too because we wanted to be respectful of spending the community's money well, but it was a lot of work. Last board meeting we got approval from the board for those individuals who had been successful with the accelerated grants in the past, especially multiple times instead of making them come back to us every two weeks for now. Can I have this much money to work on these things just instead giving them a chunk of money and for a longer period of time and say just work on critical for 20 hours a week for four weeks. I think that overall has been going really well. I think the challenge has been that they're working on Drupalate more than I'm working on Drupalate and so sometimes it's like whoa! We have to do some work to sync up that. We've been talking on the core committer team about how to better coordinate the efforts of people who are working on Drupalate a lot, whether they're funding through D8 Accelerator or otherwise. But that's sort of separate from the D8 Accelerate process. In terms of D8 Accelerator, I think it's been working well. We can see that line going like this, which before was going like this, so it's been really good. We'll have to meet and kind of revisit. We wanted to let the experiment play out for a month and then kind of revisit and see what we wanted to do. I can't tell exactly how that's going to go, but yeah, we were grateful for the opportunity to do that and try to see how it flew. Andre's been fixing a number of upgrade path issues. Daniel's been blazing forward on views and the API integration as well as multi-lingual issues. It's been great to just trust them to get their stuff done and not have to baby them along and do a bunch of discussion about it. Overall, I think positive, but it is a little bit more challenging when there's larger chunks of time and not quite as much oversight as when they tell you, I want to fix these three issues and you say, cool. Does that make sense? What happens with the rest of the money when we hit zero critical before we burn through it all? That's a good question. The question was what happens if we get to zero critical before we spend all of the money? Well the good news is even after we release eight, we'll find you critical. I mean, even today we have criticals in Drupal 7. I guess we could use it towards those criticals. Yeah, we could use it towards there or we could maybe have a discussion about switching it to quarter critical. There's a lot of things. Once Drupal 8 is out, then adoption is dependent on how it passes. I don't know that there will be though because honestly my intent is to spend most of that money soon because the sooner we spend it, the more of an impact it has on the acceleration of the release. But if we do have a big chunk of money or someone decides to write us a $50,000 check at the very end, it's like awesome, we will definitely find it. No more questions? I think that was the last item. It was. Any other questions in general? About anything else? Do we have another question? If there are no other questions, emotion from the floor or a group photo with our Indian contingent and the board? Good. Alright, thank you everybody. Great meeting. I got the sunglasses. Bye everybody. Everyone say paneer. Three, two, one. It's a I'm a You bet you are. Be there with the crown on. So