Date: Tue, 19 Mar 2024 13:26:38 +0000 (UTC) Message-ID: <527694702.57071.1710854798019@cwiki-he-fi.apache.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_57070_1187125971.1710854798019" ------=_Part_57070_1187125971.1710854798019 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Although Sling is a relatively young project, only recently graduated fr= om the incubator, it already has a growing following of adopters. This page= lists those adopters (or at least those that agree to be listed).
Being on the community wiki, if you are using Sling and your not listed = here, please add yourself with a brief description of your project and how = you have adopted Sling.
The Sakai project is a project that was started in 2004 funded by a rese= arch grant from the Andrew Mellon Foundation. Its aim was to create an= open source collaborative environment to support teaching and learning and= research within Higher Education. The initial project members were Stanfor= d University, University of Michigan, Indiana University and the Massachuse= tts Institute of Technology. These four were rapidly joined my many other i= nstitutions growing to over 160 Universities running Sakai in production to= day. The project funding has come to an end and sustainability has been ach= ieved as a result of community contributions.
The University of Cambridge (UK) was one of the early adopters and rapid= ly became involved in shaping the core of Sakai. In early 2008, shortly aft= er Google made its OpenSocial announcement a decision was made to re-archit= ect Sakai to be more user focused and socially aware, building on the colla= borative experiences seen in networks like Ning and Facebook. After a perio= d of evaluation Sakai chose Sling as its core technology partly because it = had the solid backing of the Apache Foundation, but also because it was bas= ed on OSGi for componentised development, solid REST semantics and a solid = JCR production backend in Apache Jackrabbit.
This adoption has had a huge impact on the Sakai code base. Although the= core development is not complete, Sakai's line count has dropped from abou= t 1.8M lines of code to about 200K as Sling has replaced many of modules th= at satisfied the Enterprise Content Management use cases. As a result, the = code quality, scalability and performance have all risen whilst the memory = footprint of production JVM's has halved. Perhaps the most startling impact= has been the new ease with which UX designers and UI developers are able t= o work with the framework, where previously the Java web environment had pr= ecluded a UX/UI driven rapid development cycle.
Sakai 3 based on Sling will be going into production at the University o= f Cambridge by December 2009, with a number of other early adopters. For mo= re information see an early screencast or look at the project site (frontend, backend) or live demo
License: ECL2/Apache2
Sling started as an internal project at Day Software, and has been contr= ibuted to the Apache Incubator in September 2007. It can be considered an i= mportant part of Day's software stack, and was open-sourced to make the tec= hnical innovations contained therein available to the public.
Sling powers Day's entire CQ5 family of content management products= (Web Content Management, Social Collaboration, Digital Asset Management), = and is included in Day's CRX content repository, which is itself based on <= a class=3D"external-link" href=3D"http://jackrabbit.apache.org" rel=3D"nofo= llow">Jackrabbit.
Quite a few high profile mission critical websites are powered by CQ5 - = Day's customer list mentions some of them. Day's websit= e runs on CQ5/Sling as well.
CQ5 has been very well received by the press and by analysts, and Sling = has played a major part in this success, by enabling the CQ5 development te= am to create robust and higly modularized software very efficiently.
License: Commercial product
The TB project is dev= eloped by Tibtec, a nonprofit techno= logy center based in Dharamsala (India) that helps the Tibetan community in= harnessing modern technologies to help the community. The aim of the proje= ct is to build a system to monitor the tuberculosis among tibetan communiti= es in India, Nepal and Bhutan. Thanks to technology advances in mobile and = web computing, it is now possible to design a recording and reporting web p= ortal supporting the WHO DOTS protocol.
The project of monitoring the tuberculosis among tibetan commu= nities in India was born 1 year ago thanks to four actors: the DoH (Department of Health, Tibetan Government = in Exile), Tibetan Delek Hospital (Gangchen Kyishong - India), AISPO (Italian Association for Solidarity Of Per= sons), and the Johns Hopkins University<= /a> (USA). TibTec is working on a system for the above four actors to monit= or TB in the Tibetan communities living in India, Nepal and Bhutan.
The main goal of the project is to build a simple, low-cost and versatil= e framework so that communities all over the world could benefit from it. T= he system could be easily customized for other works as well since it based= on open source software.
There was a need to put in place a centralized solution (web portal) wit= h mobile data gathering (SMS) to understand and fight with more efficiency = against tuberculosis. The system also provides an information platform with= data analysis and management for medical staff and health workers. The sys= tem is capable to cope with electricity power cuts and IP network inaccessi= bility. Finally, a reminder system for taking drugs and/or coming to visit = doctors is available.
Technically, the solution consists in the implementation of a remote rep= ository that stores data related to the project (e.g. Doctors, Patient reco= rds, DOTS reports, etc.) and which is accessible via a mobile gateway (andr= oid-based) that send HTTP POST/GET requests to a RESTfull API of a web fram= ework (Apache Sling).
The system also implements Sling accessors to this remote repository: a = server for analyzing SMS running on an android phone and a website built wi= th a combination of server-side scripts in JSP and client-side script in Ja= vascript. Finally, the reminder service for patients is managed thanks to t= he Google Agenda reminders service that send reminders on phones at a speci= al date and hour through a gateway running on the android server to patient= s mobile phone.
Norwegian CMS vendor Idium is using Apache Sling for its Idium Web produ= ct. The product, available as a subscription service only, is aimed towards= small businesses, who need a simple way of setting up and managing their w= ebsite.
The product uses Sling and Dojo to create a very rich drag-and-drop inte= rface, where the user drags elements onto a webpage. Elements can be text, = image galleries, Google maps or other multimedia. The system also creates g= raphics and CSS dynamically, in order to provide consistent color and desig= n schemes, while being fully configurable.
Upon establishing this project, Idium evaluated several server-side fram= eworks. Sling was chosen for its RESTful interface to a hierarchy repositor= y, which proved to be a very good match for a web-based CMS.
License: SaaS only