From owner-freebsd-ports@freebsd.org Tue Dec 26 23:16:46 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A3DA1E89A91 for ; Tue, 26 Dec 2017 23:16:46 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from mout.gmx.com (mout.gmx.com [74.208.4.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mail.gmx.com", Issuer "thawte SSL CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6B1E66BF51 for ; Tue, 26 Dec 2017 23:16:46 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from [108.70.50.7] ([108.70.50.7]) by 3c-app-mailcom-lxa05.server.lan (via HTTP); Wed, 27 Dec 2017 00:16:43 +0100 MIME-Version: 1.0 Message-ID: From: Sid To: sid@bsdmail.com Cc: freebsd-ports@freebsd.org Subject: Re: License and adopting software Content-Type: text/plain; charset=UTF-8 Date: Wed, 27 Dec 2017 00:16:43 +0100 Importance: normal Sensitivity: Normal In-Reply-To: References: Content-Transfer-Encoding: quoted-printable X-UI-Message-Type: mail X-Priority: 3 X-Provags-ID: V03:K1:AFkrek6Fsj71jTo1rfNKoxEgrDxqBa4nhbuseBz3qs9 zuIJ6dqLjqZMOEkBp750fxuWFJbbIV5C+bnAXX6ikloEQSbfbj l7zDVEPP1nT3FU5/82UQGueiqt90GkuzkODMPJtnyCgaLXcqyF junVBrRfzi4IRD8Q4xY2LsgCKaRznQ+f1b2GmdU37cWif/0JZE /12IpeeuaAHnRrYvnA4/KPxR3OMvjOP2oME7NQTmN1Rlc/NmV0 JuAa89LZoYl8gZGSC1FZoSk5B+SMwgwXuTIhBIkUT4RdZLILtT SQ/h6Y= X-UI-Out-Filterresults: notjunk:1;V01:K0:ewQ/uMF2ZMo=:4P+pSdxo5MIgEdD/kzjPiw iT5B/iPtEb+8MTkLe3+Cml7BPSPEEgimR4ab+K5/tfusNXu8oWsLk9zkfGZkyHBl6w4JGkWz6 HdWo2+ObPtGZuWxTAnGLckLjS3h4gSyf2lLB+qygaOjcOc2plZA1YzYb1Ga7ovQ7SPpXQWQJS c2icqMX2b6R+9J+z0DZONLeJ42ts1CS9W2oWkdmabhNmiGi1x2cWOcxj9skekNyEh/1t7bhDZ YRv4NzqYE48/dHLxieInQDep+j5B84U9W5HjaZViS1bw/Y2Bs7WkuVR1+suy2eXGsVsEQDUzo /X0QTnaAHc46O9oayEmj5zYvAgVBqBOiHptPmNKY6qyBoF00vCXJkGbuTkadaBXnWrtwB/JKg xPklR/QVhi2z3moarltFONrvfAkfOHTEXDbeEopOjvAowgrGPntxb1r58Mdo1NUL+wj4orCUx QP6veNC+QQEhEnUraC46dRo4pMB3YKOnE5R15QAutm8YXqbCC7x4YWLgqgnr3+aUKNHm8NYvE JLygu4Z7XF0RTHfq9rDeALDa1DxxGRLfpeGWeOTdB7f X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Dec 2017 23:16:46 -0000 > '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