 Hello, everyone. I am Vika and I am part of the Pipelines group during the Hackathon, and I will show you now how we will work. So first of all, before I start and forget anything, the slide deck you see here, you can find on Slack. If you go to the Pipelines channel, you can see the progress slides up in our bookmark here. And you can also find them when you go to the website to the Hackathon events page. Let's link there. Anyway, so what we will do during the Hackathon, or our main purpose is to maintain the existing inner core Pipelines, start new inner core Pipelines, if you have any in mind, but also work on your own Pipelines that might use the inner core infrastructure like if you want to use modules or sub-work flows. This is still a good place or still group to join. So in general, James, Susanna and me will try to coordinate this group, give you any pointers if you are, if you have any questions or general advice. You can always ping us in the Slack channel that you have here, the Hackathon March Pipelines one, and we'll try to help you and hopefully also many other people in the community will help everyone out. So as general tasks I mentioned, we want to work on the existing inner core Pipelines. So there's quite a few developmental tasks to do. One of the big ones is for the Pipelines that are still in DSL1 to work on the DSL2 transition. Then always, of course, bug fixes or extend functionality, add new features and so on. And if you have a new Pipeline in mind, you can of course use this time to get started. Just make sure to first go to the new Pipeline Slack channel, propose it and then we can have a discussion and review it and see if it fits as a new Pipeline or if it's maybe something that can be added into one of the existing ones. To work or to get reviews done quickly, we started using a review buddy system. So we have a table at the end of the slide deck where you can enter your name and then find a buddy and then you can hopefully very rapidly switch or exchange PR reviews so you can get the merged fast and make progress fast and don't have to wait for reviews for a long time. So just enter your name and then or enter your name into one of the slots and then you hopefully find a buddy there. And then we have hopefully a lot of people that will want to contribute to some of these Pipelines and here we have a couple of ideas about how that can be done. If you have other ideas that we didn't come up with yet then of course it's also always welcome. But one of the things that is always super helpful is to read the documentation that we have on the website, make sure it's coherent, you understand what you're supposed to do if you would want to run the Pipeline. If you feel like you're missing anything, if there are any questions that you would like to have answered, this would be great if you can extend and work on this during the hackathon. Then a lot of the Pipelines may need new modules or some of the modules may need to be extended or in some way fixed or have new features added. So this is also a great way to help Pipeline developers and maybe also in collaboration with the modules group during the hackathon. And then as I mentioned here we have bug fixes, small and big ones. We need new features for a lot of the Pipelines so hopefully there's something for everyone around to do. Just remember, so this is the slide deck that I showed you, we will try to track the progress over the next few days on these slides. So add yourself to the team members slide just so we know who's working on it and we can celebrate each other's progress and also find Pipeline developers that might be working on the same Pipeline. We have an issue board on GitHub where first of all if you're a Pipeline developer you can add your issues to but also you can use it to find issues to work on. So we have the different tabs here for documentation, infrastructure, modules and so on. So we can go to the Pipelines tab and we can see a bunch of issues have already been added. So we can then go to the to-do list here. You'll see the RNA-seq Pipeline has added issues such as show good and bad examples in documentation. You can click on the issue, read what it's about, see if you want to work on it, maybe get in touch also with the Pipeline developers of RNA-seq. Then assign yourself. This is really important so you can click here and then find yourself in the developer and the GitHub handle here. And this is really important just to make sure that not multiple people are working on the same thing and you accidentally duplicate your work. And then once you start working on it you can move it from to-do to in progress. Once you are done with this you think it's finished and you open a pull request. You can move it to the ready for review section and then last but not least to the once it's reviewed and merged you can move it to done. And this is hopefully how we can keep track of all the things we'll work on. So I already mentioned to add yourself to the project board. And then also on these slides here it would be great if you can post your progress daily. We have one slide per Pipeline per day and this will hopefully help us keep track and celebrate all of the achievements. Yeah, so James, Suzanne and me we have already signed up as team members and just add yourself here and with your GitHub name and then we can see who joins us. Here we have the reviewing body list and then we subdivide it as I mentioned for day one and day two. So for day one for example here we have this slide for the EGAR Pipeline. We have a goal for the hackathon the DSL2 conversion. Then we have the little group emoji here to highlight all the people that work on it. And then you can indicate all the issues and poor requests they are working on. So I don't know at Falko as fast you see alternative. This was already accomplished. So we have a green tick. Then we have one that's adding pre-sec that is under review. We have the little eyes and then multiplexing mapping support and multiplex mapping support is still under construction. So we have the little construction signs. And please use these emojis because they help us keep an overview about what the progress is. Yeah and that's it and I hope to see you there and if you have any questions then just contact us on Slack and we'll be happy to help.