On Wednesday, July 18, 2001, at 03:33 PM, Jason van Zyl wrote:
>
> <cut>
>
> I would like to see all projects use the TDK than we have a single
> well defined development model. When the model is improved all turbine
> projects benefit. The TDK should allow the CVS setup to be simple for
> a project and allow developers to work directly with what's in cvs and
> not have to copy anything like templates in order to test. The TDK
> will manage the complexity. The TDK will provide migration strategies,
> a testing framework for apps, a benchmarking suite and deployment
> strategies. With a TDK like this there will be no benefit for a single
> project to try and duplicate anything the TDK does.
>
So the TDK will become an aggregation of all of the old parts of Turbine
that are being broken apart currently (turbine, torque, services, etc)
and then the example app will be built on top of that?
I think that if this is the case and applications such as Tambora,
Jetspeed, and Scarab are going to move to being built on top of the TDK
and the services provided by it, instead of building upon straight
Turbine, then the example app should be broken out into it's own
repository when the time is right and we actually have two questions
here.
1. What generic set of services should be provided by the TDK for apps
to build upon?
2. What do we want to do to the example app to make it more relevant
for people evaluating Turbine as a possible solution and what should
added to show off more of Turbine's features to these people?
Am I correct in my understanding here?
----------------------------------
Kurt Schrader
[EMAIL PROTECTED]
http://www.kurtschrader.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
