Re: [VOTE] Accept Rave into the Incubator
+1 On Fri, Feb 25, 2011 at 10:02 PM, Henry Saputra wrote: > +1 > > Looks like a good project. > > - Henry > > On Thu, Feb 24, 2011 at 4:08 PM, Ate Douma wrote: >> Given the feedback received so far I think the Rave proposal is in good >> shape so I'd like to bring up the vote for accepting Rave into the >> Incubator. >> >> The proposal is at: http://wiki.apache.org/incubator/RaveProposal and also >> copied as text below. >> >> Please vote. >> >> [ ] +1 Accept Rave into the incubator >> [ ] +0 Don't care' >> [ ] -1 Reject for the following reason: >> >> I'll close the vote at Tuesday morning 1st March CET to accommodate for the >> coming weekend. That's a little over 5 days from now. >> >> Regards, >> >> Ate >> >> - COPY OF PROPOSAL FROM http://wiki.apache.org/incubator/RaveProposal >> - >> = Apache Rave Proposal = >> >> >> == Abstract == >> >> Apache Rave is A new WEb And SOcial Mashup Engine. It will provide an >> out-of-the-box as well as an extendible lightweight Java platform to host, >> serve and aggregate (Open)Social Gadgets and services through a highly >> customizable and Web 2.0 friendly front-end. >> Rave is targeted as engine for internet and intranet portals and as building >> block to provide context-aware personalization and collaboration features >> for multi-site/multi-channel (mobile) oriented and content driven websites >> and (social) network oriented services and platforms. >> For the [[http://www.opensocial.org/|OpenSocial]] container and services the >> (Java) [[http://shindig.apache.org|Apache Shindig]] will be integrated. At a >> later stage further generalization is envisioned to also transparently >> support [[http://www.w3.org/TR/widgets/|W3C Widgets]] using >> [[http://incubator.apache.org/wookie/|Apache Wookie]]. >> >> >> == Proposal == >> >> The reason for starting Rave is to bring together and combine several >> existing projects and teams currently working towards more or less the same >> or overlapping goals but each in their own small(er) target audience and >> community. >> >> The goal for Rave is to become a lightweight and open-standards based >> extendible platform for using, integrating and hosting !OpenSocial and W3C >> Widget related features, technologies and services. >> It will also provide strong context-aware personalization, collaboration and >> content integration capabilities and a high quality out-of-the-box >> installation as well as be easy to integrate in other platforms and >> solutions. >> >> The initial features for Rave will at least be based on the current >> capabilities from the contributing external projects, for which they will >> provide the necessary code contributions. >> However, the code base for Rave will be built anew with strong focus on >> generalization, customization and extendibility to support the intended >> multi-purpose adoption and integration. >> The contributing external projects will start using and switch to the new >> Rave based solution as soon as the initial features become available to >> ensure the continued participation and interest from their side as well as >> their own communities. >> >> The intended initial features include: >> >> '''Core Features''' >> 1. Advanced !OpenSocial compliance and optional features support >> 1. !OpenSocial persistence and SPI (Service Provider Interface) >> implementation >> 1. Self-service application administration including security, gadget >> management and page templates >> 1. User and group management with full privacy model >> 1. Gadget repository with life-cycle management (install/update/remove) and >> extended meta data (categories, comments, ratings, etc.) >> 1. Dynamic and highly customizable front-end engine (skins, pages, tabs, >> layouts, navigation) >> 1. Full OAuth support >> 1. Support for security restrictions on both Gadgets and page/tag/layout >> customizations >> 1. Set of common and general purpose Gadgets to be usable out-of-the-box >> 1. Support for inter-gadget messaging with examples >> >> '''Extensible Features''' >> 1. Pluggable persistence >> 1. Pluggable security model with example modules for authentication and >> authorization >> 1. Support for !OpenSocial extensions not (yet) defined in the >> specification >> 1. Support for other (non-standard, yet) pluggable container services and >> extensions >> >> Beyond these initial features the vision and scope for Rave goes much >> further and includes integrating and providing other highly desired/needed >> features like: >> >> * native W3C Widgets support through >> [[http://incubator.apache.org/wookie|Apache Wookie]] >> * pluggable and extendible content integration and management services >> * space extensions and management features, like >> http://wiki.opensocial.org/index.php?title=Space_extension >> * context aware features and extensions integration for personalized and >> social network and (mobile) device oriented sites and channels >> * enhanced client-side
Re: [VOTE] Accept Rave into the Incubator
+1 Looks like a good project. - Henry On Thu, Feb 24, 2011 at 4:08 PM, Ate Douma wrote: > Given the feedback received so far I think the Rave proposal is in good > shape so I'd like to bring up the vote for accepting Rave into the > Incubator. > > The proposal is at: http://wiki.apache.org/incubator/RaveProposal and also > copied as text below. > > Please vote. > > [ ] +1 Accept Rave into the incubator > [ ] +0 Don't care' > [ ] -1 Reject for the following reason: > > I'll close the vote at Tuesday morning 1st March CET to accommodate for the > coming weekend. That's a little over 5 days from now. > > Regards, > > Ate > > - COPY OF PROPOSAL FROM http://wiki.apache.org/incubator/RaveProposal > - > = Apache Rave Proposal = > > > == Abstract == > > Apache Rave is A new WEb And SOcial Mashup Engine. It will provide an > out-of-the-box as well as an extendible lightweight Java platform to host, > serve and aggregate (Open)Social Gadgets and services through a highly > customizable and Web 2.0 friendly front-end. > Rave is targeted as engine for internet and intranet portals and as building > block to provide context-aware personalization and collaboration features > for multi-site/multi-channel (mobile) oriented and content driven websites > and (social) network oriented services and platforms. > For the [[http://www.opensocial.org/|OpenSocial]] container and services the > (Java) [[http://shindig.apache.org|Apache Shindig]] will be integrated. At a > later stage further generalization is envisioned to also transparently > support [[http://www.w3.org/TR/widgets/|W3C Widgets]] using > [[http://incubator.apache.org/wookie/|Apache Wookie]]. > > > == Proposal == > > The reason for starting Rave is to bring together and combine several > existing projects and teams currently working towards more or less the same > or overlapping goals but each in their own small(er) target audience and > community. > > The goal for Rave is to become a lightweight and open-standards based > extendible platform for using, integrating and hosting !OpenSocial and W3C > Widget related features, technologies and services. > It will also provide strong context-aware personalization, collaboration and > content integration capabilities and a high quality out-of-the-box > installation as well as be easy to integrate in other platforms and > solutions. > > The initial features for Rave will at least be based on the current > capabilities from the contributing external projects, for which they will > provide the necessary code contributions. > However, the code base for Rave will be built anew with strong focus on > generalization, customization and extendibility to support the intended > multi-purpose adoption and integration. > The contributing external projects will start using and switch to the new > Rave based solution as soon as the initial features become available to > ensure the continued participation and interest from their side as well as > their own communities. > > The intended initial features include: > > '''Core Features''' > 1. Advanced !OpenSocial compliance and optional features support > 1. !OpenSocial persistence and SPI (Service Provider Interface) > implementation > 1. Self-service application administration including security, gadget > management and page templates > 1. User and group management with full privacy model > 1. Gadget repository with life-cycle management (install/update/remove) and > extended meta data (categories, comments, ratings, etc.) > 1. Dynamic and highly customizable front-end engine (skins, pages, tabs, > layouts, navigation) > 1. Full OAuth support > 1. Support for security restrictions on both Gadgets and page/tag/layout > customizations > 1. Set of common and general purpose Gadgets to be usable out-of-the-box > 1. Support for inter-gadget messaging with examples > > '''Extensible Features''' > 1. Pluggable persistence > 1. Pluggable security model with example modules for authentication and > authorization > 1. Support for !OpenSocial extensions not (yet) defined in the > specification > 1. Support for other (non-standard, yet) pluggable container services and > extensions > > Beyond these initial features the vision and scope for Rave goes much > further and includes integrating and providing other highly desired/needed > features like: > > * native W3C Widgets support through > [[http://incubator.apache.org/wookie|Apache Wookie]] > * pluggable and extendible content integration and management services > * space extensions and management features, like > http://wiki.opensocial.org/index.php?title=Space_extension > * context aware features and extensions integration for personalized and > social network and (mobile) device oriented sites and channels > * enhanced client-side widget messaging, coordination and co-location > support like using [[http://www.openajax.org|OpenAjax]] Hub and Registry > * space, page and Gadget based linking, navigation, co
Re: [VOTE] Accept Rave into the Incubator
[ ] +1 Accept Rave into the incubator - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Rave into the Incubator
+1 salu2 On Fri, 2011-02-25 at 01:08 +0100, Ate Douma wrote: > Given the feedback received so far I think the Rave proposal is in good shape > so > I'd like to bring up the vote for accepting Rave into the Incubator. > > The proposal is at: http://wiki.apache.org/incubator/RaveProposal and also > copied as text below. > > Please vote. > > [ ] +1 Accept Rave into the incubator > [ ] +0 Don't care' > [ ] -1 Reject for the following reason: > > I'll close the vote at Tuesday morning 1st March CET to accommodate for the > coming weekend. That's a little over 5 days from now. > > Regards, > > Ate > > - COPY OF PROPOSAL FROM http://wiki.apache.org/incubator/RaveProposal > - > = Apache Rave Proposal = > > > == Abstract == > > Apache Rave is A new WEb And SOcial Mashup Engine. It will provide an > out-of-the-box as well as an extendible lightweight Java platform to host, > serve > and aggregate (Open)Social Gadgets and services through a highly customizable > and Web 2.0 friendly front-end. > Rave is targeted as engine for internet and intranet portals and as building > block to provide context-aware personalization and collaboration features for > multi-site/multi-channel (mobile) oriented and content driven websites and > (social) network oriented services and platforms. > For the [[http://www.opensocial.org/|OpenSocial]] container and services the > (Java) [[http://shindig.apache.org|Apache Shindig]] will be integrated. At a > later stage further generalization is envisioned to also transparently > support > [[http://www.w3.org/TR/widgets/|W3C Widgets]] using > [[http://incubator.apache.org/wookie/|Apache Wookie]]. > > > == Proposal == > > The reason for starting Rave is to bring together and combine several > existing > projects and teams currently working towards more or less the same or > overlapping goals but each in their own small(er) target audience and > community. > > The goal for Rave is to become a lightweight and open-standards based > extendible > platform for using, integrating and hosting !OpenSocial and W3C Widget > related > features, technologies and services. > It will also provide strong context-aware personalization, collaboration and > content integration capabilities and a high quality out-of-the-box > installation > as well as be easy to integrate in other platforms and solutions. > > The initial features for Rave will at least be based on the current > capabilities > from the contributing external projects, for which they will provide the > necessary code contributions. > However, the code base for Rave will be built anew with strong focus on > generalization, customization and extendibility to support the intended > multi-purpose adoption and integration. > The contributing external projects will start using and switch to the new > Rave > based solution as soon as the initial features become available to ensure the > continued participation and interest from their side as well as their own > communities. > > The intended initial features include: > > '''Core Features''' > 1. Advanced !OpenSocial compliance and optional features support > 1. !OpenSocial persistence and SPI (Service Provider Interface) > implementation > 1. Self-service application administration including security, gadget > management and page templates > 1. User and group management with full privacy model > 1. Gadget repository with life-cycle management (install/update/remove) and > extended meta data (categories, comments, ratings, etc.) > 1. Dynamic and highly customizable front-end engine (skins, pages, tabs, > layouts, navigation) > 1. Full OAuth support > 1. Support for security restrictions on both Gadgets and page/tag/layout > customizations > 1. Set of common and general purpose Gadgets to be usable out-of-the-box > 1. Support for inter-gadget messaging with examples > > '''Extensible Features''' > 1. Pluggable persistence > 1. Pluggable security model with example modules for authentication and > authorization > 1. Support for !OpenSocial extensions not (yet) defined in the specification > 1. Support for other (non-standard, yet) pluggable container services and > extensions > > Beyond these initial features the vision and scope for Rave goes much further > and includes integrating and providing other highly desired/needed features > like: > > * native W3C Widgets support through > [[http://incubator.apache.org/wookie|Apache Wookie]] > * pluggable and extendible content integration and management services > * space extensions and management features, like > http://wiki.opensocial.org/index.php?title=Space_extension > * context aware features and extensions integration for personalized and > social network and (mobile) device oriented sites and channels > * enhanced client-side widget messaging, coordination and co-location > support > like using [[http://www.openajax.org|OpenAjax]]
Re: [VOTE] Accept Rave into the Incubator
+1 On Fri, Feb 25, 2011 at 1:10 PM, Craig L Russell wrote: > +1 > > Craig > > On Feb 24, 2011, at 4:08 PM, Ate Douma wrote: > > Given the feedback received so far I think the Rave proposal is in good >> shape so I'd like to bring up the vote for accepting Rave into the >> Incubator. >> >> The proposal is at: http://wiki.apache.org/incubator/RaveProposal and >> also copied as text below. >> >> Please vote. >> >> [ ] +1 Accept Rave into the incubator >> [ ] +0 Don't care' >> [ ] -1 Reject for the following reason: >> >> I'll close the vote at Tuesday morning 1st March CET to accommodate for >> the coming weekend. That's a little over 5 days from now. >> >> Regards, >> >> Ate >> >> > > Craig L Russell > Secretary, Apache Software Foundation > Chair, OpenJPA PMC > c...@apache.org http://db.apache.org/jdo > > > > > > > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Kevin ___ This email, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost, if you receive it and you are not the intended recipient(s), or if it is transmitted/received in error. Any unauthorised use, alteration, disclosure, distribution or review of this email is prohibited. ___
Re: [VOTE] Accept Rave into the Incubator
On 2/24/2011 6:08 PM, Ate Douma wrote: > > [X] +1 Accept Rave into the incubator - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Rave into the Incubator
+1 Craig On Feb 24, 2011, at 4:08 PM, Ate Douma wrote: Given the feedback received so far I think the Rave proposal is in good shape so I'd like to bring up the vote for accepting Rave into the Incubator. The proposal is at: http://wiki.apache.org/incubator/RaveProposal and also copied as text below. Please vote. [ ] +1 Accept Rave into the incubator [ ] +0 Don't care' [ ] -1 Reject for the following reason: I'll close the vote at Tuesday morning 1st March CET to accommodate for the coming weekend. That's a little over 5 days from now. Regards, Ate Craig L Russell Secretary, Apache Software Foundation Chair, OpenJPA PMC c...@apache.org http://db.apache.org/jdo - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Rave into the Incubator
+1 Woonsan --- On Fri, 2/25/11, Ate Douma wrote: > From: Ate Douma > Subject: [VOTE] Accept Rave into the Incubator > To: general@incubator.apache.org > Date: Friday, February 25, 2011, 1:08 AM > Given the feedback received so far I > think the Rave proposal is in good shape so I'd like to > bring up the vote for accepting Rave into the Incubator. > > The proposal is at: http://wiki.apache.org/incubator/RaveProposal and also > copied as text below. > > Please vote. > > [ ] +1 Accept Rave into the incubator > [ ] +0 Don't care' > [ ] -1 Reject for the following reason: > > I'll close the vote at Tuesday morning 1st March CET to > accommodate for the coming weekend. That's a little over 5 > days from now. > > Regards, > > Ate > > - COPY OF PROPOSAL FROM http://wiki.apache.org/incubator/RaveProposal > - > = Apache Rave Proposal = > > > == Abstract == > > Apache Rave is A new WEb And SOcial Mashup Engine. It will > provide an out-of-the-box as well as an extendible > lightweight Java platform to host, serve and aggregate > (Open)Social Gadgets and services through a highly > customizable and Web 2.0 friendly front-end. > Rave is targeted as engine for internet and intranet > portals and as building block to provide context-aware > personalization and collaboration features for > multi-site/multi-channel (mobile) oriented and content > driven websites and (social) network oriented services and > platforms. > For the [[http://www.opensocial.org/|OpenSocial]] > container and services the (Java) [[http://shindig.apache.org|Apache > Shindig]] will be > integrated. At a later stage further generalization is > envisioned to also transparently support [[http://www.w3.org/TR/widgets/|W3C > Widgets]] using [[http://incubator.apache.org/wookie/|Apache Wookie]]. > > > == Proposal == > > The reason for starting Rave is to bring together and > combine several existing projects and teams currently > working towards more or less the same or overlapping goals > but each in their own small(er) target audience and > community. > > The goal for Rave is to become a lightweight and > open-standards based extendible platform for using, > integrating and hosting !OpenSocial and W3C Widget related > features, technologies and services. > It will also provide strong context-aware personalization, > collaboration and content integration capabilities and a > high quality out-of-the-box installation as well as be easy > to integrate in other platforms and solutions. > > The initial features for Rave will at least be based on the > current capabilities from the contributing external > projects, for which they will provide the necessary code > contributions. > However, the code base for Rave will be built anew with > strong focus on generalization, customization and > extendibility to support the intended multi-purpose adoption > and integration. > The contributing external projects will start using and > switch to the new Rave based solution as soon as the initial > features become available to ensure the continued > participation and interest from their side as well as their > own communities. > > The intended initial features include: > > '''Core Features''' > 1. Advanced !OpenSocial compliance and optional features > support > 1. !OpenSocial persistence and SPI (Service Provider > Interface) implementation > 1. Self-service application administration including > security, gadget management and page templates > 1. User and group management with full privacy model > 1. Gadget repository with life-cycle management > (install/update/remove) and extended meta data (categories, > comments, ratings, etc.) > 1. Dynamic and highly customizable front-end engine > (skins, pages, tabs, layouts, navigation) > 1. Full OAuth support > 1. Support for security restrictions on both Gadgets and > page/tag/layout customizations > 1. Set of common and general purpose Gadgets to be usable > out-of-the-box > 1. Support for inter-gadget messaging with examples > > '''Extensible Features''' > 1. Pluggable persistence > 1. Pluggable security model with example modules for > authentication and authorization > 1. Support for !OpenSocial extensions not (yet) defined in > the specification > 1. Support for other (non-standard, yet) pluggable > container services and extensions > > Beyond these initial features the vision and scope for Rave > goes much further and includes integrating and providing > other highly desired/needed features like: > > * native W3C Widgets support through > [[http://incubator.apache.org/wookie|Apache > Wookie]] > * pluggable and extendible content integration and > management services > * space extensions and management features, like > http://wiki.opensocial.org/index.php?title=Space_extension > * context aware features and extensions integration for > personalized and social network and (mobile) device oriented > sites and channels > * enhanced client-side widget messagin
Re: [VOTE] Accept Rave into the Incubator
+1 Mike On Thu, Feb 24, 2011 at 7:08 PM, Ate Douma wrote: > Given the feedback received so far I think the Rave proposal is in good > shape so I'd like to bring up the vote for accepting Rave into the > Incubator. > > The proposal is at: http://wiki.apache.org/incubator/RaveProposal and also > copied as text below. > > Please vote. > > [ ] +1 Accept Rave into the incubator > [ ] +0 Don't care' > [ ] -1 Reject for the following reason: > > I'll close the vote at Tuesday morning 1st March CET to accommodate for the > coming weekend. That's a little over 5 days from now. > > Regards, > > Ate > > - COPY OF PROPOSAL FROM http://wiki.apache.org/incubator/RaveProposal > - > = Apache Rave Proposal = > > > == Abstract == > > Apache Rave is A new WEb And SOcial Mashup Engine. It will provide an > out-of-the-box as well as an extendible lightweight Java platform to host, > serve and aggregate (Open)Social Gadgets and services through a highly > customizable and Web 2.0 friendly front-end. > Rave is targeted as engine for internet and intranet portals and as building > block to provide context-aware personalization and collaboration features > for multi-site/multi-channel (mobile) oriented and content driven websites > and (social) network oriented services and platforms. > For the [[http://www.opensocial.org/|OpenSocial]] container and services the > (Java) [[http://shindig.apache.org|Apache Shindig]] will be integrated. At a > later stage further generalization is envisioned to also transparently > support [[http://www.w3.org/TR/widgets/|W3C Widgets]] using > [[http://incubator.apache.org/wookie/|Apache Wookie]]. > > > == Proposal == > > The reason for starting Rave is to bring together and combine several > existing projects and teams currently working towards more or less the same > or overlapping goals but each in their own small(er) target audience and > community. > > The goal for Rave is to become a lightweight and open-standards based > extendible platform for using, integrating and hosting !OpenSocial and W3C > Widget related features, technologies and services. > It will also provide strong context-aware personalization, collaboration and > content integration capabilities and a high quality out-of-the-box > installation as well as be easy to integrate in other platforms and > solutions. > > The initial features for Rave will at least be based on the current > capabilities from the contributing external projects, for which they will > provide the necessary code contributions. > However, the code base for Rave will be built anew with strong focus on > generalization, customization and extendibility to support the intended > multi-purpose adoption and integration. > The contributing external projects will start using and switch to the new > Rave based solution as soon as the initial features become available to > ensure the continued participation and interest from their side as well as > their own communities. > > The intended initial features include: > > '''Core Features''' > 1. Advanced !OpenSocial compliance and optional features support > 1. !OpenSocial persistence and SPI (Service Provider Interface) > implementation > 1. Self-service application administration including security, gadget > management and page templates > 1. User and group management with full privacy model > 1. Gadget repository with life-cycle management (install/update/remove) and > extended meta data (categories, comments, ratings, etc.) > 1. Dynamic and highly customizable front-end engine (skins, pages, tabs, > layouts, navigation) > 1. Full OAuth support > 1. Support for security restrictions on both Gadgets and page/tag/layout > customizations > 1. Set of common and general purpose Gadgets to be usable out-of-the-box > 1. Support for inter-gadget messaging with examples > > '''Extensible Features''' > 1. Pluggable persistence > 1. Pluggable security model with example modules for authentication and > authorization > 1. Support for !OpenSocial extensions not (yet) defined in the > specification > 1. Support for other (non-standard, yet) pluggable container services and > extensions > > Beyond these initial features the vision and scope for Rave goes much > further and includes integrating and providing other highly desired/needed > features like: > > * native W3C Widgets support through > [[http://incubator.apache.org/wookie|Apache Wookie]] > * pluggable and extendible content integration and management services > * space extensions and management features, like > http://wiki.opensocial.org/index.php?title=Space_extension > * context aware features and extensions integration for personalized and > social network and (mobile) device oriented sites and channels > * enhanced client-side widget messaging, coordination and co-location > support like using [[http://www.openajax.org|OpenAjax]] Hub and Registry > * space, page and Gadget based linking, navigation, coordination and > collaboration
Re: [VOTE] Accept Rave into the Incubator
+ 1 --Suresh On Feb 24, 2011, at 7:08 PM, Ate Douma wrote: > Given the feedback received so far I think the Rave proposal is in good shape > so I'd like to bring up the vote for accepting Rave into the Incubator. > > The proposal is at: http://wiki.apache.org/incubator/RaveProposal and also > copied as text below. > > Please vote. > > [ ] +1 Accept Rave into the incubator > [ ] +0 Don't care' > [ ] -1 Reject for the following reason: > > I'll close the vote at Tuesday morning 1st March CET to accommodate for the > coming weekend. That's a little over 5 days from now. > > Regards, > > Ate > > - COPY OF PROPOSAL FROM http://wiki.apache.org/incubator/RaveProposal > - > = Apache Rave Proposal = > > > == Abstract == > > Apache Rave is A new WEb And SOcial Mashup Engine. It will provide an > out-of-the-box as well as an extendible lightweight Java platform to host, > serve and aggregate (Open)Social Gadgets and services through a highly > customizable and Web 2.0 friendly front-end. > Rave is targeted as engine for internet and intranet portals and as building > block to provide context-aware personalization and collaboration features for > multi-site/multi-channel (mobile) oriented and content driven websites and > (social) network oriented services and platforms. > For the [[http://www.opensocial.org/|OpenSocial]] container and services the > (Java) [[http://shindig.apache.org|Apache Shindig]] will be integrated. At a > later stage further generalization is envisioned to also transparently > support [[http://www.w3.org/TR/widgets/|W3C Widgets]] using > [[http://incubator.apache.org/wookie/|Apache Wookie]]. > > > == Proposal == > > The reason for starting Rave is to bring together and combine several > existing projects and teams currently working towards more or less the same > or overlapping goals but each in their own small(er) target audience and > community. > > The goal for Rave is to become a lightweight and open-standards based > extendible platform for using, integrating and hosting !OpenSocial and W3C > Widget related features, technologies and services. > It will also provide strong context-aware personalization, collaboration and > content integration capabilities and a high quality out-of-the-box > installation as well as be easy to integrate in other platforms and solutions. > > The initial features for Rave will at least be based on the current > capabilities from the contributing external projects, for which they will > provide the necessary code contributions. > However, the code base for Rave will be built anew with strong focus on > generalization, customization and extendibility to support the intended > multi-purpose adoption and integration. > The contributing external projects will start using and switch to the new > Rave based solution as soon as the initial features become available to > ensure the continued participation and interest from their side as well as > their own communities. > > The intended initial features include: > > '''Core Features''' > 1. Advanced !OpenSocial compliance and optional features support > 1. !OpenSocial persistence and SPI (Service Provider Interface) implementation > 1. Self-service application administration including security, gadget > management and page templates > 1. User and group management with full privacy model > 1. Gadget repository with life-cycle management (install/update/remove) and > extended meta data (categories, comments, ratings, etc.) > 1. Dynamic and highly customizable front-end engine (skins, pages, tabs, > layouts, navigation) > 1. Full OAuth support > 1. Support for security restrictions on both Gadgets and page/tag/layout > customizations > 1. Set of common and general purpose Gadgets to be usable out-of-the-box > 1. Support for inter-gadget messaging with examples > > '''Extensible Features''' > 1. Pluggable persistence > 1. Pluggable security model with example modules for authentication and > authorization > 1. Support for !OpenSocial extensions not (yet) defined in the specification > 1. Support for other (non-standard, yet) pluggable container services and > extensions > > Beyond these initial features the vision and scope for Rave goes much further > and includes integrating and providing other highly desired/needed features > like: > > * native W3C Widgets support through > [[http://incubator.apache.org/wookie|Apache Wookie]] > * pluggable and extendible content integration and management services > * space extensions and management features, like > http://wiki.opensocial.org/index.php?title=Space_extension > * context aware features and extensions integration for personalized and > social network and (mobile) device oriented sites and channels > * enhanced client-side widget messaging, coordination and co-location support > like using [[http://www.openajax.org|OpenAjax]] Hub and Registry > * space, page and Gadget based linking, navigation,
Re: [VOTE] Accept Rave into the Incubator
+1 -Matt - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Accept Rave into the Incubator
+1 Jesse >-Original Message- >From: Ate Douma [mailto:a...@douma.nu] >Sent: Thursday, February 24, 2011 7:08 PM >To: general@incubator.apache.org >Subject: [VOTE] Accept Rave into the Incubator > >Given the feedback received so far I think the Rave proposal is in good >shape so >I'd like to bring up the vote for accepting Rave into the Incubator. > >The proposal is at: http://wiki.apache.org/incubator/RaveProposal and >also >copied as text below. > >Please vote. > >[ ] +1 Accept Rave into the incubator >[ ] +0 Don't care' >[ ] -1 Reject for the following reason: > >I'll close the vote at Tuesday morning 1st March CET to accommodate for >the >coming weekend. That's a little over 5 days from now. > >Regards, > >Ate > >- COPY OF PROPOSAL FROM >http://wiki.apache.org/incubator/RaveProposal - >= Apache Rave Proposal = > > >== Abstract == > >Apache Rave is A new WEb And SOcial Mashup Engine. It will provide an >out-of-the-box as well as an extendible lightweight Java platform to >host, serve >and aggregate (Open)Social Gadgets and services through a highly >customizable >and Web 2.0 friendly front-end. >Rave is targeted as engine for internet and intranet portals and as >building >block to provide context-aware personalization and collaboration >features for >multi-site/multi-channel (mobile) oriented and content driven websites >and >(social) network oriented services and platforms. >For the [[http://www.opensocial.org/|OpenSocial]] container and services >the >(Java) [[http://shindig.apache.org|Apache Shindig]] will be integrated. >At a >later stage further generalization is envisioned to also transparently >support >[[http://www.w3.org/TR/widgets/|W3C Widgets]] using >[[http://incubator.apache.org/wookie/|Apache Wookie]]. > > >== Proposal == > >The reason for starting Rave is to bring together and combine several >existing >projects and teams currently working towards more or less the same or >overlapping goals but each in their own small(er) target audience and >community. > >The goal for Rave is to become a lightweight and open-standards based >extendible >platform for using, integrating and hosting !OpenSocial and W3C Widget >related >features, technologies and services. >It will also provide strong context-aware personalization, collaboration >and >content integration capabilities and a high quality out-of-the-box >installation >as well as be easy to integrate in other platforms and solutions. > >The initial features for Rave will at least be based on the current >capabilities >from the contributing external projects, for which they will provide the >necessary code contributions. >However, the code base for Rave will be built anew with strong focus on >generalization, customization and extendibility to support the intended >multi-purpose adoption and integration. >The contributing external projects will start using and switch to the >new Rave >based solution as soon as the initial features become available to >ensure the >continued participation and interest from their side as well as their >own >communities. > > The intended initial features include: > >'''Core Features''' > 1. Advanced !OpenSocial compliance and optional features support > 1. !OpenSocial persistence and SPI (Service Provider Interface) >implementation > 1. Self-service application administration including security, gadget >management and page templates > 1. User and group management with full privacy model > 1. Gadget repository with life-cycle management >(install/update/remove) and >extended meta data (categories, comments, ratings, etc.) > 1. Dynamic and highly customizable front-end engine (skins, pages, >tabs, >layouts, navigation) > 1. Full OAuth support > 1. Support for security restrictions on both Gadgets and >page/tag/layout >customizations > 1. Set of common and general purpose Gadgets to be usable out-of-the- >box > 1. Support for inter-gadget messaging with examples > >'''Extensible Features''' > 1. Pluggable persistence > 1. Pluggable security model with example modules for authentication >and >authorization > 1. Support for !OpenSocial extensions not (yet) defined in the >specification > 1. Support for other (non-standard, yet) pluggable container services >and >extensions > >Beyond these initial features the vision and scope for Rave goes much >further >and includes integrating and providing other highly desired/needed >features like: > > * native W3C Widgets support through >[[http://incubator.apache.org/wookie|Apache Wookie]] > * pluggable and extendible content integration and management services > * space extensions and management features, like >http://wiki.opensocial.org/index.php?title=Space_extension > * context aware features and extensions integration for personalized >and >social network and (mobile) device oriented sites and channels > * enhanced client-side widget messaging, coordination and co-location >support >like using [[http://www.openajax.org|OpenAjax]] Hu
Re: [VOTE] Accept Rave into the Incubator
+1 On Fri, Feb 25, 2011 at 5:30 AM, Arje Cahn wrote: >> >> [X] +1 Accept Rave into the incubator >> > > > - Arjé > -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Rave into the Incubator
> > [X] +1 Accept Rave into the incubator > - Arjé
Re: [VOTE] Accept Rave into the Incubator
+1 On Thu, Feb 24, 2011 at 4:08 PM, Ate Douma wrote: > Given the feedback received so far I think the Rave proposal is in good > shape so I'd like to bring up the vote for accepting Rave into the > Incubator. > > The proposal is at: http://wiki.apache.org/incubator/RaveProposal and also > copied as text below. > > Please vote. > > [ ] +1 Accept Rave into the incubator > [ ] +0 Don't care' > [ ] -1 Reject for the following reason: > > I'll close the vote at Tuesday morning 1st March CET to accommodate for the > coming weekend. That's a little over 5 days from now. > > Regards, > > Ate > > - COPY OF PROPOSAL FROM http://wiki.apache.org/incubator/RaveProposal > - > = Apache Rave Proposal = > > > == Abstract == > > Apache Rave is A new WEb And SOcial Mashup Engine. It will provide an > out-of-the-box as well as an extendible lightweight Java platform to host, > serve and aggregate (Open)Social Gadgets and services through a highly > customizable and Web 2.0 friendly front-end. > Rave is targeted as engine for internet and intranet portals and as building > block to provide context-aware personalization and collaboration features > for multi-site/multi-channel (mobile) oriented and content driven websites > and (social) network oriented services and platforms. > For the [[http://www.opensocial.org/|OpenSocial]] container and services the > (Java) [[http://shindig.apache.org|Apache Shindig]] will be integrated. At a > later stage further generalization is envisioned to also transparently > support [[http://www.w3.org/TR/widgets/|W3C Widgets]] using > [[http://incubator.apache.org/wookie/|Apache Wookie]]. > > > == Proposal == > > The reason for starting Rave is to bring together and combine several > existing projects and teams currently working towards more or less the same > or overlapping goals but each in their own small(er) target audience and > community. > > The goal for Rave is to become a lightweight and open-standards based > extendible platform for using, integrating and hosting !OpenSocial and W3C > Widget related features, technologies and services. > It will also provide strong context-aware personalization, collaboration and > content integration capabilities and a high quality out-of-the-box > installation as well as be easy to integrate in other platforms and > solutions. > > The initial features for Rave will at least be based on the current > capabilities from the contributing external projects, for which they will > provide the necessary code contributions. > However, the code base for Rave will be built anew with strong focus on > generalization, customization and extendibility to support the intended > multi-purpose adoption and integration. > The contributing external projects will start using and switch to the new > Rave based solution as soon as the initial features become available to > ensure the continued participation and interest from their side as well as > their own communities. > > The intended initial features include: > > '''Core Features''' > 1. Advanced !OpenSocial compliance and optional features support > 1. !OpenSocial persistence and SPI (Service Provider Interface) > implementation > 1. Self-service application administration including security, gadget > management and page templates > 1. User and group management with full privacy model > 1. Gadget repository with life-cycle management (install/update/remove) and > extended meta data (categories, comments, ratings, etc.) > 1. Dynamic and highly customizable front-end engine (skins, pages, tabs, > layouts, navigation) > 1. Full OAuth support > 1. Support for security restrictions on both Gadgets and page/tag/layout > customizations > 1. Set of common and general purpose Gadgets to be usable out-of-the-box > 1. Support for inter-gadget messaging with examples > > '''Extensible Features''' > 1. Pluggable persistence > 1. Pluggable security model with example modules for authentication and > authorization > 1. Support for !OpenSocial extensions not (yet) defined in the > specification > 1. Support for other (non-standard, yet) pluggable container services and > extensions > > Beyond these initial features the vision and scope for Rave goes much > further and includes integrating and providing other highly desired/needed > features like: > > * native W3C Widgets support through > [[http://incubator.apache.org/wookie|Apache Wookie]] > * pluggable and extendible content integration and management services > * space extensions and management features, like > http://wiki.opensocial.org/index.php?title=Space_extension > * context aware features and extensions integration for personalized and > social network and (mobile) device oriented sites and channels > * enhanced client-side widget messaging, coordination and co-location > support like using [[http://www.openajax.org|OpenAjax]] Hub and Registry > * space, page and Gadget based linking, navigation, coordination and > collaboration > * i
Re: [VOTE] Accept Rave into the Incubator
+1 Upayavira On Fri, 25 Feb 2011 01:08 +0100, "Ate Douma" wrote: > Given the feedback received so far I think the Rave proposal is in good > shape so > I'd like to bring up the vote for accepting Rave into the Incubator. > > The proposal is at: http://wiki.apache.org/incubator/RaveProposal and > also > copied as text below. > > Please vote. > > [ ] +1 Accept Rave into the incubator > [ ] +0 Don't care' > [ ] -1 Reject for the following reason: > > I'll close the vote at Tuesday morning 1st March CET to accommodate for > the > coming weekend. That's a little over 5 days from now. > > Regards, > > Ate > > - COPY OF PROPOSAL FROM http://wiki.apache.org/incubator/RaveProposal > - > = Apache Rave Proposal = > > > == Abstract == > > Apache Rave is A new WEb And SOcial Mashup Engine. It will provide an > out-of-the-box as well as an extendible lightweight Java platform to > host, serve > and aggregate (Open)Social Gadgets and services through a highly > customizable > and Web 2.0 friendly front-end. > Rave is targeted as engine for internet and intranet portals and as > building > block to provide context-aware personalization and collaboration features > for > multi-site/multi-channel (mobile) oriented and content driven websites > and > (social) network oriented services and platforms. > For the [[http://www.opensocial.org/|OpenSocial]] container and services > the > (Java) [[http://shindig.apache.org|Apache Shindig]] will be integrated. > At a > later stage further generalization is envisioned to also transparently > support > [[http://www.w3.org/TR/widgets/|W3C Widgets]] using > [[http://incubator.apache.org/wookie/|Apache Wookie]]. > > > == Proposal == > > The reason for starting Rave is to bring together and combine several > existing > projects and teams currently working towards more or less the same or > overlapping goals but each in their own small(er) target audience and > community. > > The goal for Rave is to become a lightweight and open-standards based > extendible > platform for using, integrating and hosting !OpenSocial and W3C Widget > related > features, technologies and services. > It will also provide strong context-aware personalization, collaboration > and > content integration capabilities and a high quality out-of-the-box > installation > as well as be easy to integrate in other platforms and solutions. > > The initial features for Rave will at least be based on the current > capabilities > from the contributing external projects, for which they will provide the > necessary code contributions. > However, the code base for Rave will be built anew with strong focus on > generalization, customization and extendibility to support the intended > multi-purpose adoption and integration. > The contributing external projects will start using and switch to the new > Rave > based solution as soon as the initial features become available to ensure > the > continued participation and interest from their side as well as their own > communities. > > The intended initial features include: > > '''Core Features''' > 1. Advanced !OpenSocial compliance and optional features support > 1. !OpenSocial persistence and SPI (Service Provider Interface) > implementation > 1. Self-service application administration including security, gadget > management and page templates > 1. User and group management with full privacy model > 1. Gadget repository with life-cycle management (install/update/remove) > and > extended meta data (categories, comments, ratings, etc.) > 1. Dynamic and highly customizable front-end engine (skins, pages, > tabs, > layouts, navigation) > 1. Full OAuth support > 1. Support for security restrictions on both Gadgets and > page/tag/layout > customizations > 1. Set of common and general purpose Gadgets to be usable > out-of-the-box > 1. Support for inter-gadget messaging with examples > > '''Extensible Features''' > 1. Pluggable persistence > 1. Pluggable security model with example modules for authentication and > authorization > 1. Support for !OpenSocial extensions not (yet) defined in the > specification > 1. Support for other (non-standard, yet) pluggable container services > and > extensions > > Beyond these initial features the vision and scope for Rave goes much > further > and includes integrating and providing other highly desired/needed > features like: > > * native W3C Widgets support through > [[http://incubator.apache.org/wookie|Apache Wookie]] > * pluggable and extendible content integration and management services > * space extensions and management features, like > http://wiki.opensocial.org/index.php?title=Space_extension > * context aware features and extensions integration for personalized > and > social network and (mobile) device oriented sites and channels > * enhanced client-side widget messaging, coordination and co-location > support > li
Re: [VOTE] Accept Rave into the Incubator
[X] +1 Accept Rave into the incubator - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Rave into the Incubator
+1 Niels On 02/25/2011 01:08 AM, Ate Douma wrote: > Given the feedback received so far I think the Rave proposal is in > good shape so I'd like to bring up the vote for accepting Rave into > the Incubator. > > The proposal is at: http://wiki.apache.org/incubator/RaveProposal and > also copied as text below. > > Please vote. > > [ ] +1 Accept Rave into the incubator > [ ] +0 Don't care' > [ ] -1 Reject for the following reason: > > I'll close the vote at Tuesday morning 1st March CET to accommodate > for the coming weekend. That's a little over 5 days from now. > > Regards, > > Ate > > - COPY OF PROPOSAL FROM > http://wiki.apache.org/incubator/RaveProposal - > = Apache Rave Proposal = > > > == Abstract == > > Apache Rave is A new WEb And SOcial Mashup Engine. It will provide an > out-of-the-box as well as an extendible lightweight Java platform to > host, serve and aggregate (Open)Social Gadgets and services through a > highly customizable and Web 2.0 friendly front-end. > Rave is targeted as engine for internet and intranet portals and as > building block to provide context-aware personalization and > collaboration features for multi-site/multi-channel (mobile) oriented > and content driven websites and (social) network oriented services and > platforms. > For the [[http://www.opensocial.org/|OpenSocial]] container and > services the (Java) [[http://shindig.apache.org|Apache Shindig]] will > be integrated. At a later stage further generalization is envisioned > to also transparently support [[http://www.w3.org/TR/widgets/|W3C > Widgets]] using [[http://incubator.apache.org/wookie/|Apache Wookie]]. > > > == Proposal == > > The reason for starting Rave is to bring together and combine several > existing projects and teams currently working towards more or less the > same or overlapping goals but each in their own small(er) target > audience and community. > > The goal for Rave is to become a lightweight and open-standards based > extendible platform for using, integrating and hosting !OpenSocial and > W3C Widget related features, technologies and services. > It will also provide strong context-aware personalization, > collaboration and content integration capabilities and a high quality > out-of-the-box installation as well as be easy to integrate in other > platforms and solutions. > > The initial features for Rave will at least be based on the current > capabilities from the contributing external projects, for which they > will provide the necessary code contributions. > However, the code base for Rave will be built anew with strong focus > on generalization, customization and extendibility to support the > intended multi-purpose adoption and integration. > The contributing external projects will start using and switch to the > new Rave based solution as soon as the initial features become > available to ensure the continued participation and interest from > their side as well as their own communities. > > The intended initial features include: > > '''Core Features''' > 1. Advanced !OpenSocial compliance and optional features support > 1. !OpenSocial persistence and SPI (Service Provider Interface) > implementation > 1. Self-service application administration including security, gadget > management and page templates > 1. User and group management with full privacy model > 1. Gadget repository with life-cycle management > (install/update/remove) and extended meta data (categories, comments, > ratings, etc.) > 1. Dynamic and highly customizable front-end engine (skins, pages, > tabs, layouts, navigation) > 1. Full OAuth support > 1. Support for security restrictions on both Gadgets and > page/tag/layout customizations > 1. Set of common and general purpose Gadgets to be usable out-of-the-box > 1. Support for inter-gadget messaging with examples > > '''Extensible Features''' > 1. Pluggable persistence > 1. Pluggable security model with example modules for authentication > and authorization > 1. Support for !OpenSocial extensions not (yet) defined in the > specification > 1. Support for other (non-standard, yet) pluggable container services > and extensions > > Beyond these initial features the vision and scope for Rave goes much > further and includes integrating and providing other highly > desired/needed features like: > > * native W3C Widgets support through > [[http://incubator.apache.org/wookie|Apache Wookie]] > * pluggable and extendible content integration and management services > * space extensions and management features, like > http://wiki.opensocial.org/index.php?title=Space_extension > * context aware features and extensions integration for personalized > and social network and (mobile) device oriented sites and channels > * enhanced client-side widget messaging, coordination and co-location > support like using [[http://www.openajax.org|OpenAjax]] Hub and Registry > * space, page and Gadget based linking, navigation, coordination and > collaboration > *
Re: [VOTE] Accept Rave into the Incubator
Here is my own vote: +1 Ate - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Accept Rave into the Incubator
+1 Sander > From: Ate Douma [mailto:a...@douma.nu] > Sent: 25 February 2011 00:08 > To: general@incubator.apache.org > Subject: [VOTE] Accept Rave into the Incubator > > Given the feedback received so far I think the Rave proposal is in good > shape so > I'd like to bring up the vote for accepting Rave into the Incubator. > > The proposal is at: http://wiki.apache.org/incubator/RaveProposal and also > copied as text below. > > Please vote. > > [ ] +1 Accept Rave into the incubator > [ ] +0 Don't care' > [ ] -1 Reject for the following reason: > > I'll close the vote at Tuesday morning 1st March CET to accommodate for the > coming weekend. That's a little over 5 days from now. > > Regards, > > Ate > > - COPY OF PROPOSAL FROM http://wiki.apache.org/incubator/RaveProposal - > > = Apache Rave Proposal = > > > == Abstract == > > Apache Rave is A new WEb And SOcial Mashup Engine. It will provide an > out-of-the-box as well as an extendible lightweight Java platform to host, > serve > and aggregate (Open)Social Gadgets and services through a highly > customizable > and Web 2.0 friendly front-end. > Rave is targeted as engine for internet and intranet portals and as > building > block to provide context-aware personalization and collaboration features > for > multi-site/multi-channel (mobile) oriented and content driven websites and > (social) network oriented services and platforms. > For the [[http://www.opensocial.org/|OpenSocial]] container and services > the > (Java) [[http://shindig.apache.org|Apache Shindig]] will be integrated. At > a > later stage further generalization is envisioned to also transparently > support > [[http://www.w3.org/TR/widgets/|W3C Widgets]] using > [[http://incubator.apache.org/wookie/|Apache Wookie]]. > > > == Proposal == > > The reason for starting Rave is to bring together and combine several > existing > projects and teams currently working towards more or less the same or > overlapping goals but each in their own small(er) target audience and > community. > > The goal for Rave is to become a lightweight and open-standards based > extendible > platform for using, integrating and hosting !OpenSocial and W3C Widget > related > features, technologies and services. > It will also provide strong context-aware personalization, collaboration > and > content integration capabilities and a high quality out-of-the-box > installation > as well as be easy to integrate in other platforms and solutions. > > The initial features for Rave will at least be based on the current > capabilities > from the contributing external projects, for which they will provide the > necessary code contributions. > However, the code base for Rave will be built anew with strong focus on > generalization, customization and extendibility to support the intended > multi-purpose adoption and integration. > The contributing external projects will start using and switch to the new > Rave > based solution as soon as the initial features become available to ensure > the > continued participation and interest from their side as well as their own > communities. > > The intended initial features include: > > '''Core Features''' > 1. Advanced !OpenSocial compliance and optional features support > 1. !OpenSocial persistence and SPI (Service Provider Interface) > implementation > 1. Self-service application administration including security, gadget > management and page templates > 1. User and group management with full privacy model > 1. Gadget repository with life-cycle management (install/update/remove) > and > extended meta data (categories, comments, ratings, etc.) > 1. Dynamic and highly customizable front-end engine (skins, pages, tabs, > layouts, navigation) > 1. Full OAuth support > 1. Support for security restrictions on both Gadgets and page/tag/layout > customizations > 1. Set of common and general purpose Gadgets to be usable out-of-the-box > 1. Support for inter-gadget messaging with examples > > '''Extensible Features''' > 1. Pluggable persistence > 1. Pluggable security model with example modules for authentication and > authorization > 1. Support for !OpenSocial extensions not (yet) defined in the > specification > 1. Support for other (non-standard, yet) pluggable container services and > extensions > > Beyond these initial features the vision and scope for Rave goes much > further > and includes integrating and providing other highly desired/needed features > like: > > * native W3C Widgets support through > [[http://incubator.apache.org/wookie|Apache Wookie]] > * pluggable and extendible content integration and management services > * space extensions and management features, like > http://wiki.opensocial.org/index.php?title=Space_extension > * context aware features and extensions integration for personalized and > social network and (mobile) device oriented sites and channels > * enhanced client-side widget messaging, coordination and co-location >
Re: [VOTE] Accept Rave into the Incubator
[x] +1 Accept Rave into the incubator (binding) Sylvain -- Sylvain Wallez - http://bluxte.net - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Rave into the Incubator
[X] +1 Accept Rave into the incubator On 25 Feb 2011, at 00:08, Ate Douma wrote: > Given the feedback received so far I think the Rave proposal is in good shape > so I'd like to bring up the vote for accepting Rave into the Incubator. > > The proposal is at: http://wiki.apache.org/incubator/RaveProposal and also > copied as text below. > > Please vote. > > [ ] +1 Accept Rave into the incubator > [ ] +0 Don't care' > [ ] -1 Reject for the following reason: > > I'll close the vote at Tuesday morning 1st March CET to accommodate for the > coming weekend. That's a little over 5 days from now. > > Regards, > > Ate > > - COPY OF PROPOSAL FROM http://wiki.apache.org/incubator/RaveProposal > - > = Apache Rave Proposal = > > > == Abstract == > > Apache Rave is A new WEb And SOcial Mashup Engine. It will provide an > out-of-the-box as well as an extendible lightweight Java platform to host, > serve and aggregate (Open)Social Gadgets and services through a highly > customizable and Web 2.0 friendly front-end. > Rave is targeted as engine for internet and intranet portals and as building > block to provide context-aware personalization and collaboration features for > multi-site/multi-channel (mobile) oriented and content driven websites and > (social) network oriented services and platforms. > For the [[http://www.opensocial.org/|OpenSocial]] container and services the > (Java) [[http://shindig.apache.org|Apache Shindig]] will be integrated. At a > later stage further generalization is envisioned to also transparently > support [[http://www.w3.org/TR/widgets/|W3C Widgets]] using > [[http://incubator.apache.org/wookie/|Apache Wookie]]. > > > == Proposal == > > The reason for starting Rave is to bring together and combine several > existing projects and teams currently working towards more or less the same > or overlapping goals but each in their own small(er) target audience and > community. > > The goal for Rave is to become a lightweight and open-standards based > extendible platform for using, integrating and hosting !OpenSocial and W3C > Widget related features, technologies and services. > It will also provide strong context-aware personalization, collaboration and > content integration capabilities and a high quality out-of-the-box > installation as well as be easy to integrate in other platforms and solutions. > > The initial features for Rave will at least be based on the current > capabilities from the contributing external projects, for which they will > provide the necessary code contributions. > However, the code base for Rave will be built anew with strong focus on > generalization, customization and extendibility to support the intended > multi-purpose adoption and integration. > The contributing external projects will start using and switch to the new > Rave based solution as soon as the initial features become available to > ensure the continued participation and interest from their side as well as > their own communities. > > The intended initial features include: > > '''Core Features''' > 1. Advanced !OpenSocial compliance and optional features support > 1. !OpenSocial persistence and SPI (Service Provider Interface) implementation > 1. Self-service application administration including security, gadget > management and page templates > 1. User and group management with full privacy model > 1. Gadget repository with life-cycle management (install/update/remove) and > extended meta data (categories, comments, ratings, etc.) > 1. Dynamic and highly customizable front-end engine (skins, pages, tabs, > layouts, navigation) > 1. Full OAuth support > 1. Support for security restrictions on both Gadgets and page/tag/layout > customizations > 1. Set of common and general purpose Gadgets to be usable out-of-the-box > 1. Support for inter-gadget messaging with examples > > '''Extensible Features''' > 1. Pluggable persistence > 1. Pluggable security model with example modules for authentication and > authorization > 1. Support for !OpenSocial extensions not (yet) defined in the specification > 1. Support for other (non-standard, yet) pluggable container services and > extensions > > Beyond these initial features the vision and scope for Rave goes much further > and includes integrating and providing other highly desired/needed features > like: > > * native W3C Widgets support through > [[http://incubator.apache.org/wookie|Apache Wookie]] > * pluggable and extendible content integration and management services > * space extensions and management features, like > http://wiki.opensocial.org/index.php?title=Space_extension > * context aware features and extensions integration for personalized and > social network and (mobile) device oriented sites and channels > * enhanced client-side widget messaging, coordination and co-location support > like using [[http://www.openajax.org|OpenAjax]] Hub and Registry > * space, page and Gadget based
Re: [VOTE] Accept Rave into the Incubator
+1 Hadrian On Feb 24, 2011, at 7:08 PM, Ate Douma wrote: > Given the feedback received so far I think the Rave proposal is in good shape > so I'd like to bring up the vote for accepting Rave into the Incubator. > > The proposal is at: http://wiki.apache.org/incubator/RaveProposal and also > copied as text below. > > Please vote. > > [ ] +1 Accept Rave into the incubator > [ ] +0 Don't care' > [ ] -1 Reject for the following reason: > > I'll close the vote at Tuesday morning 1st March CET to accommodate for the > coming weekend. That's a little over 5 days from now. > > Regards, > > Ate > > - COPY OF PROPOSAL FROM http://wiki.apache.org/incubator/RaveProposal > - > = Apache Rave Proposal = > > > == Abstract == > > Apache Rave is A new WEb And SOcial Mashup Engine. It will provide an > out-of-the-box as well as an extendible lightweight Java platform to host, > serve and aggregate (Open)Social Gadgets and services through a highly > customizable and Web 2.0 friendly front-end. > Rave is targeted as engine for internet and intranet portals and as building > block to provide context-aware personalization and collaboration features for > multi-site/multi-channel (mobile) oriented and content driven websites and > (social) network oriented services and platforms. > For the [[http://www.opensocial.org/|OpenSocial]] container and services the > (Java) [[http://shindig.apache.org|Apache Shindig]] will be integrated. At a > later stage further generalization is envisioned to also transparently > support [[http://www.w3.org/TR/widgets/|W3C Widgets]] using > [[http://incubator.apache.org/wookie/|Apache Wookie]]. > > > == Proposal == > > The reason for starting Rave is to bring together and combine several > existing projects and teams currently working towards more or less the same > or overlapping goals but each in their own small(er) target audience and > community. > > The goal for Rave is to become a lightweight and open-standards based > extendible platform for using, integrating and hosting !OpenSocial and W3C > Widget related features, technologies and services. > It will also provide strong context-aware personalization, collaboration and > content integration capabilities and a high quality out-of-the-box > installation as well as be easy to integrate in other platforms and solutions. > > The initial features for Rave will at least be based on the current > capabilities from the contributing external projects, for which they will > provide the necessary code contributions. > However, the code base for Rave will be built anew with strong focus on > generalization, customization and extendibility to support the intended > multi-purpose adoption and integration. > The contributing external projects will start using and switch to the new > Rave based solution as soon as the initial features become available to > ensure the continued participation and interest from their side as well as > their own communities. > > The intended initial features include: > > '''Core Features''' > 1. Advanced !OpenSocial compliance and optional features support > 1. !OpenSocial persistence and SPI (Service Provider Interface) implementation > 1. Self-service application administration including security, gadget > management and page templates > 1. User and group management with full privacy model > 1. Gadget repository with life-cycle management (install/update/remove) and > extended meta data (categories, comments, ratings, etc.) > 1. Dynamic and highly customizable front-end engine (skins, pages, tabs, > layouts, navigation) > 1. Full OAuth support > 1. Support for security restrictions on both Gadgets and page/tag/layout > customizations > 1. Set of common and general purpose Gadgets to be usable out-of-the-box > 1. Support for inter-gadget messaging with examples > > '''Extensible Features''' > 1. Pluggable persistence > 1. Pluggable security model with example modules for authentication and > authorization > 1. Support for !OpenSocial extensions not (yet) defined in the specification > 1. Support for other (non-standard, yet) pluggable container services and > extensions > > Beyond these initial features the vision and scope for Rave goes much further > and includes integrating and providing other highly desired/needed features > like: > > * native W3C Widgets support through > [[http://incubator.apache.org/wookie|Apache Wookie]] > * pluggable and extendible content integration and management services > * space extensions and management features, like > http://wiki.opensocial.org/index.php?title=Space_extension > * context aware features and extensions integration for personalized and > social network and (mobile) device oriented sites and channels > * enhanced client-side widget messaging, coordination and co-location support > like using [[http://www.openajax.org|OpenAjax]] Hub and Registry > * space, page and Gadget based linking, navigation,
Re: [VOTE] Accept Rave into the Incubator
On 25/02/2011 00:08, Ate Douma wrote: [+1] +1 Accept Rave into the incubator +1 Binding - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Rave into the Incubator
> [X ] +1 Accept Rave into the incubator -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Rave into the Incubator
+1 ...ant On Fri, Feb 25, 2011 at 12:08 AM, Ate Douma wrote: > Given the feedback received so far I think the Rave proposal is in good > shape so I'd like to bring up the vote for accepting Rave into the > Incubator. > > The proposal is at: http://wiki.apache.org/incubator/RaveProposal and also > copied as text below. > > Please vote. > > [ ] +1 Accept Rave into the incubator > [ ] +0 Don't care' > [ ] -1 Reject for the following reason: > > I'll close the vote at Tuesday morning 1st March CET to accommodate for the > coming weekend. That's a little over 5 days from now. > > Regards, > > Ate > > - COPY OF PROPOSAL FROM http://wiki.apache.org/incubator/RaveProposal > - > = Apache Rave Proposal = > > > == Abstract == > > Apache Rave is A new WEb And SOcial Mashup Engine. It will provide an > out-of-the-box as well as an extendible lightweight Java platform to host, > serve and aggregate (Open)Social Gadgets and services through a highly > customizable and Web 2.0 friendly front-end. > Rave is targeted as engine for internet and intranet portals and as building > block to provide context-aware personalization and collaboration features > for multi-site/multi-channel (mobile) oriented and content driven websites > and (social) network oriented services and platforms. > For the [[http://www.opensocial.org/|OpenSocial]] container and services the > (Java) [[http://shindig.apache.org|Apache Shindig]] will be integrated. At a > later stage further generalization is envisioned to also transparently > support [[http://www.w3.org/TR/widgets/|W3C Widgets]] using > [[http://incubator.apache.org/wookie/|Apache Wookie]]. > > > == Proposal == > > The reason for starting Rave is to bring together and combine several > existing projects and teams currently working towards more or less the same > or overlapping goals but each in their own small(er) target audience and > community. > > The goal for Rave is to become a lightweight and open-standards based > extendible platform for using, integrating and hosting !OpenSocial and W3C > Widget related features, technologies and services. > It will also provide strong context-aware personalization, collaboration and > content integration capabilities and a high quality out-of-the-box > installation as well as be easy to integrate in other platforms and > solutions. > > The initial features for Rave will at least be based on the current > capabilities from the contributing external projects, for which they will > provide the necessary code contributions. > However, the code base for Rave will be built anew with strong focus on > generalization, customization and extendibility to support the intended > multi-purpose adoption and integration. > The contributing external projects will start using and switch to the new > Rave based solution as soon as the initial features become available to > ensure the continued participation and interest from their side as well as > their own communities. > > The intended initial features include: > > '''Core Features''' > 1. Advanced !OpenSocial compliance and optional features support > 1. !OpenSocial persistence and SPI (Service Provider Interface) > implementation > 1. Self-service application administration including security, gadget > management and page templates > 1. User and group management with full privacy model > 1. Gadget repository with life-cycle management (install/update/remove) and > extended meta data (categories, comments, ratings, etc.) > 1. Dynamic and highly customizable front-end engine (skins, pages, tabs, > layouts, navigation) > 1. Full OAuth support > 1. Support for security restrictions on both Gadgets and page/tag/layout > customizations > 1. Set of common and general purpose Gadgets to be usable out-of-the-box > 1. Support for inter-gadget messaging with examples > > '''Extensible Features''' > 1. Pluggable persistence > 1. Pluggable security model with example modules for authentication and > authorization > 1. Support for !OpenSocial extensions not (yet) defined in the > specification > 1. Support for other (non-standard, yet) pluggable container services and > extensions > > Beyond these initial features the vision and scope for Rave goes much > further and includes integrating and providing other highly desired/needed > features like: > > * native W3C Widgets support through > [[http://incubator.apache.org/wookie|Apache Wookie]] > * pluggable and extendible content integration and management services > * space extensions and management features, like > http://wiki.opensocial.org/index.php?title=Space_extension > * context aware features and extensions integration for personalized and > social network and (mobile) device oriented sites and channels > * enhanced client-side widget messaging, coordination and co-location > support like using [[http://www.openajax.org|OpenAjax]] Hub and Registry > * space, page and Gadget based linking, navigation, coordination and > collabor
Re: [VOTE] Accept Rave into the Incubator
+1 Regards, Alan On Feb 24, 2011, at 4:08 PM, Ate Douma wrote: > Given the feedback received so far I think the Rave proposal is in good shape > so I'd like to bring up the vote for accepting Rave into the Incubator. > > The proposal is at: http://wiki.apache.org/incubator/RaveProposal and also > copied as text below. > > Please vote. > > [ ] +1 Accept Rave into the incubator > [ ] +0 Don't care' > [ ] -1 Reject for the following reason: > > I'll close the vote at Tuesday morning 1st March CET to accommodate for the > coming weekend. That's a little over 5 days from now. > > Regards, > > Ate > > - COPY OF PROPOSAL FROM http://wiki.apache.org/incubator/RaveProposal > - > = Apache Rave Proposal = > > > == Abstract == > > Apache Rave is A new WEb And SOcial Mashup Engine. It will provide an > out-of-the-box as well as an extendible lightweight Java platform to host, > serve and aggregate (Open)Social Gadgets and services through a highly > customizable and Web 2.0 friendly front-end. > Rave is targeted as engine for internet and intranet portals and as building > block to provide context-aware personalization and collaboration features for > multi-site/multi-channel (mobile) oriented and content driven websites and > (social) network oriented services and platforms. > For the [[http://www.opensocial.org/|OpenSocial]] container and services the > (Java) [[http://shindig.apache.org|Apache Shindig]] will be integrated. At a > later stage further generalization is envisioned to also transparently > support [[http://www.w3.org/TR/widgets/|W3C Widgets]] using > [[http://incubator.apache.org/wookie/|Apache Wookie]]. > > > == Proposal == > > The reason for starting Rave is to bring together and combine several > existing projects and teams currently working towards more or less the same > or overlapping goals but each in their own small(er) target audience and > community. > > The goal for Rave is to become a lightweight and open-standards based > extendible platform for using, integrating and hosting !OpenSocial and W3C > Widget related features, technologies and services. > It will also provide strong context-aware personalization, collaboration and > content integration capabilities and a high quality out-of-the-box > installation as well as be easy to integrate in other platforms and solutions. > > The initial features for Rave will at least be based on the current > capabilities from the contributing external projects, for which they will > provide the necessary code contributions. > However, the code base for Rave will be built anew with strong focus on > generalization, customization and extendibility to support the intended > multi-purpose adoption and integration. > The contributing external projects will start using and switch to the new > Rave based solution as soon as the initial features become available to > ensure the continued participation and interest from their side as well as > their own communities. > > The intended initial features include: > > '''Core Features''' > 1. Advanced !OpenSocial compliance and optional features support > 1. !OpenSocial persistence and SPI (Service Provider Interface) implementation > 1. Self-service application administration including security, gadget > management and page templates > 1. User and group management with full privacy model > 1. Gadget repository with life-cycle management (install/update/remove) and > extended meta data (categories, comments, ratings, etc.) > 1. Dynamic and highly customizable front-end engine (skins, pages, tabs, > layouts, navigation) > 1. Full OAuth support > 1. Support for security restrictions on both Gadgets and page/tag/layout > customizations > 1. Set of common and general purpose Gadgets to be usable out-of-the-box > 1. Support for inter-gadget messaging with examples > > '''Extensible Features''' > 1. Pluggable persistence > 1. Pluggable security model with example modules for authentication and > authorization > 1. Support for !OpenSocial extensions not (yet) defined in the specification > 1. Support for other (non-standard, yet) pluggable container services and > extensions > > Beyond these initial features the vision and scope for Rave goes much further > and includes integrating and providing other highly desired/needed features > like: > > * native W3C Widgets support through > [[http://incubator.apache.org/wookie|Apache Wookie]] > * pluggable and extendible content integration and management services > * space extensions and management features, like > http://wiki.opensocial.org/index.php?title=Space_extension > * context aware features and extensions integration for personalized and > social network and (mobile) device oriented sites and channels > * enhanced client-side widget messaging, coordination and co-location support > like using [[http://www.openajax.org|OpenAjax]] Hub and Registry > * space, page and Gadget based linking, navigat
Re: [VOTE] Accept Rave into the Incubator
+1 Ralph On Feb 24, 2011, at 4:08 PM, Ate Douma wrote: > Given the feedback received so far I think the Rave proposal is in good shape > so I'd like to bring up the vote for accepting Rave into the Incubator. > > The proposal is at: http://wiki.apache.org/incubator/RaveProposal and also > copied as text below. > > Please vote. > > [ ] +1 Accept Rave into the incubator > [ ] +0 Don't care' > [ ] -1 Reject for the following reason: > > I'll close the vote at Tuesday morning 1st March CET to accommodate for the > coming weekend. That's a little over 5 days from now. > > Regards, > > Ate > > - COPY OF PROPOSAL FROM http://wiki.apache.org/incubator/RaveProposal > - > = Apache Rave Proposal = > > > == Abstract == > > Apache Rave is A new WEb And SOcial Mashup Engine. It will provide an > out-of-the-box as well as an extendible lightweight Java platform to host, > serve and aggregate (Open)Social Gadgets and services through a highly > customizable and Web 2.0 friendly front-end. > Rave is targeted as engine for internet and intranet portals and as building > block to provide context-aware personalization and collaboration features for > multi-site/multi-channel (mobile) oriented and content driven websites and > (social) network oriented services and platforms. > For the [[http://www.opensocial.org/|OpenSocial]] container and services the > (Java) [[http://shindig.apache.org|Apache Shindig]] will be integrated. At a > later stage further generalization is envisioned to also transparently > support [[http://www.w3.org/TR/widgets/|W3C Widgets]] using > [[http://incubator.apache.org/wookie/|Apache Wookie]]. > > > == Proposal == > > The reason for starting Rave is to bring together and combine several > existing projects and teams currently working towards more or less the same > or overlapping goals but each in their own small(er) target audience and > community. > > The goal for Rave is to become a lightweight and open-standards based > extendible platform for using, integrating and hosting !OpenSocial and W3C > Widget related features, technologies and services. > It will also provide strong context-aware personalization, collaboration and > content integration capabilities and a high quality out-of-the-box > installation as well as be easy to integrate in other platforms and solutions. > > The initial features for Rave will at least be based on the current > capabilities from the contributing external projects, for which they will > provide the necessary code contributions. > However, the code base for Rave will be built anew with strong focus on > generalization, customization and extendibility to support the intended > multi-purpose adoption and integration. > The contributing external projects will start using and switch to the new > Rave based solution as soon as the initial features become available to > ensure the continued participation and interest from their side as well as > their own communities. > > The intended initial features include: > > '''Core Features''' > 1. Advanced !OpenSocial compliance and optional features support > 1. !OpenSocial persistence and SPI (Service Provider Interface) implementation > 1. Self-service application administration including security, gadget > management and page templates > 1. User and group management with full privacy model > 1. Gadget repository with life-cycle management (install/update/remove) and > extended meta data (categories, comments, ratings, etc.) > 1. Dynamic and highly customizable front-end engine (skins, pages, tabs, > layouts, navigation) > 1. Full OAuth support > 1. Support for security restrictions on both Gadgets and page/tag/layout > customizations > 1. Set of common and general purpose Gadgets to be usable out-of-the-box > 1. Support for inter-gadget messaging with examples > > '''Extensible Features''' > 1. Pluggable persistence > 1. Pluggable security model with example modules for authentication and > authorization > 1. Support for !OpenSocial extensions not (yet) defined in the specification > 1. Support for other (non-standard, yet) pluggable container services and > extensions > > Beyond these initial features the vision and scope for Rave goes much further > and includes integrating and providing other highly desired/needed features > like: > > * native W3C Widgets support through > [[http://incubator.apache.org/wookie|Apache Wookie]] > * pluggable and extendible content integration and management services > * space extensions and management features, like > http://wiki.opensocial.org/index.php?title=Space_extension > * context aware features and extensions integration for personalized and > social network and (mobile) device oriented sites and channels > * enhanced client-side widget messaging, coordination and co-location support > like using [[http://www.openajax.org|OpenAjax]] Hub and Registry > * space, page and Gadget based linking, navigation, coor
Re: [VOTE] Accept Rave into the Incubator
+1 D. On Fri, Feb 25, 2011 at 1:08 AM, Ate Douma wrote: > Given the feedback received so far I think the Rave proposal is in good > shape so I'd like to bring up the vote for accepting Rave into the > Incubator. > > The proposal is at: http://wiki.apache.org/incubator/RaveProposal and also > copied as text below. > > Please vote. > > [ ] +1 Accept Rave into the incubator > [ ] +0 Don't care' > [ ] -1 Reject for the following reason: > > I'll close the vote at Tuesday morning 1st March CET to accommodate for the > coming weekend. That's a little over 5 days from now. > > Regards, > > Ate > > - COPY OF PROPOSAL FROM http://wiki.apache.org/incubator/RaveProposal > - > = Apache Rave Proposal = > > > == Abstract == > > Apache Rave is A new WEb And SOcial Mashup Engine. It will provide an > out-of-the-box as well as an extendible lightweight Java platform to host, > serve and aggregate (Open)Social Gadgets and services through a highly > customizable and Web 2.0 friendly front-end. > Rave is targeted as engine for internet and intranet portals and as building > block to provide context-aware personalization and collaboration features > for multi-site/multi-channel (mobile) oriented and content driven websites > and (social) network oriented services and platforms. > For the [[http://www.opensocial.org/|OpenSocial]] container and services the > (Java) [[http://shindig.apache.org|Apache Shindig]] will be integrated. At a > later stage further generalization is envisioned to also transparently > support [[http://www.w3.org/TR/widgets/|W3C Widgets]] using > [[http://incubator.apache.org/wookie/|Apache Wookie]]. > > > == Proposal == > > The reason for starting Rave is to bring together and combine several > existing projects and teams currently working towards more or less the same > or overlapping goals but each in their own small(er) target audience and > community. > > The goal for Rave is to become a lightweight and open-standards based > extendible platform for using, integrating and hosting !OpenSocial and W3C > Widget related features, technologies and services. > It will also provide strong context-aware personalization, collaboration and > content integration capabilities and a high quality out-of-the-box > installation as well as be easy to integrate in other platforms and > solutions. > > The initial features for Rave will at least be based on the current > capabilities from the contributing external projects, for which they will > provide the necessary code contributions. > However, the code base for Rave will be built anew with strong focus on > generalization, customization and extendibility to support the intended > multi-purpose adoption and integration. > The contributing external projects will start using and switch to the new > Rave based solution as soon as the initial features become available to > ensure the continued participation and interest from their side as well as > their own communities. > > The intended initial features include: > > '''Core Features''' > 1. Advanced !OpenSocial compliance and optional features support > 1. !OpenSocial persistence and SPI (Service Provider Interface) > implementation > 1. Self-service application administration including security, gadget > management and page templates > 1. User and group management with full privacy model > 1. Gadget repository with life-cycle management (install/update/remove) and > extended meta data (categories, comments, ratings, etc.) > 1. Dynamic and highly customizable front-end engine (skins, pages, tabs, > layouts, navigation) > 1. Full OAuth support > 1. Support for security restrictions on both Gadgets and page/tag/layout > customizations > 1. Set of common and general purpose Gadgets to be usable out-of-the-box > 1. Support for inter-gadget messaging with examples > > '''Extensible Features''' > 1. Pluggable persistence > 1. Pluggable security model with example modules for authentication and > authorization > 1. Support for !OpenSocial extensions not (yet) defined in the > specification > 1. Support for other (non-standard, yet) pluggable container services and > extensions > > Beyond these initial features the vision and scope for Rave goes much > further and includes integrating and providing other highly desired/needed > features like: > > * native W3C Widgets support through > [[http://incubator.apache.org/wookie|Apache Wookie]] > * pluggable and extendible content integration and management services > * space extensions and management features, like > http://wiki.opensocial.org/index.php?title=Space_extension > * context aware features and extensions integration for personalized and > social network and (mobile) device oriented sites and channels > * enhanced client-side widget messaging, coordination and co-location > support like using [[http://www.openajax.org|OpenAjax]] Hub and Registry > * space, page and Gadget based linking, navigation, coordination and > collaboration >
