 Yes. Thank you very much for being here today. It's a pleasure to meet you and for your attention. For those who are visually impaired, I will just do a quick bio description. I'm a man wearing a blazer. I'm bothered with a beard. And we are in a seminar full of nice people. So yes, what is a license? Well, I think that the free software movement is very much concerned about licenses. And we talk about this a lot. But I would like today to introduce you the license from the legal aspects. And for that, I would like to explain first what we consider as software. So when we talk about license, we need to understand from the legal perspective what software is, especially here in the European Union, and why we are so concerned about software licensing, why license is so important for us. And in the end of my presentation, I will move a little bit just from the legal aspect and go also to the community aspect of license as enable of software communities. So please bear with me. And if you have some questions, right. Niharika did a great presentation about copyright. And she explained to us that copyright here in the European Union, or at least in those countries that are signatories of the Berne Convention, it applies by default. It means that when a software developer starts writing a software, she does not necessarily need to register this work in any kind of governmental agency. But copyright is starting to apply by default. And what does this lead? Well, basically, people say, oh, I'm not concerned about this. I think I just can go and use the copyrighted work, the software that has been developed by someone. But we also learned today in our legal track that no license does not mean public domain. So basically, when the set of copyrights is being enforced, is already being valid, you are not allowed to take copyrighted work. And in our case here is software and just use it. You need a permission. You need an authorization of the copyright holder. So in this sense, license is nothing more and nothing less than permission as an authorization. So who has the copyright? For an example, a software developer has developed our company, whatever. And if you wanted to reuse this work, you needed to get permission. So license are permissions, are authorizations. So if there is no license, basically there is no authorization. So you are not allowed to do this. So we love free software, and the entire free software movement is license dependable. While we have this copyright system here, we need license in order to empower people to reuse software. Otherwise, reuse is not possible with authorization. So we understood that license is an authorization, but authorization for what? So we need to understand what is software. And for that, I would like to quote the software directive. So directive originally from 2001, but there was some requirement in 2009. And in European legislation, there is no precise definition of software. But usually we talk and we take the definitions from some technical boards. We can consider that software is a set of instructions, instructions that are executed by a machine, by my precisely a computer. And the software directive, this European legislation, does not define this, but establish some principles for copyright protection over software. And they use the term computer programs. And the first one I would like to highlight here is that's it. Member states, the European government states, shall protect computer programs by copyright. So as literary work. So it's not choosing, for an example, patent law. It's not choosing any other area of the law, but it's considering software as literary works as today we learned also from Niharika's presentation. And this is very important because the copyright protection shall apply to expression to any form of computer program. So we are not talking about ideas. For example, a software developer has an idea and wants to implement this. But the idea that she has in her head, it's not protected by copyright. But at the moment that these ideas are being implemented, are being put in some medium, then copyright protection starts to apply. And ideas and principles which underlie any element of a computer program are not protected. So these are very important principles. Right, so now we're understanding about this dichotomy about what is a software idea, or idea for a software, and what is the expression. But right, so when we're talking about this expression for the law, what is the expression? Well, today we learned, especially in Gabriel's presentation, that software is everywhere, and it concerns everything. So basically when we are analyzing software from the legal perspective, usually there is some classification. When we are talking about drivers, basically is this software used for device control. So the first late interaction with some kind of hardware. So we are talking about driver for mouse, for memory, or Wi-Fi, et cetera. But also there's another classification, other types of software. We call it the kernel. And for example, the GNU Linux, where this software executes the core functions of a system. And of course, we as users, usually we have contact more with applications. So this type of software that are used to perform specific tasks, so browser games, and any other type of apps. But for software licenses, there is a very important definition and differentiation that we need to talk. And especially people that are talking about free software, it's much concerned about source code. So source code is what is really important for the community and for free software licensing in general. And I will just explain a little bit what is the difference between source code and executable code. So basically, let's take a look here. For example, we have here in our devices software that has been running here. But usually the software that has been running is in a type of expression from the resolution point of view that should be understood by the machine that it's running. So basically, it is in executable form. So we also call that binaries or objectable code. Because basically, computers understand this binary code. So this is not suitable for human reading or understanding. This is a bunch of 0 and 1. In order for humans to start working with software, and of course, there is some exception when you're talking about reverse engineering and the compilation, of course. But the basic, the human readable form of software code is source code. And that's why this is extremely important for licensing. And the source code is not just the set of instructions for the machine, but it's also the working environment for software development. There is comments there in source code. There is information about license. There is information about copyright holders. So source code is the working environment. So that's why this is really important for software licensing and precisely for free software. And when we are talking about proprietary and free software, usually we need to take into consideration this differentiation. So when we talk about licensing, these permissions, because copyright law gives the copyright holders a full spectrum of rights management. And there is also this gradation, this spectrum. When we see all rights retained, perhaps we are talking about trade secrets, but the public domain is all rights waived. But copy left and permissive or non-recipical license are here. Sometimes more rights are granted, sometimes not so much. When we are talking about software license models, basically we have two. We have proprietary, which the main purpose is to limit ways to access and control source code. We are talking about source code, so where all the fun happens. And free and open source, that we know that the main purpose is software freedom. And here we have differentiation between reciprocal and non-recipical license. And these types of software licensing directly impacts on software business model, I'm sorry, and in software development. Right, but this is also an important element that I would like to point that, that we are talking about software license, but also when there are computer programs and for an example video games that are software but it implements other layers of information. For an example, audio, video, and text. It's important to say that sometimes software license is not the best instrument to regulate this kind of permissions. That's why we are talking about license for content and data. And here I would like to point out for the creative common licenses that are suitable for audio, videos, and image documentation, data, and metadata. Okay, so the last part of my presentation, when we are talking about free and open source licensing, we are talking about the sets of permissions and authorizations, but this is also very important. The license itself is very important for software community when we are talking about it. And that's why we are so concerned about the type of license. Because the license sometimes is considered as constitution of the communities because it sets the term of use and distribution of software. It constitutes the basis for working environment among developers and users and establish the ground for software maintenance and further development, okay? So with that, I hope that we made some progress in making license a little bit clear. And I thank you very much for your attention and hope to counter with your questions. Thanks. Thank you.