Date: Wed, 27 Dec 2017 00:16:43 +0100 From: Sid <sid@bsdmail.com> To: sid@bsdmail.com Cc: freebsd-ports@freebsd.org Subject: Re: License and adopting software Message-ID: <trinity-ccfcc285-df56-483d-a2ef-013415edff62-1514330203839@3c-app-mailcom-lxa05> In-Reply-To: <CALM2mEmYsPs3ta7pMHq=KHpw==0ukvdtXad5bJcL08tKegmYTg@mail.gmail.com> References: <CALM2mE=OW=7EUn4ZQUA0CCpYHjOn8WrKe3_FPevYBq3onoJRDw@mail.gmail.com> <CALM2mEn%2BTxwKYpOQekdPzJ4xeuJZts1gOKT3tV%2B57PFbFjdu-Q@mail.gmail.com> <trinity-6b4e8d0d-bf5d-4f62-ac8a-a58e207cdfeb-1514301518528@3c-app-mailcom-lxa16> <CALM2mEmYsPs3ta7pMHq=KHpw==0ukvdtXad5bJcL08tKegmYTg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 'someone else said something to the effect of=C2=A0 "If I looked at the c= ode already, the license is already contaminated"' That makes no sense to me=2E That advice seems counterproductive=2E In the= source code, I'm sure you saw this, but there are different licenses in th= e files=2E =C2=A0 Usually, when someone adds on top of FreeBSD's license, that part belongs = (or is at least dual/multi-licensed) in FreeBSD=2E =C2=A0 The only separator I understand is, the files, to have their distinctive l= icenses, to differentiate it from the rest of the packaged source code, but= first distinguish it as your creation, copyright and license=2E I don't kn= ow if a line within a file can have a different license, unless that line w= as already established as MIT, or the creator releasing that line to GPL=2E =C2=A0 The odd part is, if a code goes into GPL, they get to license it=2E But if= those lines are already MIT, that code is multi-licensed under both MIT an= d GPL=2E If code goes into a GPL code first, and the author didn't claim it= as their own first, it's odd, (that code will be for GPL, but) I don't kno= w if you can use that code for outside of GPL, even if you wrote it=2E I do= n't know about that, but it's safer to claim that code as your own, your pr= oject's or your pseudonym, before writing it into a GPL code to fix it=2E I= wish there was someone who can clarify that=2E I guess you're trying to find out or audit if everything within a code is = GPL? That may be hard=2E I would start a new file, with your own license, i= nformally copyright your creation with simple copyright text and license (n= ot through the office: use the copyright office for your best or proprietar= y work), then maybe merge it afterwards=2E There is better advice on protec= ting your contribution's license, and how they interact=2E Some of that can= be found by looking around, but it would be nice if someone who is really = familiar with that would tell what they can=2E
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?trinity-ccfcc285-df56-483d-a2ef-013415edff62-1514330203839>