From owner-freebsd-current@FreeBSD.ORG Fri Apr 9 05:25:43 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 5A51F16A4CE for ; Fri, 9 Apr 2004 05:25:43 -0700 (PDT) Received: from energistic.com (mail.virtual-voodoo.com [65.204.79.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8BC743D31 for ; Fri, 9 Apr 2004 05:25:42 -0700 (PDT) (envelope-from steve@energistic.com) Received: from energistic.com (steve@localhost [127.0.0.1]) by energistic.com (8.12.11/8.12.11) with ESMTP id i39CRTQi019203; Fri, 9 Apr 2004 07:27:29 -0500 (EST) (envelope-from steve@energistic.com) Received: (from steve@localhost) by energistic.com (8.12.11/8.12.11/Submit) id i39CRToJ019202; Fri, 9 Apr 2004 07:27:29 -0500 (EST) (envelope-from steve) Date: Fri, 9 Apr 2004 07:27:29 -0500 From: Steve Ames To: Stijn Hoop Message-ID: <20040409122729.GA19110@energistic.com> References: <20040408224527.GA8299@norsu.kameli.org> <20040409121542.GD26247@pcwin002.win.tue.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040409121542.GD26247@pcwin002.win.tue.nl> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org cc: Atte Peltomaki Subject: Re: Future of FreeBSD 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: Fri, 09 Apr 2004 12:25:43 -0000 On Fri, Apr 09, 2004 at 02:15:42PM +0200, Stijn Hoop wrote: > As a user the best you can do is document all your problems to the developers; > if you want the project to go in a certain direction, or 'finish' a particular > project, you'll have to step in as a developer because that's how opensource > (or at least this project) works. You can't sit by the sideline and say 'hey > this is going wrong' while generally waving your arms about. You could also gather some money together and financially encourage a developer or two to move in a direction you prefer. Rewards for certain features have been posted and accepted in the past. Putting together the necessary financial commitment to help nudge or accelerate the project in a certain direction doesn't seem totally out of question. If your talents lean more toward fund-raising than coding this is certainly a viable strategy for you. Just another option. Griping has traditionally not accomplished anything. Document your problems specifically, fix them, or encourage others to fix them for you. -Steve