From owner-freebsd-chat@FreeBSD.ORG Mon May 5 10:01:26 2003 Return-Path: Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A615237B401 for ; Mon, 5 May 2003 10:01:26 -0700 (PDT) Received: from HAL9000.homeunix.com (12-233-57-131.client.attbi.com [12.233.57.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1126343FBF for ; Mon, 5 May 2003 10:01:26 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.9/8.12.5) with ESMTP id h45H1LdN007999; Mon, 5 May 2003 10:01:21 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.9/8.12.5/Submit) id h45H1LTV007998; Mon, 5 May 2003 10:01:21 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Date: Mon, 5 May 2003 10:01:21 -0700 From: David Schultz To: "Jeremy C. Reed" Message-ID: <20030505170121.GA7950@HAL9000.homeunix.com> Mail-Followup-To: "Jeremy C. Reed" , chat@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: cc: chat@FreeBSD.ORG Subject: Re: open source license with 24 month proprietary clause X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 May 2003 17:01:26 -0000 On Sat, May 03, 2003, Jeremy C. Reed wrote: > Has anyone heard of an open source license where new code based on it can > be kept proprietary for 24 months? > > Then after the 24 months that code becomes part of the public code base. The easiest way to do this is to attach a restrictive license or no license to your code for the first 24 months, then release it under a less restrictive license such as the BSD license. For most purposes, you don't need an uber-license that covers the terms both before and after the 24-month period. It's your code, so you can change the distribution terms as you see fit (aside from being able to revoke privileges granted by an earlier license.)