On Sat, Aug 26, 2000 at 11:01:00PM -0500, Mike Haberman wrote:
> But I sincerely think that the interests of both WebMacro and
> Turbine/WebMacro user base will be best served if the two
> (Velocity & WebMacro) are united.
I think so too. And also my schedule over the past few months have
prevented me from working on Wm to the extent that I might have wanted
to. Therefore it's time to open it up to a more community level of
development anyawy.
I've already put it under an Apache license. The next step is to put
it on a more public CVS server and development environment. The Apache
Group would be a great place for it if it's welcome here.
Otherwise I can go to SourceForge or something.
> Justin has been saying about Velocity essentially only having
> a great parser, then not that much is lost by integrating the two.
If we act quickly that's pretty much true. The more development that
they do on Velocity, the less true this will become.
A possible roadmap is that Velocity can be WebMacro v2, and by putting
WM under the Apache tree it will be freed from the requirement of
being exactly compatible with WM.
I'm not sure whether that's viable. WM is pretty extensible and pretty
fast. But I'm throwing it out there.
> 2. Justin, concede all licensing issues to Jon.
Pretty much done now. The other issues are proejct management issues
and so forth.
> I'm sure your name will be listed as a major contributor.
Good enough.
> It's not like WebMacro's code base is a bunch of crap.
As it's author I will say I think WM's parser is a bunch of crap. It
works, and it supports the dynamically loaded syntax, but it certainly
has been the single largest source of bugs.
Above the parser interface the rest of the code has been pretty much
rock solid and is much faster than almost any other equivalent thing
out there now.
> If Velocity does stop WebMacro development, you/i/us will have
> a lot off pissed of managers/clients. But if we work together to
> actually give them an improved tool it gives us more ammunition.
Exactly. And I have some pretty big clients on the verge of adopting
WebMacro. Some of them big enough that it will be news that they
are even using Java.
WM is going to do well with or without Velocity, but it won't do as
well without as with. And Velocity won't do as well if it starts out
with a lot of animosity in the WM community.
Clearly we're better off together. Why have two Apache licensed tools
that do exactly the same thing?
Justin
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
