From owner-freebsd-chat Wed Jul 30 10:06:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA15886 for chat-outgoing; Wed, 30 Jul 1997 10:06:14 -0700 (PDT) Received: from xmission.xmission.com (xmission.xmission.com [198.60.22.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA15860 for ; Wed, 30 Jul 1997 10:05:53 -0700 (PDT) Received: (from softweyr@localhost) by xmission.xmission.com (8.8.5/8.7.5) id KAA12699; Wed, 30 Jul 1997 10:59:52 -0600 (MDT) From: Wes Peters - Softweyr LLC Message-Id: <199707301659.KAA12699@xmission.xmission.com> Subject: Re: Is FreeBSD really a project? (introduction to WISE) To: pgiffuni@fps.biblos.unal.edu.co (Pedro Giffuni) Date: Wed, 30 Jul 1997 10:59:50 -0600 (MDT) Cc: chat@freebsd.org In-Reply-To: <33D977F7.77DB@fps.biblos.unal.edu.co> from "Pedro Giffuni" at Jul 25, 97 09:08:11 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-chat@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Pedro Giffuni recently commented, with respect to a WWW-based project manager: > I don't consider FreeBSD a project because, technically speaking, a > project has precisely defined it's start and it's ending dates. The > initiation of the FreeBSD project evidently existed, but the goals seem > very generic, and we don't really want this end. In purely bureaucratic > linings, FreeBSD wouldn't be considered a project. True, but "The FreeBSD Project" has created a number of "projects" in the past. Each "release" of FreeBSD is really a project in it's own right, with ongoing development on the -current branch. Once a release is started, it typically gets a number of changes that are then applied back to -current; these are typically bugfixes. >From a source code control standpoint, CVS is quite good at this. The model adopted by FreeBSD has been used by a number of commercial users I am familiar with, including my previous employer. > This makes me think we would have to do modifications on this software > to help in the purpose of enhancing FreeBSD's development (was Jordan > suggesting something like this when someone proposed to shoot him? :-) > ). Anyway, we should test this... Perhaps not. If this is basically a problem tracking and reporting system, I don't really think we would have to make changes. Whenever a new release is undertaken, say a 2.2.5 or 3.0, a "project" for that release would be created. The project would be closed out when a superceding release comes out -- 2.2.2 closes 2.2.1, etc. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.xmission.com/~softweyr softweyr@xmission.com