 Good morning, Drupal. Come to Los Angeles. Oh, I almost forgot. I'm Holly Ross. And oh, thanks. I'm the Executive Director of the Drupal Association, and we're so glad to have all of you here. And before we kick things off, I do want to say a huge special thanks to folks in the room who are helping us make Drupal 8 happen, because of course, that's one of the biggest parts of what's happening in our community right now. So if you have made a donation to the Drupal 8 Accelerate campaign, could you just stand up for a second? Thank you so much. These guys have helped us fund the work of getting our last release blockers out of the way. And if you can do the same thing today, if you go to Drupal, the, sorry, association.drupal.org, you can get details about how to donate. But more importantly, how many of you guys have a patch in Drupal 8 Core? Can you stand up? Way to go, you guys. Thank you for literally making Drupal 8 happen. That's amazing. Awesome. Well, I'm here to represent the association, and I want to tell you a little bit about our mission. The first part of our mission is this. Drupal powers the best of the web. True story, right? And our job at the association is to unite this global community that builds and promotes Drupal. That's our job. And really, what that means is that we recognize that you power Drupal, so it's our job to empower you. We do that in a number of ways. We help grow and sustain the community. What we hear all the time is for folks who are new to Drupal, and how many of you here are at a Drupal con for the first time? Awesome. Welcome. Welcome. So we hear all the time that getting into the Drupal community is actually somewhat difficult. It's hard to get behind the velvet ropes and understand how to get engaged. That's part of our job is to help you guys figure that out. Anyone come to the first time attendee social last night? Awesome. We're going to help you do that at Drupal cons by helping to orient you to what happens here at the con. But we do that also on Drupal.org, the home of the community. You'll notice we have new profile pictures. This gentleman is very snazzy. And we get to do things like Mark, this is someone who's new to the community. So maybe go easy on the lingo, right, with that person. What's that? Oh, let's see slides. Okay, thanks. So we're helping to tell people, you know, be nice to new folks, right? And we're confirming folks who are part, you know, confirming that they're not spam bots, but they're real actual people that gives them superpowers on Drupal.org. So we do it at the cons, we do it in the community. We also want to make sure that Drupal jobs get filled, right? That we help developers find not just a great community, but also a means of employment with Drupal. So we have jobs.drupal.org. And we also hear from folks, I want to get engaged in my local community, and I want to help organize my local Drupal developers. So we have camp kids and fiscal sponsorship. We have a new community organizer newsletter. And if you haven't seen, we have community cultivation grants. So if you want to get a new camp, a new meet-up, a new Drupal users group going in your area, check that out on association.drupal.org. So we grow and sustain the community, but we're also looking to help increase Drupal adoption. So we work with all of the shops in our ecosystem to help them sell Drupal 8. If you go to Drupal.org.drupal-8.0 because we're nerds, so what would you all be without a point and a hyphen? We have lots of materials about Drupal 8 there showing what the best features are that are coming out. You can get infographics for all kinds of different use cases. We also have landing pages that talk about the various ways that we can use Drupal. We also have a new tri-Drupal program that we're launching with currently two, about to be three, soon to be five partners, helping people spin up 30-day free development, free 30-day trial Drupal sites so they can evaluate Drupal and decide to become Drupal users themselves. So we help increase Drupal adoption. We also help you build the software. How many of you guys have started using the comment credit attribution on Drupal.org? Awesome. We've had so many people use this. We're helping you understand how we're building the software together as a community, and we're helping you do that also by giving you better profiles so that when you need help or want to connect with someone in the community who has the skills you need, you can learn more about them. Michael has, you look very handsome here. Nice profile picture. So Drupal powers the best of the web. You power Drupal. Thank you for doing that. And I also want to thank the tremendous ecosystem that's built around Drupal, our partners who help fund the work that we do at the association and within the community. They give us not only money, but they give us amazing time for our entire Drupal year. And specifically here at the conference, the folks who have helped make sure that you could be here and we're going to have a great time. So thank you so much to all our Drupal and Drupal con sponsors. Yeah. Excellent. Okay. Also, a few housekeeping notes I have to give out. If you've been here before, you know that it is a tradition to take a group photo immediately following the Drees note. And what you're going to do is stand up, exit the building out that way. You're going to follow Jam. You may remember him from the Minnie Mouse costume earlier. I understand he's taken it off. That's too bad. But you're going to follow him out into the plaza for our group photo immediately following the Drees note. So hustle out, do that. You don't want to miss it. Also, coffee. Apparently you like it. I want to let you know that there is paid coffee all day in the 300 aisle of the exhibit hall. And there is a free sponsored coffee break at 10.15 this morning. So thanks to Isovera on site ground for making that happen. They are sponsoring those coffee breaks today, tomorrow, and Thursday at 10.15. Yes. Applause for coffee. Wi-Fi. Here is the access. And if you see any Drupal Association staff around today, they also have it printed across their backs. So just be like, hey, nice to meet you. Could you turn around? You'll get the password. Also, if you are in this room right now, one of the things that we do that's amazing about DrupalCon is that we record every session and make it available practically immediately online. It will be much more difficult for us to do that. We also live stream the keynote, but it will be much more difficult for us to do that if you are currently sucking the Wi-Fi dead with your Mi-Fi devices. So if you could turn those off, that would be amazing. Thank you so much. Okay. And food. Lunch options. If you are a vegetarian, you can pick up your food at lunch in the main buffet lines in the exhibit hall. If you are vegan or you have another special meal, you have your own buffet station. And if you just decide you want to be vegan today, don't. Today's not the day to start. Don't eat the vegan's food. Don't make them starve. Okay? So if you are not vegan, halal, or have other special food needs, don't go on that line, please. All right. A couple of schedule changes that I think we need to get through today from 5 to 6 p.m. room 518, the core conversation is now going to be constructive conflict resolution. We're going to be talking about conflict resolution with Donna Benjamin. I'll see you there. It's on my schedule. And in the Drupal.org track, content strategy for Drupal.org will be at 1 to 2 p.m. today now instead of 2.15 to 3.15. So if you've got your schedules out, jot those notes down. Code of conduct. This is probably the reason that I love the Drupal community so much is that we value our commitment to each other. We value inclusivity. We value transparency. We just really respect one another. And our code of conduct is part of that. So let's make sure we live up to it here at the Drupal con Los Angeles. It's up on the website. It's also printed in your program book. And if you do have any issues, we do want you to talk to the community working group. So contact details are there in the code of conduct for that. All right. So also Drupal Association has a board meeting on Wednesday. We do always have public board meetings, but they're usually not in person. So this is your chance to see Dries and Angie and all of our other amazing board members in person. It's so exciting. Board meetings live and in person. Yeah. Approve those minutes. We're going to do that. It's a better agenda than that. But we're going to do that on Wednesday at noon. We're going to be in room 410. So come join us. And trivia night. Who loves trivia night? Yeah. Thank you so much, Palantir.net for sponsoring this. The amazing Jeff Eaton is going to be hosting again. So we'll see you at 3333 live. Doors open at 8 on Thursday. Even if you are new to Drupal and know nothing, feel like you can't answer any trivia questions. Don't worry. By the time we get started, no one else can remember any answers either. So it's going to be good. Women in Drupal. This meetup. Yep. The meetup happens tonight at 6 o'clock at the engine code number 28 on Figueroa. So we hope to see you there at this great mixer. And if you haven't gotten your Drupal gear yet, come over to the Drupal store. It's booth 422 in the exhibit hall. You can get a Drupal t-shirt for your dog, which is obviously what that dog needs. Yeah. Contribution sprints. Who's already sprinted here at Drupalcon? Way to go. We're going to see even more sprinting going on throughout the week. But Friday, of course, is the big all conference sprint. So even if you've never sprinted before, we strongly encourage you to come out and figure out how to make your contribution to Drupal. We have first time sprinters workshops available. They're going to get you all set up with the tools you need. We're going to have mentors on hand to help you walk you through it, and then folks that will help you find your very first issue. You're going to write your first patch. And if you're one lucky person, it's going to have that very first patch committed live on the spot by our very own Dree. So you want to be part of that. Come to the sprints. And with that, I just want to say you, I want to say thank you to a couple of longtime community members that you may remember as pro people and blink reaction. But today they're here to announce an exciting new joint venture. In the year 2015, two of the largest Drupal companies in the world decided to join forces and create a powerful new brand. I'm sorry. I think I had a little bit of CQ five on my throat. As I was saying, at the end of March, blink reaction and pro people decided to join together, creating a brand new agency called FFW. We are a digital agency built on technology driven by data and focused on user experience. FFW is 420 people spread across 19 offices and 11 countries. Let's take a tour of our offices. It's important for us to give back to the Drupal community. And we do so all around the world. We have organized and sponsored camps, cons and training events on four continents. We have two full time community contributors on staff and hundreds more that are active in the development and maintaining of critical Drupal modules. Drupal is about the people who work to grow it. And the key to continuing our global progress is to support the local communities and individuals that drive the project forward every day. Hey buddy, my name is Nancy Stango. And I'm Michael Dreher and together we're FFW. These past couple of months has been very exciting for us. We've been spending the time getting ready for DrupalCon but also ready to launch our new joint brand. It sure has been exciting. And we'd love to tell you more about it. Please stop by our booth, number 300 where you can also get a chance to win a trip to DrupalCon in Barcelona. But before we move on to what you guys are really here for the keynote, we want to make sure to thank the Drupal Association for giving us the opportunity to show off our new brand. And we want to thank you guys for spending these past five minutes with us. So let's get started. It's with my pleasure to introduce the keynote speaker, the reason why we're all here today, the founder of Drupal and Project Lead, co-founder and CTO of Acquia, Dries Baitar. Woo! Good morning everybody. I was actually just like, as I was listening I was trying to figure out how many of these DrupalCon have been to and I think it's number 23. And so this is my 23rd keynote, which I think is pretty exciting. So I'll be talking about, let's see if this works. I'm not sure if it works. There we go. Sorry about that. I'll be giving another state of Drupal, but before I do, I wanted to take a minute and think about Aaron Windborn, who unfortunately lost his battle with ALS. For those that don't know Aaron, he was a very well respected contributor. He was a friend of many of us and really a role model for many of us in the community. And so one of the things that we've decided to do is that the community working group created a new program and award, which we will call the Aaron Windborn Award, which every year we will give to somebody in the Drupal community that we believe represents our values and basically is a great asset to us. And so we'll do that in respect of Aaron. And if you want, you can start nominating people. There's a little bit more information on Drupal.org, so please check it out and nominate other people for this award. All right, so today I'll be talking about a number of different things, really. One of the things that I realized is as I was traveling around the world and I was telling some of the stories about the history of Drupal, I kind of noticed that many people didn't know those stories. And so what I want to do today is spend some time retelling some of these stories. And I think it's important to help us reinforce the culture and some of the things that we've gone through to help everybody in this room understand where we came from. In addition to that, I'll also be talking about the future in Drupal 8, I'll give you an update on where we're at, as well as some other things. And so some of you may have heard me talk about some of these things, but I'm going to try to add new elements to it and kind of make it interesting for everybody. All right, so I think it was about nine months ago and I was in Brussels and I went to this hotel to have a meeting with a potential Drupal user and so I was a little early to this meeting and so I decided to walk around a little bit in this amazing lobby, actually, and what I saw was quite interesting. On the wall, there was this little photo and it turns out that many, many years ago they would organize conferences at this hotel in Brussels and so they put up a photo of the people that attended the conference and so as I was looking at this photograph and some of the names of the people at this conference I was actually quite amazed. I was amazed by the fact that all these people kind of lived in the same little time frame. Like in my mind, I was maybe more spread out. I was also amazed by the fact that they would all come together instead of maybe going off on their own or inventing some of these things on their own and then if you think about it, these people came together in Brussels. They each invented some really, truly amazing things, things that saved the lives of millions of people and things that evolved into multi-billion-dollar businesses. You know, they all came together and so by no means am I trying to compare or sell to these people by no means but as I was looking at this photo it kind of struck me like the way we come together and the way we make connections between people has definitely caused some really cool things to happen and so I'd like to talk a little bit about that today. As many of you know, I started the Drupal project in my dorm room in Antwerp in 2000s and I wouldn't have been able to do so if it wasn't for the work of some other great people like the ones that you can see here that eventually ended up creating a LAMP stack and so the LAMP stack was born and really allowed me to get started with Drupal and so my initial plan was to create a quick message board so me and my friends could share messages but very quickly this message board evolved into an experimental platform like I was interested in the web and I would look at emerging trends and I would incorporate these in Drupal and so within a year actually we did three major versions of Drupal sorry, I'm a little behind we did three major versions of Drupal in one year and as you can see from the slides there are some really fundamental things that we added early early on in the lifetime of Drupal and some of these things like blogs weren't called blogs at the time we would call them public diaries and people started to use the internet to share diaries online and later it became blogging for RSS feeds I was on the mailing list where RSS feeds were invented and I don't take any credit for that but I was there lurking and it would implement RSS feeds in Drupal and so one of the things that I started to do is I really wanted to have people use Drupal and so I would effectively reach out to people and before I started with Drupal I was into the Linux kernel I contributed a little bit to the Linux kernel and so I would follow a website which was called KernelTrap and KernelTrap was managed by Jeremy Andrews and at the time Linux and the Linux kernel was a very hot topic when everybody wanted to read about it and so what Jeremy would do is he would basically listen in on the kernel mailing list and he would take interesting conversation and he would blog about it and so Slash. I don't know how many people know Slash. Do you know Slash. A lot of people do but back in the day there was something called the Slash.Effect and so this was in a time where dealing with unexpected traffic spikes or hosting wasn't what it is today but this time somebody got on Slash. The site would typically go down and so they called this the Slash.Effect or if your site didn't go down people usually ended up with a hosting bill of thousands of dollars so it is a big thing at the time and so every time Jeremy got on Slash. His site went down and so he was using something called PHP Nuke or PHP Post Nuke I believe and so I emailed Jeremy and I said you know you should really convert your website to Drupal and here's a screenshot of that email actually this is the original email and I used pine back in the day where those that remember pine and I basically said if you convert your website to Drupal it will never crash again and to close the deal I offered you can see it here I offered to give him access admin access to my own website which was based on Drupal and so I offered that up to him and I did and this is what it looked like at the time and so this was Drupal around 2002 I think of course that sealed the deal it was very pretty for those that were around you may remember all these admin links we sorted the admin links by module name and so things like information architecture, usability it was basically non-existing and so Jeremy did convert his website to Drupal and of course the first time he ends up on slash dot and the site crashed and so we were like but we used it as a learning point and we made some changes to Drupal where I improved the caching of Drupal and Jeremy took the lead in creating a module called the Trottle Module and the Trottle Module was cool because what it would do is it would look for spikes in traffic and then automatically disable features based on the load and so for example if the load reached level 5 we would say let's disable the 4 module block when the load would reach level 6 we would disable commenting all together and so you can configure all of these things and so next time you got on slash dot it worked and so everybody was very happy and so a lot of that work basically translated in early 2002 which became Drupal 4.0 and so we added the node system by the way in 2002 we added a caching layer and then we added the Trottle Module and then also we started getting all of these patches to make Drupal faster including a new taxonomy module that was more scalable turns out later that a lot of these patches came from somebody that was running an adult entertainment website and so he had a need to take Drupal to sort of the next level in terms of scaling and so you know Drupal 4 was a lot about scalability and making it work better alright and so and so that's pretty cool because what happened next is that Jeremy was really hooked on Drupal and ended up starting a company called Tag1 which ended up employing a lot of our key contributors that ended up doing a lot of great things for Drupal he also started Drupal Watchdog and all of these things so this little email that I sent and basically stretching the truth maybe a little bit has actually been a good thing because Jeremy joined our community and has given back you know 100 times more and a few years ago actually Jeremy emailed me back that email that's why I still have it and he said this email changed my life which was kind of nice of him to do and so there's two quick lessons the first lesson you may not like because sometimes I give presentations at other conferences about startups and how to grow things whether it's a company or an open source project and one of the things that's key is that you have to sell and when I say sell I mean that in the broad sense like you have to evangelize your vision even if you're working on a patch you need to sell your vision for that patch if you're working on an initiative you have to sell your vision for that initiative or even for those of us that run companies if you're recruiting getting people to join your company is a form of selling as well and then once they join your company you then need to sell them where you want to go with your company when I do these presentations from time to time a room full of engineers not unlike this and I tell them the one thing you have to learn is to sell usually the room gets a little quiet but I do believe it's true and I also do believe it's not like pure selling it's like selling as a in the broad sense so to speak and then once you sold somebody the key is to make them successful it's actually very simple growing your community is bringing people on board and then making them successful and if you do so amazing things will happen and Jeremy I think is a great example at least named 12 other examples of people that join their community and ended up doing amazing things so these are my first two lessons for you so by 2000 we had Drupal 4 and all of these features and in many ways we were ahead of the curve this was before Web 2.0 I think it only came in 2005 and so we had a lot of these building blocks at the time to build dynamic websites and to build interactive websites which would later become Web 2.0 and so the fact that we had these features caused something really cool to happen so basically in 2004 Howard Dean who was a presidential candidate here in the United States decided to do something very innovative and he was the first presidential candidate to use or leverage the internet to campaign and he would raise millions of dollars and he did that with something called Dean Space and Dean Space effectively was a Drupal distribution and so while he was the underdog and he obviously didn't win the elections he actually got very far to the point that people said wow this is game changing to the point that by the next presidential elections every presidential candidate will use the internet to do this and so Dean Space was actually a very big turning point for us and we got mentions in all sorts of media like Time and Wall Street Journal and all these kinds of things also a lot of great people joined the Drupal project through Dean Space and you can see some of the names here and the Rappaport actually ended up on the board of the Huffington Post there's David Strauss and Zach Rosen herein who was an amazing connector still today and sort of brought a lot of these people together and so even though Dean Space or however Dean didn't win it was a great win for Drupal these people joined and some great things happened all right so then and the Rappaport was also an investor he said you know I like this idea you know I think we need to invest in this Dean Space idea and he decided to start a company or fund the team behind Dean Space or a part of that team to create a company called Civic Space and the idea behind Civic Space was to take the Dean you know Dean Space platform if you will and get it ready for the next presidential elections it was the next presidential elections it wasn't for another four years and so they could build all of this technology but they couldn't test it and so they built this company some other great people joined actually Chris Messina was very active in Drupal he ended up being instrumental in OpenID and also ended up inventing the hashtag he joined the Drupal community and basically what they said is you know what because there is no presidential election we're going to campaign for something else and so they said and at the time Mozilla which we all know basically had created Firefox and they said we're going to campaign for Firefox and they built this website called spread Firefox and they got some other people on board and they started to use Drupal and make Drupal better to promote Firefox and so they did all sorts of cool things like one of the things that I remember is at some point they said we're going to raise $50,000 and we're going to use that money to buy a two page ad in the New York Times to kind of make fun at the time of Microsoft Internet Explorer to tell the world there is a great alternative and so they did they raised $50,000 and they ended up promoting Firefox in the New York Times as well as in many other locations and so in many ways Drupal helped spread Firefox and Firefox become a thing like we were instrumental in getting them adoption all right and so here we are we just used Drupal spread Firefox as a great success and it really kind of helped us grow as a community it gave us credibility and then just like in that photo that I showed you a lot of these early adopters they went on to do many great things it's kind of amazing actually one of them ended up starting a company Blue State Digital and when President Obama decided to run they said I want to work with that agency because they were involved with Deanspace and so Blue State Digital helped President Obama win the election from a digital point of view so all of these people were involved with Drupal which is kind of amazing and to me that is lesson number three it's all about the people attract great people and amazing things will happen lesson four I showed you earlier it's like you want to recognize trends early and you want how do you attract these great people with things that people really love and so I think there's also a very important lesson there recognize trends early and embrace them and so by this time in the history of Drupal we really felt like we were on to something like it was kind of hard to believe all of these things that happened and so we decided to organize the very first Drupal con we organized it in Antwerp where I was living at the time and we had 27 people in attendance and I remember I couldn't believe that 27 people wanted to travel to Antwerp to talk about Drupal for three days I thought I was like unheard of I thought I was crazy because for the most part I would work on it from home and I would talk to my friends about it or it was kind of like what I did and so we organized the very first Drupal con in Antwerp and these people I'll travel to Antwerp to talk about Drupal at the time by the way we had the node system I think it was Bergesels he had created Flexinode which was kind of like CCK before CCK and at Drupal con Antwerp we did it for three days sort of architecting CCK and so now CCK is the entity API and all of these things so if you think about it it took ten years for us to go from Flexinode to CCK to the entity API that we know today kind of interesting all right and so as we grew and as more people joined the project something else happened around 2005 there was a big server meltdown and I've told this story before as well but at the time I was running Drupal.org on a shared hosting account so one of the Drupal people Kertan Manus he had like a little server somewhere on which he hosted client projects and he said yeah sure you can have a shell account you can run the Drupal.org website from my shell account and so by 2005 we had so many people coming to the Drupal.org website to deed it out and basically the server crashed and like I shifted a lot of my focus and Kertan did the same from actually working on Drupal to tuning the machine but as I said at some point it just it crashed so the only thing that I could think of is to replace all of the pages on d.do with like a white page and there was a donate button with a PayPal donate button and we had a little bit of text like please donate some money so we can buy a bigger server because I was a student I didn't have any money and we did some quick back of the envelope calculations and we said we have $3,000 we can buy this huge server like we wouldn't have to buy a server for like five years and so we replaced every single page on d.do with a blank page and something amazing happened like within 24 hours people had contributed $10,000 and so I never had $10,000 in my life and so completely freaked out I remember changing my PayPal password to be like this long PayPal immediately blocked my account because for the first five years of Drupal I got like $50 over five years and all of a sudden we get like $10,000 in two days and so we had to deal with unblocking that and then something else happened Tim Brabe was a CTO at Sun Microsystems but also co-invented XML by the way he emailed and said you know what I've been tracking Drupal it's kind of cool we use it within Sun I just shipped you a $7,000 and I was like wow here we are $10,000 and basically the next day a $7,000 Sun server arrived on the curb so we ended up using this machine and we called it Sun Price because it was a surprise from Sun it may still be in use I don't know no longer in use it's and then something else happened the OSL the open source labs in Portland they said you know what we can host a server for you like we'll give you bandwidth, electricity and oh by the way we have some students they can help run it for you just ship as a server I'm like wow within two days all of these things came together and so we shipped the Sun machine and we ended up buying I think three more servers with the $10,000 because we felt like we raised the money for servers so we should use it for servers and so all of a sudden we went from a little shared hosting account to this like but looked like capacity for the next 20 years but in many ways this was like an amazing point in the history of Drupal because for the first time you could see sort of the magic of the Drupal community like how people would come together you know and chip in and really sort of do something great here and so what we did is we made this Drupal poster inspired by the spread firefox New York Times which basically would list all of the names of the people that chipped in money and we would take it around to the world to our events and put it up as a thank you and so it was really nice and so I think the lesson there is you know it's all about the community if you want to go far you want to go together alright later in 2005 we all got together at OSCMS so this was kind of like a Drupal con really but we decided to invite other projects and I was like 90% Drupal people and 10% other people but we tried to embrace them and welcome them by changing the name of our conference for one time and so Boris Mann and Kieran and myself we sat down on this couch in Portland and we said we need to start the Drupal Association we need to start the Drupal Association because I just accepted $10,000 in my personal checking account and technically I have to pay income tax on that that's not cool I still to date I think I owe the tax authorities income tax on that $10,000 but we said really we need to organize ourselves a little bit better start an association so at least we have a checking account so we can you know take in money and use it to help grow Drupal and also because we didn't have any money and so this was at the OSCOM O'Reilly conference O'Reilly was nice enough to give us a little booth area without having to pay and they gave us literally like the booth area in the corner the first away from the entrance and we didn't have any money so we couldn't afford to buy a table like you had to buy these you could buy a table you could buy carpet and so we had none of this but what's really cool is all the other booths that are really nice tables and you know whatever all these things that no people there but we had so many people in our booth and people would sit on the floors and hack and coat and you can see some of it in the photo that it really felt like all right this is kind of the beginning of something great and so what happened next really the next few years I mean there's a lot of stories there as well but I would describe it as the era of lots of people joining you know companies being started the commercial ecosystem around Drupal was created and so you know Drupal kept on growing and growing lots of great things more and more bigger users came along so a lot of sort of expansion but at some point I think it was around Drupal Comparis we started because we had grown so much like we started like what are we we started having sort of existential questions like are we a product are we a framework and we were kind of confused about that and I think that's when we started talking about things like small core and what's nice about the Eiffel Tower by the way that it's both a product and a framework we get it and so we started talking about this and the way that happened in my opinion from where I was sitting is when I started Drupal it was really for me by me I was building it for myself nobody else was using it nobody else was contributing to it and then I made an open source and really what happened was now by developers for developers like other people that wanted to use Drupal as their experimental platform and all of a sudden by this time there was this idea of there's users and some technical users and so they came in they started asking for things and a lot of us wanted to cater to them and so there was a lot of tension I would say around do we just care about ourselves as developers or do we also want to care more about end users and so one of the things that came out of that I think is we decided to focus on providing better usability and we made actually bold moves which created all sorts of shock waves in the community and we said we're going to hire Mark and we're going to hire him to redesign the Drupal 7 admin UI and so he did he looked at our information architecture he created the 7 theme all sorts of things came out of that we also started doing usability testing in Minnesota where we would observe people using Drupal and it was shocking it was shocking to see how hard it was to use Drupal we also ended up doing things like Spark and so in many ways these things weren't natural for us to embrace them to start doing but we decided to do them anyway and I think it helped I think we have a long way to go but I do believe that we've got much better at talking to end users and embracing end users and I think as we grow we'll see more and more users to cater to them all right so and I think it took us a little while at least for me maybe but we started to get this idea like you know Drupal is both a framework and it's an application it's a framework it's for developers by developers but if you have a great framework people can build great applications on top of that and what happens is there is like this flywheel almost it's better the applications can become better and as the applications get better they start to be more demanding of the framework and so it's like this vicious circle almost that makes it better and better and better anyway so we did a lot of work around UX and it was a difficult time in many ways from a community point of view at the same time we also decided for the reasons that I just explained there should be a better framework too it wasn't one or the other and so a lot of this is reflected in Drupal 8 but we ended up spending a lot of time making Drupal a better framework things like symphony embracing object oriented programming the entity API and fields API and plugins and CMI there's a long list of things that make Drupal a better framework and so we really chose to be both and I still today believe that it's the right thing to do I think the fact that we can do both makes us both a great framework and a great product and it's really the combined thing is called a platform and I think it's really what's unique about Drupal that we're probably the only you know maybe not the only but one of very few real platforms and so the lesson though here is that sometimes we don't always agree on things and it takes us a while to discuss but discussion is a good thing it's not a bad thing we don't always have to agree we just have to work through these disagreements because we started making these frameworks better and products better Drupal became bigger and bigger and bigger in a way so the last few years there's been a lot of talk about how do we sustain Drupal if it becomes so bigger like too complex maybe for volunteers to dive in and take on big projects or a lot of burden on relatively few people and their risk burning out or how do we keep innovating fast so there's all of these questions because we grew in size over the years and so I spoke a lot about this especially in Amsterdam at Drupalcon Amsterdam and prior to that keynote I spent a lot of time reading about academic research and books about these kinds of problems because we're not the only one we're not the only organization that has this problem like every public good actually has this problem and so one of the books I read is the logic of collective action I encourage you to read it as well but basically what this book says it's based on research is as you grow as an organization, as a public good and as an open source community the cost of contributing increases I think we can all relate to that if the code base gets more complex it's harder and harder to get in and make changes or to do really fundamental work but also the second thing is as you grow the benefits of contributing decrease because think about it like in the early days of Drupal I could put every contributor on a slide and you could clearly see here's five contributors to Drupal today it's actually hard to put them in a tag cloud let alone in a slide with images and all of these things and so the individual reward from contributing in the eyes of many people decreases so you have these two trends which actually make it more and more difficult to contribute and so there's a lot of material around this but there's basically this notion of freeloaders people that use the software without giving back to the software and that's not necessarily a bad term it has a negative connotation but it's perfectly fine for people to just use the software we need those people actually and there is what they call caretakers these are the people that help us maintain and build the software and so basically if you put this theory in practice what you have is something like this when the project is small and everything is by developers for developers you have a very healthy ratio probably between free loaders and caretakers but as you grow that ratio starts to change you have relatively few caretakers compared to the number of users but really what you want is probably something that has a bit of a healthier ratio maybe something like this this is also commonly referred to as a tragedy of the commons and so this is the stuff that I talked about in my keynote and I encourage you to go watch that keynote if you want to know more about the details sorry and so we decided to leave Amsterdam to start experimenting more and more with these things and so I wanted to give you a quick update so one thing you can do with the scale is reducing costs the scales if you reduce the cost you lower the barriers to contribution and in fact we've kind of done a lot of things here I think like for example the fact that we embrace symphony it's a way of outsourcing a lot of the code if you will and so that reduces the cost of the code base we also empower to Drupal Association to do more of the maintenance of Drupal.org and so it used to be that the core developers very few people may notice but used to be the case that the core developers also maintain Drupal.org and that's also an artifact I guess when I was starting with Drupal I would basically develop life on Drupal.org and so obviously that had to change but things like better governance work on the test bots all of these things help to reduce the cost and we should also keep doing more and more of these things we should all be thinking like how can we reduce the cost of contributing to Drupal because at the same time we're also increasing the cost let's be honest Drupal 8 is maybe a little bit more complex too right and so it's a balancing act there as well alright the other thing I talked about is this idea of selective benefits and this is the academic terms you can go read about it but the way they solve this problem with other public goods is they give the people that contribute that help maintain the public good whether it's Drupal or if it's a park or anything they give them benefits and so that increases the benefits and so out of that idea we launched I think I started talking about this over a year ago about this idea of organizational commit credits and you can see here it's a little animated gives it loops around but that's actually deployed since Amsterdam and so as you contribute to Drupal on Drupal.org you can now attribute your contribution maybe not every contribution today but you can attribute your contribution to the organization that's paying you to do this work and even the customer that's paying your organization to do so what's nice about that is that we can start to see how our community actually works we can see how much is volunteer driven how much is driven by the commercial ecosystem but we can also reward the organizations that let their developers contribute right and so we don't have that data on the website yet but we ran some quick numbers and you can see that there's actually, this is just the top 10 but there's actually a good list of companies that allow their employees to contribute to Drupal and this is not just for Drupal code this is also for contribute modules so the way we could use this information and these are the things that we're going to work on next is the way we can use that information is by providing some benefits to these organizations and so here's an example of you know, Capgemini so we have organizational profiles on D2DO and we could do these little badges or some statistics and the organizations that I talk to they're very excited about this because for them what they want is they want to be able to attract great developers and so the fact that that organization is contributing to Drupal is something that a lot of us like we want to go work for companies that give back right but also they like to use it when they need to convince customers you know, we know Drupal because we contribute to Drupal so these are mockups it may not look exactly like this but that's a kind of thinking and it doesn't have to be limited but on Drupal pages we can you know, trickle these things in across the website for example job boards like if you're looking for jobs companies that allow their employees to contribute we can highlight them in the job boards and makes it easier for individuals to find great companies to work so the idea is that that hopefully will allow organizations to justify contributing letting their employees contribute to Drupal alright so the other thing that we decided to try is fundraising and Holly talked a little bit about this already but we said we're going to raise some money from everybody in the community to try and accelerate the release of Drupal 8 right and so we set a goal if we want to raise $250,000 and we would use that money to fund sprints where core contributors core developers get together and they work on release blocking issues in addition to organizing sprints we also decided to pay developers for fixing release blocking bugs so fixing this bug we're going to give you $1,000 or whatever to help fix that and so we raised a good amount of money again a lot of that money comes from either users of Drupal or the Drupal shops and I'm proud to announce that Timing has just committed to donate another $25,000 to Drupal Accelerates very generous and so the slider will move up a little bit alright so these are some of the things we're experimenting with to contribute to Drupal 8 Accelerates we're still raising money alright and so the history of Drupal you know obviously it's been years in the working it's been 15 years almost working on Drupal and so a lot of people that I talk to they don't realize it's been 15 years or like the example of FlexiNode becoming CCK becoming the entity API these things don't evolve super fast but definitely the history of Drupal has been one of overcoming a lot of milestones whether it's fixing the performance issues for Jeremy on Kernel Trap or whether it's having to start the Drupal Association so we can actually take in money to buy hardware or organize conferences or whether it's working through things like Smallcore or how do we get more end users engaged than designers into the project to how do we sustain the development of core over the next 5 to 10 years if not longer and so the history of Drupal is this chain if you will of different milestones and I'm sure there will be many more milestones ahead of us and this is not a bad thing overcoming these milestones is actually what makes us strong it's a fact that we didn't have $3,000 to buy a new server the fact that we had to come together as a community and chip in money is really what created camaraderie what created the sense of community and so learning to overcome these obstacles is actually what makes us better it's not a bad thing if you look at all these lessons and there is many more and I'm sure I'm forgetting a lot of important stories and I forgot a lot of other key people in the history of Drupal but if you apply these lessons when you look forward I think we need to continue to do the same things we need to recognize the next trends early we need to implement those because we want to attract more amazing people to our project that can go on and do great things with Drupal we need to stick together as a community we need to build this together we shouldn't be afraid to have disagreements and to have discussions because overcoming these disagreements is a key part of what makes us successful and we shouldn't be afraid to evangelize or sell our vision or the things that we want to achieve we should definitely stay committed to making our users successful just like we made Jeremy successful and so if you do all of these things we have done a lot of these things and I feel we've made a real difference and this is when I wake up in the morning this is what I'm proud about the fact that we've made a difference we've made a difference to the lives of individuals I mentioned that Jeremy emailed me this one email that I sent maybe a couple emails I said it changed my life and I'm sure it changed the lives of many people in this room so not only did we directly change the lives of individuals I think we're also making a difference in the world, indirectly by enabling a lot of great organizations to do great things you know like hundreds of thousands of non-profits using Drupal they use Drupal to better fulfill their mission to raise money for their cost to activate their members and so if we can make Drupal a little bit better we basically enabled them to be more efficient at changing the world right we're enablers indirect enablers too obviously governments related things like the ones I talked about but even commercial organizations like Tesla Tesla Motors runs on Drupal and they're doing some great cool things in the world too, electric cars are not a bad thing batteries are not a bad thing and so Tesla is somewhere in the room here as well definitely encourage you to talk to them to the stuff we've done for we the people like we took a basic fundamental right of every American citizen to petition their government something I don't even know how people used to do these things like probably writing a letter on the corner streets and so now everybody can petition the government right these are all things small little bits that help make things better and so that got me thinking like what can we do you know that's what kind of fires me up what can we do to make an even bigger difference and so what if I gave you a thousand dollars what would you use a thousand dollars for to make an even bigger difference right something to think about and so I started thinking about that I didn't know what I want to do with my thousand dollars but I do have an idea of how we can make a bigger difference and so a lot of things right now are a little bit broken or it could be improved upon and I think one example is education there's nothing wrong with education as it is today but it's an example of where the web and digital is kind of transforming things for better so if you think about education the way it works today it's like usually it's in a classroom style environment you have to go there physically then there's a teacher that tells you all sorts of things you know first of all if you want to have the best teachers you need to have a lot of money right if you want to be you want to study computer science and you want to go to MIT it's kind of expensive and often these teachers are in front of like hundreds or dozens of students at the same time they can actually control which students are falling behind they don't necessarily know which are the weaker students and which students may need extra attention or extra lessons or exercises and so I think there is a huge opportunity for the web and Drupal to change that what if we could provide the best teacher in the world and I think that's where the web is really disrupting education like Tim Berners-Lee if you want to learn about the web could teach kids everywhere in the world thanks to some of the technology that's coming along some of these technologies are also smart I don't know if you have used Duolingo to learn languages but what they'll do is if you're behind on a certain aspect of the language say Spanish it will automatically start giving you more exercises on the areas that you're weak at so some of these things I feel like have the opportunity to benefit billions of people I really do believe it some quick other examples like disaster relief and we actually have some examples of this but if things go bad in the world like getting the right information to the right people very fast you know I think you ski what should you do if this happens so I really believe like information can actually help save lives doesn't have to be for the greater good or that kind of stuff even in business I think there's a lot of great examples travel for example right now if you open a travel website say you flew from A to B you arrived in B, you opened the website and asked you to book another flight but really what you probably want is if you lost your luggage you want the website or the app to say hey your luggage is lost here's what you should do next or if you lost your connecting flight it should be smart enough to say do you want to book this new flight or if you lost your connecting flight then there is no more flights it should say there's no more flights I can book you a room in this hotel there's so many things that we can do to build better experiences for people to make their lives a little bit better and so I think the opportunity that we have here is pretty much limitless and so I think all of these examples and I can give you many more examples but I think what it all comes down to is providing the right information to the right person at the right time and I really believe that that would make the world a better place, so to speak and so the question is how would you do these things and that kind of stuff and so I've written about this recently which is this idea of the big reverse of the web and I think if you want to see that vision the right information at the right time to the right user in the right format even become a reality we need to make some very big changes to the web and specifically I believe that we have to transform from what I call the pool-based web to a push-based web today too often you have to go to somewhere to find the information multiple websites to get the information you want or if an emergency happens you have to go and find out what you should do like it's very pool-based the opportunity is to become push-based where information where content starts to find you right I think I think this will be a very big transformation that will happen the next ten years sorry I'm ahead of my slides content will find you and in fact it's already happening and very few people realize this but if you think about some of the big industries or the big platforms out there in media typically people consume media by going to multiple websites go to the New York Times another website and read the things you like but then Flipboard came along how many of you use Flipboard many people quite a few people so Flipboard is interesting because you tell it what you're interested in cars for example and it will look across hundreds of thousands of websites and find you all the car related articles that may be of interest and it will push it to you it's very disruptive it's a very successful platform and it doesn't mean like there's no room for serendipity I mean there's a lot of content that it pushes to you and you can explore within that stream of content it's happening for products as well not just for news think about Pinterest where you like things or you organize things in boards and automatically Pinterest will start to push you other things you might be interested in in fact my favorite example is staying in touch like the way that used to work and still does today is you would call your mom or your dad and say hey how are things going and call your friends very pull based you have to reach out to them and really Facebook changed that using Facebook you can stay in touch with many more friends and family and that information is pushed to you you know same thing is happening with media where you're used to dial in into different radio stations things like Spotify and Pandora are really examples of going from pull to push so I think it's a very powerful trend that I think we'll see more and more of but all of these things have in common is that they establish one-on-one relationships I think this is actually a very big deal like they know the user they know the visitor they know their interests they're very content rich too they actually often use more content because a lot of these examples I gave are actually aggregators but they don't have to be they're also contextual meaning they know your interests and they work on different channels and so let's go back to the example of you know education right and so how can we provide the best teacher to these kids well you know first of all you know we need to know a few things about these users like where do they live you know what do they like what are their interests and you know maybe we know that they're interested in building websites and so how can we basically provide them the best possible training how can we get MIT teachers to you know on their machines or whatever the best teacher is and how can we make it so that they can continue to learn and if they get behind they get extra lessons all of these things so how do we do that so this is a little bit more technical but still very high level but here's what I think you need first of all you need this idea of users and you want to enrich these users with metadata maybe it's location maybe it's their interest you know whatever it is you want to enrich more user profiles and I think Drupal 8 is actually in a great spot to do so like you know users are entity they're you know fieldable they can be extended in many ways so I think we're in a great position there the same time you need lots of content like if you're trying to match lessons with students you need all these lessons and so being able to create great content is very important and in fact as late as out in your head we may actually need much more content than we have today because the opportunity here is that we could tailor some of these lessons very much more closely to the audience for example if we know the students are young you know we can kind of send a variant of those lessons or if we know it's maybe to you know young boys or young girls we can even tweak the lessons based on these kinds of things there's a lot of ways we could actually leverage more content to provide better lessons and so this idea of being able to create more content and then also attach metadata to it so we can you know categorize the content for adults for young people whatever it is and so it turns out Drupal 8 is really good at this too like a lot of the work we've done around the entity API and the taxonomy system improvements the fact that content is more structured and more semantic and the fact that we can translate content more easily I think are all key things in Drupal 8 that will help us do that as well and then the trick is how do we match the right content to the right user and I think there's this magic function if you will which is get the best next experience I think this is kind of the holy grail of what I think most websites will start to figure out how do we implement get best next experience if you're a student looking for the next lesson whatever is the next lesson based on how you did in the previous lessons based on your interest for example these kids in Africa maybe it's rain season or something like can we find lessons that will leverage the context of the students to provide a great learning experience or get best an experience in the travel example could be if a luggage is lost do this if missed connecting flights do this and so this is the closest I've come to coding in a few months but you can probably imagine some pseudo code in your head of how we could implement some of these things so you have these enriched user profiles and you have this enriched content and this magical function get best next experience is what will bring these things together I think often you can implement these things in Drupal but I think also very often you want to make calls to third party services I could imagine in the example of education that you want to do a call to a scoring service maybe there's another system that scores students but you want to get their score to help with the matchmaking I think that's kind of an intuitive example and once you've found the right content I think you have to output it in the right format so it's great that Drupal supports structure content and then send it to the right end point in the case of a smartphone with native apps or like an Apple Watch I think you want to use things like JSON and RESTful Web Services like how many people realize that the Apple Watch doesn't have a browser most people don't but the Apple Watch doesn't have doesn't have a browser it's something to think about and how that changes things if these things will actually take off obviously we will also output these things to actual browsers and so we've made a lot of great improvements in Drupal 8 around layouts and templating with Twig and responsive design and HTML5 and all of these things so Drupal also for that will do a great job and then this like imagine in a world where most websites next experience no two experiences might actually be the same like my Facebook page looks very different than your Facebook page and looks very different than your Facebook page and actually no two pages Facebook generates are identical so imagine in extremis where Drupal now has to serve pages where no two pages are identical that makes it a lot harder to cache it's a world that is 100% dynamic not saying that's what it will be like but it could be like that for some cases and so there's a lot of work that we've done around performance and scalability where we can use more precise caching more precise caching validation we can offload some of the work to the client or to different layers in the stack to the edge maybe we're also working towards and this is not in core this idea of the Facebook big pipe which basically flips the entire Drupal rendering pipeline kind of upside down but will allow us to hopefully build these kinds of experiences experiences and to scale them effectively again something that we aspire to do not yet in core and so all these things considered I do really believe that Drupal 8 will be a game changer for four years with hundreds of new features I think a lot of the new features are at the right time at the right place and hopefully in a way that the deanspace people are attracted to Drupal because it had all of these great features at the right time hopefully people will start doing the same thing with Drupal 8 and will be inspired by some of the possibilities that Drupal 8 will enable of course when can we use it the answer is that it's actually already in use today not everybody might realize this but there's several hundreds of websites that are in production built on Drupal 8 it's not something we recommend but if you know what you're doing you can start using Drupal 8 today the upgrade path isn't fully supported we're trying to support it through projects we do that upgrade I encourage you to check that out but the point is it's getting better and better and some people, the early adopters the risk takers they're willing to to start using it the reality is it's done when it's done or it's ready when it's ready we have a stretch goal is to release by Drupal Con Barcelona I don't know if that will be possible as I said it's a stretch goal I know it will not be possible without the help of more people it will not be possible without the help of more people we have an amazing team of people that have been working on Drupal 8 every day for weeks, for months and we cannot ask them to do more and so it's really important that more people get involved if we want to make that stretch goal and this is just the top 10 contributors so how can you help? there's many ways you can help you can start porting modules if you're an owner of a Drupal company you can let your people contribute give them time to contribute attend the sprints we'll have sprints here at Drupal Con it's a great way to get involved and to learn how you can make a difference to Drupal 8 you can donate to Drupal 8 if you don't have the time but you have the money, donate and we'll make sure we spend the money to accelerate Drupal 8 and to pay the people that can and obviously you can try Drupal and test it and report bugs where exactly are we? well, there's 28 critical bugs left today maybe it's... I created this slide two days ago it may be inaccurate at this point but it's around 28, if not 28 so you can see we've made some good progress but we still have 28 bugs left once we get to zero we'll start doing release candidates and hopefully there will be a big party so Drupal 8 we've had a lot of people contribute more than 2,800 people contributed which is about three times the number of people that contributed to Drupal 7 core and I'd like to thank all of these people that contributed to Drupal not just to Drupal 8 people that contributed in the past some of which have left us and the ones that are here today working on Drupal 8 thank you