From owner-freebsd-current@FreeBSD.ORG Thu Aug 19 13:03:19 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 AEBAA16A4CE for ; Thu, 19 Aug 2004 13:03:19 +0000 (GMT) Received: from speicher.org (speicher.org [208.199.76.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1796243D48 for ; Thu, 19 Aug 2004 13:03:19 +0000 (GMT) (envelope-from geoff@speicher.org) Received: from speicher.org (localhost [127.0.0.1]) by speicher.org (8.12.11/8.12.11) with ESMTP id i7JD3I17066796; Thu, 19 Aug 2004 09:03:19 -0400 (EDT) (envelope-from geoff@speicher.org) Received: (from geoff@localhost) by speicher.org (8.12.11/8.12.11/Submit) id i7JD3ISU066795; Thu, 19 Aug 2004 09:03:18 -0400 (EDT) (envelope-from geoff) Date: Thu, 19 Aug 2004 09:03:18 -0400 From: Geoff Speicher To: drhodus@machdep.com Message-ID: <20040819130318.GA66353@sirius.speicher.org> References: <200408160104.03708.chris@behanna.org> <41234FC6.1000005@cronyx.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org Subject: Re: Public Access to Perforce? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Aug 2004 13:03:19 -0000 On Wed, Aug 18, 2004 at 01:24:51PM +0000, David Rhodus wrote: > On Wed, 18 Aug 2004 16:47:02 +0400, Roman Kurakin wrote: > > David Rhodus wrote: > > > > >On Mon, 16 Aug 2004 01:04:03 -0400, Chris BeHanna wrote: > > > > > > > > >> Forgive me if this already exists. I searched the list archives, > > >>google, and freebsd.org and did not find any way for non-committers to > > >>have read-only access to the p4 repo. > > >> > > >> Is there a read-only account that the general public could use? > > >> > > >> > > > > > >With the perforce trees being hidden away without public access to the > > >changes, this makes the FreeBSD project no longer an open source > > >project. > > > > > > > > This hides only development proccess, not a stable result. > > If you don't have access to my home disks were I keep my > > intermediate code with additional debug/hacks and so on > > while I am debuggin new functionality would affect open > > source status of results of my work? > > > > rik > > No this is not what I'm talking about, I don't think that level of > development work is able to sustain here. The development work should > be done in the public cvs tree were it is open to public scrutiny and > were a section of the community can help on the development process. FreeBSD src committers certainly don't need to have public scrutiny forced upon them for the work they are doing. Do you demand access to the kitchen when you go out to a restaurant? Would you want people watching over your back while you were experimenting, all the while telling you how you might be doing it better? It's already bad enough with all the myopic armchair-quarterbacks around here. Please, I appreciate your position, but don't be absurd. Geoff