From owner-freebsd-stable@FreeBSD.ORG Sat Sep 20 02:39:20 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 A236C1065675 for ; Sat, 20 Sep 2008 02:39:20 +0000 (UTC) (envelope-from jrhett@netconsonance.com) Received: from mail.netconsonance.com (mail.netconsonance.com [198.207.204.4]) by mx1.freebsd.org (Postfix) with ESMTP id 84ED88FC26 for ; Sat, 20 Sep 2008 02:39:20 +0000 (UTC) (envelope-from jrhett@netconsonance.com) Received: from [172.16.12.8] (covad-jrhett.meer.net [209.157.140.144]) (authenticated bits=0) by mail.netconsonance.com (8.14.1/8.14.1) with ESMTP id m8K2cWcK052565; Fri, 19 Sep 2008 19:38:32 -0700 (PDT) (envelope-from jrhett@netconsonance.com) X-Virus-Scanned: amavisd-new at netconsonance.com X-Spam-Flag: NO X-Spam-Score: -2.413 X-Spam-Level: X-Spam-Status: No, score=-2.413 tagged_above=-999 required=3.5 tests=[ALL_TRUSTED=-1.44, AWL=-0.973] Message-Id: <851F09A2-788D-4343-9E00-A0AB5C3AC063@netconsonance.com> From: Jo Rhett To: Aragon Gouveia In-Reply-To: <20080920020703.GA82392@phat.za.net> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v928.1) Date: Fri, 19 Sep 2008 19:38:32 -0700 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> <20080920020703.GA82392@phat.za.net> X-Mailer: Apple Mail (2.928.1) 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:39:20 -0000 On Sep 19, 2008, at 7:07 PM, Aragon Gouveia wrote: >> 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 Of course. This is what the requirements analysis is ;-) > 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. Of course. If this was something that could be done without working with the freebsd developers, do you think I would put up with this kind of abuse? I'd much rather have something I could just go and do ;-) The issue is that nobody is willing to answer the question: "what resources are too limited to provide longer support? How can we help?" This the elephant that everyone ignores. To develop a plan, you need to know the limitations. Once those are spelled out, you sit down and try to determine what resources are necessary to achieve a certain goal. Then you find those resources, etc etc... Without input from the current release team extending the support schedule is not possible. -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness