From owner-freebsd-current Sat Aug 2 13:53:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA13622 for current-outgoing; Sat, 2 Aug 1997 13:53:58 -0700 (PDT) Received: from genghis.eng.demon.net (genghis.eng.demon.net [193.195.45.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA13612 for ; Sat, 2 Aug 1997 13:53:51 -0700 (PDT) Received: from genghis.eng.demon.net [193.195.45.10] by genghis.eng.demon.net with esmtp (Exim 1.62 #1) id 0wulBA-00008k-00; Sat, 2 Aug 1997 21:53:36 +0100 To: "Jordan K. Hubbard" cc: current@freebsd.org Subject: Re: ports-current/packages-current discontinued Organization: Demon Internet Ltd. Reply-To: ade@demon.net In-reply-to: Your message of "Sat, 02 Aug 1997 13:38:09 PDT." <16092.870554289@time.cdrom.com> Date: Sat, 02 Aug 1997 21:53:35 +0100 From: Ade Lovett Message-Id: Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "Jordan K. Hubbard" writes: > >That option's already been discussed to death. ;-) *smile* I'm sure it has.. dontcha just love the cyclic nature of project management concepts? :) >The question is how to do this effectively, not in the concept. >The concept is the easy part. ;) Well, given the major amount of work this is going to require in order to do things effectively, surely the first step is a mandate from the core team that a particular 'way forward' is the right way to go. IMHO, 'leaving things as they are' isn't a valid option in this case, since we can see that things are starting to break down, as the system gets more complex. Once the decision is made, then things can progress to discussion about how best to implement the decision, followed by resourcing the whole thing. Until the decision is made about the way forward, however, then much of the talk here is moot. -aDe -- Ade Lovett, Demon Internet Ltd.