 Goedemorgen allemaal. Leuk dat jullie er allemaal zijn zo vroeg. De tijdstip al. Top. Het is ongeveer een 15-minuut walk van het centraal station of je kunt een tram nemen. Het is ongeveer vijf minuten. De Quiznight, ik denk dat het een van de meest geweldige eventen is. En je moet daar als je er niet naar vond. De deur is open bij 8. Oh, en ik heb nog een ding. Als je een sponsorige giftpack voor de Quiznight hebt, hand hem in, in pakketjes of vijf op de receptie desk. We kunnen gebruiken wat fun prizes en ik ga niet over t-shirts. Social media, er is de DrupalCon Europe account, die ik onder de enige die de account rijdt voor de laatste paar maanden. Als je vragen over dat, please. Do not hesitate to contact me afterwards. There's the hashtag DrupalCon, DrupalSpring, DrupalRadio. En we're all using them to make this event better. There it goes. So we need pictures. Don't keep the photos for yourself. If you have pictures, please put them in the... Upload them to the Flickr group. We need all of them. So please do if you have them, don't keep them for yourself. Then there's the session recordings. You might have noticed they're blazingly fast here at DrupalCon. It takes an hour or so after each session to put them online. All sessions of yesterday and the day before are already online. There's a YouTube channel and this link takes you to it. And there's sprints. Like last weekend we had sprints in the burst of Berlagen. Next weekend there will be sprints as well. It's free to attend, you don't need a ticket to get there. This Friday there will be a sprint as well. It's the main sprint. 100 people in a room working on DrupalCore, DrupalConscript. There's mentors to help you if you are new. If you have never worked with code before, you are really valuable. To help writing documentation, to test patches. And there's mentors to help you set up your environment. So please go there. It's really fun and you learn a lot. Keep in mind it's the e-entrant. So not the entrance that you took today. It's in the Ruby Lounge in the Forum Lounge. And there's more info about the sprints in the Mentors Boot at 4.15. All about the store. There is a store with goodies and fun stuff. It's in the lunch area. Get there before after lunch, before lunch ends. The store might close. We close it. We don't let it open until the end of the day. What did you think about the sessions? Please help us make DrupalCon better. Evaluate sessions, it takes a minute of your time. Every session page has a link to evaluate it. The link will be posted when the session is over. We help speakers to get better. Dan a few words about the local community. Our local foundation is called Stichting Drupal Nederland. Try to pronounce it. It's fun. We are a foundation. We are run by seven volunteers. I'm the chair. There's six others. The foundation helps growing Drupal in the Netherlands by enabling the community to share their knowledge at events and online. We are funded by the sponsors of our events like the Drupal association, organization partners and individual partners. These amazing partners help us to fund all the events we do. For each event we organize we form small groups about five or six people. Each group has one board member of the foundation in the team. Some of the events we organize are the Drupal Jam which is the oldest event we organize. We do this for nine years now. It's the biggest yearly Drupal event in the Netherlands. About 300-400 attendees. This is last year. Dries was live on Skype to chat with the audience. It's comparable with DrupalCon. There's tracks and sessions. It's sponsored by several companies as well. This is the event I'm really excited about. This is the Drupal training day to answer the large demand for Drupal currently in the Netherlands. We think it's going to be even more after DrupalCon. To answer for that demand, we organized a free training day for students all over the Netherlands and Belgium to come to Amsterdam and to get a free Drupal training for a day. We aimed for about 30-40 students and we ended up with 250 students and 35 volunteers. One day, one place. It was amazing. We believe with even 80 people on the waiting list that we organized the largest Drupal training worldwide. Ever. We shared our knowledge on how we set this training up and all the learnings we gained. We did that last Monday on the community summit. We will also do it again at Drupal Camp Gent. If you go there, you can learn how we set this up. We will share all the virtual box images that we've made and all the knowledge that we gained. All the trainings that we did. We decided to make this yearly event now. It will be there next year and we aim to even make it bigger. We aim for about 500 students next year. Another new event this year that we organized is the Splash Awards which is kind of like the Blue Drupal Awards for those who know it. It's like an awards event. The best website, the best module, the best team. With several categories. Government, community, modules, code. It's a website. SplashAwards.org went live this morning. Go there. If you're curious about the event we will reach out to Dutch and Flemish companies in the next couple of weeks. The first event is the Ant Culture Community. The two of us are now working on this together in an event show that we have thank you with Northern cant до andós ensemble to encourage to participate today in some events alive. In 2000. In 2000, we reported that we would have to work as a department in the World Hub. Over 2,줘op якs om te weisten en in Flemish ook known as Yoroi, to announce that it will be here in Amsterdam. And they also asked us to help making Drupalcon Rock. You know, not just beat in events, but also add some more, make it local, make it Amsterdam. So yeah, we did, we went upstage, we talked about, for fun just why not take a bike and a bike to Amsterdam, you can do that. Well, and that turned out into the, what's it called, to the Drupal, isn't that fun? And we also announced that it would be de beste Drupalcon ever. En I believe that we succeeded, but it's up to you to decide. And I'd like to share a bit of the process on how we managed to get there. So, about six months ago in March, we organized the first meeting in the Parabruri. We have been there maybe yesterday and the day before with the logo that looks like the Drupalcon. And Stephanie and Watson came up as members of the Drupal Association to get to know the local community and to tell them what they were hoping that we could do here. So, this was the first meeting, we continued this meeting like every month at one of the Amsterdam-based companies. They sponsored food and drinks, the companies. And for the last six weeks, we switched to a weekly Skype call. And we helped the DA with providing information about event locations, about bike rental, about transport passes and how to include those in the registration form. Also, we organized a lot of events here, social events. So, one of them is the arrival of the Tour de Drupal in the Fondelpark last Sunday. I'm not sure how many of you went there. There were about 100 people who showed up. So, we made a finish line and this is the group of bikers who biked all the way to Amsterdam from England, from Ireland, from Belgium, from Switzerland. They all came on the bike, some took four days to get here. Isn't that amazing? And it was like drinks and it was food for free, all sponsored by the local foundation. We also organized the pub crawl. Thanks. So, we organized the pub crawl on Tuesday. There were like three major pubs, smaller pubs as well in the Blue Light District. There were three boats that you can join for free. Probably a lot of you did. We had even, we had one boat with live musicians on board. So, we got some street musicians. So, join us, go on board. And they did, so it was fun. Also, we organized yesterday's cultural night. The free entrance to museums, live music in the proud brewery. It was fun. I thought it was fun. So, I hope you had fun too. But we needed budget to fund all this and how do we did it? So, what we did is that we approached about 20 companies and we asked them one question. Would you please chip in 250 euros and then you can help make Drupalcon Rock. There's no like gold options, silver options, bronze options, there's just one budget, 250 each, but 20 companies paying 250. We had a 5000 euro budget to fund all these events. And we promised them a noise map with their logos on. And this was a killer selling feature for us. So, I'm pretty sure that you've all used this map the whole week very extensively for the last few days. So, before I conclude, I want to thank the local team for doing an amazing job. It was fantastic. This is not even the complete team. We are like with 15 people. And I hope that we've raised the bar for the next Drupalcon country, wherever that may be. I challenge them to raise the bar, to even make it better to beat us. So, come to the closing sessions at 3.30 to find out where the next Drupalcon will be. It's going to be fun as well, I guess. So, I'm really proud of what we achieved the past months, not only with Drupalcon, also with the other events that we organized. And I want to thank all the volunteers, all the sponsors, all our partners who make this happen. So, can I get a warm applause for those who did this? All right, so that was my talk. We continue with the lightning talks. They are hosted by Schnitzel. You might know him as Michael Schmidt. Thanks for the attention and have a great Drupalcon day. Thanks, Boris. Good morning. It's Thursday already. How fast it goes. So, lightning talks. Let me shortly introduce what we're doing. As you know, there are sessions. They're one hour long. People present a really long talk for them. They prepare them, they give them. And it's mostly one-way discussions. Then we have buffs, which are multiple people talking together. But did you ever have that small idea, maybe on a shower while you were cycling here, that idea that you really wanted to get out, but you don't really have time to give a session or you don't have time to prepare a session because it wouldn't fill a whole hour. But you also don't know if anybody is interested in that because it's only your small idea. That's what lightning talks are for. So, lightning talks are already used by other conferences and the track chairs of Drupalcon Amsterdam said, okay, let's try them. Let's try them out and see if they work for Drupalcon as well. And we really believe that we have some really great ideas in the community. So, we give people the stage here for five minutes to present their lightning talks, their idea they have. And we did that actually last week. So, they did not have like the others in multiple weeks or so to prepare. It's really in a short notice and I heard even some people stayed up really late to prepare them. So, that's cool. So, we found seven speakers that said, okay, I want to give something. I want to tell you something, an idea that I had and I use max five minutes for that. It will actually make sure that they stop after five minutes. There is a really big red clock in front of me right now which says five zero zero and it will start running whenever the people come up. So, we're gonna try that out and if you all like it, we'll see. We do it more at Drupalcons. So, we are ready for the first speaker. It's Jonathan and he will talk us about Bitcoin. Okay, hello. So, I've been using Drupal for six or seven years but I've discovered something new. It's called Bitcoin and I'm very excited about it. So, what makes Bitcoin different compared to a regular bank transfer or PayPal? Well, it's got this invention called the blockchain but what is the blockchain? Well, it is a shared autonomous ledger. What this means is that whenever you make a Bitcoin transaction, you have total confidence that it will go through. No one can step in and say, well, you can't send money to that country or you're on PayPal and they don't like the look of one of your transactions. It'll just happen by itself. It's a means for consensus to be reached among peers about what happens in the past. So, because there's no authority, how do you decide what happened? Who sent money to who? That's a very difficult problem. So, it orders the transactions and this avoids the double spending problem. What happens if I send Bitcoin to one person and then I send the same Bitcoin to another person? Which transaction is the valid transaction? So, with the blockchain, it orders the transactions en if some Bitcoins are spending one transaction, a subsequent transaction can't spend the same Bitcoins. But this is a really powerful technology but Bitcoin is just one implementation. You can do a lot of things with the blockchain and pretty much everything we do on the web at the moment will actually work better if it's implemented on a blockchain. So, I've got a few examples. Git, for example, there's a lot of parallels between Git and a blockchain. But with Git, you have to always push to a centralized server. If Git was implemented on a blockchain, it would just be, you would just push, you would broadcast your transaction. You wouldn't have to talk to a specific server. So, there's no downtime and there's actually a project called GitChin. I think they're trying to implement this. Twitter, sometimes there's censorship on Twitter. People aren't happy about that if they're in certain countries. So, there's a project called Twister which is Twitter implemented on a blockchain. Same with WhatsApp. Maybe you're happy with WhatsApp on Facebook chat and Google chat. But in theory, this could also be implemented on a blockchain and there's a project called BitMessage that does this. So, this can be highly secure, no downtime, no censorship. DNS. In theory, this could be implemented on a blockchain and there's a technology called Namecoin that does this. So, it could be quite a big political step if we replace DNS with blockchain, but it's a possibility. And asset trading. With some of these technologies, colored coins, counter-party, master coin, you can issue coins and then have people trade them. And this is actually going to be a big deal in the crowdfunding industry. It's going to revolutionise it. Elections are also a good use for blockchains. It's really hard to do e-voting, but with blockchain technology, this is actually achievable. And contracts. Let's say you want to get married. You can just write your contract and publish it on the blockchain and then anyone can see that. It can have a time stamp. So, you've got proof that a contract was agreed at a certain point of time. En in fact, with a project called Ethereum, you can implement anything on a blockchain. There's a programming language built into Ethereum and all of these platforms we use, someone has executive authority and can say what happens on the platforms. But if we rebuild these platforms on a blockchain, then we've got total control. We can do what we want. So, I've got one minute left. I can tell you about my project called Cointools on Drupal.org. So, I'm interested in Bitcoin-Drupal integration. So, I've made some widgets for Bitcoin for an address, an amount, a transaction, some formatters. There's a transaction browser. You can send your Bitcoin. You can receive your Bitcoin and you can pull in the exchange rates so that you can render your Bitcoin with the feed amount. So, Drupal.org is going to be a great platform for startups. I believe. I wanted to make it the best platform for Bitcoin startups because Bitcoin is the new web. So, that's all I've got to say. So, thank you very much. It's okay. Thank you, Jonathan. So, Bitcoin and money. Next one has also to do with money. I think it's a bit different. We'll have Steve talking about the unforeseen. Thanks to the Drupal Association for the Vodka. I'm much appreciated. So, I'm Steve Parks from Wunderkraut and I run the UK office for us. But I also do a lot of coaching with our clients on projects, how they can improve projects. And today I specifically want to talk about project risk, the unforeseen. Has anyone ever had anything unforeseen happen on a project that they were doing? Anything crop up last minute? Yeah, it's strange, isn't it? It happens. But large organizations are terrified of risk. They're terrified of the unforeseen. They're terrified of things derailing their projects. It all tends to come from some previous project that went terribly wrong. There is some mythical project in their history that is like, don't mention the project, project X. And it's scarred them for life. And what happens is that their procurement departments, their legal teams, they put in place lots and lots of rules to prevent similar things happening again. That's it. Put that in the contract. That'll protect us with all our future projects. Suddenly we are safe. And these rules build up and they build up and they become more and more petty all the time. Contracts fill up with these tiny little rules and contracts become huge stacks of documents. Is that protecting the projects? No, it's not. Because what happens, the only way to get things done when there are this many rules is the mavericks, the people in the organization that will just push things, do things under the radar. Have you ever had product owners or clients work under the radar in the organization not tell the stakeholders? And that's not good for projects either. But worse for projects is the idea of those people that stick to the rules. And they stick to the rules a little bit too far because you end up with all these petty rules en suddenly everything grinds to a halt. A rule that's designed to stop cars stops the pedestrian. And it gets crazy like that. But then you have the organizational enforcers that come in. And they, their job is to make sure that every single rule is enforced completely. And they bring the organization and the projects to a standstill. But still you end up with all these rules, all this craziness, all this trying to manage risk by putting everything, locking everything down. Let me tell you to Wales. Wales obviously has the language Welsh. It's a minority language spoken by a relatively small percentage of the population. The Welsh government is trying to promote it. And of course government procurement as it is, everything's got very strict rules. Their road science department obviously doesn't have many well any Welsh speakers because what they need to do is email off a translation. And obviously they've done the procurement, they've got the huge contract, they've managed the risk. So they email off a translation. They send off, welcome to Wales by email. And back by email comes the translation and they put it on the bottom of the road sign. So this road sign in Welsh says, I'm out of the office at the moment, but I'll reply to your translation request in the morning. So no matter how many rules you put in place, how many detailed contracts, things will always go wrong. But the warnings get more and more intense, more and more crazy. Everything tries to be protected by the procurement departments. But something's missing. There's this huge gaping void of trust. Trust is what makes projects work. Trust is what makes teams able to collaborate together effectively, not the rules. Let's move beyond rules to a position of trust. But as agencies we have to earn that trust. First of all that means we have to use experienced people. Good quality staff who are well trained. We've got the professional development that's continuously ongoing. We're not just offshoring it. We're not just using kids straight out of school university without training and just billing them out a lot. You've got to have the right staff. And you've also got to have the right tools and it doesn't mean no planning. These guys were hired to stop cars from parking in that space there and they put up the bullards. Can you see the lack of planning? Very entertaining watching them at the end of the day. You also have to bear in mind the user en what they actually want cause the contract can't predict that. And the key thing of trust, transparency. If everything is going to be visible that happens on the project, what people do, then suddenly it becomes a lot easier. And you have to live this as well. You can't just say, yes, we run projects in this way and it's full of trust and we do all these fantastic things. Live the way that you believe in. And that means not taking no risk. It means there is risk on projects. We have to accept that there is risk on projects. And we have to go in there bravely with the right training, the right tools and go and get our cheese. Thank you very much. Thank you, Steve. Next one up, completely different topic. But definitely interesting as well. We have Alek telling us about Drupet. If I say that right. Hi everybody, my name is Alek and I'm going to make your life a bit easier. So currently we have a lot of development stacks available for daily basis users. We have Acquired Dev Desktop. We have Open Server. We have Palm Server. Somebody uses Mempro. But I believe that from my base on my own production experience, it's not enough for enterprise or big projects because eventually in big projects we need profiliers, debuggers, we need other automation tools, we need build systems. And in big projects we work with distributed teams when people, there are newcomers, people joining and leaving the projects and as a team leaders, we want to unify the environments and unify the development practice. Here you can see planets I have found in enterprise projects. We deal with PHP. In some projects we deal with Hip-Hop VM. We use Xdebug. We can use Mailcasters. And actually there are tremendous amount of tools we use on our daily basis in our enterprise projects. Hoe te customiseren, hoe te maken het gevoelig, hoe te share onze on-experiënt, ontwikkelde on-experiënt met iedereen in onze grote team. En er is een solution voor het. Het is called Pupfit. En het kan echt helpen. En ik kan het aanstellen voordat ik je een demo laat zien. Dat is het open source. En natuurlijk, als je meer wil dan het gevoelig is, kan je het voorkeken. En dat is hoe Pupfit, het voorkeken van Pupfit, eigenlijk kan het alles met Pupfit met een paar extra features. En wat voor demo? Laten we je laten zien hoe het aan het moment is om op je eigen laptop te rijden, zodat je veel virtual boxen hebt. Ik recommend installeren de laatste versie van Wegrant en virtual boxen. En het is heel makkelijk. Als je Wegrant installeert, er zijn veel gebruikbare plug-ins, especially voor developers, zoals Wegrant host manager, die het gewoon makkelijk is om hosten te configureren op je lokale environment. Er is een Pupfit website waar je kunt, zoals je kunt zien, je kunt de versie van PHP selecten. Je kunt het database selecten, je kunt de Xdebug configureren, dan kan je downloaden. En hier downloaden we de archive. Als je het extracteert, vind je eventually een Wegrant file. En zo kun je Wegrant app. En in addition, de config van de VM is alle available in JSON format. En je kunt een aantal hosts je nodig hebt, een aantal databases, je nodig Rebitmq, je nodig Elasticsearch, je nodig Apache Solar, alles is configurabel hier. En als je de config van JSON kon configureren, dan kan je gewoon met Wegrant app gewoon met Wegrant aanbieden. Dus... Dus eigenlijk, er zijn 6 strafvormige stepen om de VM te gaan. Je kunt downloaden en installeren in de virtual box. De volgende step is om Wegrant te installeren. De volgende is om Google en downloaden met Drupferd of Pufferd. En je kunt gewoon de VM in het JSON file customeren. Dan kun je de Wegrant plug-ins installeren. In Drupferd page er zijn notes over het. Bijvoorbeeld de Wegrant host manager. En dan kun je gewoon Wegrant app en de VM op elk environment gaan rijden. Dus een paar notes over de provisioning systems. Ze proberen eigenlijk onze mogelijkheid te ontdekken en te ontdekken. En dus we niet laten mensen in onze bedrijven om drogen te worden. Dus ze zitten op de top van de ontdekking en het niet te ontdekken met andere oude newcomers of junior-developers. En het maakt onze leven makkelijker om nieuwe newcomers te ontdekken. En natuurlijk het maakt de isolatie van de tools en de isolatie van het environment. Dus het kan makkelijk veel nummers van VMs op onze lokale machine rijden. Dus dat is alles aan mijn kant. Dank je. Dank je wel. Dank je. Goed, volgende week hebben we Michael. Niet mij eigenlijk. Er zijn alle Michael's in deze wereld. Deze topic is continu de delivery als 8-child succesor. Can we have the slides? Yeah. This is clicker. That's the clicker. Right here. Got it. Hello, Michael Godek. So there's a hashtag for this talk, which is Go For CD, F-O-R-C-D, which is also on the slide. So please post any comments and questions and then we can continue the discussion online. And I'll start by acknowledging the inspiration for this talk, which was an article by Andrew Benstock, whose editor-chief at Dr. Dobbs. So you can see his article out there. And Jez Humble, who's the author of the book Continuous Delivery and Martin Fowler, whose chief scientist at ThoughtWorks. So if I end up just confusing you with this, then that parts on me. So how many of you here remember the days when software projects started out by burning up weeks and months, producing some big monolithic requirements document filled with detailed and colorful flow charts and sequence diagrams which became really increasingly irrelevant with each new line of code. You know, nobody could bring themselves to throw this stuff out. So we got this documentation brick that became a sort of like a fat coffee cup coaster called The Little Book of Lies. So there were a lot of problems then that mature Agile teams today don't really have to deal with for the very reason that Agile steers us clear of that trouble. So some people seem to still enjoy sailing among the rocks, but for those of us who with an appetite for mitigating risk, Agile came in with just the right balance of abstraction and detail to take the software industry to a new plateau. So Agile is effective and it's become the standard of practice. Embracing change, coding in short sprints, an emphasis on automated testing and short feedback loops all of these things lead to improvements in quality and productivity. In a decade from now we'll still be improving on it, but the principal benefits are realizable today by organizations and teams that take Agile seriously. But you'll have noticed that software teams today haven't exactly run out of problems as a result of this. The central problem that Agile was intended to address was the inability of software teams to adapt to changing customer requirements. So now we're getting good at adapting to change, but that really only compounds what's still one of the most intractable problems in the face of real ever increasing complexity. And that's actually finally releasing software. So continuous delivery practice intends to deal with this delivery question as Agile did with that of adapting to change. As with Agile, the central focus of CD is to mitigate risk. CD was built, it's built on a foundation of DevOps practices so that comes first. Continuous integration is a cornerstone of CD, but first class software build pipelines are really the main show in continuous delivery. So Martin Fowler talked about build pipelines, what they're about. So here's his quote. One of the challenges of an automated build and test environment is you want your build to be fast so that you can get fast feedback, but comprehensive tests take a long time to run. A deployment pipeline is a way to deal with this by breaking up your build into stages. Each stage provides increasing confidence, usually at the cost of extra time. Early stages can find most problems yielding faster feedback while later stages provide slower and more thorough probing. Deployment pipelines are a central part of continuous delivery. So this is the end of his quote. But still at this point we're still really only talking about the technical side of the delivery puzzle, right? We need a full stack solution. We need the whole team in on this. You don't really get to the best benefits of continuous delivery simply by automating deployment. As with Agile, we need to move culture to engage the whole team with people in less technical and non-technical roles assuming more responsibility in the actual delivery process. The software build pipeline is where your team rehearses for delivery so that by the time you're ready to go out on stage and deliver, the technical issue should be resolved. One of the really great unrealized benefits of delivery automation is that it allows devs en ops te nemen zodat de delivery is no longer een technische silo. De responsibiliteit voor de release nu beantwoordt de businessanalyste. Project managers of stakeholders waar het beantwoordt. Effectief de delivery wordt een businessdecision voordat het een technische een. Dit verandert alles. Agile verantwoordt dat wanneer stakeholders eerst de werking software verandert de percepciën van de requirements. Dus nu gaan we niet de budget vervangen voordat we ze iets laten zien. In de delivery praktisch als de release een businessdecision wordt, vervoudt het vervangen van de percepciën van de proces. Dat betekent een potentie voor een groter custome relatie en de kansen om de software industrie tot een hele nieuwe niveau. Dank u. Dank u, Michael. Naast het, we hebben Stella praten over iets d8 in 8 die ons zelfs vertellen wat dat is. Hallo, iedereen. Dus, zoals Michael zei, mijn naam is Stella. Ik ben van een Drupal-agent in Arland, called AnurTek. En zoals welk van jullie dit week ontdekken, we hebben onze website recentelijk ontdekt AnurTek.com in Drupal 8. Dus een van de dingen dat we in preparatie voor dat was, we gingen een internale competitie, die we konden d8 in 8. Dus de aim van de competitie was om de hele team met Drupal 8 te bekijken, wanneer er een frontend developer, een bakend developer, projectmanager, het is niet moeilijk. We wilden iedereen downloaden met Drupal 8, een plek over het contributeren met Drupal Core, contributeren met Contribus ook. En ja, om wat fun along de way ook. Dus hoe het project was gegaan, was dat iedereen, met de 8-team hier nu, iedereen was gegaan 8 weken om het project te completen. Het is niet moeilijk wat het was, het zou nemen een website, het zou portieren een module, werken op patchen, zoals het was iets te doen met Drupal 8, dat was oké bij ons. Aan de eind van de 8 weken hebben we de hele team samen, en er waren iedere 8 minuten om te presenteren in wat ze hadden gedaan. Er is geen judgeenpanel per se, iedereen die participaties was gegeven 8 punten om te distributeren zoals ze wilden. Dus als ze dachten dat een persoon did een geweldige werk, ze konden alle 8 punten tot dat persoon of wanneer ze dachten dat er een paar verdermde projecten zouden het between ze wilden. Dus wat hadden we geleerd van alle van dit? Nou, we hebben zeker veel meer verwerking met Drupal 8, maar in termen van downloaden het om het te werken, ploegen met sitebouw en om in de code. We hebben ook geleerd hoe de Drupal 8 te ploegen. Websites in particular leren van de hele nieuwe configuratie management tool die is gewoon maar die taken weg was we het echt showed us hoe we te get our team involved in contributing to Drupal core. Dat was erg important te us. Zo hier zijn de dingen dat we achieved. One of our developers Antony built a fancy photogadder site. Complete met a custom light box style overlay. So you could click on the image or pop up in the light box and then for extra bonus points he added a by print button en integrated it with the relax payment gateway which is a popular payment gateway in Ireland. Another developer mark created a fully responsive multilingual video site. I think he was embedding YouTube videos on that. But as without any Irish Drupal initiative it wouldn't be complete without some trivia. So Tommy created a trivia game based on custom entities with some no Dutch AS for a really slick user interface. However who won? That's what you all want to know, right? So I'm pleased to announce that your friendly volunteer and entertainer Andrew MacPherson won the competition. He got a number of commits into Drupal core including knocking out a field API beta blocker. He ported not one but three modules to Drupal eight as well creating a brand new one. So well done Andrew. Did we have fun en contribute code? I think the answer to that is definitely yes. We certainly learned an awful lot. There is admittedly not without a fair amount of hair pulling. Have to remember this is about six months ago that I think when we started this certainly during the summer. So we're working with you know earlier versions of the alpha Drupal eight things weren't quite as ready as we had hoped. There was certainly a lack of documentation and nothing on doodle was returning what we wanted. But we had fun along the way. Would we do it again? Absolutely. Especially now that there's a beta blocker out. I think it might be fair game for everybody else to get in on this. So I would highly encourage you to all whether within your organization within your local community group run a Drupal eight in eight competition. It's a great way to get involved with the community to give back and to learn Drupal eight along the way. Just the keep of the team all the eights. So eight hours, eight minutes, eight days, whatever it is, that's the general team. If you want to find out more, check out our blog post on andrcheck.com or come find me afterwards. Thank you. Thank you, Stella. Now even have better one. So it's actually easier to upgrade websites because that was one of the big issues before. Good. The next one. We have Jesus Manuel, which will talk about a Drupal eight console, which is not rush. Don't say that. OK, we'll want to talk about a project called Drupal Drupal eight console and say the main purpose of this project is to take advantage of the symphony console component in order to provide a CLI tool to generate Drupal eight modules and take care of all the recurring task. OK, and the best way to explain this is showing you this little video. I'm going to play here. OK, I'm listing you there's no any module. I'm going to start generating a new and you Drupal eight modules so just go something like this and start asking me a few questions. What will be the module name? What will be the module problem in the module project name? Then will be the pad where this module will generate it can add any description I want to. From there is going to start asking me all a few questions like we should what package name or the version if I want to generate a controller I say no the whole directory structure and once I finish the generation we will see we will execute a three command we will see all this files was generated the info file module file so now let's go ahead and generate a new controller. Same thing now it's going to ask me which will be the module that I want this this controller get generated so I'm going to say Drupal code which I want to just create it the controller name I want to add service I want to need a service confirm generation yes and now we can see there's a new file here and also the routing files generate let's go ahead and create a new any other component let's say how about generate a form and don't get bored we will see how it looks executing just for now let's say default form it's fine I don't know let's say event form the ID I'm going to say that's default I don't want any service generate a structure and I say yes it's going to start asking me for adding a fields for the form let's say I'm going to want to add a new field called event name which will be the field type in this by default is text field so I just hit enter let's use another name something like it's always hard getting a new name right so event oh come on yeah city that will be a good one let's say text which is fine but I can use arrows for auto completion and see all the field types that I can add and let's end up adding a new different kind of I mean file type field type so in this case it's a daytime so I'm going to update route yes from here I can see there's a new new php file edit let's let's go ahead and enable this this new module that I just created say enable drush in and then and then let's see how this looks in code and how it looks and when I'm running it so what was generated what the info jammel file was generated with the info that I just entered you can see the name and also the dot module file which is simply meant to hooks help and team hook en also this default control was generated in the proper directory while adding the namespace the use statement was added this controller is extending the controller raised and also this little action hello action was added and this as you can see also the route register I mean was registered in the route and also spawning to the controller that will be executed this means if I go something like Drupalcon hello Drupal I will say something like this happening I can see is reading the parameter dat I'm passing from the argument I can change that and see how it's is being updated but how that's how the controller works let's see how the form generation part works it also generates a pad for you a routing and in this case is pointing to the full class which is a form class we can see same thing namespace added they use a statement the class extending you know form base and remember the fields that I asked me to add cd text event name text event date dat is de datafilm en ook de uiteraardheid van een verbinding verbinding de vormmethod en ook de uiteraardheid om alle values te krijgen dat de user in de vorm en de vorm in de configuratie je ziet hoe het werkt de vorm is hier en ik heb de values gezet html5 we hebben html5 hier dat is de date de saving en als ik een koppel en de pad en op een nieuwe tab ik zie de values hier want ik heb het gezet op de verbinding vorm en ik krijg het wanneer ik de vorm rendeer wat kunnen we hier doen laten we gaan genereren een nieuwe bloggingblok laten we gaan accepteren alle defaults ik wil niet een vorm creëren gewoon genereren nieuwe dingen en het betekent hetzelfde aan de proper class en de proper directie aan alle namespaces in de particularis van blog aan de annotatie om te laten weten Drupal, dit is een blog en in het begin het project was de meeste generatoren maar nu we hebben een aantal andere feature's zoals laten we zien hoe om en op de routes op de verbinding systeem je kunt iets zoals dit als je een route in detail wilt je kunt het specifiek passen als parameter je ziet al de details van de route en je kunt ook doen hetzelfde voor de container op de hele services in de servicecontainer en wat we hebben command generators controle generators entity config I mean config entity config entity content er is like bloggingblok imageblok you can generate services there's little thing more you can do how can I get from here where you can find this project you can find it here Drupal.org slash project console or if you don't have a Drupal account and you have a GitHub account is etch in Drupal slash Drupal app project Drupal app console sorry and who started this used to finish it I started this project with David Flores another developer from Mexico and myself I'm Jesus Manuel Olivas 2Data account is jm jm oliva is but you can even blame this guy for this project actually we're discussing we're talking with Larry David and myself at Drupal Camp Costa Rica about you know which new tools from symphony can be integrated in Drupal 8 in one of the topics was like how about the Drupal I mean how about the symphony console component and we just from there we start working on the project was last year so what does we have what's out of the box is what I show you generate modules info files it takes care of register register in the routes in the jammel files even services take care of carrying classes put in the right directory setting all the user statements that you need to setting all the I mean making this class extend this other class like that and how about Noisca Noisca folding our generators what I told you you can listing routes en listing services living in service container and who can benefit of using this tool module containers can create and migrate your current contribute modules to Drupal 8 Drupal trainers en consulteurs can take advantage of this in order to train people en teach how Drupal 8 works en obviously Drupal shop because can reduce the time of developing Drupal 8 modules en I think it's all thank you thank you so obviously the question is as I said before is there a draw integration it's not but I was your question is if it is draw integration there is not currently a draw integration but I was talking to a developer yesterday and we were actually we have an issue on the project and he showed me how to do that so probably we have an issue I mean draw integration in a soon so you can do something like draw console and since console you can draw you can do like something like draw console draw console thank you so we're already the last one last person is Lee en he will tell us us about security can you hear me okay my name is Lee Kelsey and online I'm known as AmsterCad I'm thrilled to have joined the core Migrate module team this week and Friday we'll be helping everyone at the sprints all day we want everyone to join us at the sprints we want so everyone can comfortably ease into the process of using Drupal.org as a tool to perform the work required to release Drupal 8 especially after everyone returns back home everyone can learn what they can do to help Friday at the sprints just show up these are the lightning talks and I'm here to raise a few security questions now here at Drupalcon Amsterdam 2014 for us to consider and discuss why does it take so long for people who maintain distributions of Drupal to update modules with security updates that have otherwise been available on Drupal.org for many many weeks already what can be done to push all security updates faster and with more reliability through the distribution chain what should developers using these distributions do about the problem how many of you can relate to the problem as I've tried to describe it pleased to see that so clearly we need to improve how distributions are actually distributed if we plan to further develop our secure business processes using continuous integration this is a simple problem that needs to be fixed otherwise the value of using a distribution is greatly diminished especially by less technical developers that are not so familiar with Drupal.org and security I can be reached at Drupal.org's contact form and my username is Amsterdam that spelled Amsterdam like Amsterdam then Charlie, Apple, David Amsterdam thank you thank you Lee so if you're worried about distribution security talk to Lee he is also available tomorrow ok, that's it that was the lightning talks we had seven speakers and I really talked to them I really thanked them that they took the time to prepare something in a really super sort notice if you really liked what we did today in the last hour tell us via the contact form well, the survey form so fill it out either directly feedback to the speakers we will or I will forward it or to the lightning talks itself and we'll see if we're going to continue doing that and other constant camps now I wish you a really nice day enjoy the last session day and please all make sure that you come to the closing keynote I heard there will be announcements interesting videos and stuff where we go next year in Europe enjoy it, bye