myfaces-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Galligan" <>
Subject Re: Corporate Open Source Strategy
Date Wed, 04 Oct 2006 18:02:12 GMT
In my personal experience, commercial support sounds nice, but you're
more likely to run into resistance and denail.  No offense to BEA, but
we had to figure out all sorts of problems with their app server and
workflow product, and then convince them of their problems, and
essentially code around them, in proudction no less.

There were times I would've begged to have been on an open source
platform.  I don't think non-tech corporate people understand the

Commercial support for myfaces doesn't seem like too bad of an idea.

On 10/4/06, Mike Kienenberger <> wrote:
> The best way to fix a showstopper in open source is to do it yourself
> and submit a patch back to the project :-)
> If you are asking if your local changes have to be submitted back to
> ASF, the answer is no.
> If you are asking what "guaranteed" support services are provided
> directly by ASF, the answer is none.   The project (and community
> support) is provided on a voluntary basis.
> is one possibility for obtaining commercial
> support for JSF and MyFaces if that's something you want to purchase.
>  A number of the MyFaces committers appear to do work for
> There is currently no process in place for fixing bugs on older
> release branches, although I'm hopeful that we will start doing so
> from 1.1.4 onward.
> On 10/4/06, Ryan Wynn <> wrote:
> > 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.
> >

View raw message