On 14 Jul 2011, at 14:22, Franklin, Matthew B. wrote: > On 7/14/11 6:54 AM, "Evgeny Bogdanov" <[email protected]> wrote: > >> Hi all, > > Hi Evgeny, welcome to Rave :)
Hi Evgeny! > >> >> I am working on space proposal for OpenSocial. As some of you might know >> it should appear >> in OpenSocial 2.1. I'd be happy to help in integrating it. > > A few of us have been watching your spaces proposal with great interest. > As you are probably aware, one of Rave's main goals is to support shared > spaces. We are always looking for people to help pitch in, and I think it > is great that you would like to do the work of integrating spaces in Rave. Yes, (work)spaces are definitely a feature we want for Rave. (Wookie uses a slightly different way of working from Shindig - it sends the shared space data when loading a widget rather than at runtime - but having a model for representing spaces in Rave that works with all widget types will be really good.) > >> >> I have few question to the team. >> 1. What is the targeted OpenSocial version. How do you plan to go along >> with OpenSocial versioning. > > We expect to support the latest version of OpenSocial when we release > (minimum of 2.0). We are using Shindig 3.0 B2 now and leveraging some of > the common container work. Our plan is to remain aligned with the latest > versions of OpenSocial, primarily by keeping our Shindig dependency up to > date. > >> >> 2. Do you just plug Apache Shindig into RAVE, or you do some >> modifications in Apache Shindig code >> so that it will be difficult to adapt to newer Shindig versions. > > Our plan is to modify Shindig as little as possible so that we can easily > "plug in" new versions. Any major changes we make to the way Shindig > works, we will be submitting back to the Shindig community via patches. > >> >> 3. I have a web platform that uses Shindig to render widgets and manage >> OpenSocial APIs. >> Shindig is integrated into our platform. What is the main use case >> scenario for RAVE? >> Is it supposed to be integrated into some existing platform or is it more >> a standalone application that I can install for my community? > > We have visions for both. The primary use case we are working on now is > the standalone application that leverages Shindig and Wookie instances for > OpenSocial and W3C widget rendering respectively. Currently, we have > working "Portal" pages where users can add gadgets to a page visible only > to themselves; however, we will be adding profile and common (space) pages > soon. Eventually, we want to support rendering regions of widgets as a > service for other applications to consume. This last one looks like it could be quite a popular feature: https://scottbw.wordpress.com/2011/07/13/awesome-the-emergence-of-a-design-pattern-for-widget-based-sharable-workspaces/ > >> >> Thank you in advance >> Evgeny >
