I definitly agree, although I know that Scarab is closing in on it's 1.0
version, and swapping over to Summit at the last moment might not be a good
idea!

However, that is not to say I am not in favor of Summit.  I think any
movement is better then no movement, and I am ready for Turbine to move
forward after sitting at 2.2 forever.

I am definitly +1 in favor of Summit, and just wish that it would become 4.0
or 3.5 sooner versus later.  I will be building from scratch a new Turbine
app in a month or so, and I would really rather base it on Summit versus
T2.2 or T3.  I have looked at the internals of Turbine, and I agree, it is
horribly difficult to figure out...  And please, give me a pluggable Turbine
User and Security ;-) !

When the march to Summit is a go, I would be more then willing to help out
if some of the more experienced developers could put together a todo list..

Eric

-----Original Message-----
From: Stephen Haberman [mailto:stephenh@;chase3000.com]
Sent: Thursday, October 31, 2002 2:33 PM
To: 'Turbine Developers List'
Subject: RE: Turbine community contributions


> I don't know about having one version right now...  Since I use Scarab
at
> work, that is running under version 3.0.  And since Scarab seems
pretty full
> fledged ;-), I would say that if it is good enough for Scarab, then it
is
> good enough for me.

I'd thought the same thing for awhile. And I do think it's great that
Turbine was a sort of poster child that some of the Turbine developers
work on to showcase the technology and keep development active and what
not.

But just because Scarab uses T3 doesn't mean T3 is a good code base (not
that it's bad, but in comparison to Summit) and should be released.

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.

- Stephen



--
To unsubscribe, e-mail:
<mailto:turbine-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail:
<mailto:turbine-dev-help@;jakarta.apache.org>

Reply via email to