Return-Path: Delivered-To: apmail-myfaces-users-archive@www.apache.org Received: (qmail 78871 invoked from network); 4 Oct 2006 19:39:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 4 Oct 2006 19:39:40 -0000 Received: (qmail 48367 invoked by uid 500); 4 Oct 2006 19:39:35 -0000 Delivered-To: apmail-myfaces-users-archive@myfaces.apache.org Received: (qmail 48318 invoked by uid 500); 4 Oct 2006 19:39:35 -0000 Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Discussion" Delivered-To: mailing list users@myfaces.apache.org Received: (qmail 48307 invoked by uid 99); 4 Oct 2006 19:39:35 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Oct 2006 12:39:35 -0700 X-ASF-Spam-Status: No, hits=4.6 required=5.0 tests=DNS_FROM_RFC_POST,DNS_FROM_RFC_WHOIS,HTML_MESSAGE,MIME_BOUND_NEXTPART Received: from [204.127.192.83] ([204.127.192.83:58986] helo=rwcrmhc13.comcast.net) by idunn.apache.osuosl.org (ecelerity 2.1.1.8 r(12930)) with ESMTP id D5/42-20288-3FD04254 for ; Wed, 04 Oct 2006 12:39:32 -0700 Received: from rmailcenter88.comcast.net ([204.127.197.188]) by comcast.net (rwcrmhc13) with SMTP id <20061004193928m1300m2pq5e>; Wed, 4 Oct 2006 19:39:28 +0000 Received: from [165.127.77.148] by rmailcenter88.comcast.net; Wed, 04 Oct 2006 19:39:28 +0000 From: gvanmatre@comcast.net (Gary VanMatre) To: "MyFaces Discussion" Subject: Re: Corporate Open Source Strategy Date: Wed, 04 Oct 2006 19:39:28 +0000 Message-Id: <100420061939.27359.45240DF000016F4A00006ADF22092299270A9D9B0E03020E9009@comcast.net> X-Mailer: AT&T Message Center Version 1 (Apr 11 2006) X-Authenticated-Sender: Z3Zhbm1hdHJlQGNvbWNhc3QubmV0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="NextPart_Webmail_9m3u9jl4l_27359_1159990768_0" X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --NextPart_Webmail_9m3u9jl4l_27359_1159990768_0 Content-Type: text/plain Content-Transfer-Encoding: 8bit >From: "Ryan Wynn" > > Trying to get approval for a myfaces-shale stack in a corporate > environment and facing the question of what is the strategy for fixing > a production showstopper in the open source code. Anyone have any > recommendations on this topic? Or any links regarding the topic? > > Filing through JIRA does not seem to be an answer for these > emergencies because there is really no guarantee there? Especially > for previous versions. > > What is the protocol if say myfaces-1.1.1 src is modified? Is the > requirement the same that the fix needs to be looped back in? Or is > the policy different for older versions? > > Thanks for the consideration. Hey Ryan, you might talk to OpenLogic. They are making a business out of providing services for open source. They also offer packaging of open source products. The packaging also makes a point to define the open source license agreements. I believe their packaging product also allows you to create your own bundling. http://www.openlogic.com/index.php Gary --NextPart_Webmail_9m3u9jl4l_27359_1159990768_0 Content-Type: text/html Content-Transfer-Encoding: 8bit
>From: "Ryan Wynn" <bigwynnr@gmail.com>
>
> Trying to get approval for a myfaces-shale stack in a corporate
> environment and facing the question of what is the strategy for fixing
> a production showstopper in the open source code. Anyone have any
> recommendations on this topic? Or any links regarding the topic?
>
> Filing through JIRA does not seem to be an answer for these
> emergencies because there is really no guarantee there? Especially
> for previous versions.
>
> What is the protocol if say myfaces-1.1.1 src is modified? Is the
> requirement the same that the fix needs to be looped back in? Or is
> the policy different for older versions?
>
> Thanks for the consideration.
 
Hey Ryan, you might talk to OpenLogic.  They are making a business out of providing services for open source.  They also offer packaging of open source products.  The packaging also makes a point to define the open source license agreements.  I believe their packaging product also allows you to create your own bundling.
 
 
 
Gary
 
 
--NextPart_Webmail_9m3u9jl4l_27359_1159990768_0--