IP risks for OSS developers
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Sype, Yung Shin Van Der
Provoost, Soo Mee
Open source software developers, just like any other developers, have to be aware of the legal liability they can incur. The topic of this talk is the infringement liability of contributors in open source projects. Typical for open source projects is that they contain multiple (more or less anonymous) contributions by multiple developers. Since the regulation on patent and copyright protection applies also in case of open source software development, co-authors in the project should take care that the re-use of pieces of code does not infringe intellectual property rights of third parties. The proposed talk aims to address two pertinent questions in this regard: - Can co-authors, contributing to an open source project, be held liable for the wrongful re-use of code by other co-authors, contributing to the project? - If so, which legal mechanisms could be used to protect good faith OSS developers against such liability? This research is funded by the EU FP7 Framework Programme under grant agreement No. 318508
 I don't know where my two speakers went, so... I don't know. They're in the hall. I should probably remind them that it's my turn. It is, sir. It's just us. Are you getting ready? Yeah. I'll look at that. That's it, right? Okay, well, thank you for coming back to the Legal and Policy Issues Dev Room. For those of you that didn't have too much beer last night, and we're really excited to start off, talking today about IP risks with Jung Shin and Su Mi. Yeah, here it is. Good morning. The scope of this... Oh, wait. Okay. The topic of this talk is IP risks for open source developers. And yesterday I went to a very interesting keynote of James Turnbull on software archaeology for beginners. And I really enjoyed, I don't know if anyone else was there, but I really enjoyed the talk. And I learned a lot, although I don't think I understood everything. But there were two minor things that disturbed me a little bit. The first thing, but I discussed it with him, so he knows. And the first thing was, even if his messages was that you always have to write, to ask the same, the right question at the right time. And as an example of how it should not be, he gave the example of don't ask the developer what his favorite contract is. I think that's a bit unfortunate because I think that the developers should be aware of contracts because its law is inevitable and you need to know what you're working with on a daily basis. The second thing that was a little missing from my point of view was in his step-by-step process of what you should do when you join an open source project. He didn't mention the licensing compliance check. And I asked him afterwards and he said that he just trusts the people in a good project. So we will talk about this today because we think there are some issues. So what we do want to share with you today is some thoughts on how to protect yourself against IP infringements by others. And we will also talk a little bit about how to protect yourself. Before we really start the presentation, I just want to give you the message that if you are involved in an open source project, there are still copyrights hanging there. Because copy left is only an exception for your copyright. So you really need to consider copyright and you really need to know what the risks are. But first, before we get to the protection of the protection mechanisms for you, we will have Sumi talking about copyright. So I will explain the problem shortly. You have an open source project X and developer 1, he is actually in good faith. He has an infringing contribution to the developer's chain. The piece of code that he uses infringes the IP right of the third party who is not directly involved in the project and then gave permission to use this code. Now, every subsequent developer can be held liable for this infringement even when they are not aware of the fact that his contribution is infringing. In general, creating a computer program, even open source, completely unaware of the existence of any IP rights of the third party can be used as a defense to willful IP infringement, but it's not a defense to IP infringement in general. Because it is common for open source projects that they are developed by community rather than one person or one organization, these problems occur in real life. In case of a big project when you have thousands of developers, it's not reasonable to expect that every developer will check if there are infringements in the code by other developers. But in smaller projects, these expectations might be different. You can use version management systems to see which developer made which contribution to the project. The risk of IP infringement, it is not a specific problem to open source projects, but of course the risk is greater because open source allows you to distribute and modify the software freely. The infringement will carry through subsequent versions of the program and further development of the software. So a small and quick remark is that everything we say today is seen from a Belgian point of view. Of course, when you have an international project, it's possible that there is another law applicable. So this can also have influence on the outcome of the results of your claim. So the problem consists of two elements. When do we have an IP risk and how can you protect yourself? So first I will explain about when you will have an infringement. And I will explain you which kind of intellectual property should be taken into account when you are dealing with open source projects. The most important are copyright and patent law. First I will tell you something about copyright and how you can know if the source code of someone else is protected by copyright. So in Belgium, in general, computer programs are protected by copyright because there is an assimilation with literary works with the burn convention. So it's not exactly the same as general copyright, but you can see it as a kind of modified version of copyright for software. Because of the general principle that copyright doesn't protect the underlying idea of your program, but only the original expression, you are allowed to copy the functionality of computer program, provided that you do not copy the source code, but you rewrite it to your own original code. The mere fact that software is developed in an open source context does not mean that there is an extension on this general principle that copyright plays a role. In Belgium we don't have a definition of what a computer program exactly is, but for instance the UK does. So it is possible that different elements of your program are protected in different countries. The European Court of Justice did indicate that your object code, source code and your preparatory design will be considered as an expression of your computer program. What matters is that your expression enables the reproduction of your computer program and it enables the computer to perform its task. So what are the criteria for copyright protection? You need originality. Article one of the European Software Directive says that the computer program shall be protected in the sense that it is the author's own intellectual creation, in the sense that he made creative choices that are an expression of his own personality. So you cannot apply any other criteria for copyright protection. There will be given protection to the expression in any form of your computer program, provided that nature is such as that a computer program can result from it in a later stage. As a consequence you will not get protection for your functionality of your program, the programming language and format of data files, and the graphic user interface. Nevertheless, a graphic user interface can be protected by the general copyright if it fulfills the criteria of originality. This also applies to the programming language. It can also be protected if it is an original expression. So are there any formalities to obtain copyright? There are none. The mere act of creating your computer program is sufficient to obtain copyright protection. It's also not necessary that your software is finished, so you will be able to get protection for every stage of your computer program. And who is the author? In principle, it is a creator. You have some assumptions in the case of employees or when it's in an... Yeah, when you are working for someone else. So you have various works in copyright. In the context of open source projects, you could say that you have a maze of different works. So when you have your first original work in an open source project, a developer will base himself on the contributions of the previous developers. So he will make a derivative work because he will use essential elements of the first original creation. However, you can get protection for your derivative work if it fulfills the criterion of originality itself. So you will have an independent and fully functioning protection for your derivative work, but you will need authorization from the previous developer to use his piece of code. A lot of open source licenses, they will have a provision on how it works, derivative rights. The set of copyrights, they cover patrimonial rights or economic rights and moral rights. Moral rights, they want to safeguard the link with the author. Whereas economic rights are more... you can use them to exploit your work. In the case of a joint authorship, which is typically for open source projects, those rights will belong equally to all the authors unless you have agreed otherwise. Now, who is a co-author? In order to be considered as a co-author, it's not necessarily that all the developers worked on it at the same time, which is of course not the case when you have an open source project. It's also not necessary that your contribution was equally important, but it is required that your contribution fulfills the criteria of originality, or that your contribution was necessary in order to get the computer program the way it is now. So this means that someone who only proposed an ID or made something on instructions of someone else, he will not be considered as a co-author. An exception of copyright protection is given by the case when the rights of the author are limited by private agreements or a license. Especially in the case when open source is available, there are licenses that might limit the use of your code. It's a very difficult and complicated matter, and the clauses are often rather unclear, especially if you have individual programmers who wrote the provisions. There's also this agreement about the interpretation of open source licenses, but in any case, it's very important that you always reach your open source agreement and know what's in it, so that you won't be surprised at the end. There are many types of open source licenses. We will not talk about it in detail, but just leave it at the ID that you have a lot of them. Now, when will you have an infringement of copyright? You have two types of infringement. Either your code is an unlawful use of the code, or you have an infringement of your license terms. A license will not be honored, for example, when you were required to apply a notice and you didn't do this. The question is if a developer was aware of the fact that he was infringing someone else's code, it could play a role in copyrights because of the fact that copyright doesn't require any formality, and comes into existence following the mere creation of it. It's of course not easy to know if something is protected by copyright. However, the Copyright Act does not require that the infringer has knowledge of the infringement or the copyright, so it is not an exception to copyright. Another IP infringement might follow from a breach of patent law. Although computed programs are excluded from copyright from patent protection as such, the European patent of it does grant such software patents. They are part of a new and non-obvious technical solution for a technical problem. Moreover, in many other countries, software patents are accepted. In a way, patents allow you to protect the underlying idea of your computer program, which is something that copyright doesn't. Now, since most of the patent claims do not include the source code, it is impossible to do technical searches based on the available patent data and open source code. In practice, it may be possible just to avoid well-known infringing patents and to look at the patents of your direct competitors. So it's not easy to know if your code is an infringement of a patent. But you should know that a patent is a territorial right. This means that its scope of protection is limited to the country under which it was granted. So if I have obtained a patent for Belgium, I cannot exercise my rights in France, for instance. Since getting patent protection all over the world is very costly, there are only very few companies who can do this. The biggest risk in our discussed problem is this when developer 1, when he would contribute code in a way that is not allowed by the license, or is an infringement of a patent protection. But you should also know that you can have a combination for protection of copyright and patent law because they will protect a different subject matter. Now, for this presentation, it won't make a big difference if you have a patent infringement or a copyright infringement. The main concern is that there was an infringement somewhere along in the developer's chain. You could ask, is it possible to exonerate the other open source developers when someone made an infringement? Now, the starting point when you address the effect of an agreement on third parties is Article 1165 of the Belgian Civil Code. This article entails the Relativity Principle, which means that the effect of an agreement towards third parties will only be very limited. When you apply this principle to the open source agreement between the different developers who deliver a contribution, this has as a consequence provisions who are in exoneration, which exonerate developers for the use of infringing materials. They cannot be successfully invoked against the third party, so the person whose rights were infringed. However, you can use such provision against the developer who made the infringing contribution because it is only fair that if someone who was in good faith and innocent, that he can reclaim the damages that he should pay from the infringing developer. So, that was it about the Wernherse Riesgart. I will now talk about how to protect yourself. Don't raise your expectations too high because you can't do that much. I think that most of all we have to make a distinction between your own code and the code of orders. When you join a project, there are some things you have to do for your own code that is right in good faith. First of all, try to avoid duplication. If you don't need the code of someone else, start from zero and write it yourself. That's pretty easy. Then, also keep records. If you keep clean and clear records of all your actions, it will be easier for the next contributors in the project to check your code and to understand what the legal applications are connected to your code. Then, about the code of orders, I call it here, joining in good faith. Then, there are some preventive mechanisms and some remedial efforts. About prevention is you, first of all, only contribute, clean code yourself again, also for when you join. Then, be aware of the previous contributions. This means that you need to identify all the pieces of the code and where they come from. You need to identify the person, the developer who wrote it, the licenses that are burdened, the code, and what the obligations and limitations are that follow from these licenses. Therefore, you need to read the documentation and that will be a lot of work. You can have open source insurances, but due to the fact that they're quite expensive and they don't cover everything, all the legal issues, they don't seem to become very popular. What to do if you have figured out that someone previous has used infringing code? First of all, you can try to modify the code, but that will be very time consuming and leak consuming. I guess that's only a solution when you're in the very early stages of the project. Secondly, you can negotiate additional licenses because if a previous person was the author of the code, he has the right to give another license with other obligations and other limitations. I guess that our main conclusions are that there are no specific solutions. A Stitch in Time saves nine. Read the licenses and try to comply as we just here get, basically. That was it. If someone has questions, more concrete questions. Any questions? No. Okay, well thank you very much. Thank you. Go ahead. Thank you. Thank you. The screen is already synced. Yes. I'm sure I'm getting lots of malware installed on my laptop on my plug-e-z. Oh, these free software developers in there. Sorry, I'm so sorry. Sorry, we had a vlog time. Oh, I am flash drive. I saw that in the mail. Come on, show up and make it. Yeah, I figured he would. He sat last night. He eats four hours a day. Yeah, I know. It's like highly overrated. Did you go to like an overdue? Yes, shit. I stopped by to say hello and then she was still there. She stayed like, slow speeder. I stayed really late. And then like a few smaller people, two different groups of people. I got to like this time. This is a USB 3 port, it's possible. The flash drive doesn't like USB 3. Yeah, yeah, yeah. So, yeah, my bag is there. Yeah, thanks. Wow. Let me get it. Ta-da! Great. Do you have an interest? Sure. Say it again. Are you ready to go? Yeah. No, no, I've actually heard you did. Yeah, okay. And I think that this is a... We haven't heard many repeat speakers, but I like to say it's a repeat. Yeah. But no, it will be... It's new content. He was on a panel. It's like me, he's been on panels. I had never spoken either. He's in the same situation I am in. We should have bugged her. I'm sorry, I'm sorry. Martin, Martin, you could submit a talk. Yeah, why didn't Martin submit a talk? You still have time. You can have my slot. Did you manage to connect it up? Yeah, Jeremy actually solved the problem. I talked to Jeremy for an hour last night about it, and he solved everything. So it's all connected. So, I have time. I think we've got... You have a time thing? So it's 9.30 this week, we'll start, right? Yeah, I think mine is more accurate than yours. Mine just syncs with NTP. Yeah, well then... So what's your point? Mine is only microseconds off. Microseconds off? That's a good point. But it syncs like an hour ago. Don't you know the Android bug about how American phones are... What is it? 30 seconds off? But it syncs with... I have the NTP client installed. It syncs with NTP. It did 30 seconds in two hours? No, no, no, it's because of the off. There's like, it didn't take into account some offset thing. It's 30 seconds wrong. Even if you have NTP client installed? Yes. That's Paul. He was here yesterday. He would know. I don't believe it. I believe that the NTP client's not installed. If you have an NTP client installed, you're telling me the NTP guys didn't... This isn't an NTP thing. It's something about the... Goofy OS 3. I'm wondering if you can actually see it. Maybe Paul fix it. So I'll take it off back. So I'm running Paul's code. Wait a second. I'm running Paul's code. I just realized what Paul you were talking about. The guy who's code I'm running, you said it's broken. No, no, no. I thought you were running... Yeah, I forgot that you were running the real thing. I'm running the real thing. I'm running that Google crap. Okay, just checking. So, um... So I'm actually... Alexis? Alexis. Alexis. Is it Lexios? There's an I. Say the I. I don't think they pronounce the I's in Google. Lexios. You're in the form of names, presidents. I have a really bad problem with pronouncing names. Even US ones. It's not like I'm just a dumb American. I pronounce a US name wrong too. I switched doctors with like humblest. I could sort of pronounce Smith. But occasionally I've said smith, right? I mean... It's because everybody pronounces my name wrong. I'm getting back at the world. I've been called Kahn so many times. My name's Kuhn. People say Kahn all the time. For instance, I was a kid. Kuhn. Yeah, people like that. That's actually close. It's a German name and the umlaut was dropped at some point in the US. So it's actually a Kuhn name, but... Technically it's a Kuhn. But the umlaut, the umlaut, it's... And without a year. Yeah. Actually there are people... A lot of people in the US who are translated with my name, that's K, U, E, H, and E. Oh, okay. You'll find those cuties in... But they still say Kuhn. Those people still say Kuhn. You don't have to say name, right? Yeah. So, um... I might want to talk to the... I don't really want to be... And, um... And then I'll go and... I might talk to the... I don't really know if you can tell. I don't really know if you can tell. I need you to tell me. I don't know if you can tell. Yeah, I think you can tell. So, uh... It gets started, but since we have a couple of short talks, I want to make sure...
 I don't know where my two speakers went, so...  I don't know.  They're in the hall.  I should probably remind them that it's my turn.  It is, sir.  It's just us.  Are you getting ready?  Yeah.  I'll look at that.  That's it, right?  Okay, well, thank you for coming back to the  Legal and Policy Issues Dev Room.  For those of you that didn't have too much beer last night,  and we're really excited to start off,  talking today about IP risks with Jung Shin and Su Mi.  Yeah, here it is.  Good morning.  The scope of this...  Oh, wait.  Okay.  The topic of this talk is IP risks for open source developers.  And yesterday I went to a very interesting keynote of James Turnbull on software archaeology for beginners.  And I really enjoyed, I don't know if anyone else was there, but I really enjoyed the talk.  And I learned a lot, although I don't think I understood everything.  But there were two minor things that disturbed me a little bit.  The first thing, but I discussed it with him, so he knows.  And the first thing was, even if his messages was that you always have to write, to ask the same, the right question at the right time.  And as an example of how it should not be, he gave the example of don't ask the developer what his favorite contract is.  I think that's a bit unfortunate because I think that the developers should be aware of contracts because its law is inevitable and you need to know what you're working with on a daily basis.  The second thing that was a little missing from my point of view was in his step-by-step process of what you should do when you join an open source project.  He didn't mention the licensing compliance check.  And I asked him afterwards and he said that he just trusts the people in a good project.  So we will talk about this today because we think there are some issues.  So what we do want to share with you today is some thoughts on how to protect yourself against IP infringements by others.  And we will also talk a little bit about how to protect yourself.  Before we really start the presentation, I just want to give you the message that if you are involved in an open source project, there are still copyrights hanging there.  Because copy left is only an exception for your copyright.  So you really need to consider copyright and you really need to know what the risks are.  But first, before we get to the protection of the protection mechanisms for you, we will have Sumi talking about copyright.  So I will explain the problem shortly.  You have an open source project X and developer 1, he is actually in good faith.  He has an infringing contribution to the developer's chain.  The piece of code that he uses infringes the IP right of the third party who is not directly involved in the project and then gave permission to use this code.  Now, every subsequent developer can be held liable for this infringement even when they are not aware of the fact that his contribution is infringing.  In general, creating a computer program, even open source, completely unaware of the existence of any IP rights of the third party can be used as a defense to willful IP infringement,  but it's not a defense to IP infringement in general.  Because it is common for open source projects that they are developed by community rather than one person or one organization, these problems occur in real life.  In case of a big project when you have thousands of developers, it's not reasonable to expect that every developer will check if there are infringements in the code by other developers.  But in smaller projects, these expectations might be different.  You can use version management systems to see which developer made which contribution to the project.  The risk of IP infringement, it is not a specific problem to open source projects, but of course the risk is greater because open source allows you to distribute and modify the software freely.  The infringement will carry through subsequent versions of the program and further development of the software.  So a small and quick remark is that everything we say today is seen from a Belgian point of view.  Of course, when you have an international project, it's possible that there is another law applicable.  So this can also have influence on the outcome of the results of your claim.  So the problem consists of two elements.  When do we have an IP risk and how can you protect yourself?  So first I will explain about when you will have an infringement.  And I will explain you which kind of intellectual property should be taken into account when you are dealing with open source projects.  The most important are copyright and patent law.  First I will tell you something about copyright and how you can know if the source code of someone else is protected by copyright.  So in Belgium, in general, computer programs are protected by copyright because there is an assimilation with literary works with the burn convention.  So it's not exactly the same as general copyright, but you can see it as a kind of modified version of copyright for software.  Because of the general principle that copyright doesn't protect the underlying idea of your program, but only the original expression,  you are allowed to copy the functionality of computer program, provided that you do not copy the source code, but you rewrite it to your own original code.  The mere fact that software is developed in an open source context does not mean that there is an extension on this general principle that copyright plays a role.  In Belgium we don't have a definition of what a computer program exactly is, but for instance the UK does.  So it is possible that different elements of your program are protected in different countries.  The European Court of Justice did indicate that your object code, source code and your preparatory design will be considered as an expression of your computer program.  What matters is that your expression enables the reproduction of your computer program and it enables the computer to perform its task.  So what are the criteria for copyright protection? You need originality.  Article one of the European Software Directive says that the computer program shall be protected in the sense that it is the author's own intellectual creation,  in the sense that he made creative choices that are an expression of his own personality.  So you cannot apply any other criteria for copyright protection.  There will be given protection to the expression in any form of your computer program, provided that nature is such as that a computer program can result from it in a later stage.  As a consequence you will not get protection for your functionality of your program, the programming language and format of data files,  and the graphic user interface. Nevertheless, a graphic user interface can be protected by the general copyright if it fulfills the criteria of originality.  This also applies to the programming language. It can also be protected if it is an original expression.  So are there any formalities to obtain copyright? There are none. The mere act of creating your computer program is sufficient to obtain copyright protection.  It's also not necessary that your software is finished, so you will be able to get protection for every stage of your computer program.  And who is the author? In principle, it is a creator. You have some assumptions in the case of employees or when it's in an...  Yeah, when you are working for someone else. So you have various works in copyright. In the context of open source projects, you could say that you have a maze of different works.  So when you have your first original work in an open source project, a developer will base himself on the contributions of the previous developers.  So he will make a derivative work because he will use essential elements of the first original creation.  However, you can get protection for your derivative work if it fulfills the criterion of originality itself.  So you will have an independent and fully functioning protection for your derivative work, but you will need authorization from the previous developer to use his piece of code.  A lot of open source licenses, they will have a provision on how it works, derivative rights.  The set of copyrights, they cover patrimonial rights or economic rights and moral rights.  Moral rights, they want to safeguard the link with the author.  Whereas economic rights are more... you can use them to exploit your work.  In the case of a joint authorship, which is typically for open source projects, those rights will belong equally to all the authors unless you have agreed otherwise.  Now, who is a co-author?  In order to be considered as a co-author, it's not necessarily that all the developers worked on it at the same time,  which is of course not the case when you have an open source project.  It's also not necessary that your contribution was equally important,  but it is required that your contribution fulfills the criteria of originality,  or that your contribution was necessary in order to get the computer program the way it is now.  So this means that someone who only proposed an ID or made something on instructions of someone else, he will not be considered as a co-author.  An exception of copyright protection is given by the case when the rights of the author are limited by private agreements or a license.  Especially in the case when open source is available, there are licenses that might limit the use of your code.  It's a very difficult and complicated matter, and the clauses are often rather unclear,  especially if you have individual programmers who wrote the provisions.  There's also this agreement about the interpretation of open source licenses,  but in any case, it's very important that you always reach your open source agreement and know what's in it,  so that you won't be surprised at the end.  There are many types of open source licenses.  We will not talk about it in detail, but just leave it at the ID that you have a lot of them.  Now, when will you have an infringement of copyright?  You have two types of infringement.  Either your code is an unlawful use of the code, or you have an infringement of your license terms.  A license will not be honored, for example, when you were required to apply a notice and you didn't do this.  The question is if a developer was aware of the fact that he was infringing someone else's code,  it could play a role in copyrights because of the fact that copyright doesn't require any formality,  and comes into existence following the mere creation of it.  It's of course not easy to know if something is protected by copyright.  However, the Copyright Act does not require that the infringer has knowledge of the infringement or the copyright,  so it is not an exception to copyright.  Another IP infringement might follow from a breach of patent law.  Although computed programs are excluded from copyright from patent protection as such,  the European patent of it does grant such software patents.  They are part of a new and non-obvious technical solution for a technical problem.  Moreover, in many other countries, software patents are accepted.  In a way, patents allow you to protect the underlying idea of your computer program, which is something that copyright doesn't.  Now, since most of the patent claims do not include the source code,  it is impossible to do technical searches based on the available patent data and open source code.  In practice, it may be possible just to avoid well-known infringing patents  and to look at the patents of your direct competitors.  So it's not easy to know if your code is an infringement of a patent.  But you should know that a patent is a territorial right.  This means that its scope of protection is limited to the country under which it was granted.  So if I have obtained a patent for Belgium, I cannot exercise my rights in France, for instance.  Since getting patent protection all over the world is very costly, there are only very few companies who can do this.  The biggest risk in our discussed problem is this when developer 1, when he would contribute code in a way that is not allowed by the license,  or is an infringement of a patent protection.  But you should also know that you can have a combination for protection of copyright and patent law  because they will protect a different subject matter.  Now, for this presentation, it won't make a big difference if you have a patent infringement or a copyright infringement.  The main concern is that there was an infringement somewhere along in the developer's chain.  You could ask, is it possible to exonerate the other open source developers when someone made an infringement?  Now, the starting point when you address the effect of an agreement on third parties is Article 1165 of the Belgian Civil Code.  This article entails the Relativity Principle, which means that the effect of an agreement towards third parties will only be very limited.  When you apply this principle to the open source agreement between the different developers who deliver a contribution,  this has as a consequence provisions who are in exoneration, which exonerate developers for the use of infringing materials.  They cannot be successfully invoked against the third party, so the person whose rights were infringed.  However, you can use such provision against the developer who made the infringing contribution  because it is only fair that if someone who was in good faith and innocent,  that he can reclaim the damages that he should pay from the infringing developer.  So, that was it about the Wernherse Riesgart.  I will now talk about how to protect yourself. Don't raise your expectations too high because you can't do that much.  I think that most of all we have to make a distinction between your own code and the code of orders.  When you join a project, there are some things you have to do for your own code that is right in good faith.  First of all, try to avoid duplication. If you don't need the code of someone else, start from zero and write it yourself.  That's pretty easy.  Then, also keep records. If you keep clean and clear records of all your actions, it will be easier for the next contributors in the project  to check your code and to understand what the legal applications are connected to your code.  Then, about the code of orders, I call it here, joining in good faith.  Then, there are some preventive mechanisms and some remedial efforts.  About prevention is you, first of all, only contribute, clean code yourself again, also for when you join.  Then, be aware of the previous contributions. This means that you need to identify all the pieces of the code and where they come from.  You need to identify the person, the developer who wrote it, the licenses that are burdened, the code, and what the obligations and limitations are that follow from these licenses.  Therefore, you need to read the documentation and that will be a lot of work.  You can have open source insurances, but due to the fact that they're quite expensive and they don't cover everything, all the legal issues,  they don't seem to become very popular.  What to do if you have figured out that someone previous has used infringing code?  First of all, you can try to modify the code, but that will be very time consuming and leak consuming.  I guess that's only a solution when you're in the very early stages of the project.  Secondly, you can negotiate additional licenses because if a previous person was the author of the code,  he has the right to give another license with other obligations and other limitations.  I guess that our main conclusions are that there are no specific solutions.  A Stitch in Time saves nine.  Read the licenses and try to comply as we just here get, basically.  That was it.  If someone has questions, more concrete questions.  Any questions?  No.  Okay, well thank you very much.  Thank you.  Go ahead.  Thank you.  Thank you.  The screen is already synced.  Yes.  I'm sure I'm getting lots of malware installed on my laptop on my plug-e-z.  Oh, these free software developers in there.  Sorry, I'm so sorry.  Sorry, we had a vlog time.  Oh, I am flash drive.  I saw that in the mail.  Come on, show up and make it.  Yeah, I figured he would.  He sat last night.  He eats four hours a day.  Yeah, I know. It's like highly overrated.  Did you go to like an overdue?  Yes, shit.  I stopped by to say hello and then she was still there.  She stayed like, slow speeder.  I stayed really late.  And then like a few smaller people, two different groups of people.  I got to like this time.  This is a USB 3 port, it's possible.  The flash drive doesn't like USB 3.  Yeah, yeah, yeah.  So, yeah, my bag is there.  Yeah, thanks.  Wow.  Let me get it.  Ta-da!  Great.  Do you have an interest?  Sure.  Say it again.  Are you ready to go?  Yeah.  No, no, I've actually heard you did.  Yeah, okay.  And I think that this is a...  We haven't heard many repeat speakers, but I like to say it's a repeat.  Yeah.  But no, it will be...  It's new content. He was on a panel.  It's like me, he's been on panels.  I had never spoken either. He's in the same situation I am in.  We should have bugged her.  I'm sorry, I'm sorry.  Martin, Martin, you could submit a talk.  Yeah, why didn't Martin submit a talk?  You still have time.  You can have my slot.  Did you manage to connect it up?  Yeah, Jeremy actually solved the problem.  I talked to Jeremy for an hour last night about it, and he solved everything.  So it's all connected.  So, I have time.  I think we've got...  You have a time thing?  So it's 9.30 this week, we'll start, right?  Yeah, I think mine is more accurate than yours.  Mine just syncs with NTP.  Yeah, well then...  So what's your point?  Mine is only microseconds off.  Microseconds off? That's a good point.  But it syncs like an hour ago.  Don't you know the Android bug about how American phones are...  What is it? 30 seconds off?  But it syncs with... I have the NTP client installed.  It syncs with NTP.  It did 30 seconds in two hours?  No, no, no, it's because of the off.  There's like, it didn't take into account some offset thing.  It's 30 seconds wrong.  Even if you have NTP client installed?  Yes. That's Paul.  He was here yesterday. He would know.  I don't believe it.  I believe that the NTP client's not installed.  If you have an NTP client installed, you're telling me the NTP guys didn't...  This isn't an NTP thing. It's something about the...  Goofy OS 3.  I'm wondering if you can actually see it.  Maybe Paul fix it. So I'll take it off back.  So I'm running Paul's code. Wait a second.  I'm running Paul's code.  I just realized what Paul you were talking about.  The guy who's code I'm running, you said it's broken.  No, no, no. I thought you were running...  Yeah, I forgot that you were running the real thing.  I'm running the real thing.  I'm running that Google crap.  Okay, just checking.  So, um...  So I'm actually...  Alexis?  Alexis.  Alexis.  Is it Lexios?  There's an I.  Say the I.  I don't think they pronounce the I's in Google.  Lexios.  You're in the form of names, presidents.  I have a really bad problem with pronouncing names.  Even US ones. It's not like I'm just a dumb American.  I pronounce a US name wrong too.  I switched doctors with like humblest.  I could sort of pronounce Smith.  But occasionally I've said smith, right?  I mean...  It's because everybody pronounces my name wrong.  I'm getting back at the world.  I've been called Kahn so many times.  My name's Kuhn.  People say Kahn all the time.  For instance, I was a kid.  Kuhn.  Yeah, people like that. That's actually close.  It's a German name and the umlaut was dropped  at some point in the US.  So it's actually a Kuhn name, but...  Technically it's a Kuhn.  But the umlaut, the umlaut, it's...  And without a year.  Yeah.  Actually there are people...  A lot of people in the US who are translated  with my name, that's K, U, E, H, and E.  Oh, okay.  You'll find those cuties in...  But they still say Kuhn.  Those people still say Kuhn.  You don't have to say name, right?  Yeah.  So, um...  I might want to talk to the...  I don't really want to be...  And, um...  And then I'll go and...  I might talk to the...  I don't really know if you can tell.  I don't really know if you can tell.  I need you to tell me.  I don't know if you can tell.  Yeah, I think you can tell.  So, uh...  It gets started, but since we have a couple of short talks,  I want to make sure...
_FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_0_1235.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_1236_5147.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_5148_5195.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_5196_8819.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_8820_8963.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_8964_9779.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_9780_12539.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_12540_12695.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_12696_16199.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_16200_19559.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_19560_19787.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_19788_21503.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_21504_23519.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_23520_23687.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_23688_27155.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_27156_28127.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_28128_28271.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_28272_28835.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_28836_30671.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_30672_34343.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_34344_35027.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_35028_36791.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_36792_36899.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_36900_36971.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_36972_37103.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_37104_37415.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_37416_38519.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_38520_39263.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_39264_39563.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_39564_39647.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_39648_39791.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_39792_40007.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_40008_40247.png _FOSDEM_2014__IP_risks_for_OSS_developers_KhllUDe9AXA_40248_40384.png