From owner-freebsd-current@FreeBSD.ORG Wed Aug 18 15:19:30 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A0BD616A4CE for ; Wed, 18 Aug 2004 15:19:30 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3713443D31 for ; Wed, 18 Aug 2004 15:19:30 +0000 (GMT) (envelope-from sdrhodus@gmail.com) Received: by mproxy.gmail.com with SMTP id 77so146440rnl for ; Wed, 18 Aug 2004 08:19:29 -0700 (PDT) Received: by 10.38.164.57 with SMTP id m57mr118199rne; Wed, 18 Aug 2004 08:19:29 -0700 (PDT) Message-ID: Date: Wed, 18 Aug 2004 11:19:29 -0400 From: David Rhodus To: Doug Rabson In-Reply-To: <200408181611.45299.dfr@nlsystems.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <200408160104.03708.chris@behanna.org> <200408181611.45299.dfr@nlsystems.com> cc: chris@behanna.org cc: freebsd-current@freebsd.org cc: Roman Kurakin cc: drhodus@machdep.com cc: current@freebsd.org Subject: Re: Public Access to Perforce? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: drhodus@machdep.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Aug 2004 15:19:30 -0000 On Wed, 18 Aug 2004 16:11:44 +0100, Doug Rabson wrote: > On Wednesday 18 August 2004 15:28, David Rhodus wrote: > > On Wed, 18 Aug 2004 17:57:19 +0400, Roman Kurakin > wrote: > > > I fully agree with you. But this not affect "open source"ness. > > > I'd rather call it open development. > > > > > > rik > > > > Yes, it does when the public doesn't have direct access to the > > development work going on. Thats what started this thread in the > > first place. > > This is ludicrous. You don't have access to my private source trees on > my private machines where I test and develop software before committing > it to CVS. How does that change the fact that when I commit that > software it has a standard two clause BSD open source license. Well that is fine if that is the method in which you are using the perforce system. But when overly large commits hit the cvs tree from perforce which should have came with incremental changes so there could be more detail public scrutiny, etc.. there is a problem. -- -David Steven David Rhodus