Date: Fri, 19 Sep 2008 19:38:32 -0700 From: Jo Rhett <jrhett@netconsonance.com> To: Aragon Gouveia <aragon@phat.za.net> Cc: freebsd-stable <freebsd-stable@FreeBSD.org> Subject: Re: Upcoming Releases Schedule... Message-ID: <851F09A2-788D-4343-9E00-A0AB5C3AC063@netconsonance.com> In-Reply-To: <20080920020703.GA82392@phat.za.net> References: <alpine.BSF.1.10.0809162043380.64176@fledge.watson.org> <0C2C7E9B-61E3-4720-B76F-4745A3C963DA@netconsonance.com> <alpine.BSF.1.10.0809180022580.13100@fledge.watson.org> <658B8861-1E78-4767-8D3D-8B79CC0BD45F@netconsonance.com> <alpine.BSF.1.10.0809181935540.16464@fledge.watson.org> <15F15FD1-3C53-4018-8792-BC63289DC4C2@netconsonance.com> <448wtpcikb.fsf@be-well.ilk.org> <C096D142-4572-48DF-8CCA-053B41003A07@netconsonance.com> <alpine.BSF.1.10.0809191158330.40909@fledge.watson.org> <34C3D54B-C88C-4C36-B1FE-C07FC27F8CB5@netconsonance.com> <20080920020703.GA82392@phat.za.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?851F09A2-788D-4343-9E00-A0AB5C3AC063>