Our contrib is not "stopped" and from what I've seen, qooxdoo team is not slow 
at all.
I would say qooxdoo support and community is really quick compared to other 
framework or product I've used or tried.

For the need of our contribution I'm in direct contact with someone in the 
qooxdoo team and, please, let us manage it without trying to interfere or 
deduce things you don't know.

I replied to your initial message because I think our contribution can be 
useful and I also answer that I don't have answer about any delay because it is 
not in our hand currently (we're waiting for a legal answer).
Note that I never express anything about qooxdoo team.
All I said is :
"
About the delay, I have no idea, so I'll use that email to ask the question to 
qooxdoo team : any news ?

If it take too long, I can give you the code via email as I already did it for 
Petr.
The license is LGPL/EPL but I'd love to provide it also under Apache (that 
triple licenses look like possible).
"

As I did for Petr, I can send that contrib to you by email.
Send me a private email and write that you are OK for a LGPL/EPL/Apache license 
and I'll send back the contrib as soon as I packaged it :-)

JBB.

On Apr 27, 2010, at 12:21 , Stefan Andersson wrote:

> Qooxdoo team, which I do not think is slow, but has in this item not reacted 
> yet, when can we checkout the contribution of Jean-Baptiste et al? Why has it 
> been stopped?
> 
> Let loose the power of the community!
> 
> Stefan
> 
> Hotmail: Trusted email with Microsoft’s powerful SPAM protection. Sign up 
> now. 
> ------------------------------------------------------------------------------
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

------------------------------------------------------------------------------
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to