Hi Oliver, Indeed Adobe hosts multiple open-source projects in various locations. Nevertheless, Adobe is also committed to the projects it started at Apache Software Foundation through Day Software, and also after the acquisition of Day (see Apache DeviceMap, Apache Cordova, Apache Flex, etc.).
Given the fact that Sightly was built for AEM and also that some of its language features were built with Sling in mind1) it only makes sense for us to contribute the Java implementation, currently tied to the dynamic classloader from Sling and to the resource and servlets API, to Apache Sling. If we manage to build a community around Sightly itself, and that community would want Sightly to be decoupled from Apache Sling, nothing stops us from creating a Sightly top-level project, as mentioned in the previous emails. Like Robert and Bertrand said in this thread, we're currently trying to build a community for Sightly where it makes most sense now and we believe that this place is Apache Sling, one of the core open-source project on top of which we build AEM. Thanks, Radu 1) see data-sly-resource and data-sly-include; however these concepts, although not named the same, exist in other web frameworks as well: Django, Struts 2 On Thu, Oct 23, 2014 at 4:12 PM, Robert Munteanu <[email protected]> wrote: > On Thu, Oct 23, 2014 at 4:01 PM, Oliver Lietz <[email protected]> > wrote: > > On Monday 29 September 2014 10:58:05 Radu Cotescu wrote: > >> Hi Oliver, > > > > Hi Radu, > > > >> As Bertrand said in his reply in this thread, we haven't seen much > interest > >> in Sightly beyond Sling / AEM users. While there are two plugins that > hint > >> at Sling specifics (data-sly-resource / data-sly-include) we actually > think > >> that these functionalities exist in various other web frameworks, under > >> different names: > >> > >> * data-sly-resource merely includes a resource from somewhere in your > web > >> app > >> * data-sly-include provides a way to render a part of the output with a > >> different view / controller combo in the context of the current request > >> > >> If in the future we see the interest of Sightly increasing outside of > the > >> Sling / AEM community we can always start a new project under the ASF > >> umbrella and then provide a bridge for Sling. > > Let me rephrase and expand on that a little bit, but through my > perception rather than Radu's. > > This will also be an exercise in community-building. I believe that > it's easier to focus attention of developers in both the consumer and > contributor role to Sling and Sightly by putting them under the same > umbrella rather than by keeping them apart. > > Once Sightly attracts enough attention it can move to another location > if that's beneficial to the project. But I don't think that a > scripting language tied deeply as an implementation to Sling and JCR > should live outside Sling from the beginning. > > Well, maybe someone will be interested enough to decouple Sightly from > JCR and from Sling and make it usable as a standalone project. But for > that we need contributors ( see my second paragraph :-) ). > > So IMO the best location for Sightly is Sling and we should accept the > donation as it was made. > > Cheers, > > Robert > > >> > >> The specification will be hosted at > >> https://github.com/Adobe-Marketing-Cloud in a few days. > >> > >> BTW, Brackets is an open-source code editor so it has nothing to do with > >> Sightly, except for the fact that we've also developed an extension for > it > >> to ease web app development with Sightly in AEM. > > > > sure, Brackets and Topcoat are just examples for Adobe hosting open > source web > > projects on top level. > > > > Regards, > > O. > > > >> Cheers, > >> Radu > >> > >> On Sat, Sep 27, 2014 at 3:23 PM, Oliver Lietz <[email protected]> > wrote: > >> > Good to see one more modern alternative to JSP and ESP, welcome > Sightly! > >> > > >> > The open-sourcing is really an important step in the right direction, > but > >> > I think there are better places for Sightly as template language. > >> > Do not tie Sightly to close to Sling (AEM) when it could also be > useful > >> > for others in different projects and environments and prevent its > >> > proliferation unnecessarily. > >> > > >> > A templating language/engine like Sightly could reach momentum like > >> > Angular, > >> > Bootstrap, Font Awesome, Markdown or Brackets. > >> > > >> > Adobe has already some places where they host successful open-source > web- > >> > related projects, e.g.: > >> > http://html.adobe.com/opensource/ > >> > https://github.com/adobe > >> > https://github.com/adobe-webplatform > >> > http://brackets.io > >> > http://topcoat.io > >> > > >> > So +1 for hosting the integration but -1 for hosting the language > >> > implementation. Which clearly means +1 for Sightly in general. >
