RE: Turbine community contributions

[Stephen Haberman <st...@chase3000.com>]

> > I'd venture to say that Scarab could/should be easily ported to
Summit,
> > assuming Summit becomes T3/T4, as Turbine is just a framework that
sits
> > above the actions/templates and handles hooking them together
(Fulcrum
> > aside). As long as Summit does things the same way, albeit much
cleaner
> > internally, and Plexus can handle Fulcrum services with little
> > modification, I see little reason for not moving to the new Summit
code
> > base and letting T3 stay at alpha.
>
> I guess that's easy enough to say when you don't have products based
> on the code.  However, that is unreasonable without an existing
> replacement in Apache CVS.

True. I wasn't saying Scarab should immediately port to Summit (e.g.
pre-1.0 or what not); sorry if I implied otherwise. I was just saying
two things:

1) Just because Scarab and a few other web apps use T3 alpha doesn't
mean it should be suddenly decided that it's release quality and labeled
as T3.0 release. This would be a disservice to future users thinking
that it'll be maintained and what not.

I think it should be held at alpha and pretty much not mentioned on the
website once T4 comes along. If the other apps want to stick with T3
alpha, that's just fine, but it should be just that, T3 alpha.

(Now that I think about, no one specially said that T3 alpha should be
made T3.0, I just was responding to Eric's comments as I used to share
his view towards Scarab's use of Turbine technology and had sense
changed my mind, so thought I'd express my opinion)

2) Perhaps I'm showing the naivety of my knowledge of the Scarab code
base, but my, again, naïve, impression is that you don't tightly
integrate with T3 alpha. Perhaps you have a custom pipeline?, and of
course some Fulcrum services. But given that Summit is going to fairly
strictly mimic the T2/T3 module/action resolution, I don't see much that
would change.

Though I can imagine it would be tedious (e.g. changes to imports,
slightly renamed methods, etc.), I was just thinking that given that
Summit does the same thing T3 does, only cleaner, that Scarab shouldn't
have to be stuck with T3 alpha forever.

Oh, I liked the cheap version numbers thing. Having summit be T4 does
make sense.

- Stephen



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>