<snip/> > - Plexus is brought in and accepted by the community (and > ideally would have it's own community). Turbine is already > stretched thin with people working on Turbine/Torque/Fulcrum, > so without a new influx of developers, adding Plexus to the > mix would make things even more chaotic. > > Also note that, and I mean this with all due respect, from my > short time at Turbine, Jason is a revolutionary who likes to > pushing out new code to solve new and interesting problems. > This is great and results in some really cool applications, > e.g. Maven and Plexus. > > But at the same time, we need the support of our > evolutionaries, e.g. Henning and Martin, or bring in some > more evolutionaries (which I think is a great idea to ease > the load on Henning and Martin) to make sure that after Jason > has gone on to the next new project (which is perfectly fine, > I enjoy doing the same thing, only, unfortunately, to a more > frivolous extent, which is an attribute I'm working on), we > have people here in Turbine willing to maintain Plexus, > assuming it is donated.
If plexus is donated to the turbine project I will definitely volunteer to at least do a lot of testing and I will try to free up some spare time to also help with (evolutionary) development. I'm very interested in getting turbine Avalonized as quickly as possible. Big question: what happens to Summit ? Summit is Jason's next-generation Turbine core and I haven't really had time to look at it yet. Will we first try using Plexus with the turbine-2 code base in 2.3/2.4 or do we jump straight to Plexus/Summit as a fresh start ? I favour the first option because we have a lot of time invested in our Turbine 2.2/2.3-dev apps. I'm pretty sure I'm not the only one :) Age --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
