incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raphaël Luta <>
Subject Re: ajax proposal?
Date Wed, 25 Jan 2006 08:24:24 GMT
Andrew Clark wrote:
> Raphaël Luta wrote:
>>- no source control access
> We have read-only CVS access[1] already for the entire
> project. The details should definitely be more visible,
> though. I'll talk to someone about getting it more
> prominent on the main site.

I missed the link. It should indeed be more visible :)

>>I understand that you wouldn't want to setup your own public
>>dev infrastructure but using, codehaus, tigris or
>>whatever public infra wouldn't have been very onerous.
>>My concern here is if no resources have been dedicated
>>so far to really build the AjaxTk into an OSS project why
>>would that change once it is in incubation ?
> Let me try to summarize what I think your point is and
> you can tell me if I'm wrong. You would feel better
> about the submission if it were already a fully formed
> OSS project on an external site with full development
> infrastructure and long-time active community. Is this
> accurate? 

The "long time active community" is not accurate and building
such a community is a main reason for the Incubator.

As far I can tell, what needs to happen to fully OSS AjaxTk
is something like this:
- cleanup the code/doc/install so that Tk can be consumed
  by a public community
- rework a clear internal separation  between AjaxTk and
  ZCS with different repos, dependency management, indep
  release cycle, and so on...
- adjust internal dev processes to deal with the public
  infra (and possibly some early external dev)
- start building a long term external community by
  actively attracting new committers

I would feel more comfortable if the first 3 steps would be
done somewhere else before any incubation starts so that
incubation can really focus on the last point.
Apache does not bring any value in the first 3 steps that you
can't bring by yourself as an ASF member and the amount of
work and risk of failure in those 3 first steps is IMO
The benefit of such a 2 step process is that this gives
you an actual public track record before incubation is
decided and voids most concerns about incubation being a pure
branding exercicse since a significant amount of work would
already have been spent in making the AjaxTk OSS independantly
of any Apache commitment.

Raphaël Luta -
Apache Portals - Enterprise Portal in Java

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message