Date: Thu, 17 Jun 2010 09:14:48 +0200 From: Erwin Lansing <erwin@FreeBSD.org> To: freebsd-ports@freebsd.org Subject: Re: License Framework: Develop Best Practices Message-ID: <20100617071448.GY76036@droso.net> In-Reply-To: <1276710494.20002.1.camel@vcampaign> References: <C83CE053.19693%freebsdlists-ports@chillibear.com> <4C1729E1.60000@infracaninophile.co.uk> <1276710494.20002.1.camel@vcampaign>
next in thread | previous in thread | raw e-mail | index | archive | help
--Y+Z5jE7Arku/2GrR Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jun 16, 2010 at 10:48:14AM -0700, Micheas Herman wrote: > >=20 > > I don't think the FreeBSD project could afford to have this license > > cataloging scheme regularly inspected by appropriate legal counsel for > > each of the various different jurisdictions around the world and for > > them to approve it as accurate and legally watertight. >=20 > I think that FreeBSD should piggy back on the OSI and just list > the following licenses: > http://www.opensource.org/licenses/alphabetical plus "other". Using the list from OSI or NetBSD or similar would be a good way do an initial population of the file. > =20 > This could be a filter of sorts for those that want it. IANAL > but just listing the license should not be more or less risky > for the project than distributing the source code, and it might > even reduce the risk of distributing pre compiled binaries as > there is at least a good faith effort to comply with the > license(s) and make it easy for the end user to be aware of the > license(s) of the code. >=20 We already have a mechanism to prevent distribution distfiles and packages on our mirrors with the current NO_CDROM, RESTRICTED and NO_PACKAGE flags. The license framework is ment to make these more finegrained and give endusers a better handle to avoid using specific licenses. As you say, this does not change that it will be done on a best effort basis, which may, or may not, be good enough for your specific use case, but it does provide better control. -erwin --=20 Erwin Lansing http://droso.org Prediction is very difficult especially about the future erwin@FreeBSD.org --Y+Z5jE7Arku/2GrR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iD4DBQFMGctoqy9aWxUlaZARAmhpAKDcGld8fD+iK2nQnrtO0ZQKxcdtggCWNt7B L7+Tpz4kXzzUmgfooOfaDA== =sgjd -----END PGP SIGNATURE----- --Y+Z5jE7Arku/2GrR--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100617071448.GY76036>