From owner-freebsd-stable@FreeBSD.ORG Sat Sep 20 02:07:05 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7B0401065670 for ; Sat, 20 Sep 2008 02:07:05 +0000 (UTC) (envelope-from aragon@phat.za.net) Received: from mail.geek.sh (decoder.geek.sh [196.36.198.81]) by mx1.freebsd.org (Postfix) with ESMTP id 14F298FC08 for ; Sat, 20 Sep 2008 02:07:05 +0000 (UTC) (envelope-from aragon@phat.za.net) Received: by mail.geek.sh (Postfix, from userid 1000) id 9C66F24D22; Sat, 20 Sep 2008 04:07:03 +0200 (SAST) Date: Sat, 20 Sep 2008 04:07:03 +0200 From: Aragon Gouveia To: Jo Rhett Message-ID: <20080920020703.GA82392@phat.za.net> References: <0C2C7E9B-61E3-4720-B76F-4745A3C963DA@netconsonance.com> <658B8861-1E78-4767-8D3D-8B79CC0BD45F@netconsonance.com> <15F15FD1-3C53-4018-8792-BC63289DC4C2@netconsonance.com> <448wtpcikb.fsf@be-well.ilk.org> <34C3D54B-C88C-4C36-B1FE-C07FC27F8CB5@netconsonance.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <34C3D54B-C88C-4C36-B1FE-C07FC27F8CB5@netconsonance.com> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 4.10-RELEASE-p2 i386 Cc: freebsd-stable Subject: Re: Upcoming Releases Schedule... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Sep 2008 02:07:05 -0000 >From what I've gathered so far... | By Jo Rhett | [ 2008-09-20 02:46 +0200 ] > To get a business to commit resources to a project there must be an > actual goal. [1] The FreeBSD project would have to commit resources too. Its community that provides those resources need to see tangible work that is useful to the project before committing any resources to it. > And to reach that actual goal there must be both (a) a > plan to get there, (b) a reasoned assessment of the effort involved, > etc etc and (z) the effort taking place to reach that goal. For (a), (b), and (z), this is where you come in. Define the goal. Make a plan to get there. Assess the effort involved. Convince your employer that (a), (b) and (z) is worth it to him/her and that the result of (z) will convince the FreeBSD project to commit the resources needed to integrate it. If they're happy, start working on (z) and bring it to the FreeBSD project when you think it's ready. If the FreeBSD project has to be involved in (a), (b), or (z), it will have to commit its own resources to the effort. See [1]. Just my humble observation as a fellow FreeBSD user... Regards, Aragon