So why do I have this twice? Let's try that. Okay, I hope you can see my slides.

Yes. Okay, great. So, and it changes here. Okay, so from my side, a short presentation on what I've learned during the last four months.

And so I'm from KM3Net and they're working also in the wider context of open science in different project, in which we are developing our KM3Net efforts.

And during these efforts, of course, we had to be hit on the topic of licenses. And I want to give just take you on a short journey of basically what I've been through during the last four months.

And perhaps you can take something from this or give further recommendations on how to go. Because basically I think I came to the topic of licenses like many people do in our context.

So on the one hand, you have your own software project where somebody says, yeah, we have to put a license on this. And then you're there at Git and you click on license and you have a long list of what you should choose.

And usually what we do is, well, let's just take that one. Sounds nice. And Git automatically puts your name in there. So fine, we're done with the license.

And to be honest, this is basically I think how we handled it so far also in our collaboration.

But then they come to you with a collaboration requirement that actually we need a really good strategy how to do that.

And then basically the first result is panic because I have no idea how to do this.

So what I think we usually do is we start to read up and try to understand, first of all, what are the basic concepts for licensing that I have to take into account?

What are my options? What's out there? What can I take? What can't I? Which considerations are important? So can somebody help me to find the right choice?

And then in the end, if I made the choice, how can I actually implement this in my collaboration? How can we actually use this?

So there's a lot of stuff that that is needed. And first of all, it's expertise.

And one acronym that I learned very early on is I am not a lawyer because I think I actually haven't heard anything from a lawyer about this.

But a lot of people who say I'm not a lawyer, but I know a lot of stuff about it.

So I try to find people who can actually give this information and try to find allies who can help me on that way.

And thankfully, within escape, there were a few. And so what you see here also in my presentation, there are a few slides that are from David group from me.

And that comes from the fact that we started a small discussion group within escape on licenses, which is also why we have the session now.

So I will understand it is not available today. I will just put in some of his slides and you can find the whole presentation that he provided to us beforehand.

Also on the Indico. So. First of all, to get I try to get straight some basic concepts of licenses.

Carina already pointed some out, but here is my short version of it.

So copyright itself is something that always needs a creative act.

So somebody does something creative and this is actually then by definition protected by copyright in a country.

So you always have a creator and you have this product, whichever the creator makes.

And of course, if you do it together with other people, you kind of joint copyright by several creators.

As I said, this act of creation is protected or that the work of creation is protected by national law.

And basically, this is also more or less the only law that counts.

So in the end, it's always down to the national law and it's regulated in national intellectual property rights to actually protect this created work.

And of course, there's a lot of standardization going on. So there are treaties, for example, of the World Trade Organization and for the EU, very important.

A lot of EU directives on different protect copyright protections.

But these always have to be transported international law to be effective for your own country and for your own product.

And then it becomes complicated because it's not usually not only you doing this, but because you are bound by a lot of different contracts as an employer, as an employee.

Or you want others to perhaps pay for what you've done.

Then there's a lot of contract law that goes around all this.

And so the most important part of copyright, Karina also made this distinction between the basic copyright that you can't really give away.

So you will always stay the creator of this work. But of course, the right to reuse and redistribute the ancillary copyright can be transferred.

And this is a matter of contract law, most important for us governed by employment or two party contracts like buyouts or then in the end by licenses, which is also just a contract between the creator and any user.

So then it's a question if we are we are talking here about software. But if we talk about a whole collaboration, there's not only software that we want to take put out in an open sign context.

There is our publications, all the graphs, the media, the videos we make the PowerPoint slides we have.

That is the data and the databases.

And this is basically the part that can be protected by copyright, because as I said before, the act to create something makes copyright work.

So if I have this kind of creative work, then it's protected by copyright. But what I can't protect by copyright is something that all this basically is building on.

So basic ideas and concepts, also very basic data like today's weather is not something I can protect by copyright.

I can't protect general relativity by copyright, but I can of course protect a text I've wrote about general relativity by copyright.

So there is a boundary between the public domain and the copyrighted material that also varies a bit from country to country.

So one nice example are databases, which have a special protection within the European, by European directive.

So to protect the effort that goes into creating these databases. So it's a it's a varying boundary here.

So then is the question, what do I actually have to, where do I have to put my copyright on? So my license is on.

So what's the feature space that I'm looking at? And as we are in this legal environment, there's a lot of these different laws on the one hand.