So welcome. Yes, it was already mentioned. My name is Karina Haupt. I work for the Institute

for Software Technology at the German Aerospace Center. Some of you might already have seen

a talk from me last Friday about the software engineering guidelines which my group and

I developed. But today I'm going to talk about open source and the legal aspects of it. Next

to my official positions, one of my tasks at DLR is to consult people regarding open

source questions. It's kind of a favorite topic of mine and I started like dealing with

open source and running an open source conference together with a whole team back after my bachelor's

at my university. So since I have no clue what really, at which level you start, I try

to give an overview and hopefully I don't lose all of you all the time. But let's start

with a really simple thing. What is the definition of open source or free software? Here I'm

taking the definition of the free software foundation. There's some different definitions

because it's not like in a really official term to be honest, which is trademarked in

a way. But most of the time they all mean the same thing. And that means that for free

or open source software, you have the freedom to do whatever you want with it. I mean you

should be able to use it, to modify it, meaning you need to have access to the code and so

on and improve it and share it again. So free here means freedom and not free ass and free

beer. That's a picture of Richard Stallman at FOSSTEM, another open source conference

in Belgium, really nice one. So yeah, it's what's important to say, it's not about free

use it and also getting the freedom to do everything doesn't mean it doesn't come with

obligations. So when we deal with open source software, there's normally three use cases

which are important to identify and to deal with. The first one is you have an existing

project and you want to publish this as open source. The second one is a kind of sub use

case you could say, meaning you already have an open source software project and you get

an external contribution. So somebody wants to contribute to your project. So what do

you have to deal with then? And last but not least, if you want to contribute to another

open source software project. Despite the title of this talk, I want to focus on the

first two use cases because I think these are the most common ones you have to deal

with in your position. Also the last one is kind of a sub sing from publishing software

because you have to take care of more or less the same thing regarding your contribution,

but obviously not everything around it. So if we talk about open source, there's some

legal basis you have to think about. As I mentioned, it's not just freedom of use, it's

obligations and these obligations are given by the law. So there's three things you have

to know and I will perhaps use from time to time in this talk. So I want to give an overview

really quickly. And the first one is copyright. In German,

we're hierberecht. So copyright law is different from, there exists one in Germany, there exists

for example one in the US and it's quite different. So I will talk mainly about the German one.

So copyright is really your right of authorship. This can't be taken from you, at least in

Germany, you can't even give it up. So if you create something, you always have to copyright

as an author. That's something different from the exploitation rights, meaning at first

they are also with you, but based on contracts or something, you can give away the exploitation

rights. This is quite typical, for example, if you have a work contract, normally it's

written in there that everything you create while you work is owned, you can often say

by the company, but the correct way is you still have the copyright, so they can't say

they created it, you still have, I'll allow you to say that you created it, but they have

all the rights to exploit it. So this is a big difference we have to keep in mind during

this talk because we come to this from time to time. And the next one is that, yeah, it's

a very well known concept of contract law and that every license is a contract and meaning

it has exactly the same liabilities and stuff and the same laws are valid for it. So if

you don't oblige a license or if you do copyright infringement, then you can be regulated by

civil law, for example. So a lot of people think open source licenses are kind of a suggestion