 Good morning everyone, how are you going? Join Drupal Goal? Hopefully. So just a quick thing about this is historically the first time contributor workshops being very focused towards getting people set up to do coding but we realise that not everyone does. So you only need to download the tools if you're wanting to do coding as the form of contribution that you want to do. And that's like ready for Thursday so you don't have to do it right now necessarily but it will help. So this is the first time contributor workshop, I'm Brian Gilbert, reality loop on Drupal.org and this is Jordana on Drupal.org or Jordana underscore F on Twitter as well. So the code of conduct applies everywhere, you have a Drupal code of conduct which is a little bit more prescriptive that applies everywhere in the venue but also all of the after parties and if there's any moment that you feel unsafe or you feel like the code of conduct has been breached you can contact any event staff and they will know what to do and to help you out. There's also a Drupal code of conduct so when you're working in issue queues, the forums everywhere there's a general code of conduct that we also have where it basically just means be nice and keep everything safe. So the key thing to realise is even if you can't make a patch you can still contribute. There's a lot of people who don't do any coding at all and have been huge assets to the project and that might be you as well. A contribution day which is what happens on Thursday is really just a gathering of people to do focus work on projects or issues and like Drupal is a great opportunity that because we have so many people from diverse backgrounds coming from many different countries, cultures races and everything. It's a really great chance to meet new people, make friends, it also helps when you're working on stuff remotely to use the connections that you make at sprint days to help review your patches, you can send messages to friends and so on. We recommend that it's a really good idea to work in groups of two or three people that way you might have someone who's doing code related tasks. Have an over the blinds. Someone doing review tasks and I'm going to go over the sound. Thank you and it helps to have people to talk with to discuss the issue and form a consensus about the approach to taking, trying to resolve it. So basically it's a group of people sit around a table, find an issue to work on together, discussions establish that consensus and then work on updating the issue summary if that's required which doesn't need any coding skills generally, writing a patch, that's the coder task generally, adding tests again if that's required, manual testing which anyone can do, reviewing the work which can be a part of manual testing the patch and then showing screen software before and after and things like that and then marking the issue as ready to be committed. So RTBC means ready to be committed. I always thought it was reviewed and tested by the community. It is reviewed and tested by the community. I'm sorry. It's like both, they're kind of interchangeable. It's a little bit different when you do documentation. Documentation you generally do in a group and you edit the pages as you go. So with only a Drupal.org account, you can do all of these things. If you add using the issue queue, it goes on to these. If anyone wants the slides, we've got the URL on the bottom of every page so you can look at them directly on your screen and look at them later. You can also add comments to the slide. So if you have any feedback you want to add and there's the URL at the top if you want to ask any questions. So basically it doesn't matter what level you're at. You'll be able to help contribute in some way. I'm not going to read through all of the dot points just because that would be fun. So if you add a local development environment to the previous things, then you can work on code fixes and submit patches. And then with some additional specialized tools, you can help work on Drupal 9 readiness to contribute for your own website. Use a guide writing and use a guide translation, which the link at the bottom gives information on how to do that. Just to review, like we said, we really want to highlight the fact that even if you're not a coder, your contribution is generally very welcome and very helpful. Project managers are always something that people really want. Marketing people, people that write documentation, people that translate. So something like updating the issue queue to make it more clear what's happening is something that's also very important. Taking screenshots to make sure that the before and afters work. So there's a lot you could do. And also like your Drupal Association membership or donating through Patreon to the modules we all use are also welcome contributions. I mean, and if you look at the listings we have here, there's far more you can do as someone who doesn't have coding skills than the typical tasks that someone who is a coder would do. How we generally communicate with each other at the con and after the con because you might be in a different part of the room. Obviously it's still good to talk face to face, but we have the Drupal Slack, which you can sign up at with the URL there. If you're not there already, I would suggest you do it. We've set up a channel just for the first-time contributors in Amsterdam, which is you can go there and just say hello or whatever. And then while we're doing core contributions, you would be in hash contribute. That's the channel to go to. Do we people would go mentoring as well? Or is that mentors? I think. Sorry. So in contribute and in the first-time contributors, so that's where we'll all be as well. You can find us all on Slack. And most of the mentors you'll see walking around. We're on Slack as well. We have a green badge that says mentor. Autistic, yeah. Also, there's the Drupal.org-slash-chat page. It has some information about other regional chat online things that are more regional focused and so on. So now we're just going to go through some things that most of you probably already know, but there might be some people who are here who are brand new. So it's mainly key websites and URLs and things that you might want to know about. So we have Drupal.org, obviously, the main site for everything Drupal related. Hopefully you all have a Drupal user account already, but if you don't, I would suggest you go and create one because you can't really do much in the way of contribution without it. So some things that people might not know is on your user profile, there's a bunch of stuff you can edit to say things you've been to and so on. So this is my profile page, like all the Drupal events that I've been to. So this is my 14th DrupalCon. And it's a little bit tricky to find where to get to some of these. So if we go edit. So just a quick thing. The two things you should definitely do is join the Slack and create a Drupal.org account if you haven't already. I can't see everything from here. That's right. So for conferences and so on you've been to, you go edit and you scroll down to where the vertical tabs are and Drupal. And then down here, there's a list of all of the events. So as soon as you know you're going to one, you should come here and tick it. And then if you've got other friends who have you on their profile, as they look at your profile, they'll know you're going to be there so they can catch up. You can also add your mentors. So I would encourage you all if you want to, you can add me. So it's just you just type reality loop. This is a great way to connect with the people you're meeting right now, the mentors, because this is a way you always have them on your profile page so you'll always find them again if you need to contact them. So reality loop is Brian here and he's a very great asset to have. Also the pronouns in the language. Yep. I can't see easily here. Is that on the person? The second. Yeah. You sure? Yeah. So there's also the pronoun section under personal information where you can add how you prefer to be referred to, I guess. Referred pronouns. Yep. And that's free text so you can do whatever you like. I also have added that on my Slack username. A lot of people have been doing that. And there's a whole bunch of other stuff. A bit about yourself. Your IRC nickname, which not as many people use IRC anymore, but I'm probably going to try and get the Slack username added on this after the workshops on Thursday. You can also add the language you usually speak, because in issue queues it helps to let people know that maybe recognize that maybe you're speaking a different language or English is not your first language so that you know that there might be language barriers. Yeah. So that's under language and location. I think you can list other languages spoken as well, can't you? Yeah. Okay. So we have the Drupal association where you can become an association member and that starts from $15 US up to as much as you want to pay, basically. And being an association member is also a way of contributing because it's there that makes any of this possible. I mean their primary remit is to make sure Drupal remains sustainable and lives. Pretty important to us who mostly are not living from it. So Drupal orgs slash community. There's a whole bunch of information about all different initiatives that you contribute to, governance information, information about licensing licenses and so on, the security working group, technical working groups, documentation around community and getting involved, all of that sort of stuff. So these pages have documentation. I would probably go with the second one as the primary start point because it gets you into all of this stuff as well. We just need to update that slide. So that's all been migrated essentially into the slash documentation area. And if you're a developer, api.drupal.org is kind of the Bible. It will help you figure out how you should approach and tackle issues pretty much. The core Drupal project. So that's where you can download Drupal core and create and manage issues, I guess, anything you might do. You might want to, you've found an issue in core. You can search to see whether it's already been identified. There might be patches to help you resolve it on your particular installation, all of that sort of thing. So yeah, so every project on Drupal.org has an issue queue. If we go back here, I can't see what's there. So it's all down here. Most of you probably already know this. So you can go to all the open issues here or you can do a search straight away for looking for issues. And then the key thing is the advanced search that we wanted to show off. So as someone who's a first time contributor, there's a few key things that can help you find issues that are relevant to work on. So we would want to be looking for, at least at this conference, 8.9.x issues. So 8.9.x.dev. If you have an interest in a particular area of Drupal, say theming or something like that, then you can choose the subsystem that's relevant to help you filter down more. But we would most likely want to look for active open issues, or open issues I guess. You might want to, if you're only looking to review patches, then you could look for ones that needs a review. It would give you a much shorter list. Sorry, it's a bit hard for me to see from here. And the issue tags. Yep. And the issue tags. So are we saying what it is now, or? My eyes are bad and I have a hard time reading the text in the browser. Can you? Okay. Yep. Hopefully. Are we saying the issue tag right away? What's the issue tag that I should be using for that? Just novice. Yep. Is that the tag? Yep. So there's a tag we normally have called novice. And these are populated outside of Drupal cons as well, aren't they? I think generally. So isn't there an uppercase one? Or is it lowercase now? Hmm. Well, there's only one there. So if we now do that search, we should get a much shorter list of issues that we could look through to try to identify something we could work on. So the novice tags are great ways for you guys for people to start working on Drupal because it's not as... You're not going to get stuck as much. Yeah, you might not get stuck as much. So it's a great tag to use to get going. Now you'll find out a lot in the core project that might not be tagged as that as much in contrups. And I would encourage you if you want to get involved in contributing to a contrib to contact the module developers themselves or maintainers, I should say. Can you show where you see the maintainers? Yep. Is that Drupal? Drupal. All right, you can see this list which is not necessarily the maintainers only. If you click up here, it says maintainers. So this will show a list of anyone who has attributed commit to the project and that's just date-ranged. If you go into maintainers, then that will be people who can actually do stuff on the project. So I'm there as well. And the way I would generally contact someone would be click on their username. I should have clicked someone else because I can't send myself a message. I don't know who's still there. And then not everyone has it. So there's a setting in your profile that allows you to have a contact form on your profile page that people can send your message without exposing your email address. So I have that turned on. Yeah. Probably. Yep, there you go. So contact. Just because you're a form, we can fill it out. Something that you may not know of if you are a, like, someone who does code, if you find a project on dribble.org that you want to get involved with, and if it's semi-dead, I guess, you can put an issue on the project saying I'm requesting maintainer access. And if there's no response within two weeks, you can then assign that issue to the webmaster's queue and you will basically get access. So you can help take over and bring back to life a module that's not really getting looked after. So it's pretty awesome. So we've gone through all of those. There's a kind of a rough image. It's in the slides as well that gives that, although the issues that we're filtering on are a bit different. So how to choose an issue is really about looking at what status it's in, reading the issue summary. The way I do that personally is I read the first summary and then I usually scroll to the last of the comments and start reading backwards to get an idea of where it's at now. And that's a really good task to help developers if you're a non-coder is to do that and then you can update the summary at the top to make life a lot easier for them. When you're at events like this, we ask that you add a comment to the issue to say that you're at DribbleCon Amsterdam and I am currently looking at this issue. You don't actually assign the issue to yourself. I'll just go take a knee. So although I'm only a contrib here, you can do all of this on the main pages as well. I can't see. So in the issue metadata, there's a section where you can... Where is it? Ah, assigned. So in a project it's limited, but in some projects that's a field that you can populate yourself. You don't generally do that because that means you're taking over and no one else will pick it up if you do that. So it's... So don't do this thing that he's showing you. So the way to do it is to go... I'm at DribbleCon Amsterdam 2019 and I'm working on this today at least. And then there's also the issue tag but did we create one for... Yep. So... Is it just DribbleCon Amsterdam or...? I don't have Slack open. I don't have Slack open. So it should auto search. So it's the Amsterdam 2019, not the DribbleCon Amsterdam 2019. And that will help us track what issues people worked on throughout the conference, which is good for showing the DA that we do cool stuff to help people get involved with the call. So please do that. And throughout the sprints and mentored sprints on Thursday, there'll be mentors there. So if you get stuck, you can ask us and we'll do our best to help you. We don't all know everything, but it's a good opportunity for us to show you how we find out the answers to questions so you know how to go about that later as well. And the mentors in the room right now are besides us, there are a few in here. So the mentors can raise their hand. The mentors can raise their hands. It's basically the people between them. So we're here, we are also at the booth so you can always approach us. Generally everyone in Dribble is approachable. There are no big deals. You could just walk up to anybody and just kind of talk. And when you comment on an issue it will also show up in your dashboard. So when you go to your profile dashboard so it'll list in here as issues that you're somehow involved in. The other really key thing to do is you might not finish fixing the issue on the day, but it's really important to before you leave just update with a comment to say what you did, what you found, where it's at, because it might make it a lot easier for someone else to pick up. So that can be really helpful. You don't have to resolve the issue to actually make a big difference in helping it get resolved. So patch creation although you might not be doing it is actually a lot easier than you think. So a lot of these are developer tasks but we're still shuffling the slides around. So essentially you're going to download the project from the repo which as part of the tool setup happens for you for doing core contributions at least and we're going to make some code changes save those changes and then make a patch. Now that might sound scary but when you go to any project page on Drupal.org you're nice if I could see this. Is that Diff? You know how you can see. I'll just do it here. Oh thank you. That helps. In every project on Drupal.org there's a tab that says version control when you click that it actually tells you how to download the repo for it and you can pick the version number. So in Drupal.org we're picking 8.9.x-dev and then it gives you the command line that you would run on your machine and down below that we have all the information about how to commit change locally and make patches. That's on every project page so you don't have to remember it off my heart you can go and use this as a reference. There is also some other tools that are available but I'm not going to go into them today. Sorry. They give you command line helpers to make it a bit easier. But if you're interested come find this. Yep. So one thing that you might do as a non-developer is test patches on simply test.me and in three slides I have a video that explains how to do that so I won't go into it now but this is how you can do a lot of things without actually having Drupal running on your machine. The most important thing is also to communicate well in the comments. So explain exactly what you were doing. So why we kind of like harp on that a little bit is it makes everything much clearer and cleaner and better for everybody to kind of work on it together and to test things out and to move the issue forward. I need to get back to Drupal and if So the other thing you would do after you've done that so he was saying you know we want to update after we've tested a patch saying how we tested it adding screenshots and updating the status. So that would be you know I was doing that with this issue so I'll go back down to where I can add comments. Keyboard shortcuts. So I would add my comment here and in the issue metadata assuming that you tested it and it was good and did everything you would expect you would change this to reviewed and tested by the community. Make your notes and then click safe. Attach a screenshot. So there's a file section somewhere here and so you can just browse and upload your screenshots that you took locally and there is a way to put them in the body but that's a bit harder I think Dreditor makes that easier. So the other tools that are very helpful for reviewing code and patches is there's an extension called Dreditor which currently only works with Chrome but I ported it to Firefox this morning so it should be available as a Firefox extension within the next couple of days and then there's simply test.me which allows you to install and run a Drupal site remotely and you can add patches as part of that so I'll do a quick demo of Dreditor just to show you what it gives you so I'll just go to the top at the moment and keep shortcuts again Did you click it in? Yeah, okay, so I have the tab to add Dreditor here just reloading the page hopefully yep, there we go so you get these buttons that will automatically set up a simply test.me instance with the patch applied a lot easier review goes into this interface where you can look at the lines of code so you don't have to do this level of review as a non-coder but it can be helpful So the Dreditor extension just for the simply test.me link is really, really nice because it's a one click solution to kind of make you test the patches and everything so it does a lot of heavy lifting for you it does other stuff besides that but that's two things I can show very quickly so simply test.me I have this video that is basically demonstration why is that? so I'm just looking for an issue filtering for a 9.x issue 8.9.x issue and then I'm scrolling down to the patch that's the newest patch which is that one copying the URL and going to simply test.me I want to type in Drupal to find the core project and then select 8.9.x there which is way down in the list for some reason and then I expand the advanced option section and there's an add patch and you just paste the URL of the patch you can add more than one patch so once you've added one you can just add another add another if there's some that work together and then launch sandbox and within two or three minutes I'll have a working Drupal instance I cut out sections of this to make it look faster so if you have the dreaded or extension you just press that button and those things those steps would have been done for you and then once it's finished it will load to the sandbox that it's created the login for this is admin and admin and admin is the password and you can log into the site and browse around and do all your testing which should come up on there there you go so a really good way to do a quick test of something if you don't have an active development environment locally and this is also community run so this is also a lot of volunteer time people are just doing this because they love you so this slide just ignored at the moment but our aim is to split up the people who don't want to do code and get them actively doing stuff at this stage and then the rest of the presentation is about setting up tools so those of you who don't want to do that you could probably leave now if you like or I can jump to some extra slides at the end first can I give you an example of if I'm a non-coder and I'm interested in the provoked Drupal issue queue or one of the community projects that are non-code based and how I would use the issue queue there a quick example of what a good comment is is not just it works a good comment would be I tested it on this for example on this branch the Drupal I did these steps and I made sure it worked by doing this and this so a little bit of expanding and with screenshots of people and after and screenshots would be helpful I can't see the screen I know but I can't read it to find where to put my pointer to find and promote Drupal stuff where is my pointer Matthew where is like is it what's the project name for that project name okay thanks so I'm typing Drupal.org Drupal.org Drupal and then there's open issues here so I assume I haven't worked with this Matthew have you just the way I'm looking at this it looks like they've got steps for people who are getting involved to do before they start contributing so go and read the guidelines I assume if I click through there it's going to give me links to where the guidelines are yep and you don't have to actually comment or anything on that one so a task you can do is help translate the Drupal pitch deck click it click it and so I would still recommend writing a comment with your interest because it will actually comment so this has got some interactive information and then links to help you how to get involved and people to contact and so on so I can't tell from here I can't see it for example the trans the promote Drupal they have a zoom training they have meetups and office hours and that kind of stuff so all that information is going to be either in the issue queue or on the issue page the page itself so there are many different ways of contributing that has nothing to do with code so this is for example translation and working on the materials like finding finding typos making text clear making the information clear that kind of stuff another thing you could do here is I haven't seen yet but probably there is go search through the channels that are on Slack you might find that there is channels for that and you can go and talk to people in real time to find out what's the best way to proceed so was there people who wanted to get tools set up today show of hands okay cool I'm going to jump to the other slides first so the other people can take off if they want to are there any questions now that you guys are something that you want to have experience can you do it in the mic just so it gets recorded please thanks so maybe my question is a question it's about documentation considering documentation I would like to know more about this what kind of documentation documentation of code or menus or demos or something like that because today on the keynote we saw a diagram that shows the new Drupal customers and users are in the beginning not so happy with the Drupal interface and so on but then they realize that Drupal is also I think the same and I'm excited to share this part how to write better manual documentation to show the clients what actually Drupals can do so that's there's multiple levels of this I'm just trying so the documentation that's on Drupal.org so there is documentation that's on Drupal.org that's very easy to edit so every page on Drupal.org that is a documentation type page anyone who has an account on Drupal.org has the ability to edit so you can make improvements so I'll just go somewhere and so the documentation there's a documentation working group there's a documentation Slack channel and they're always looking for help and those people will be on Thursday there will be quite a few tables that are contributing on documentation so we can definitely get you to the right people but has that changed like I didn't get edit on any of these if you know better than me stand up like mentioned there's five or six different documentation areas of documentation Chris there mentioned one to be just a few minutes ago there's the localize.drupal.org so if you speak another language or if you speak multiple languages being able to localize the Drupal interface is one way of documenting the Drupal 8 user guide is is now a code based documentation and so there's a $1.00 project for the user guide there is the so the user guides one I had the link at the bottom of the slide earlier so if you want to look at that later you could go back to the slides and you'd be able to find that link and there's a couple community related documentation efforts that are more relevant recent projects and initiatives Rachel Lawson the kind of initiative lead on that as the community organizer so she has the I think the project is sorry I have it on my laptop in Slack but there's two main drivers one is improving if you're on Drupal.org and you see a community link at the very top is improving that whole section and that relates to how we can change improve documentation for different people and roles and skills and more easily improving the documentation about what we're talking about right now getting involved basically helping people get involved helping how to get involved they're rewriting the whole getting involved guide from scratch a little bit so you wanting to get involved is a great way to help get the getting involved documentation so this is a new initiative and it's I'm pretty sure I think there's an issue for it up now I'll try to find help I wanted to just mention one thing it's really hard trying to find a new space to contribute in because there's so much you just don't do something random or just pull something out of an issue but if you have something that annoys you that's really a good place to start but if you have something that annoys you and it isn't being worked on or is being worked on maybe you can help work on it maybe you can test it but there's plenty there's plenty of everything but if you have something that annoys you and you can work on it at the contribution day you'll feel some value and you can expect to get sucked into that and maybe make a longer term contribution to that so try to if you can, if you're looking for something and something annoys you, go with that I've got my I think it's a cool story about that so I posted an issue about a feature I wanted to see which was to make the permissions for revisions be per content type instead of global and that was just after code freeze for Drupal 7 I think and Dries was the first person to comment on it saying he thought it was a great idea and I got super motivated about it it took two years to get in but it's now in call and if you don't know if you have that idea and you don't know how to get started that's why we have Drupal chat Drupal slot chat and asking a question and if you do work with a mentor the mentor may not know but they may know someone who does know down the chain so we can help introduce and point you in the right direction I think the key thing is yeah, asking in chat is can be very helpful and please do ask so to show you if you go to Drupal.org to go to community and getting involved did I press it? I can't tell there you go see this whole you can read how to get involved but right here it's documentation can you click? and this is the way to get involved with documentation it explains how to contribute so right here you see the new contributors task page that's where you're probably going to go to figure out what's going on and there is an issue for changing up the getting involved guide write that and you would be valuable because you're just getting involved so you would know best what questions you have as someone who wants to be a new contributor and what path how to find out what path to take the other area is possibly the marketing effort might be somewhere that's relevant because the marketing can help people understand how to use the product so in case we haven't already made it clear there's a first time contributor workshop on Thursday that's in the Diamond Lounge, wherever that is I'm not sure and you probably won't want to go to the workshop because it's essentially what we've just run now but there's mentor contribution in Europe 4.2 that is basically mentors helping people who have done this workshop to find issues to work on people to work with and being there to ask questions if you need help so after today you know all of this contribution can happen remotely online it's the vast majority of my contributions have happened when I've been at home in Australia somewhere you know there's not drip icons every weekend you can't meet with all these cool people and do that every week so there's core mentoring hours on Slack so 4 to 6pm Eastern time based in America but I believe there is or has been times that fit the European time slot better as well and if you go there and say that you would like to see that I'm sure people would step up and help with that so to join that you would join the hash contribute on that time and say hi I'm here to contribute mentors always available at least someone's available generally always in Slack so that's another way and then there's always contribution days at events and then you could organise if you have a local group or you're very motivated yourself you could organise an event on a global contribution day this is so there's links there you can go to these are on the slides basically there's all the links that we had in the in the document the community page the triple dot org slash community page has recently gotten a refresh and it's like the place you want to start at if you have like you want to contribute it will tell you how do you it has like a few questions like I want to help contribute by or I want to help run a camp or organise a meet up it has links there to show you where to go that's a great place to start thank you we'll stay around for I think we've still got some time to help people who want to get tool set up but everyone else thanks for coming hopefully we see you on Thursday and if you have any questions feel free of course they're in here so I'll just keep going the tools that we've set up is basically a rapid way to get people set up with a local development environment that doesn't use lots of external network activity so it's sending from my machine and other mentors machine so it all stays within the network that's just to make sure wifi doesn't die it gives us basically access to all these things with the tools that we need to do local development so it's called quick sprint it's based on a tool called DDEV that's down in the exhibition hall from DDEV Randy who was here talking before he's one of the developers it does have some requirements Windows 7 64 bit or higher Mac, Sierra 10.12 or higher and a decent amount of memory and the ability to actually install stuff on your computer so if you've got a locked down work machine that might be a problem in the case we'd recommend using simply test me so what it is is the installers for Docker, Git, etc the DDEV command line tool helper and this is all packaged once you download the sync that I mentioned earlier which is at dribble.org tools and it will essentially create a dribble 8.9 environment for you that you can use to work on and you can blow it away and create a new one really easily and it's well documented and well tested so if you've been in syncing the tools which it doesn't look like anyone is was there people who were syncing it during this yeah has it finished downloading or is it still yeah cool so basically all you have to do is go into the directory that you downloaded it to and extract the big file that's there which is explained on the tools page as well sorry and when you extract it you'll have a dribble sprint package folder and if you don't already have Docker installed inside that there'll be an install directory where you can install Docker but if you do have Docker then it should be and it's a recent version you don't need to additionally install that and then if you're on windows there's also git bash so you have to install the git stuff to get git bash you would open the git bash and then run the .installsh and it does all the magic and on Mac you just open a terminal and run that so I'm happy to walk around if people need help doing that that's the basics and the one thing in Docker you need to change the memory allocation to 3git do you have any questions about that or do you want me to help what you're doing or have you already installed it my computer is locked I don't have virtualization on the cpu so Matthew for people who don't have virtualization enabled on the cpu is that where we use docker tool box instead or that would be a chance to test me or what you're expecting it would be an alternative it should be it should be able to turn off I can help someone last year turn on virtualization on windows it's pretty easy to do if you don't have access to the BIOS but if you don't have access to the BIOS then with two alternatives you can simply test me and triple core itself has installed 3git without pd special environment installed on the demo site it's called quick start in the documentation for the spring user reading for the tools there's very top what I do it will link to the quick start quick start meant for demoing promotional work playing around not really the best word if you want to work on code on Thursday it would be great if you can get the tools installed by Thursday if you're having trouble with the installation steps you can probably come to the mentor booth in the exhibition hall or find me if you see me around I'm happy for you to come and talk to me I'll give you a hand will this presentation be available anywhere because I have to go right now the link is in the bottom of every slide so the other thing I'd really appreciate if you've got feedback you can add comments on any of the slides if you think we've not touched on something as well as you would have liked please let us know because this is a living document it gets updated every conference and it's more than welcome for people to use the slide if they want to try and present this to people in their own area thank you