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 ;-)
