 Okay, I will try my best to squeeze this into five minutes. We have all these great technical topics here, so I decided to do this time something a little bit different and just summarize all the license questions I received during the year from community members, from employees, and just to give a short overview for everybody to maybe in the future you can answer at least some easy questions by yourself or know how to look at to find the right answers. So first question, of course some of you might ask you why should I care? Well, first point is maintainability of your whole project. We as a developer we care really much about maintainability of our code. We make sure that we can easily extend it, that we can apply tests to it and all the stuff so that we can use our code for a long time. And often we forget that also the legal side of our project need to be maintainable for a long time because also the environment around our projects can change. We can, the laws can change, technical environment can change so that at some point you might want to adapt your license to the new world you live in basically. And of course if you develop an app you want to know if a third party library is compatible with your app and you want probably to know what other people can do with your software and what they can't. And another important point for me is that a license is really also somehow on document which constitutes the community you build around your software. So it describes the basic rules, how people work together, which rules are applied to the code they create together. So it's really important to think about how your community will look like under which rules you want to work together. So just really quick, if you look at the free software and open source license you can break this down in two main categories that's everything I want to say. And one is a copy left license which protect basically your freedom to use, study, share and improve the software and the non-protecting license if you give you exactly the same rights but allow other people to do with them whatever they want. So that's really cut down to the easiest answer to how different kind of free software license exists but I think that's enough for here. So with next slide we choose the GNU-HGPL which is a strong protecting license so it makes sure that the software will always stay free. We also recommend to use any later version clause because as I said at the beginning that's exactly which allows us to keep also the legal side of the project in the long run maintainability. So if something will pop up where the license needs to be updated to make sure that we can also move to the next version of the license. We have no contributor agreement or anything else so everybody has exactly the same rights on the code. There is no differentiation. Nobody can make the code ever proprietary. Expect you can of course take your pass you write and use it in any other program you want because you always keep the copyright on your stuff. And I think that's really important to create this level playing field to grow the community with users, customers and partners all together. To still create some certainty about the legal situation of the project especially for customers. We introduced the developer certified of origin that's a thing which is done by most of the large free software projects these days like the Linux kernel, Aclips, Docker and many more and it's basically if someone commits and code it by signing his commit he just says, okay, I wrote this code by my own and I can contribute this to the project on the IGPL on the project license or if I'm employed my customer allowed me to do it or if I took the code from somewhere else I checked as good as possible that I'm allowed to give the code to you under the license. So that why it's really important to sign your comments even if I know developers often find this a little bit. Say oh I have to do it but it's really add some legal certainty to our project. When you write a next cloud app you always have to make sure that both license are compatible, your next cloud, the next cloud server and your app. We recommend to just use the same license as we use for the server, the new HGPL or later for your app but if you really wish you could also choose some of the compatible license and if you choose one of the compatible license of course the combination will be always new HGPL but you can also if you prefer to choose a different license for your app and the same goes for third party libraries if you need the library for your app and then you also have to make sure that they are compatible. So what does it mean to be compatible? That's just mean in order to combine two programs which is the app and the server you need to make sure that both developers develop of the app and develop of the server give you the rights to the same rights to do this with the software. So if both license allow you to use the software the same way then they are compatible and then you can use them together. And of course often the question came up so when does the license need to be compatible and that's always if you form a single program out of each other. So if you combine it in a way that at the end you would say it results in a single program and there are some criterias you can also look up in the FAQ from the GNU project which gives you a hint if this is the case and one is if a program is linked together with the app if it shares data structures and run in the same memory if it makes function calls to each other in both direction and if you look at NextCloud and Next.Apps you will see that that's the case in both directions so that's why both sites and it's always compatible to each other. And the good thing about GNU-A GPL v3 is that a lot of license are compatible with each other so all main license you find out there you can normally just use with your project. So GPL v3 only by GPL v2 you have to be a little bit careful this need to be GPL v2 or later GPL v2 only doesn't work but as you see all other main license like the LGPL, the Apache license Mozilla license all those things you normally see out there work. At the end some resources where I also regularly look up if people ask me some stuff is the FAQ from the GNU project is really great if you have some questions how all the stuff works. The Free Software Foundation has a great network of legal experts which has also a public mailing list where you can send questions to if you have some legal questions and there's a new project a relatively new project from the Linux Foundation spdx.org which also tries to unify a little bit away how you define copyright in your project which also makes it easier to automate this test if everything is compatible which is always a comment to use this best practice defined there. So this was a really quick run through this topic. If you have further questions just catch me on the floor I'm here the whole day and yeah thank you.