29. Apache Rave
Timeline
• December 2010: OpenSocial Europe Summit, first
brainstorm & discussion session
• January 2011: draft for Apache Incubator proposal
• March 2011: Apache Rave enters the Apache
Incubator, existing code is donated
• June 2011: first release: 0.1-incubating
• January 2012: proposal to graduate
• March 2012: Apache Rave becomes a TLP
Apache Meetup 26-04-2012
31. Apache Rave
Why Apache Rave?
• Old style portals are too heavy and difficult
Apache Meetup 26-04-2012
32. Apache Rave
Why Apache Rave?
• Old style portals are too heavy and difficult
• Client side technology
Apache Meetup 26-04-2012
33. Apache Rave
Why Apache Rave?
• Old style portals are too heavy and difficult
• Client side technology
• Gadgets are easy to write
Apache Meetup 26-04-2012
34. Apache Rave
Why Apache Rave?
• Old style portals are too heavy and difficult
• Client side technology
• Gadgets are easy to write
• OpenSocial standard adopts features fast
Apache Meetup 26-04-2012
35. Apache Rave
Why Apache Rave?
• Old style portals are too heavy and difficult
• Client side technology
• Gadgets are easy to write
• OpenSocial standard adopts features fast
• The web is social
Apache Meetup 26-04-2012
36. Apache Rave
Why Apache Rave?
• Old style portals are too heavy and difficult
• Client side technology
• Gadgets are easy to write
• OpenSocial standard adopts features fast
• The web is social
• The web is mobile
Apache Meetup 26-04-2012
Personalized: it’s MY content and I defined which blocks are on the page \nThey all use OpenSocial gadgets that can be reused (see Evernote gadget)\nStudents can write gadgets. They already write apps for smart phones.\nThey look like portals, but don’t use portal technologies\n
Personalized: it’s MY content and I defined which blocks are on the page \nThey all use OpenSocial gadgets that can be reused (see Evernote gadget)\nStudents can write gadgets. They already write apps for smart phones.\nThey look like portals, but don’t use portal technologies\n
Personalized: it’s MY content and I defined which blocks are on the page \nThey all use OpenSocial gadgets that can be reused (see Evernote gadget)\nStudents can write gadgets. They already write apps for smart phones.\nThey look like portals, but don’t use portal technologies\n
\n
Mix of several technologies. Some parties are interested in the front end (ROLE project), some in the backend, social features (Sakai).\n
OpenSocial: initiated by Google to exchange data on social networks (Hyves, MySpace)\nW3C Widgets: targeting for mobile, mainly driven by Nokia\n
Just as I can choose my own bag of M&M’s, in Rave the user can define which content he sees.\n
Other skin\n
Other skin\n
Desktop, iPad, mobile\nThe web is anywhere now. \nStudents with smartphones who are bored in public transport -> social media!\n
Desktop, iPad, mobile\nThe web is anywhere now. \nStudents with smartphones who are bored in public transport -> social media!\n
SURFnet: SURFconext collaboration infrastructure. Demo “portal” based on OpenSocial\nMITRE: non-profit organization. Intranet “portal” based on OpenSocial\nOGCE: science gateway, widget store & rendering of OpenSocial gadgets\nHippo: content management & portals. OSS Watch: knowledge of Open Source projects, involvement in Wookie community\n
We’re going fast!\n
\n
server side, web 1.0, mobile?!, no communication between portlets. specification is evolving slowly\nSmart clients, client side saves data\nStudents can write gadgets\nGoogle has personalized search results\nAlso using mobile phones at home on the couch\nMobile gives opportunity to show content based on your location (am I on the campus or not?)\n
server side, web 1.0, mobile?!, no communication between portlets. specification is evolving slowly\nSmart clients, client side saves data\nStudents can write gadgets\nGoogle has personalized search results\nAlso using mobile phones at home on the couch\nMobile gives opportunity to show content based on your location (am I on the campus or not?)\n
server side, web 1.0, mobile?!, no communication between portlets. specification is evolving slowly\nSmart clients, client side saves data\nStudents can write gadgets\nGoogle has personalized search results\nAlso using mobile phones at home on the couch\nMobile gives opportunity to show content based on your location (am I on the campus or not?)\n
server side, web 1.0, mobile?!, no communication between portlets. specification is evolving slowly\nSmart clients, client side saves data\nStudents can write gadgets\nGoogle has personalized search results\nAlso using mobile phones at home on the couch\nMobile gives opportunity to show content based on your location (am I on the campus or not?)\n
server side, web 1.0, mobile?!, no communication between portlets. specification is evolving slowly\nSmart clients, client side saves data\nStudents can write gadgets\nGoogle has personalized search results\nAlso using mobile phones at home on the couch\nMobile gives opportunity to show content based on your location (am I on the campus or not?)\n
server side, web 1.0, mobile?!, no communication between portlets. specification is evolving slowly\nSmart clients, client side saves data\nStudents can write gadgets\nGoogle has personalized search results\nAlso using mobile phones at home on the couch\nMobile gives opportunity to show content based on your location (am I on the campus or not?)\n
Current features\n
\n
\n
\n
This list can be extended by your input (next session)\n
This list can be extended by your input (next session)\n
This list can be extended by your input (next session)\n
This list can be extended by your input (next session)\n
This list can be extended by your input (next session)\n
This list can be extended by your input (next session)\n
