You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Brian McCallister <br...@apache.org> on 2007/11/09 19:03:49 UTC
[PROPOSAL] Shindig, an OpenSocial Container
Shindig Proposal
--
= Abstract =
Shindig will develop the container and backend server components
for hosting OpenSocial applications.
= Proposal =
Shindig will develop a JavaScript container and implementations of
the backend APIs and proxy required for hosting OpenSocial applications.
= Background =
OpenSocial provides a common set of APIs for social applications
across multiple websites. With standard JavaScript and HTML,
developers can create social applications that use a social network's
friends and update feeds.
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.
More information can be found about OpenSocial at
http://code.google.com/apis/opensocial/
== Rationale ==
Shindig is an implementation 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.
= Current Status =
This is a new project.
= Meritocracy =
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.
=== Community ===
Shindig seeks to develop developer and user communities during
incubation.
= Core Developers =
The initial core developers are all Ning employees. We hope to
expand this very quickly.
= Alignment =
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.
= Known Risks =
== Orphaned products ==
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.
== Homogenous Developers ==
The initial group of developers is quite homogenous. Remedying this
is a large part of why we want to bring the project to Apache.
== Reliance on Salaried Developers ==
The initial group of developers are employed by a potential consumer
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, except that Apache HTTPD is the best place to
run PHP, which the server-side components Ning intends to donate
have been implemented in.
== 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.
= Documentation =
Google's OpenSocial Documentation:
http://code.google.com/apis/opensocial/
Ning's OpenSocial Documentation:
http://tinyurl.com/3y5ckx
= Initial Source =
Ning, Inc. intends to donate code based on their implementation of
OpenSocial. The backend systems will be replaced with more generic
equivalents in order to not bind the implementation to specifics
of the Ning platform.
This code will be extracted from Ning's internal development, and
has not been expanded on past the extraction. It will be provided
primarily as a starting place for a much more robust, community-
developed
implementation.
= External Dependencies =
The initial codebase relies on a library created by Google, Inc.,
and licensed under the Apache Software License, Version 2.0.
= Required Resources =
Developer and user mailing lists
A subversion repository
A JIRA issue tracker
= Initial Committers =
Thomas Baker <ba...@ninginc.com>
Tim Williamson <ti...@ninginc.com>
Brian McCallister <br...@apache.org>
Thomas Dudziak <to...@apache.org>
Martin Traverso <ma...@ning.com>
= Sponsors =
== Champion ==
Brian McCallister <br...@apache.org>
== Nominated Mentors ==
Brian McCallister <br...@apache.org>
Thomas Dudziak <to...@apache.org>
Santiago Gala <sg...@apache.org>
Upayavira <up...@apache.org>
== Sponsoring Entity ==
The Apache Incubator.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Shindig, an OpenSocial Container
Posted by Matthieu Riou <ma...@offthelip.org>.
Interesting project, there's not so many business specific containers
around, following its development is going to be fun.
Also could you add the proposal in the incubator wiki [1] with the others?
Just for reference/versioning purpose.
Thanks!
Matthieu
On Nov 9, 2007 10:03 AM, Brian McCallister <br...@apache.org> wrote:
> Shindig Proposal
> --
>
> = Abstract =
>
> Shindig will develop the container and backend server components
> for hosting OpenSocial applications.
>
> = Proposal =
>
> Shindig will develop a JavaScript container and implementations of
> the backend APIs and proxy required for hosting OpenSocial applications.
>
>
> = Background =
>
> OpenSocial provides a common set of APIs for social applications
> across multiple websites. With standard JavaScript and HTML,
> developers can create social applications that use a social network's
> friends and update feeds.
>
> 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.
>
> More information can be found about OpenSocial at
> http://code.google.com/apis/opensocial/
>
> == Rationale ==
>
> Shindig is an implementation 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.
>
>
> = Current Status =
>
> This is a new project.
>
> = Meritocracy =
>
> 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.
>
> === Community ===
>
> Shindig seeks to develop developer and user communities during
> incubation.
>
>
> = Core Developers =
>
> The initial core developers are all Ning employees. We hope to
> expand this very quickly.
>
> = Alignment =
>
> 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.
>
> = Known Risks =
>
> == Orphaned products ==
>
> 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.
>
> == Homogenous Developers ==
>
> The initial group of developers is quite homogenous. Remedying this
> is a large part of why we want to bring the project to Apache.
>
> == Reliance on Salaried Developers ==
>
> The initial group of developers are employed by a potential consumer
> 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, except that Apache HTTPD is the best place to
> run PHP, which the server-side components Ning intends to donate
> have been implemented in.
>
> == 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.
>
> = Documentation =
>
> Google's OpenSocial Documentation:
> http://code.google.com/apis/opensocial/
>
> Ning's OpenSocial Documentation:
> http://tinyurl.com/3y5ckx
>
> = Initial Source =
>
> Ning, Inc. intends to donate code based on their implementation of
> OpenSocial. The backend systems will be replaced with more generic
> equivalents in order to not bind the implementation to specifics
> of the Ning platform.
>
> This code will be extracted from Ning's internal development, and
> has not been expanded on past the extraction. It will be provided
> primarily as a starting place for a much more robust, community-
> developed
> implementation.
>
> = External Dependencies =
>
> The initial codebase relies on a library created by Google, Inc.,
> and licensed under the Apache Software License, Version 2.0.
>
> = Required Resources =
>
> Developer and user mailing lists
>
> A subversion repository
>
> A JIRA issue tracker
>
> = Initial Committers =
>
> Thomas Baker <ba...@ninginc.com>
> Tim Williamson <ti...@ninginc.com>
> Brian McCallister <br...@apache.org>
> Thomas Dudziak <to...@apache.org>
> Martin Traverso <ma...@ning.com>
>
> = Sponsors =
>
> == Champion ==
>
> Brian McCallister <br...@apache.org>
>
> == Nominated Mentors ==
>
> Brian McCallister <br...@apache.org>
> Thomas Dudziak <to...@apache.org>
> Santiago Gala <sg...@apache.org>
> Upayavira <up...@apache.org>
>
> == Sponsoring Entity ==
>
> The Apache Incubator.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: [PROPOSAL] Shindig, an OpenSocial Container
Posted by Bertrand Delacretaz <bd...@apache.org>.
On 11/9/07, Brian McCallister <br...@apache.org> wrote:
> Shindig Proposal...
+1
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Shindig, an OpenSocial Container
Posted by Eelco Hillenius <ee...@gmail.com>.
+1
Eelco
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Shindig, an OpenSocial Container
Posted by Martijn Dashorst <ma...@gmail.com>.
Sounds like a nice addition with a lot of interest. Love the name btw.
+1
Martijn
On 11/9/07, Brian McCallister <br...@apache.org> wrote:
> Shindig Proposal
> --
>
> = Abstract =
>
> Shindig will develop the container and backend server components
> for hosting OpenSocial applications.
>
> = Proposal =
>
> Shindig will develop a JavaScript container and implementations of
> the backend APIs and proxy required for hosting OpenSocial applications.
>
>
> = Background =
>
> OpenSocial provides a common set of APIs for social applications
> across multiple websites. With standard JavaScript and HTML,
> developers can create social applications that use a social network's
> friends and update feeds.
>
> 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.
>
> More information can be found about OpenSocial at
> http://code.google.com/apis/opensocial/
>
> == Rationale ==
>
> Shindig is an implementation 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.
>
>
> = Current Status =
>
> This is a new project.
>
> = Meritocracy =
>
> 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.
>
> === Community ===
>
> Shindig seeks to develop developer and user communities during
> incubation.
>
>
> = Core Developers =
>
> The initial core developers are all Ning employees. We hope to
> expand this very quickly.
>
> = Alignment =
>
> 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.
>
> = Known Risks =
>
> == Orphaned products ==
>
> 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.
>
> == Homogenous Developers ==
>
> The initial group of developers is quite homogenous. Remedying this
> is a large part of why we want to bring the project to Apache.
>
> == Reliance on Salaried Developers ==
>
> The initial group of developers are employed by a potential consumer
> 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, except that Apache HTTPD is the best place to
> run PHP, which the server-side components Ning intends to donate
> have been implemented in.
>
> == 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.
>
> = Documentation =
>
> Google's OpenSocial Documentation:
> http://code.google.com/apis/opensocial/
>
> Ning's OpenSocial Documentation:
> http://tinyurl.com/3y5ckx
>
> = Initial Source =
>
> Ning, Inc. intends to donate code based on their implementation of
> OpenSocial. The backend systems will be replaced with more generic
> equivalents in order to not bind the implementation to specifics
> of the Ning platform.
>
> This code will be extracted from Ning's internal development, and
> has not been expanded on past the extraction. It will be provided
> primarily as a starting place for a much more robust, community-
> developed
> implementation.
>
> = External Dependencies =
>
> The initial codebase relies on a library created by Google, Inc.,
> and licensed under the Apache Software License, Version 2.0.
>
> = Required Resources =
>
> Developer and user mailing lists
>
> A subversion repository
>
> A JIRA issue tracker
>
> = Initial Committers =
>
> Thomas Baker <ba...@ninginc.com>
> Tim Williamson <ti...@ninginc.com>
> Brian McCallister <br...@apache.org>
> Thomas Dudziak <to...@apache.org>
> Martin Traverso <ma...@ning.com>
>
> = Sponsors =
>
> == Champion ==
>
> Brian McCallister <br...@apache.org>
>
> == Nominated Mentors ==
>
> Brian McCallister <br...@apache.org>
> Thomas Dudziak <to...@apache.org>
> Santiago Gala <sg...@apache.org>
> Upayavira <up...@apache.org>
>
> == Sponsoring Entity ==
>
> The Apache Incubator.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-beta4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta4/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Shindig, an OpenSocial Container
Posted by Brian McCallister <br...@apache.org>.
On Nov 9, 2007, at 11:47 AM, Leo Simons wrote:
> Can we see a code dump of the stuff you'll be donating?
As soon as possible :-) I am home with a nasty fever today so...
blech. We should have the ning-specific stuff gutted out by ApacheCon
at least!
-Brian
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Shindig, an OpenSocial Container
Posted by Leo Simons <ma...@leosimons.com>.
yay! Looks good.
On Nov 9, 2007, at 7:03 PM, Brian McCallister wrote:
> The initial core developers are all Ning employees. We hope to
> expand this very quickly.
Given how new this area is, and how much buzz OpenSocial seems to be
gathering atm, you can probably count on quite a bit of interest,
especially if there's any kind of press/blogbomb associated. It's
proven quite difficult to balance all that out with the average
incubation process, which tends to go a bit slower than the buzz
desires. It seems like a difficult balancing act.
> = External Dependencies =
>
> The initial codebase relies on a library created by Google, Inc.,
> and licensed under the Apache Software License, Version 2.0.
Can we see a code dump of the stuff you'll be donating?
cheers!
- Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Shindig, an OpenSocial Container
Posted by Brian McCallister <br...@apache.org>.
I'll update the proposal for changes from the discussion thus far and
bing it to a vote ASAP.
Meanwhile, initial (and gnarly, following bad is good for open
source ;-) seeder code:
http://people.apache.org/~brianm/shindig.tgz
-Brian
On Nov 9, 2007, at 10:03 AM, Brian McCallister wrote:
> Shindig Proposal
> --
>
> = Abstract =
>
> Shindig will develop the container and backend server components
> for hosting OpenSocial applications.
>
> = Proposal =
>
> Shindig will develop a JavaScript container and implementations of
> the backend APIs and proxy required for hosting OpenSocial
> applications.
>
>
> = Background =
>
> OpenSocial provides a common set of APIs for social applications
> across multiple websites. With standard JavaScript and HTML,
> developers can create social applications that use a social network's
> friends and update feeds.
>
> 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.
>
> More information can be found about OpenSocial at
> http://code.google.com/apis/opensocial/
>
> == Rationale ==
>
> Shindig is an implementation 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.
>
>
> = Current Status =
>
> This is a new project.
>
> = Meritocracy =
>
> 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.
>
> === Community ===
>
> Shindig seeks to develop developer and user communities during
> incubation.
>
>
> = Core Developers =
>
> The initial core developers are all Ning employees. We hope to
> expand this very quickly.
>
> = Alignment =
>
> 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.
>
> = Known Risks =
>
> == Orphaned products ==
>
> 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.
>
> == Homogenous Developers ==
>
> The initial group of developers is quite homogenous. Remedying this
> is a large part of why we want to bring the project to Apache.
>
> == Reliance on Salaried Developers ==
>
> The initial group of developers are employed by a potential consumer
> 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, except that Apache HTTPD is the best place to
> run PHP, which the server-side components Ning intends to donate
> have been implemented in.
>
> == 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.
>
> = Documentation =
>
> Google's OpenSocial Documentation:
> http://code.google.com/apis/opensocial/
>
> Ning's OpenSocial Documentation:
> http://tinyurl.com/3y5ckx
>
> = Initial Source =
>
> Ning, Inc. intends to donate code based on their implementation of
> OpenSocial. The backend systems will be replaced with more generic
> equivalents in order to not bind the implementation to specifics
> of the Ning platform.
>
> This code will be extracted from Ning's internal development, and
> has not been expanded on past the extraction. It will be provided
> primarily as a starting place for a much more robust, community-
> developed
> implementation.
>
> = External Dependencies =
>
> The initial codebase relies on a library created by Google, Inc.,
> and licensed under the Apache Software License, Version 2.0.
>
> = Required Resources =
>
> Developer and user mailing lists
>
> A subversion repository
>
> A JIRA issue tracker
>
> = Initial Committers =
>
> Thomas Baker <ba...@ninginc.com>
> Tim Williamson <ti...@ninginc.com>
> Brian McCallister <br...@apache.org>
> Thomas Dudziak <to...@apache.org>
> Martin Traverso <ma...@ning.com>
>
> = Sponsors =
>
> == Champion ==
>
> Brian McCallister <br...@apache.org>
>
> == Nominated Mentors ==
>
> Brian McCallister <br...@apache.org>
> Thomas Dudziak <to...@apache.org>
> Santiago Gala <sg...@apache.org>
> Upayavira <up...@apache.org>
>
> == Sponsoring Entity ==
>
> The Apache Incubator.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Shindig, an OpenSocial Container
Posted by Eddie O'Neil <ek...@gmail.com>.
+1 -- cool project and great name!
On Nov 11, 2007 12:57 PM, Brett Porter <br...@gmail.com> wrote:
> +1
>
>
> On 09/11/2007, Brian McCallister <br...@apache.org> wrote:
> > Shindig Proposal
> > --
> >
> > = Abstract =
> >
> > Shindig will develop the container and backend server components
> > for hosting OpenSocial applications.
> >
> > = Proposal =
> >
> > Shindig will develop a JavaScript container and implementations of
> > the backend APIs and proxy required for hosting OpenSocial applications.
> >
> >
> > = Background =
> >
> > OpenSocial provides a common set of APIs for social applications
> > across multiple websites. With standard JavaScript and HTML,
> > developers can create social applications that use a social network's
> > friends and update feeds.
> >
> > 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.
> >
> > More information can be found about OpenSocial at
> > http://code.google.com/apis/opensocial/
> >
> > == Rationale ==
> >
> > Shindig is an implementation 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.
> >
> >
> > = Current Status =
> >
> > This is a new project.
> >
> > = Meritocracy =
> >
> > 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.
> >
> > === Community ===
> >
> > Shindig seeks to develop developer and user communities during
> > incubation.
> >
> >
> > = Core Developers =
> >
> > The initial core developers are all Ning employees. We hope to
> > expand this very quickly.
> >
> > = Alignment =
> >
> > 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.
> >
> > = Known Risks =
> >
> > == Orphaned products ==
> >
> > 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.
> >
> > == Homogenous Developers ==
> >
> > The initial group of developers is quite homogenous. Remedying this
> > is a large part of why we want to bring the project to Apache.
> >
> > == Reliance on Salaried Developers ==
> >
> > The initial group of developers are employed by a potential consumer
> > 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, except that Apache HTTPD is the best place to
> > run PHP, which the server-side components Ning intends to donate
> > have been implemented in.
> >
> > == 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.
> >
> > = Documentation =
> >
> > Google's OpenSocial Documentation:
> > http://code.google.com/apis/opensocial/
> >
> > Ning's OpenSocial Documentation:
> > http://tinyurl.com/3y5ckx
> >
> > = Initial Source =
> >
> > Ning, Inc. intends to donate code based on their implementation of
> > OpenSocial. The backend systems will be replaced with more generic
> > equivalents in order to not bind the implementation to specifics
> > of the Ning platform.
> >
> > This code will be extracted from Ning's internal development, and
> > has not been expanded on past the extraction. It will be provided
> > primarily as a starting place for a much more robust, community-
> > developed
> > implementation.
> >
> > = External Dependencies =
> >
> > The initial codebase relies on a library created by Google, Inc.,
> > and licensed under the Apache Software License, Version 2.0.
> >
> > = Required Resources =
> >
> > Developer and user mailing lists
> >
> > A subversion repository
> >
> > A JIRA issue tracker
> >
> > = Initial Committers =
> >
> > Thomas Baker <ba...@ninginc.com>
> > Tim Williamson <ti...@ninginc.com>
> > Brian McCallister <br...@apache.org>
> > Thomas Dudziak <to...@apache.org>
> > Martin Traverso <ma...@ning.com>
> >
> > = Sponsors =
> >
> > == Champion ==
> >
> > Brian McCallister <br...@apache.org>
> >
> > == Nominated Mentors ==
> >
> > Brian McCallister <br...@apache.org>
> > Thomas Dudziak <to...@apache.org>
> > Santiago Gala <sg...@apache.org>
> > Upayavira <up...@apache.org>
> >
> > == Sponsoring Entity ==
> >
> > The Apache Incubator.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
>
> --
> Brett Porter
> Blog: http://www.devzuz.org/blogs/bporter/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Shindig, an OpenSocial Container
Posted by Brett Porter <br...@gmail.com>.
+1
On 09/11/2007, Brian McCallister <br...@apache.org> wrote:
> Shindig Proposal
> --
>
> = Abstract =
>
> Shindig will develop the container and backend server components
> for hosting OpenSocial applications.
>
> = Proposal =
>
> Shindig will develop a JavaScript container and implementations of
> the backend APIs and proxy required for hosting OpenSocial applications.
>
>
> = Background =
>
> OpenSocial provides a common set of APIs for social applications
> across multiple websites. With standard JavaScript and HTML,
> developers can create social applications that use a social network's
> friends and update feeds.
>
> 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.
>
> More information can be found about OpenSocial at
> http://code.google.com/apis/opensocial/
>
> == Rationale ==
>
> Shindig is an implementation 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.
>
>
> = Current Status =
>
> This is a new project.
>
> = Meritocracy =
>
> 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.
>
> === Community ===
>
> Shindig seeks to develop developer and user communities during
> incubation.
>
>
> = Core Developers =
>
> The initial core developers are all Ning employees. We hope to
> expand this very quickly.
>
> = Alignment =
>
> 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.
>
> = Known Risks =
>
> == Orphaned products ==
>
> 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.
>
> == Homogenous Developers ==
>
> The initial group of developers is quite homogenous. Remedying this
> is a large part of why we want to bring the project to Apache.
>
> == Reliance on Salaried Developers ==
>
> The initial group of developers are employed by a potential consumer
> 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, except that Apache HTTPD is the best place to
> run PHP, which the server-side components Ning intends to donate
> have been implemented in.
>
> == 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.
>
> = Documentation =
>
> Google's OpenSocial Documentation:
> http://code.google.com/apis/opensocial/
>
> Ning's OpenSocial Documentation:
> http://tinyurl.com/3y5ckx
>
> = Initial Source =
>
> Ning, Inc. intends to donate code based on their implementation of
> OpenSocial. The backend systems will be replaced with more generic
> equivalents in order to not bind the implementation to specifics
> of the Ning platform.
>
> This code will be extracted from Ning's internal development, and
> has not been expanded on past the extraction. It will be provided
> primarily as a starting place for a much more robust, community-
> developed
> implementation.
>
> = External Dependencies =
>
> The initial codebase relies on a library created by Google, Inc.,
> and licensed under the Apache Software License, Version 2.0.
>
> = Required Resources =
>
> Developer and user mailing lists
>
> A subversion repository
>
> A JIRA issue tracker
>
> = Initial Committers =
>
> Thomas Baker <ba...@ninginc.com>
> Tim Williamson <ti...@ninginc.com>
> Brian McCallister <br...@apache.org>
> Thomas Dudziak <to...@apache.org>
> Martin Traverso <ma...@ning.com>
>
> = Sponsors =
>
> == Champion ==
>
> Brian McCallister <br...@apache.org>
>
> == Nominated Mentors ==
>
> Brian McCallister <br...@apache.org>
> Thomas Dudziak <to...@apache.org>
> Santiago Gala <sg...@apache.org>
> Upayavira <up...@apache.org>
>
> == Sponsoring Entity ==
>
> The Apache Incubator.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Brett Porter
Blog: http://www.devzuz.org/blogs/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Shindig, an OpenSocial Container
Posted by Martin Cooper <ma...@apache.org>.
+1 for the name alone ;-) but it sounds like an interesting project to boot.
--
Martin Cooper
On Nov 9, 2007 10:03 AM, Brian McCallister <br...@apache.org> wrote:
> Shindig Proposal
> --
>
> = Abstract =
>
> Shindig will develop the container and backend server components
> for hosting OpenSocial applications.
>
> = Proposal =
>
> Shindig will develop a JavaScript container and implementations of
> the backend APIs and proxy required for hosting OpenSocial applications.
>
>
> = Background =
>
> OpenSocial provides a common set of APIs for social applications
> across multiple websites. With standard JavaScript and HTML,
> developers can create social applications that use a social network's
> friends and update feeds.
>
> 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.
>
> More information can be found about OpenSocial at
> http://code.google.com/apis/opensocial/
>
> == Rationale ==
>
> Shindig is an implementation 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.
>
>
> = Current Status =
>
> This is a new project.
>
> = Meritocracy =
>
> 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.
>
> === Community ===
>
> Shindig seeks to develop developer and user communities during
> incubation.
>
>
> = Core Developers =
>
> The initial core developers are all Ning employees. We hope to
> expand this very quickly.
>
> = Alignment =
>
> 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.
>
> = Known Risks =
>
> == Orphaned products ==
>
> 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.
>
> == Homogenous Developers ==
>
> The initial group of developers is quite homogenous. Remedying this
> is a large part of why we want to bring the project to Apache.
>
> == Reliance on Salaried Developers ==
>
> The initial group of developers are employed by a potential consumer
> 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, except that Apache HTTPD is the best place to
> run PHP, which the server-side components Ning intends to donate
> have been implemented in.
>
> == 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.
>
> = Documentation =
>
> Google's OpenSocial Documentation:
> http://code.google.com/apis/opensocial/
>
> Ning's OpenSocial Documentation:
> http://tinyurl.com/3y5ckx
>
> = Initial Source =
>
> Ning, Inc. intends to donate code based on their implementation of
> OpenSocial. The backend systems will be replaced with more generic
> equivalents in order to not bind the implementation to specifics
> of the Ning platform.
>
> This code will be extracted from Ning's internal development, and
> has not been expanded on past the extraction. It will be provided
> primarily as a starting place for a much more robust, community-
> developed
> implementation.
>
> = External Dependencies =
>
> The initial codebase relies on a library created by Google, Inc.,
> and licensed under the Apache Software License, Version 2.0.
>
> = Required Resources =
>
> Developer and user mailing lists
>
> A subversion repository
>
> A JIRA issue tracker
>
> = Initial Committers =
>
> Thomas Baker <ba...@ninginc.com>
> Tim Williamson <ti...@ninginc.com>
> Brian McCallister <br...@apache.org>
> Thomas Dudziak <to...@apache.org>
> Martin Traverso <ma...@ning.com>
>
> = Sponsors =
>
> == Champion ==
>
> Brian McCallister <br...@apache.org>
>
> == Nominated Mentors ==
>
> Brian McCallister <br...@apache.org>
> Thomas Dudziak <to...@apache.org>
> Santiago Gala <sg...@apache.org>
> Upayavira <up...@apache.org>
>
> == Sponsoring Entity ==
>
> The Apache Incubator.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Shindig, an OpenSocial Container
Posted by Raymond Feng <en...@gmail.com>.
It's a very interesting proposal.
+1 (non-binding).
Raymond
----- Original Message -----
From: "Brian McCallister" <br...@apache.org>
To: <ge...@incubator.apache.org>
Sent: Friday, November 09, 2007 10:03 AM
Subject: [PROPOSAL] Shindig, an OpenSocial Container
> Shindig Proposal
> --
>
> = Abstract =
>
> Shindig will develop the container and backend server components
> for hosting OpenSocial applications.
>
> = Proposal =
>
> Shindig will develop a JavaScript container and implementations of
> the backend APIs and proxy required for hosting OpenSocial applications.
>
>
> = Background =
>
> OpenSocial provides a common set of APIs for social applications
> across multiple websites. With standard JavaScript and HTML,
> developers can create social applications that use a social network's
> friends and update feeds.
>
> 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.
>
> More information can be found about OpenSocial at
> http://code.google.com/apis/opensocial/
>
> == Rationale ==
>
> Shindig is an implementation 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.
>
>
> = Current Status =
>
> This is a new project.
>
> = Meritocracy =
>
> 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.
>
> === Community ===
>
> Shindig seeks to develop developer and user communities during
> incubation.
>
>
> = Core Developers =
>
> The initial core developers are all Ning employees. We hope to
> expand this very quickly.
>
> = Alignment =
>
> 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.
>
> = Known Risks =
>
> == Orphaned products ==
>
> 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.
>
> == Homogenous Developers ==
>
> The initial group of developers is quite homogenous. Remedying this
> is a large part of why we want to bring the project to Apache.
>
> == Reliance on Salaried Developers ==
>
> The initial group of developers are employed by a potential consumer
> 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, except that Apache HTTPD is the best place to
> run PHP, which the server-side components Ning intends to donate
> have been implemented in.
>
> == 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.
>
> = Documentation =
>
> Google's OpenSocial Documentation:
> http://code.google.com/apis/opensocial/
>
> Ning's OpenSocial Documentation:
> http://tinyurl.com/3y5ckx
>
> = Initial Source =
>
> Ning, Inc. intends to donate code based on their implementation of
> OpenSocial. The backend systems will be replaced with more generic
> equivalents in order to not bind the implementation to specifics
> of the Ning platform.
>
> This code will be extracted from Ning's internal development, and
> has not been expanded on past the extraction. It will be provided
> primarily as a starting place for a much more robust, community-
> developed
> implementation.
>
> = External Dependencies =
>
> The initial codebase relies on a library created by Google, Inc.,
> and licensed under the Apache Software License, Version 2.0.
>
> = Required Resources =
>
> Developer and user mailing lists
>
> A subversion repository
>
> A JIRA issue tracker
>
> = Initial Committers =
>
> Thomas Baker <ba...@ninginc.com>
> Tim Williamson <ti...@ninginc.com>
> Brian McCallister <br...@apache.org>
> Thomas Dudziak <to...@apache.org>
> Martin Traverso <ma...@ning.com>
>
> = Sponsors =
>
> == Champion ==
>
> Brian McCallister <br...@apache.org>
>
> == Nominated Mentors ==
>
> Brian McCallister <br...@apache.org>
> Thomas Dudziak <to...@apache.org>
> Santiago Gala <sg...@apache.org>
> Upayavira <up...@apache.org>
>
> == Sponsoring Entity ==
>
> The Apache Incubator.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Shindig, an OpenSocial Container
Posted by Brian McCallister <br...@apache.org>.
Wow, really happy at the positive response.
I'm on my way to ATL in the morning, and am halfway healthy again, so
will try to pull out some code during hackathon.
-Brian
On Nov 9, 2007, at 10:03 AM, Brian McCallister wrote:
> Shindig Proposal
> --
>
> = Abstract =
>
> Shindig will develop the container and backend server components
> for hosting OpenSocial applications.
>
> = Proposal =
>
> Shindig will develop a JavaScript container and implementations of
> the backend APIs and proxy required for hosting OpenSocial
> applications.
>
>
> = Background =
>
> OpenSocial provides a common set of APIs for social applications
> across multiple websites. With standard JavaScript and HTML,
> developers can create social applications that use a social network's
> friends and update feeds.
>
> 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.
>
> More information can be found about OpenSocial at
> http://code.google.com/apis/opensocial/
>
> == Rationale ==
>
> Shindig is an implementation 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.
>
>
> = Current Status =
>
> This is a new project.
>
> = Meritocracy =
>
> 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.
>
> === Community ===
>
> Shindig seeks to develop developer and user communities during
> incubation.
>
>
> = Core Developers =
>
> The initial core developers are all Ning employees. We hope to
> expand this very quickly.
>
> = Alignment =
>
> 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.
>
> = Known Risks =
>
> == Orphaned products ==
>
> 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.
>
> == Homogenous Developers ==
>
> The initial group of developers is quite homogenous. Remedying this
> is a large part of why we want to bring the project to Apache.
>
> == Reliance on Salaried Developers ==
>
> The initial group of developers are employed by a potential consumer
> 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, except that Apache HTTPD is the best place to
> run PHP, which the server-side components Ning intends to donate
> have been implemented in.
>
> == 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.
>
> = Documentation =
>
> Google's OpenSocial Documentation:
> http://code.google.com/apis/opensocial/
>
> Ning's OpenSocial Documentation:
> http://tinyurl.com/3y5ckx
>
> = Initial Source =
>
> Ning, Inc. intends to donate code based on their implementation of
> OpenSocial. The backend systems will be replaced with more generic
> equivalents in order to not bind the implementation to specifics
> of the Ning platform.
>
> This code will be extracted from Ning's internal development, and
> has not been expanded on past the extraction. It will be provided
> primarily as a starting place for a much more robust, community-
> developed
> implementation.
>
> = External Dependencies =
>
> The initial codebase relies on a library created by Google, Inc.,
> and licensed under the Apache Software License, Version 2.0.
>
> = Required Resources =
>
> Developer and user mailing lists
>
> A subversion repository
>
> A JIRA issue tracker
>
> = Initial Committers =
>
> Thomas Baker <ba...@ninginc.com>
> Tim Williamson <ti...@ninginc.com>
> Brian McCallister <br...@apache.org>
> Thomas Dudziak <to...@apache.org>
> Martin Traverso <ma...@ning.com>
>
> = Sponsors =
>
> == Champion ==
>
> Brian McCallister <br...@apache.org>
>
> == Nominated Mentors ==
>
> Brian McCallister <br...@apache.org>
> Thomas Dudziak <to...@apache.org>
> Santiago Gala <sg...@apache.org>
> Upayavira <up...@apache.org>
>
> == Sponsoring Entity ==
>
> The Apache Incubator.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Shindig, an OpenSocial Container
Posted by Matthias Wessendorf <ma...@apache.org>.
that sounds very interesting !
+1
On Nov 9, 2007 7:03 PM, Brian McCallister <br...@apache.org> wrote:
> Shindig Proposal
> --
>
> = Abstract =
>
> Shindig will develop the container and backend server components
> for hosting OpenSocial applications.
>
> = Proposal =
>
> Shindig will develop a JavaScript container and implementations of
> the backend APIs and proxy required for hosting OpenSocial applications.
>
>
> = Background =
>
> OpenSocial provides a common set of APIs for social applications
> across multiple websites. With standard JavaScript and HTML,
> developers can create social applications that use a social network's
> friends and update feeds.
>
> 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.
>
> More information can be found about OpenSocial at
> http://code.google.com/apis/opensocial/
>
> == Rationale ==
>
> Shindig is an implementation 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.
>
>
> = Current Status =
>
> This is a new project.
>
> = Meritocracy =
>
> 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.
>
> === Community ===
>
> Shindig seeks to develop developer and user communities during
> incubation.
>
>
> = Core Developers =
>
> The initial core developers are all Ning employees. We hope to
> expand this very quickly.
>
> = Alignment =
>
> 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.
>
> = Known Risks =
>
> == Orphaned products ==
>
> 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.
>
> == Homogenous Developers ==
>
> The initial group of developers is quite homogenous. Remedying this
> is a large part of why we want to bring the project to Apache.
>
> == Reliance on Salaried Developers ==
>
> The initial group of developers are employed by a potential consumer
> 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, except that Apache HTTPD is the best place to
> run PHP, which the server-side components Ning intends to donate
> have been implemented in.
>
> == 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.
>
> = Documentation =
>
> Google's OpenSocial Documentation:
> http://code.google.com/apis/opensocial/
>
> Ning's OpenSocial Documentation:
> http://tinyurl.com/3y5ckx
>
> = Initial Source =
>
> Ning, Inc. intends to donate code based on their implementation of
> OpenSocial. The backend systems will be replaced with more generic
> equivalents in order to not bind the implementation to specifics
> of the Ning platform.
>
> This code will be extracted from Ning's internal development, and
> has not been expanded on past the extraction. It will be provided
> primarily as a starting place for a much more robust, community-
> developed
> implementation.
>
> = External Dependencies =
>
> The initial codebase relies on a library created by Google, Inc.,
> and licensed under the Apache Software License, Version 2.0.
>
> = Required Resources =
>
> Developer and user mailing lists
>
> A subversion repository
>
> A JIRA issue tracker
>
> = Initial Committers =
>
> Thomas Baker <ba...@ninginc.com>
> Tim Williamson <ti...@ninginc.com>
> Brian McCallister <br...@apache.org>
> Thomas Dudziak <to...@apache.org>
> Martin Traverso <ma...@ning.com>
>
> = Sponsors =
>
> == Champion ==
>
> Brian McCallister <br...@apache.org>
>
> == Nominated Mentors ==
>
> Brian McCallister <br...@apache.org>
> Thomas Dudziak <to...@apache.org>
> Santiago Gala <sg...@apache.org>
> Upayavira <up...@apache.org>
>
> == Sponsoring Entity ==
>
> The Apache Incubator.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Shindig, an OpenSocial Container
Posted by Upayavira <uv...@odoko.co.uk>.
+1. I look forward to seeing it develop.
Upayavira
On Fri, 2007-11-09 at 10:03 -0800, Brian McCallister wrote:
> Shindig Proposal
> --
>
> = Abstract =
>
> Shindig will develop the container and backend server components
> for hosting OpenSocial applications.
>
> = Proposal =
>
> Shindig will develop a JavaScript container and implementations of
> the backend APIs and proxy required for hosting OpenSocial applications.
>
>
> = Background =
>
> OpenSocial provides a common set of APIs for social applications
> across multiple websites. With standard JavaScript and HTML,
> developers can create social applications that use a social network's
> friends and update feeds.
>
> 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.
>
> More information can be found about OpenSocial at
> http://code.google.com/apis/opensocial/
>
> == Rationale ==
>
> Shindig is an implementation 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.
>
>
> = Current Status =
>
> This is a new project.
>
> = Meritocracy =
>
> 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.
>
> === Community ===
>
> Shindig seeks to develop developer and user communities during
> incubation.
>
>
> = Core Developers =
>
> The initial core developers are all Ning employees. We hope to
> expand this very quickly.
>
> = Alignment =
>
> 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.
>
> = Known Risks =
>
> == Orphaned products ==
>
> 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.
>
> == Homogenous Developers ==
>
> The initial group of developers is quite homogenous. Remedying this
> is a large part of why we want to bring the project to Apache.
>
> == Reliance on Salaried Developers ==
>
> The initial group of developers are employed by a potential consumer
> 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, except that Apache HTTPD is the best place to
> run PHP, which the server-side components Ning intends to donate
> have been implemented in.
>
> == 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.
>
> = Documentation =
>
> Google's OpenSocial Documentation:
> http://code.google.com/apis/opensocial/
>
> Ning's OpenSocial Documentation:
> http://tinyurl.com/3y5ckx
>
> = Initial Source =
>
> Ning, Inc. intends to donate code based on their implementation of
> OpenSocial. The backend systems will be replaced with more generic
> equivalents in order to not bind the implementation to specifics
> of the Ning platform.
>
> This code will be extracted from Ning's internal development, and
> has not been expanded on past the extraction. It will be provided
> primarily as a starting place for a much more robust, community-
> developed
> implementation.
>
> = External Dependencies =
>
> The initial codebase relies on a library created by Google, Inc.,
> and licensed under the Apache Software License, Version 2.0.
>
> = Required Resources =
>
> Developer and user mailing lists
>
> A subversion repository
>
> A JIRA issue tracker
>
> = Initial Committers =
>
> Thomas Baker <ba...@ninginc.com>
> Tim Williamson <ti...@ninginc.com>
> Brian McCallister <br...@apache.org>
> Thomas Dudziak <to...@apache.org>
> Martin Traverso <ma...@ning.com>
>
> = Sponsors =
>
> == Champion ==
>
> Brian McCallister <br...@apache.org>
>
> == Nominated Mentors ==
>
> Brian McCallister <br...@apache.org>
> Thomas Dudziak <to...@apache.org>
> Santiago Gala <sg...@apache.org>
> Upayavira <up...@apache.org>
>
> == Sponsoring Entity ==
>
> The Apache Incubator.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Shindig, an OpenSocial Container
Posted by Dave <sn...@gmail.com>.
On Nov 11, 2007 7:00 PM, Brian McCallister <br...@skife.org> wrote:
> On Nov 9, 2007, at 1:34 PM, Sylvain Wallez wrote:
> > Brian McCallister wrote:
> >> Shindig Proposal
+1 ... sounds like a great idea and very useful for Apache's social
software apps (Roller and JSPWiki).
- Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Shindig, an OpenSocial Container
Posted by Brian McCallister <br...@skife.org>.
On Nov 9, 2007, at 1:34 PM, Sylvain Wallez wrote:
> Brian McCallister wrote:
>> Shindig Proposal
>
> A big +1, and I'd happily be a mentor.
Thank you! We'll take you up on that :-)
-Brian
>
>
> Sylvain
>
> --
> Sylvain Wallez - http://bluxte.net
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Shindig, an OpenSocial Container
Posted by Sylvain Wallez <sy...@apache.org>.
Brian McCallister wrote:
> Shindig Proposal
A big +1, and I'd happily be a mentor.
Sylvain
--
Sylvain Wallez - http://bluxte.net
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Shindig, an OpenSocial Container
Posted by Andrus Adamchik <an...@objectstyle.org>.
+1
I have no explanation why the social networks are experiencing such
growth these days, but it is certainly another fun area for
developers :-)
Andrus
Brian McCallister wrote:
> Shindig Proposal
> --
> = Abstract =
> Shindig will develop the container and backend server components
> for hosting OpenSocial applications.
> = Proposal =
> Shindig will develop a JavaScript container and implementations of
> the backend APIs and proxy required for hosting OpenSocial
> applications.
> = Background =
> OpenSocial provides a common set of APIs for social applications
> across multiple websites. With standard JavaScript and HTML,
> developers can create social applications that use a social network's
> friends and update feeds.
> 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.
> More information can be found about OpenSocial at
> http://code.google.com/apis/opensocial/
> == Rationale ==
> Shindig is an implementation 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.
> = Current Status =
> This is a new project.
> = Meritocracy =
> 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.
> === Community ===
> Shindig seeks to develop developer and user communities during
> incubation.
> = Core Developers =
> The initial core developers are all Ning employees. We hope to
> expand this very quickly.
> = Alignment =
> 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.
> = Known Risks =
> == Orphaned products ==
> 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.
> == Homogenous Developers ==
> The initial group of developers is quite homogenous. Remedying this
> is a large part of why we want to bring the project to Apache.
> == Reliance on Salaried Developers ==
> The initial group of developers are employed by a potential consumer
> 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, except that Apache HTTPD is the best place to
> run PHP, which the server-side components Ning intends to donate
> have been implemented in.
> == 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.
> = Documentation =
> Google's OpenSocial Documentation:
> http://code.google.com/apis/opensocial/
> Ning's OpenSocial Documentation:
> http://tinyurl.com/3y5ckx
> = Initial Source =
> Ning, Inc. intends to donate code based on their implementation of
> OpenSocial. The backend systems will be replaced with more generic
> equivalents in order to not bind the implementation to specifics
> of the Ning platform.
> This code will be extracted from Ning's internal development, and
> has not been expanded on past the extraction. It will be provided
> primarily as a starting place for a much more robust, community-
> developed
> implementation.
> = External Dependencies =
> The initial codebase relies on a library created by Google, Inc.,
> and licensed under the Apache Software License, Version 2.0.
> = Required Resources =
> Developer and user mailing lists
> A subversion repository
> A JIRA issue tracker
> = Initial Committers =
> Thomas Baker <ba...@ninginc.com>
> Tim Williamson <ti...@ninginc.com>
> Brian McCallister <br...@apache.org>
> Thomas Dudziak <to...@apache.org>
> Martin Traverso <ma...@ning.com>
> = Sponsors =
> == Champion ==
> Brian McCallister <br...@apache.org>
> == Nominated Mentors ==
> Brian McCallister <br...@apache.org>
> Thomas Dudziak <to...@apache.org>
> Santiago Gala <sg...@apache.org>
> Upayavira <up...@apache.org>
> == Sponsoring Entity ==
> The Apache Incubator.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Shindig, an OpenSocial Container
Posted by Niklas Gustavsson <ni...@protocol7.com>.
+1 (non-binding), nice with Apache activity in this interesting area.
/niklas
Brian McCallister wrote:
> Shindig Proposal
> --
>
> = Abstract =
>
> Shindig will develop the container and backend server components
> for hosting OpenSocial applications.
>
> = Proposal =
>
> Shindig will develop a JavaScript container and implementations of
> the backend APIs and proxy required for hosting OpenSocial applications.
>
>
> = Background =
>
> OpenSocial provides a common set of APIs for social applications
> across multiple websites. With standard JavaScript and HTML,
> developers can create social applications that use a social network's
> friends and update feeds.
>
> 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.
>
> More information can be found about OpenSocial at
> http://code.google.com/apis/opensocial/
>
> == Rationale ==
>
> Shindig is an implementation 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.
>
>
> = Current Status =
>
> This is a new project.
>
> = Meritocracy =
>
> 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.
>
> === Community ===
>
> Shindig seeks to develop developer and user communities during
> incubation.
>
>
> = Core Developers =
>
> The initial core developers are all Ning employees. We hope to
> expand this very quickly.
>
> = Alignment =
>
> 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.
>
> = Known Risks =
>
> == Orphaned products ==
>
> 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.
>
> == Homogenous Developers ==
>
> The initial group of developers is quite homogenous. Remedying this
> is a large part of why we want to bring the project to Apache.
>
> == Reliance on Salaried Developers ==
>
> The initial group of developers are employed by a potential consumer
> 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, except that Apache HTTPD is the best place to
> run PHP, which the server-side components Ning intends to donate
> have been implemented in.
>
> == 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.
>
> = Documentation =
>
> Google's OpenSocial Documentation:
> http://code.google.com/apis/opensocial/
>
> Ning's OpenSocial Documentation:
> http://tinyurl.com/3y5ckx
>
> = Initial Source =
>
> Ning, Inc. intends to donate code based on their implementation of
> OpenSocial. The backend systems will be replaced with more generic
> equivalents in order to not bind the implementation to specifics
> of the Ning platform.
>
> This code will be extracted from Ning's internal development, and
> has not been expanded on past the extraction. It will be provided
> primarily as a starting place for a much more robust, community-developed
> implementation.
>
> = External Dependencies =
>
> The initial codebase relies on a library created by Google, Inc.,
> and licensed under the Apache Software License, Version 2.0.
>
> = Required Resources =
>
> Developer and user mailing lists
>
> A subversion repository
>
> A JIRA issue tracker
>
> = Initial Committers =
>
> Thomas Baker <ba...@ninginc.com>
> Tim Williamson <ti...@ninginc.com>
> Brian McCallister <br...@apache.org>
> Thomas Dudziak <to...@apache.org>
> Martin Traverso <ma...@ning.com>
>
> = Sponsors =
>
> == Champion ==
>
> Brian McCallister <br...@apache.org>
>
> == Nominated Mentors ==
>
> Brian McCallister <br...@apache.org>
> Thomas Dudziak <to...@apache.org>
> Santiago Gala <sg...@apache.org>
> Upayavira <up...@apache.org>
>
> == Sponsoring Entity ==
>
> The Apache Incubator.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Shindig, an OpenSocial Container
Posted by Yoav Shapira <yo...@apache.org>.
On Nov 9, 2007 1:03 PM, Brian McCallister <br...@apache.org> wrote:
> Shindig Proposal
Sweetness, +1.
Yoav
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Shindig, an OpenSocial Container
Posted by Davanum Srinivas <da...@gmail.com>.
+1 from me
On Nov 9, 2007 1:03 PM, Brian McCallister <br...@apache.org> wrote:
> Shindig Proposal
> --
>
> = Abstract =
>
> Shindig will develop the container and backend server components
> for hosting OpenSocial applications.
>
> = Proposal =
>
> Shindig will develop a JavaScript container and implementations of
> the backend APIs and proxy required for hosting OpenSocial applications.
>
>
> = Background =
>
> OpenSocial provides a common set of APIs for social applications
> across multiple websites. With standard JavaScript and HTML,
> developers can create social applications that use a social network's
> friends and update feeds.
>
> 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.
>
> More information can be found about OpenSocial at
> http://code.google.com/apis/opensocial/
>
> == Rationale ==
>
> Shindig is an implementation 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.
>
>
> = Current Status =
>
> This is a new project.
>
> = Meritocracy =
>
> 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.
>
> === Community ===
>
> Shindig seeks to develop developer and user communities during
> incubation.
>
>
> = Core Developers =
>
> The initial core developers are all Ning employees. We hope to
> expand this very quickly.
>
> = Alignment =
>
> 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.
>
> = Known Risks =
>
> == Orphaned products ==
>
> 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.
>
> == Homogenous Developers ==
>
> The initial group of developers is quite homogenous. Remedying this
> is a large part of why we want to bring the project to Apache.
>
> == Reliance on Salaried Developers ==
>
> The initial group of developers are employed by a potential consumer
> 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, except that Apache HTTPD is the best place to
> run PHP, which the server-side components Ning intends to donate
> have been implemented in.
>
> == 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.
>
> = Documentation =
>
> Google's OpenSocial Documentation:
> http://code.google.com/apis/opensocial/
>
> Ning's OpenSocial Documentation:
> http://tinyurl.com/3y5ckx
>
> = Initial Source =
>
> Ning, Inc. intends to donate code based on their implementation of
> OpenSocial. The backend systems will be replaced with more generic
> equivalents in order to not bind the implementation to specifics
> of the Ning platform.
>
> This code will be extracted from Ning's internal development, and
> has not been expanded on past the extraction. It will be provided
> primarily as a starting place for a much more robust, community-
> developed
> implementation.
>
> = External Dependencies =
>
> The initial codebase relies on a library created by Google, Inc.,
> and licensed under the Apache Software License, Version 2.0.
>
> = Required Resources =
>
> Developer and user mailing lists
>
> A subversion repository
>
> A JIRA issue tracker
>
> = Initial Committers =
>
> Thomas Baker <ba...@ninginc.com>
> Tim Williamson <ti...@ninginc.com>
> Brian McCallister <br...@apache.org>
> Thomas Dudziak <to...@apache.org>
> Martin Traverso <ma...@ning.com>
>
> = Sponsors =
>
> == Champion ==
>
> Brian McCallister <br...@apache.org>
>
> == Nominated Mentors ==
>
> Brian McCallister <br...@apache.org>
> Thomas Dudziak <to...@apache.org>
> Santiago Gala <sg...@apache.org>
> Upayavira <up...@apache.org>
>
> == Sponsoring Entity ==
>
> The Apache Incubator.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Davanum Srinivas :: http://davanum.wordpress.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Shindig, an OpenSocial Container
Posted by Kevan Miller <ke...@gmail.com>.
+1
--kevan
On Nov 9, 2007 1:03 PM, Brian McCallister <br...@apache.org> wrote:
> Shindig Proposal
>
Re: [PROPOSAL] Shindig, an OpenSocial Container
Posted by Matt Hogstrom <ma...@hogstrom.org>.
+1
On Nov 9, 2007, at 1:03 PM, Brian McCallister wrote:
> Shindig Proposal
> --
>
> = Abstract =
>
> Shindig will develop the container and backend server components
> for hosting OpenSocial applications.
>
> = Proposal =
>
> Shindig will develop a JavaScript container and implementations of
> the backend APIs and proxy required for hosting OpenSocial
> applications.
>
>
> = Background =
>
> OpenSocial provides a common set of APIs for social applications
> across multiple websites. With standard JavaScript and HTML,
> developers can create social applications that use a social network's
> friends and update feeds.
>
> 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.
>
> More information can be found about OpenSocial at
> http://code.google.com/apis/opensocial/
>
> == Rationale ==
>
> Shindig is an implementation 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.
>
>
> = Current Status =
>
> This is a new project.
>
> = Meritocracy =
>
> 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.
>
> === Community ===
>
> Shindig seeks to develop developer and user communities during
> incubation.
>
>
> = Core Developers =
>
> The initial core developers are all Ning employees. We hope to
> expand this very quickly.
>
> = Alignment =
>
> 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.
>
> = Known Risks =
>
> == Orphaned products ==
>
> 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.
>
> == Homogenous Developers ==
>
> The initial group of developers is quite homogenous. Remedying this
> is a large part of why we want to bring the project to Apache.
>
> == Reliance on Salaried Developers ==
>
> The initial group of developers are employed by a potential consumer
> 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, except that Apache HTTPD is the best place to
> run PHP, which the server-side components Ning intends to donate
> have been implemented in.
>
> == 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.
>
> = Documentation =
>
> Google's OpenSocial Documentation:
> http://code.google.com/apis/opensocial/
>
> Ning's OpenSocial Documentation:
> http://tinyurl.com/3y5ckx
>
> = Initial Source =
>
> Ning, Inc. intends to donate code based on their implementation of
> OpenSocial. The backend systems will be replaced with more generic
> equivalents in order to not bind the implementation to specifics
> of the Ning platform.
>
> This code will be extracted from Ning's internal development, and
> has not been expanded on past the extraction. It will be provided
> primarily as a starting place for a much more robust, community-
> developed
> implementation.
>
> = External Dependencies =
>
> The initial codebase relies on a library created by Google, Inc.,
> and licensed under the Apache Software License, Version 2.0.
>
> = Required Resources =
>
> Developer and user mailing lists
>
> A subversion repository
>
> A JIRA issue tracker
>
> = Initial Committers =
>
> Thomas Baker <ba...@ninginc.com>
> Tim Williamson <ti...@ninginc.com>
> Brian McCallister <br...@apache.org>
> Thomas Dudziak <to...@apache.org>
> Martin Traverso <ma...@ning.com>
>
> = Sponsors =
>
> == Champion ==
>
> Brian McCallister <br...@apache.org>
>
> == Nominated Mentors ==
>
> Brian McCallister <br...@apache.org>
> Thomas Dudziak <to...@apache.org>
> Santiago Gala <sg...@apache.org>
> Upayavira <up...@apache.org>
>
> == Sponsoring Entity ==
>
> The Apache Incubator.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org