Shindig will develop a container and backend server components for hosting OpenSocial applications.
A social application, in this context, is an application run by a third party provider and embedded in a web page, or web application, which consumes services provided by the container and by the application host. This is very similar to Portal/Portlet technology, but is based on client-side compositing, rather than server.
Shindig will provide implementations of an emerging set of APIs for client-side composited web applications. The Apache Software Foundation has proven to have developed a strong system and set of mores for building community-centric, open standards based systems with a wide variety of participants.
A robust, community-developed implementation of these APIs will encourage compatibility between service providers, ensure an excellent implementation is available to everyone, and enable faster and easier application development for users.
The Apache Software Foundation has proven it is the best place for this type of open development.
The Shindig OpenSocial implementation will be able to serve as a reference implementation of the standard.
This is a new project.
The initial developers are very familiar with meritocratic open source development, both at Apache and elsewhere. Apache was chosen specifically because the initial developers want to encourage this style of development for the project.
Shindig seeks to develop developer and user communities during incubation.
The initial set of committers includes folks from several commercial OpenSocial container providers, including Ning, Google, Hi5, and MySpace. We have varying degrees of experience with Apache-style open source development, ranging from none to ASF Members.
The developers of Shindig want to work with the Apache Software Foundation specifically because Apache has proven to provide a strong foundation and set of practices for developing standards-based infrastructure and server components.
Shindig is new development of an emerging set of APIs.
Inexperience with Open Source
The initial developers include long-time open source developers, including Apache Members.
The initial set of developers is diverse, but are all employed by OpenSocial container providers. Building a more diverse developer community is a high priority for this project.
Reliance on Salaried Developers
The initial group of developers are all employed by potential consumers of the project. Remedying this is a large part of why we want to bring the project to Apache.
Relationships with Other Apache Products
None in particular.
A Excessive Fascination with the Apache Brand
We believe in the processes, systems, and framework Apache has put in place. The brand is nice, but is not why we wish to come to Apache.
Google's OpenSocial Documentation:
Ning's OpenSocial Documentation:
The initial code relies on PHP and the jQuery library.
Developer and user mailing lists
A subversion repository
A JIRA issue tracker
- Andy Smith (Google)
Brian McCallister (Ning)
- Brian Stoler (Google)
- Cassie Doll (Google)
- Dan Bentley (Google)
Dan Farino (MySpace)
- David Glazer (Google)
- David Harkness (Google)
- Diego Doval (Ning)
- Doug Coker (Google)
- Evan Gilbert (Google)
- Graham Spencer (Google)
- Jeffrey Regan (Google)
- John Hjelmstad (Google)
- John Panzer (Google)
- Jun Yang (Google)
- Jussi Myllymaki (Google)
- Kevin Brown (Google)
- Martin Traverso (Ning)
- Paul Lindner (Hi5)
- Ramkumar Ramani (Google)
- Thomas Baker (Ning)
- Thomas Dudziak (Ning)
- Tim Williamson (Ning)
- Zhen Wang (Google)
* Brian McCallister
- Thomas Dudziak
- Brian Fitzpatrick
- Santiago Gala
- Greg Stein
- Sylvain Wallez
The Apache Incubator.