While conceptually, I think that BlazeDS would fit within a project outside 
ApacheFlex, in a practical way, until not having much commiters, etc ..., it 
should have its place in ApacheFlex until there is enough community interest 
and we stand ready to make a full project of it, the risk, otherwise, is not to 
have the upper hand on it.
It is widely used at entreprise level, especially with spring-flex, and even 
more than that, the big companies would like to have an commercial enterprise 
support on it, since Adobe decided to stop offering it for two years now if I 
remember well, today, only Farata Systems provides a such support if I'm still 
up to date,  maybe it would be appropriate that they be part of this 
discussion. 
Frédéric Thomas

> Date: Sat, 7 Jan 2012 18:37:28 -0700
> Subject: Re: BlazeDS
> From: dougart...@gmail.com
> To: flex-dev@incubator.apache.org
> 
> I am willing to be an initial committer for this effort.
> On Jan 7, 2012 2:52 PM, "Anne Kathrine Petterøe" <yoji...@gmail.com> wrote:
> 
> > On 7 January 2012 20:54, Alex Harui <aha...@adobe.com> wrote:
> >
> > >> there someone championing the project at ASF?
> > > Are you volunteering to be champion?
> >
> > I cannot champion a project because I am not an officer or a member of ASF
> > [1]
> >
> >
> > > I guess some folks are willing to work on it, but what needs to be done
> > to
> > > it?  And does it matter to Apache if it only needs a few minor tweaks and
> > > isn't very active?
> >
> > To graduate from incubation the project needs, among others, to show
> > that it has an active community. (this doesn't have to consist of
> > committers only) [2]
> >
> >
> > I would suggest finding out first if there are any initial committers.
> > Without it a core development team, I cannot see how Blaze DS would
> > survive.
> >
> >
> > /Anne
> >
> > [1]
> > http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Champion
> > [2] http://incubator.apache.org/guides/proposal.html#template-community
> >
                                          

Reply via email to