From owner-freebsd-ports@FreeBSD.ORG Tue Jan 17 02:40:07 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 683B4106566B for ; Tue, 17 Jan 2012 02:40:07 +0000 (UTC) (envelope-from code@apotheon.net) Received: from oproxy5-pub.bluehost.com (oproxy5.bluehost.com [IPv6:2605:dc00:100:2::a5]) by mx1.freebsd.org (Postfix) with SMTP id 280518FC08 for ; Tue, 17 Jan 2012 02:40:07 +0000 (UTC) Received: (qmail 10919 invoked by uid 0); 17 Jan 2012 02:40:06 -0000 Received: from unknown (HELO box543.bluehost.com) (74.220.219.143) by cpoproxy2.bluehost.com with SMTP; 17 Jan 2012 02:40:06 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=apotheon.net; s=default; h=In-Reply-To:Content-Transfer-Encoding:Content-Type:MIME-Version:References:Message-ID:Subject:To:From:Date; bh=4YIzTCBtnqrySUhOsR/8mh/JFIEDLUOKq35MweYULIo=; b=gPA/L0w+eJXr3bPv57OmvGgdj5RJ+z4ILWrv0qUzMWdsqA63uk1uHOalF1OUpJYmSJ9koGPbGskqsfP112yuXENLC6470NvZoytdvH+qfIsHsUE5AC4+O4tnkFzeFECt; Received: from c-24-8-180-234.hsd1.co.comcast.net ([24.8.180.234] helo=localhost) by box543.bluehost.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.76) (envelope-from ) id 1Rmyxx-0003us-OC for freebsd-ports@freebsd.org; Mon, 16 Jan 2012 19:40:05 -0700 Date: Mon, 16 Jan 2012 19:40:04 -0700 From: Chad Perrin To: freebsd-ports@freebsd.org Message-ID: <20120117024004.GA4736@hemlock.hydra> References: <201201162339.q0GNdG1V064832@anthesphoria.net> <201201170049.q0H0nTjC065207@anthesphoria.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <201201170049.q0H0nTjC065207@anthesphoria.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-Identified-User: {2737:box543.bluehost.com:apotheon:apotheon.net} {sentby:smtp auth 24.8.180.234 authed with code@apotheon.net} Subject: Re: Adding licensing info to my ports: some questions X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jan 2012 02:40:07 -0000 On Tue, Jan 17, 2012 at 05:40:35AM +0300, Nikola Lečić wrote: > On Mon, Jan 16, 2012 at 08:14:57PM -0500 Eitan Adler [email address > elided] wrote: > > 2012/1/16 Nikola Lečić : > > > > > > 6) I need three new items added to the licenses database because they > > >   should be considered as 'known' licenses and thus belonging to the > > >   'Case 1' in bsd.licenses.mk. There are: Common Public License, SIL > > >   Open Font License and Public Domain [non-license]. I'd gladly > > >   submit a PR, but I'd appreciate if someone could check this first, > > >   especially _LICENSE_GROUPS_* including COPYFREE status. > > > > Please submit this as a patch in a PR and email me. I'll make sure > > they get added. > > Will do. > > > Common Public License is not copyfree. > > SIL Open Font License is not copyfree. > > Ok, thanks. There are lists of licenses certified as complying with the Copyfree Standard Definition and licenses explicitly rejected at the Copyfree Initiative website: http://copyfree.org/licenses http://copyfree.org/rejected I hope this helps in the future. There are contact links on the site you can use to send messages if you have other licenses than listed there you want to ask about. It might be worthwhile to check the page for the Copyfree Standard Definition when wondering about a given license, if it is not on one of those lists, though: http://copyfree.org/standard > > > > Putting something in the Public Domain doesn't work in any meaningful > > sense and is not a license. > > converters/base64 is public domain (see COPYING from its distfile). > Do you mean that Public Domain shouldn't be added to the licenses > database? NetBSD has it. It seems like it would be useful to have a "public domain" category of some kind, from where I'm sitting, with the understanding that it may not mean anything useful depending on jurisdiction. Beyond that, I probably shouldn't say anything about it on this list. The applicability of plain ol' public domain dedications can be a contentious topic. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]