 It's on. Anything? Is it on? It should on. Yeah, it's on. All right. Well, thanks all. One, two, three, four, five, six, seven, eight people to show up to this session. As a featured speaker, I'm really honored the amount of publicity for this session and push forward for this community speak about why people association actually a good thing, which, of course, is not to do this. This is me about 20 years ago, when I was a young, hopeful, young man. Long hair, hippy beard, and all that hippie bullshit. This is me today. This is my whole name. To make it a little bit shorter, we can do it like this, modern birch. To do this, you will see a small spelling error. This is a thing I do in this community. I bitch and moan about stuff. I think that's dumb. I try to do it in a positive way. That's just an act. It's really because I am a bitch. Somebody thinks I'm a nice guy. That's not really true. Anyways, this is my new company. We do a lot of stickers. And I will have a sticker for each one of you all night. I bring a lot of Viking love to this community, which basically means cut the fucking crap and get on with it. That's the thing I really like. And that one, Mary, she do say hi. Hi, Drupal Considney. I swing by and thought for the Aussies, because Mary is, of course, always a part of us, so it's a good thing. This is actually my sponsor, Ten Collector, who actually paid for me to get down here. And if anybody have a Twitter client, can you send her a tweet and say, hey, thank you, Morten. Oh, thank you. Georgie just sent Morten down here. I am not going to do this talk again in about a week in Melbourne, because Melbourne actually ponyed up compared to what Zickie can figure. So go Melbourne. How many of these here is actually members of the Drupal Association? We have one staff member here, so it's not a member. It's actually pretty easy, and it's only $30 a year. And so you just click up here and say, become a member, and then you can get, like, t-shirts and stuff. That says Drupal, and it could be epic. If we look at this whole Drupal project, one of the first statements I've heard about Drupal was that all CMS sucks, but Drupal sucks less than all the others. There's kind of been a mantra in this community over the years, which is a good thing. But we rolled back about 10 years ago when the actor was called drop.organ. This shows how good a way we're actually starting out was starting out on a spelling error. So it should have been Dorp, which means city in Dutch. It turned out to be drop instead, which is Drupal in Dutch. Hello. So that's, of course, a good way to start. The first CMS commit comes in about 2000. The same thing with this beautiful, beautiful logo, especially the slogan, tears of technology, think it's a saying that we have seen a lot of in the issue queues over the years. It actually looks like this at this point in October of 2000. It gets a huge design upgrade a couple of months later. It really shows that this community is based for designers and really takes care of that part. This is clearly a nerd and geek project. And we look at the whole project. The first idea was actually a total world domination. This is the initial first post that actually sets the start of this whole adventure from 15th of January, 2001, which makes us soon to be a teenager. So we can make a lot of trouble. I can see a lot of folks and a lot of fun coming up the next couple of years. The fun thing when we look at the second release a couple of months later, and we only have a couple of months between each release. That says a lot of the code base at this point. Two months instead of two years. But the friendly but small community, small we could actually change it a little bit later on. We get spread Firefox, Drupal docs, to U of 4, 2, 7, actually get the first Drupal book release about seven years ago. J. Crower gets into the Drupal project which made J. Crower kind of explode at that point. This very tiny project, which by the way caused a shit ton of trouble in the community. I think Kevin can remember some of the long, long, hard discussion about why we should not rely on JavaScript to do anything because nobody used JavaScript for anything, right? Anyway, the association is born in 2007. We get the White House.gov in which kind of made everything blow up and shit ton of business rolled in, which was a good thing. Apparently everybody thought that Drupal was the new hot shit. It's kind of the old hot shit and still this hot shit. We got Symphony now into Drupal which is even more exciting. We killed CVS, which is a great thing for a lot of us so we can actually begin to contribute. We got an office in Portland so we actually really got a staff here, which is an interesting thing. This is the historical moment when Git finally came into Drupal and there was a lot of nerds who celebrated that day because CVS is a piece of shit and I hated it with such a passion. I actually have wrote Haiku poems for it. I am not kidding. But one of the things I've learned over the years in this Drupal thing is actually that this whole gathering of geeks that we have, which is a kind of celebration of Drupal. People who know this guy, this is Drum. Neil Drum back in Antwerp about 2006. We have Dries up here. We have various people that couple of emotions here. I'm not sure, yeah, kind of don't have all the names. So there's like four or five left. Portland in 2005, that was not a Drupal con by the way. It was part of OSCON, which happened again in Amsterdam. This was actually the first time that we had a panel discussion at a Drupal con or a Drupal event. That's not a good thing to do in Amsterdam. Apparently people were a bit tired that day that function. So it was mainly, as far as I know, kind of an epic fail. Vancouver, the really great thing about this is, oh thank you, let's just roll back to this one. Why are you teasing me this way? I don't hate you, you hate me. Good, a very, very young version of Dries, especially this is the very first Drupal T-shirt that actually ever came out. I think what he's trying to demonstrate here is the published option on a note. Brussels, 2006, we have WebChick here. I'm there as well. We have Andreas who's down. Today is chief architect of Polio. Cormor works at Twitter. We have a bunch of, it's kind of a bunch of going and look how many of these people are still in the community. It's about 60%, oh, and the mighty Dries as well. Yahoo, it's on. We did not take a picture here, which was really, really dumb. This was back when Yahoo was still about something. Now they have Flickr, that's it. But that was kind of a big thing. The conference sold out so quick that we could not even believe it at that point. Like holy crap, we sold 400 tickets to a conference. Ha, ha, ha, ha, ha. And we did the same thing six months later in Barcelona, which was actually the first time I heard a person go up on stage and actually say, I'm sorry for the code that they did. This was Jeff Eaton who made a public excuse for FormAPI, which have destroyed so many lives at that point. And this kind of also shows me a way of how this Drupal community works. It's okay to fuck up, we all do that. Boston, now we're beginning to be, so many people cannot even be in a photo anymore, 2,850 attendees. We went to second, right after that, second is the way the fuck out there in Hungary. It's not even the capital, it's like a student city three hours away in small little trains going through old Eastern Europe, by the way, Central Europe, it's very important to remember that, that's Central Europe. I learned that the hard way. BC requested 1,000 users, which you can see in this, one of my favorite pictures still from Jubicons. After that, Paris, 850 attendees, we should learn in the future to actually be better to make our photos. San Francisco, 3,000 users, attendees. Week and a half after sleep jobs actually came out with the iPad. We were this close to breaking the amount of units and simultaneous connections at that point. Apple beat us, we're kind of far from that. Copenhagen, which I was personally a lead of, which was still think this is the best picture we had from a Jubicons. That's just me. Chicago, now people are beginning to get married at Jubicons. London, 1800s, sorry, Croyton, 1800s attendees, and that was a riot. I mean, stuff went on fire on that content. Denver, I have no idea how many came to Denver. Holy crap. So we're up at number now where you're pretty sure you're not gonna meet anybody unless you prearrange stuff with them. Munich had only 1800 attendees, which is practically the same. When you're up at that number, it doesn't really matter. And we're even doing small events now, like frontend United that had about 210 days that we've got six years back. That was the size of a Drupal con and this is only for frontend nerds. There's kind of this cult of Drupal that have started out around these events. One of the things that, we have that very, very first time when you're ready for the Drupal charity to be popped. And you think it's gonna be easy and you're now experiencing the Drupal learning curve. And the thing is that we have mod X, WordPress, Jumler, all the other good things. It's kind of easy, like a slow curve you learn and you understand. And then we have Drupal, which is basically running into a flat wall. More and sometimes it feels like the wall actually hunts you and smacks you down. And you cannot get away from it. And the thing that I've very, very early learned that it's actually, if you need help, there's always somebody to help you because we're beginning to be that many people and kind of built into the DNA. Of course, you wanna help other people because, well, first of all, if you help them, they're gonna probably help you. And it feels good to show everybody else that you are a badass at this thing where you just click three places or show how that form API works. And it kind of, we have people who, I mean, it's becoming, this is Drupal, that's his handle. He sent me this picture after I sent him a bucket of stickers. He then put that sticker on his leg. That leg is now, by the way, covered in Drupal stickers. I'm not kidding you, it's pretty extreme. We even have, I mean... You got a downpour song. Drupal, Drupal, Drupal, Drupal, Drupal, Drupal, Drupal, Drupal, Drupal, Drupal, Drupal, Drupal. You got a website, you need a system to manage your content, Drupal. We have a song. We even have a band, which is a combination of Swedish, hard rock, Drupal, and killing kittens. They have played up until multiple Drupal events around Scandinavia. But they exist. We even got world-renowned brewmaster Miggler to make us a beer just because we can. And that is kind of the things we do. Even when we release a new version of Drupal, we need to have release parties. It's just a thing. We all know what's gonna happen, yeah, that's how it's done. I mean, why wouldn't we have a release party? This is way more than code, right? There's even like good shared memories, which is kind of where did the $20 go? There's people in the community who knows what Colleen's $20 is. I will not mention name, I protected the innocence here, so one of them is maybe here. This is the events that we have today. I just went into Drupal talk, which is the far best event overview we have. This is the amount of events that we have today in the Drupal community. I think it's pretty fucking badass, to be honest. And when that site came up, and I figured out this the first time, it went a little bit, little bit humble. And I know even for me, that sounds strange, but a little bit holy shit. And this is kind of still the goal. This is a slide, a picture I found from 2009, that this is kind of still, this is still the goal, but it seems like we have this whole thing going on around it where, I mean, we even have developers who don't even build websites anymore, where people who come to Drupal events not to be a part of seeing a session. But there is people who talk about that we actually need to have a hallway track, cause we do have people who never shows up in a session. And one thing is that this whole, oh well, okay, the code is complicated. Well, but, I mean, if we try that with people instead, then it's gonna be really fun. And we look at the number, we have over 20,000 modules. We have about 1,600 themes, one or two that does not suck ass. Ton of distributions, I have no idea what all these distributions does, but they are there, anyways. That's actually not, this number kind of blew my mind, because I knew that in, when we went to Munich, we had 20,000 developers, we just turned that thing that six months ago. As far as I can calculate here, we have about 3,500 more developers since Munich. Holy shit, that's a ton of code coming out of that. The amount of commits we have each week, the amount of comments we have each week, and actually this number is holy crap, this amount of users. That is almost one million users we have on our website. God damn it. So, it kind of takes on this whole own life, and when you look at other systems where every other system has its own kind of flavor of the day, oh, we are now gonna use, I don't wanna say other systems name, not to be an ass, but we have always new system popping up. And it's kind of easy, if you have three people down in the basement, then it's kind of easy to have your own little epic system that can do everything. But when you begin to have almost a million users, 20,000 plus developers who all have an opinion about every fucking thing you can figure out, then you begin to need some kind of management. But actually the thing I think that's really the interesting thing is, the amount of fucking power you suddenly got. This is from DrupalCon in Chicago, where Microsoft publicly says sorry for IE6 to the DrupalCon. I mean, if we had been four people down in the basement making the most epic system ever that just was perfect in any way, do anybody think that Microsoft would even give a fuck? This might be a dumb, stupid little marketing stunt, but I really don't care. Microsoft said sorry to us for IE6. They did not say sorry to the rest of the world, it was us they said that to. I think that's fucking epic, to be honest. This shit runs on about 2% of the whole, the world's websites, mm, that feels good. And that demands a brofist. And what we, it kind of in our being as I see it, like this kind of this two-legged monster where we're beginning to, we have created its own, I mean its own thing. We have people who showing up to a DrupalCon not to attend to the DrupalCon. At that point then we, I mean, in my mind we kind of change it all around. And we kind of have these different groups of people we have the developers and developers really like things that work. Like crab in, crab out, this stuff works. Then of course we have the designers and designers really like things that looks good. That's just a thing that they like. They don't agree upon anything. There might be a discussion about typography of you know what we have our own little four of those. We have the devops who was also beginning to become a part of this whole thing. We have UX people coming in now. I actually want to have an opinion, have an idea of what's going on here. We have the suits that's leaking in and we have this whole group of open source hippies that's coming around. And the whole thing is how do we get all these different groups to work together? I mean just getting devops and developers in the same room to actually agree on things and then put a design on top of that. That ain't gonna happen easy. And the whole thing is can we even live together? Pretty much things that the sad news here is actually that in the bottom line and even me as a happy little hippie is that if we don't have any money, we don't have any code. If we don't have no code, we don't have any money. So we're kind of beginning to depend on each other. And there's no way really around that. So I mean the success here is actually just to hog it out. Just to accept the fact that well we gonna have some companies who gonna push in a shit ton of money and we're gonna pay some people to do some stuff. And that's just how it is. And we all really wanna claim this ownership of this product. I mean I have my front end that I live and breathe to change and make so perfect. We have other people who wanna make that whole database abstraction with abstraction on all these small things. And when all that kind of comes together and we form this community where we actually instead of hating on each other begin to accepting that not everybody else than you actually have the right opinion. Then things actually begins to grow. And it's not easy. At some point we are a big ass fat fucking rhino that really wanna be that beautiful little creature. And it's kind of a, maybe it's a shared responsibility that we actually have to each other. When you download that Google the first time and begin to use it, it begins to become a thing that you just, when you give back you actually get more. And that's where this whole, there's some buttons walking around the community a couple years ago that's like, hey you're the theme to my module. No, I'm the module to your theme. It's corny as fuck. But it's kind of shows this whole idea of actually how we begin to use each other better. And not so much like hating on it. This is a quote I got out of the art of community by Junior Bacon which is pretty much epic. That the whole thing about if we wanna have this to work we actually need to like walk forward together at some point. If we run around in small circles and just scream and shout and battle each other we will not succeed. A thing that's interesting in this community is even though we have existed in 10 years there's only been one fork. Dean Space back in 2005 and they rolled back into Google 4.5. So there's been like one little dropout and that was it. So either people walking away from the project completely and will not touch it anymore or they kind of stays in the same kind of the same grounds. And this is kind of, I mean, I like this idea of marching forward. That's kind of a back to my viking route. This is what we understand. Like that way LA LA or if you see the tour, venga, venga, venga, venga. I'm apparently the only one here who watched Cycling, right? Yes, that joke did not work well. Well, but the directions that we need to take a community is kind of a thing that can be hard. If we just do it as we used to do, then it will be a long discussion and we will not move forward at all. Pick on all of this stuff is actually demanding a kind of group on top of it. Who can kind of set the rules, set the boundaries on making sure stuff works. This is a quote I have from a dude I know that pretty much says how he felt about the association. He loves Drupal but he doesn't give a fuck about the Drupal association. Well, we will not tell anybody this name. I think this is not a normal way of feeling about the association, the Drupal community today. And there's reasons for that. I mean, it has not been good to be open. It's not been good to doing all the right things. It just, that's just how it is. But the thing that it needs is we need some kind of organization of all these people. We have 23, 20,000 plus developers and we have a million users and we have how many events a year and all this thing. I mean, we can just run around full frontal anarchy. Everybody wants different ways. Or we can actually try to find a common path to walk. One of the first things we could begin to do is actually to look up what kind of people we have that provides this leadership. This is, by the way, the Drupal association board. This is me. This is me. This is Dries. We don't have the new leader of it all, Holly. Hi, Holly. Hi, Holly. Hi, Holly. She will be responsible for everything in the next couple of years, right? Yeah. We have a lovely staff that actually do work for us. It's been hard for a lot of people to figure out what the staff actually does. One thing the staff actually does is being at DrupalCon and making sure shit actually works. That there is chairs here, that there's coffee and water and food and drinks and a printer that works and all this stuff. I mean, if anybody ever tried to do a DrupalCon by themselves and I've tried this on my own body, that's about at least 1,000 hours of work. Doing that alongside your normal job, that pretty much means that you're not gonna be able to breathe for a year. And that's just, if we have events that has 3,000 people in it, there's no way around it, we need to have a staff. We even have our own little server team. It's a bunch of nerds, but they keep the stuff running. And one of the things that maybe the Drupal Association has not been good at doing is actually telling what it is that it does. And it's not so much things that they actually, as far as I know, they do even as a port member, but it's kind of important, like keeping the lights on, making sure we actually have a D.O. that fucking works. So we can actually go to the website. I mean, we had a couple of problems earlier, bunch of years ago where actually the server burned down. We now have people to take care of that. We actually have a bill to pay because with a million users, you don't get free access anymore, free hosting anymore. Legal stuff, when somebody fucks with the GPL, there's actually organizations who take care of that, so we don't have to think about it. Drupal funds, because they're big as fuck and it costs a shit ton of money and they provide us a shit ton of money which can make us do even more things and actually can give us an opportunity to give people things, to make stuff happen, which I think is pretty awesome. Even code spends can be, it's kind of a thing. I mean, when we have two big Drupal funds and now there's small Drupal fund down here and we have these code spends which kind of we meet, we code, we develop and getting all that shit settled up, it's demanding a Drupal fund, else we would not be able to get all these people into the same room. Even like forward planning is a simple thing like, oh, by the way, we think we wanna have a Drupal fund down in Sydney, how do we do that? If we didn't have a staff to take care of that shit, it would never be able to happen. There would be pure volunteer work, somebody who had the time for that period and it basically would not work, would not be able to get forward. We did have growing pains in 2012. I mean, we have an office now in Portland, we have structural changes all around. So 2012, we're maybe not the best year, but then it's good in 2013. Because, I mean, in that year, we know that, we just know this because we now have flames on it. I will make sure you get a Man of War, I will make sure that this gets to your office, Holly, I will make sure of that. This is the Drupal Association 2013. Apparently the people of Drupal, the Republic of Drupal, apparently have elected me in on one of the seats of this association, and that means that we have a little bit more of acts wielding a little bit less of politeness. But all of this stuff, and the thing is that, I mean, the Drupal Association have been here for five years and 2012 maybe did not go as well as it could, but we do know that shit takes time, and we will take that most essential piece of thing that we have in the community code. Let's look at one of the, actually one of the very first issues we had in Drupal. Let a user delete his own account. Simple, right? This is where I say, yes, it's simple. Not come, not smile, simple, simple, simple. Look at the date, 2001. Most mans up and says, yes, I have signed this one to myself. A month later, just curious, is there any progress in this delete user's own account? And most now gives in, you say it's my nemesis, I cannot get this done, I am done, it's over. Anyone else, it should be possible to delete a user account. This is in 2002. We have to go into 2009 before somebody finally figured how to do this and all the complex levels of stuff. That actually means that we have an issue that's created in 2001 and issue that's fixed in 2009, but it's not actually out before 2011. That's 10 fucking years to fix a thing that we thought was just a small little problem, small little problem. It's not a small problem, it's complicated as fuck. And unless we accept that some things just take a little bit more time, we might think we have the right answer. But, I mean, this was just a small thing where we begin to move around with almost a million users, 20,000 plus developers, a shit ton of people who are that devoted to a product because it's open source. So now they both comes in with their money and also with their heart into the project. That just makes things complicated. And that's kind of the whole thing is that we came for this code thing and we're staying at the end of staying for the community. That's kind of the things that I can see. It's like, oh, I don't agree with all the code, but it's kind of a second family you have around him. We did jump on a plane just to five or 22 hours to get here, to see the sunrise at six instead of eight in the morning and talk jubilant in three days. And then they'll roll back and do the same about four months again and six months again and so forth. Just kind of a thing that you just do. If anybody had feedback on this, I've made this fine little tiny URL. Actually, one of the last thing I want to show here is, actually, this is actually sponsored by the Drupal Associates. So it's starting with community. What does community mean to us? More and more I'm falling in love with the community. Drupal is built by an open source community of volunteers. So the software stays up-to-date and current. Well, one of the great things about the Drupal community is they do actually get together. I think one of the main things is that you're using a choreo and a test of code. The system's been around for 10 years now. Working together for something that's more than just yourself. It's more than just being able to finish the next project. It's more than just developing a bit of code that you're going to use once and forget about it. It's about a bunch of you challenging each other's ideas. It means you actually get to meet the people that build the core modules and the big modules face-to-face. Value for money. As a local authority, especially in the current national climate, value for money has got to be the greatest draw on the Drupal. The software itself is free. There's a whole worldwide team of Drupal developers going to choose one to build your solution. We're very keen to encourage other local authorities to start using Drupal for their content-rendered system. We think it's a waste of money for public-searched organizations to reinvent the wheel when it could put together. OK, so let's talk about Drupal and maturity. What does it mean to be a mature system? Mature system means that you get a very solid and stable environment. It's very secure and it's very scalable. And if there's an issue, someone would have dealt with it by now. The constant development of anything means that you're refining and refining. It's just going to get better and better early. I think Drupal's been quietly building and beavering way in the background. I think it's now finally starting to come of age and starting to hit the mainstream. It was a very modular system. So you can build a range of different sites to give you that flexibility to be able to shape it to what you want. There's somewhere like 10,000 modules available. You can really plug in whatever you like. So you think of it in terms of construction. Then you're adding modules, you're adding those blocks as and when you need the functionality. You can take those away at any time. You can update them. You can build your own blocks. So it really is the ultimate flexible system. You don't need to know where you're going because you know it will be able to take you there. It's actually sponsored by the Drupal Association through one of these grants, but nobody knew. And that's one of the things we're going to change in 2013. So thank you, my good friends, everybody. I almost know for coming to this epic session. It's been enjoyable. I kept it down to more than three slides a minute, which I think is pretty rough. But thank you. If anybody have any kind of questions, that lady in orange down there, you're good. OK, a little shy. Questions? Yeah. So the Drupal Association is still a little short of money. So apparently, they don't think that that fun is a part of Drupal Cons. It's all about business. That's another thing we will change in 2013. The smoke machine will return in Portland. I've even heard rumors of male strippers as well. Challenge accepted. And I now have a director of the whole Drupal events that looks a little bit tired. Little bit. I'm sorry for that. Do we have a replacement for him? Thanks for coming.