 So, I think it was a bigger year than perhaps we all remember. It's different, like, when there's this storm of react news all the time, it's easy to forget what's going on in Emberland, but as I was going through it, putting these slides together, it wore me out. There's so much happened. So, in March, Embercon's 2015 was some pretty enormous announcements, glimmer among them, an amazing lineup of speakers, apart from one Englishman who couldn't really keep it together. I don't know how many people went. I attended and absolutely loved it and attended previously and loved it too. This was an awesome, awesome conference and we managed to pull off one in London too in November and I think this turned out really, really well and it's something I hope we can repeat this year if circumstances allow. The RFC's process appeared last year. I feel like we've always had this and it's so important to the way the community works and the way new features land that I can't remember living without it, but this actually landed at the beginning of 2015 and I think it's now really fundamental to the way new stuff happens in Ember. Also Ember twiddler pit, you know, I think for a long time JS Bin was, you know, not to knock JS Bin. It's fantastic, but it was kind of good enough for the purposes of demonstrating Ember things, but as Ember CLI took off, it started to drift further and further away from the experience there and Ember twiddle has course corrected that dramatically. Now it's the thing I think we all reach for when you want to quickly sketch up an Ember app, share that code with someone else, collaborate on a problem and Ember CLI itself has been just astonishing this year, especially recently as performance improvements have snuck in from Steph Penner and build times have dropped by a factor of 10. I think this has become the delivery engine for the Ember message really. This is what's selling people in. And Babel, Babel 6 released on stage at Ember Conf. I think Babel's changed everything about the way we work with JavaScript. And it's weird to think that before Babel, again, ESnext and Tracer were these tools which people were experimenting with but didn't see adoption. It seemed like maybe just complicating things and then Babel arrives and Babel's, it's like a no brainer. It's just got that right feel. It operates at the right level. It just does all the right things. OK, so hard problems that we solve in the Ember community. Simulating data sources with Ember CLI Mirage or the Mirage project. Hands up, who uses Mirage in their apps? That's pretty much everyone. Excuse the croaky voice. This has been a real game changer. And it seems to have taken off in every step of the stack. Some people run production sites where the data is coming from Mirage just because it's such a nice way to model it. It makes testing easier. It makes development easier. And the people behind it, Sam Selleckoff and the team, just seemed so amenable to new ideas and so friendly. Deployment, Ember CLI Deploy has revolutionized this with the perfect mental model. And again, an incredibly open and welcoming team, including Aaron Chambers, who I don't think's along tonight. But he's done incredible work on that. Animation, this is another one where before Liquid Fire, it just seemed like everyone was punting on it. And there were answers here and there. And it was like, user didn't set element, hook, or just kind of roll your own solution. And then Liquid Fire landed. And it wasn't that it immediately solved everything. But it definitely gave us the primitives, I think, out of the box. The idea that the way you could declaratively mark up your templates to encapsulate animation. And I mean, this is maybe a half tick as fastboot is still alpha. But I think the progress so far is really, really promising. And fastboot definitely addresses this problem at every single level. And I think it's a really impressive act of thinking through a problem, like really, really thoroughly, like all the way to the end for every possible angle. And when it's out, it's something that should solve it in a one-line install for almost all of us. HTML bars landed in early 2015 and then was quickly followed by Glimmer and now Glimmer 2. And I think it's interesting the progress that has been made since HTML bars arrived. Handle bars seem completely fine for so long. The script metamorph tags seem completely fine for so long. But once the back was broken of that problem, it seems like progress has just come in more and more rapid iterations. Ember data became stable and has now hit version two in lockstep with Ember itself. We'll talk about JSON API in the next slide. But Ember data, I think, has reached a point where it almost, dare I say, it feels quite lightweight now. Like it's not the heavy cumbersome burden that I think we might have felt it was at the start of 2015. Now, its role and the things it does are very precise, very surgical. And JSON API version one was released. Now, this isn't Ember specific, but this is something that the Ember community was heavily involved in. And we all stand to benefit from. There are some good podcast interviews with Yehuda to speak about this. I think the last episode of the change log, he covered the philosophy behind it in quite some detail. I'd recommend checking that out. OK, now on to resources from the community. Ember 101, formerly Ember CLI 101, went creative commons and free. This is a wonderful introduction to Ember. So if you're thinking of learning Ember, you can pick up this book for free. You can contribute to it. It's excellent. Rock and Roll with Ember JS by Bama Turdy. I've not read this personally, but I know people who have and say it's fantastic. One from Pragprog. Matthew White, no relation to me, I don't think. I've heard this one's excellent too. Actually, if you look on emberwatch.com, there's a stack more fully fledged actual paper books on Ember. Ember Observer landed. This was announced by Katie Gangler at Ember Conf in March. Again, it feels like we've had this for ages now as well. It's become so important to everyone's workflow. And it's become, I don't know about all of you, but this has become my go-to resource for learning about add-ons. And also, once you have an add-on in the wild, getting that all-important 10 out of 10 on Ember Observer is the coveted prize. Ember Screencast. I've been really impressed by this. When I met Geoffrey Biles for the first time at Ember Conf, he said, yeah, I think you're starting up a regular screencast thing. I've got the domain name. I think I'm going to do it. Just churned out content, video after video, week after week. And these are excellent. So this is now a well-established, trusted resource. Podcasts, Ember Land. This is the one where Robert Jackson tells you what's really going on every couple of weeks or so, while we're subscribing to. Ember Weekend is a great companion for that. That's a couple of guys from Hash Rocket, I believe. That's really good. And the Frontside podcast, which isn't always about Ember, but largely is and often has interviews with people from the Ember community. And this is a brand new one. It's the podcast companion to the modern web UI meetups in San Francisco. And this one kicked off with Yehuda being interviewed by. I can't remember at all, but it was excellent. And the global Ember meetup is a really interesting new entrance to all of this. This is a virtual online meetup. Miguel, you're speaking in the next one, is that right? Yes, this Saturday. This Saturday. And probably the same time with the extended version of the tagging with the new. OK, for the uncut talk, tune into a global Ember meetup. OK, so that's the tip of the iceberg of what happened in 2015. Obviously, there was loads more than that, but those are the things that stuck out for me to really paint the picture of how much richer the community's become in that time. So I want to talk a little bit about what we've got planned for 2016 or the kind of things we're thinking about. This is about Ember London primarily. There's only a few points. I'm nearly at the end of this gigantic ultra-Rambel. So the first thing is diversity. Now, we are really proud of the community that's grown up around Ember here in London. We think it's done great things. We think it's contributed back to Ember in a fantastic way. But we're never as diverse as we want to be in terms of where people are coming from, in terms of gender identity, everything, the kind of context people are coming from. And we want to try and improve that as we grow. We think this community is going to grow this year. And as it does, we want it to grow in a diverse way. I spoke to a diversity consultant on the phone last week, and one of the things she suggested was to, it wasn't just a matter of me standing up here and saying, we're going to do this. I need you all behind me to do it. When I say behind me, I mean behind me and Ken and Nick, you know, organizers. So I want to give you some of the reason why we think it's important. So that first one, a richer mix of experiences and perspectives, is something that we believe feeds into the quality of the code we all write, of the kind of user experiences that we all write, of the kind of conversations we have together, the kind of apps we build, the kind of problems we try to address. The more and richer variety of points of view we have in the community, the better we think we'll be. And this is something that needs to happen for our industry as a whole. And if we can play a part in that, then that's wonderful. And finally, we just think it's the right thing to do. So what's the plan? Well, we want to have more diverse speakers. How are we going to do that? Well, largely it involves fielding speakers from other parts of the industry, from other meetups, from universities from academia and this kind of thing. And so this is something we need your help with. So if you attend any other meetups or conferences and you see a speaker and you think the kind of things they're talking about would be of interest here, then we'd love to know about it. And similarly, whenever I'm at a meetup and I see someone give an interesting talk, I always invite them to speak here. Secondly, we are beginning the process. We've always linked to the confcodeofconduct.com, which is a good kind of generic base for codes of conduct. But now we're taking a step of having our own so that we can spell out our specific policies around this. And I'll show you a bit of that in a second. Marketing is something that we don't really do in any significant way. We tweet about these meetups. We email the full mailing list, a bit of Google Plus. Beyond that, Slack a bit, I guess. But it's kind of like it's more word of mouth than anything at the moment. So we'll be looking at how we can reach out to wider audiences. And apart from that, we didn't know exactly how to approach it, which is why we've spoken to a consultant, Astridon, who's fairly well known and runs AlterConf in the US. And what I hope to do is commission her to work with us throughout the year to really, really do wonderful things and tackle this and make ourselves better and more diverse. So the Code of Conduct, we're taking a new approach with all these bits of the community. This is GitHub, EmmaLondon, slash Code of Conduct. This is the first draft that's in there at the moment. And I welcome everyone to come and give your feedback, make poor requests, suggestions. Broadly, what it says is we won't tolerate any kind of harassment of our members. Everyone who comes here should feel welcome, should feel comfortable, should feel safe. And if anyone is harassed, we will deal with it. We will have a clear policy on what will happen, how you should report it, how things will be treated in confidence. So the idea is this will make everything absolutely clear so that if anyone does have any fears about coming along to this kind of event, this should hopefully address them as best we can. So to support all these efforts, and largely to pay the commission, the consultant, we'd like to hire, we are seeking sponsors for EmmaLondon Diversity for 2016. So previously, when people have approached us about sponsorship, we've said, well, you can sponsor food at the Project Nights. And beyond that, we don't really have that many costs. This is something that would be great to put money towards. So if any companies are interested in helping us with this, we would be delighted. Next thing for 2016, Project Nights. So who's been to one of our Project Nights? So the way these work is usually they are the week after the meet-up. There's not one in January just because there's not enough time to organize. So one week after the meet-up, and the idea is it's a similar kind of gathering of programmers to work on any Ember project you fancy working on. So that could be making a pull request to Ember itself. It could be your own toy project. It could be your work project. Could be just to come along and learn or teach or hang out with people. But it's a meet-up without the talks effectively. And the thing that's different this year is that we want to host them in more different places. So last year, they were all hosted at the office I work in. This year, the plan is to build a roster of different venues around town with different companies. And we will move between these different venues each month. So you can probably just about make out who's on the roster. So far, we've got Alpha Science, Trover, with Associates, who I work for, and Zatnito. Again, if your company would like to be on this roster and host one of these Project Nights, make a pull request or email us. And this is a new idea from Deepan from British Gas, the Ember London Exchange. And the idea with this is for companies using Ember to exchange ideas, give talks at each other's offices, set up video calls. He's got some cool things in mind for this. But I think primarily it will start there with the kind of brown bag lunch exchanges and things like that. And again, we are taking the tack of hosting these things as GitHub repos. So it's really easy to contribute to them. Make changes, give feedback, and everything. And Ember Conf is coming up in March. Who's going this year? OK, I can't make it. I'm very sad about that. But it's going to be amazing. The lineup looks absolutely incredible. Enjoy it. So that's all from me. I'm sorry if it was a bit long. So, Ju, if you want to bring your laptop up, I'll get on with the first talk.