commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Madoni <>
Subject RE: [Jelly] Executable XML vs. Rich Configuration
Date Mon, 23 May 2005 18:01:38 GMT
"Marketing" to the tune of "It slices! It dices! It mows your lawn!"
certainly doesn't belong in OSS, which is one reason why folks gravitate
toward it, (i.e. to get away from all the marketing BS).

However, "Marketing" as in "OSS is a serious alternative and here's why", or
"this is an XML scripting engine, we believe you will benefit from it, and
here's why" is extremely important for OSS and for projects like Jelly. As
long as open-source remains focused on being an ideological statement
against the likes of Microsoft rather than maturing into a real alternative
that can speak corporate-ese, it won't fully realize its goal of
establishing OSS communities like Apache as the best source for useful and
reliable software. 

-----Original Message-----
From: Paul DeCoursey [] 
Sent: Sunday, May 22, 2005 6:37 PM
To: Jakarta Commons Users List
Subject: Re: [Jelly] Executable XML vs. Rich Configuration

I like the Jelly name as well.  I use it for all kinds of things, 
mostly scripting.  I can't say I have ever used it for configuration. 
As far as any sort of name change, I don't think it a good idea.  It 
may need better marketing, but does that even fit into the open source 


On May 21, 2005, at 12:52 AM, Hans Gilde wrote:

> My 2 cents: I got into Jelly as a framework for building Swing GUIs. 
> In this
> case, the Tag model works very well and the ability to implement the
> scripting is also extremely useful.
> Unfortunately, the company I did it for laid me off and I have to 
> start the
> whole framework from scratch if I want to publish it open source. 
> However, I
> find Jelly to be rather more than configuration... the name Jelly 
> really
> seems to fit for me.

To unsubscribe, e-mail:
For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message