atom feed16 messages in org.apache.incubator.sling-devRe: [RT] Shall we merge microsling in...
FromSent OnAttachments
Bertrand DelacretazDec 17, 2007 1:33 am 
Carsten ZiegelerDec 17, 2007 1:54 am 
Torgeir VeimoDec 17, 2007 1:55 am 
Bertrand DelacretazDec 17, 2007 2:03 am 
Torgeir VeimoDec 17, 2007 2:14 am 
Karl PaulsDec 17, 2007 2:21 am 
Carsten ZiegelerDec 17, 2007 2:21 am 
pi...@wasabicowboy.comDec 17, 2007 8:34 am 
Felix MeschbergerDec 17, 2007 3:02 pm 
Padraic HannonDec 17, 2007 3:09 pm 
Felix MeschbergerDec 17, 2007 3:24 pm 
pi...@wasabicowboy.comDec 17, 2007 5:32 pm 
Bertrand DelacretazDec 18, 2007 5:03 am 
Bertrand DelacretazDec 18, 2007 5:07 am 
Felix MeschbergerDec 18, 2007 5:19 am 
Bertrand DelacretazDec 18, 2007 5:55 am 
Subject:Re: [RT] Shall we merge microsling into Sling?
From:Carsten Ziegeler (czie@apache.org)
Date:Dec 17, 2007 1:54:22 am
List:org.apache.incubator.sling-dev

+1 - Funny, I didn't read ths mail before I send mine (I spent the whole weeking drafting it and now Bertrand beat me by ten minutes...)

Carsten

Bertrand Delacretaz wrote:

Hi,

I think microsling is now ready to become just a specific configuration of Sling.

That would save us the extra work (and potential community fragmentation) (and user indecision) (and fuzzy "marketing" message) that comes with having two similar-but-still-different codebases.

I'm pretty sure we can graft the microsling stuff on Sling as a set of OSGi bundles, without requiring any OSGi knowledge from beginners, and keep microsling's ease of use, all of microsling's current features, and the "testable in 15 minutes from scratch" requirement.

Empowering users to jump from simple microsling scripted stuff to full-blown OSGi-based java modules, within the same framework and webapp, sounds quite exciting to me.

WDYT?

-Bertrand, operating in Monday Morning's Wild Thinking Mode ;-)