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
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
+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, coordination and collaboration * inline widget rendering, like
Re: [PROPOSAL] Apache Rave project
Troy, I am not really sure what your point is. So you believe that: I think the 'Known Risks' section in the proposal enumerates that pretty clearly, so I won't repeat it. ... yet you raise an objection for somebody else who might think otherwise? Is that because you anticipate an objection and you want to prevent that by suggesting a solution that my prevent the objection to occur in the first place? [...] My statements were meant to speak to the folks who think otherwise, as a reasonable compromise (assuming Bill's stance, and anyone who is quietly in agreement, is to not allow it into the Incubator). Why not let the guys who have an objection speak for themselves? Regarding Bill's message, I didn't see him raising an objection, just making a valid point. Ate explained already both that it was addressed and the rationale for the wording in the proposal. I don't think my vote counts for much, but I'm a +1. ;) Well, the vote is on now. If I misunderstood your intentions I am sorry, but they are not very clear. Cheers, Hadrian - 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 linking, navigation, coordination and collaboration * inline widget rendering, like
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
+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 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
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 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 * inline widget rendering, like http://issues.apache.org/jira/browse/SHINDIG-1402 *
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: [PROPOSAL] Apache Rave project
My point was: Bill made a statement, which though rather neutral and ambiguous, seemed to indicate that he (or perhaps a silent mass of others) did not think the proposal was such a good idea, due to the risks associated with a significant amount of corporate support and involvement. At least, that's how I interpreted it. Since then, the response has been fairly one sided, supporting the project, and unfortunately, Bill has not responded to fairly direct questions about his intent or reasoning. I'd much rather be hearing more from him about this issue than continuing to express my opinions. In fact, some of the respondents have stated clearly that they missed his point. To me, his point is obvious. He's expressing that perhaps the known risks (which were accurately described in the proposal) might be significant enough that no one is willing to vocally support the proposal. Maybe they aren't significant enough to cause outcry, but significant enough to cause unspoken concerns and a lack of direct support because of it. Again, I don't agree with that opinion, but I also don't think it should be dismissed. So, supposing Bill does indeed have that assumed perspective, and supposing that it is a valid perspective, and that there may be other folks who aren't speaking up who have that perspective, my point was that, in good faith, the project make a concerted effort to address that concern, in the same way they would address issues with the code: by making a JIRA issue for it, scheduling it and resolving it. Now, back to my opinion... worthy or not as it may be. Clearly a lack of response cannot be taken as positive or negative, a silent mass is just that -- silent. No consent nor dissent expressed. Is that sufficient to move forward? In this case, I think so, and I agree with Upayavira's initial statements. I doubt if there is a large group of people out there, silently disapproving and not speaking up. That's very un-Apache, and thus, very unlikely for this situation. More than likely, people are just too busy to give an encouraging word. But, if someone does give voice to a concern, shouldn't that be taken to heart? The responses I saw from Ross seemed dismissive, and that raised enough concern, from my point of view that I felt like typing up my opinion + solution, and hitting 'Send'. Assuming silent consent is fine, but being dismissive of a voiced concern is not. Again, that's my 'strong opinion, weakly held'. Honestly, I have already said far more about this topic than I had any intention to. Hopefully this lengthy message provides enough detail into the inner workings of my mind that it satisfies any further confusion as to what the heck I was talking about. Thanks, Troy On Thu, Feb 24, 2011 at 5:33 PM, Hadrian Zbarcea hzbar...@gmail.com wrote: Troy, I am not really sure what your point is. So you believe that: I think the 'Known Risks' section in the proposal enumerates that pretty clearly, so I won't repeat it. ... yet you raise an objection for somebody else who might think otherwise? Is that because you anticipate an objection and you want to prevent that by suggesting a solution that my prevent the objection to occur in the first place? [...] My statements were meant to speak to the folks who think otherwise, as a reasonable compromise (assuming Bill's stance, and anyone who is quietly in agreement, is to not allow it into the Incubator). Why not let the guys who have an objection speak for themselves? Regarding Bill's message, I didn't see him raising an objection, just making a valid point. Ate explained already both that it was addressed and the rationale for the wording in the proposal. I don't think my vote counts for much, but I'm a +1. ;) Well, the vote is on now. If I misunderstood your intentions I am sorry, but they are not very clear. Cheers, Hadrian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - 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 Upayavira On Fri, 25 Feb 2011 01:08 +0100, Ate Douma a...@douma.nu 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: [PROPOSAL] Apache Rave project
I think the concern is in a sense valid, but this particular proposal doesn't seem to stand out for me in that regard. On one level, Apache is about individual contributions. Having said that, I wonder what would become of Apache if all corporate support of committers' activities were banned. Personally, the way I see it is that some devs at these companies met, saw a need, put it to their management and got their management's backing. Now, they're proposing to do some dev work on the project on company time. I suspect that we'll see enthusiasm for the project develop and show beyond the confines of the corporate need, but only time will tell there. That's my thoughts. Upayavira On Fri, 25 Feb 2011 02:25 -0800, Troy Howard thowar...@gmail.com wrote: My point was: Bill made a statement, which though rather neutral and ambiguous, seemed to indicate that he (or perhaps a silent mass of others) did not think the proposal was such a good idea, due to the risks associated with a significant amount of corporate support and involvement. At least, that's how I interpreted it. Since then, the response has been fairly one sided, supporting the project, and unfortunately, Bill has not responded to fairly direct questions about his intent or reasoning. I'd much rather be hearing more from him about this issue than continuing to express my opinions. In fact, some of the respondents have stated clearly that they missed his point. To me, his point is obvious. He's expressing that perhaps the known risks (which were accurately described in the proposal) might be significant enough that no one is willing to vocally support the proposal. Maybe they aren't significant enough to cause outcry, but significant enough to cause unspoken concerns and a lack of direct support because of it. Again, I don't agree with that opinion, but I also don't think it should be dismissed. So, supposing Bill does indeed have that assumed perspective, and supposing that it is a valid perspective, and that there may be other folks who aren't speaking up who have that perspective, my point was that, in good faith, the project make a concerted effort to address that concern, in the same way they would address issues with the code: by making a JIRA issue for it, scheduling it and resolving it. Now, back to my opinion... worthy or not as it may be. Clearly a lack of response cannot be taken as positive or negative, a silent mass is just that -- silent. No consent nor dissent expressed. Is that sufficient to move forward? In this case, I think so, and I agree with Upayavira's initial statements. I doubt if there is a large group of people out there, silently disapproving and not speaking up. That's very un-Apache, and thus, very unlikely for this situation. More than likely, people are just too busy to give an encouraging word. But, if someone does give voice to a concern, shouldn't that be taken to heart? The responses I saw from Ross seemed dismissive, and that raised enough concern, from my point of view that I felt like typing up my opinion + solution, and hitting 'Send'. Assuming silent consent is fine, but being dismissive of a voiced concern is not. Again, that's my 'strong opinion, weakly held'. Honestly, I have already said far more about this topic than I had any intention to. Hopefully this lengthy message provides enough detail into the inner workings of my mind that it satisfies any further confusion as to what the heck I was talking about. Thanks, Troy On Thu, Feb 24, 2011 at 5:33 PM, Hadrian Zbarcea hzbar...@gmail.com wrote: Troy, I am not really sure what your point is. So you believe that: I think the 'Known Risks' section in the proposal enumerates that pretty clearly, so I won't repeat it. ... yet you raise an objection for somebody else who might think otherwise? Is that because you anticipate an objection and you want to prevent that by suggesting a solution that my prevent the objection to occur in the first place? [...] My statements were meant to speak to the folks who think otherwise, as a reasonable compromise (assuming Bill's stance, and anyone who is quietly in agreement, is to not allow it into the Incubator). Why not let the guys who have an objection speak for themselves? Regarding Bill's message, I didn't see him raising an objection, just making a valid point. Ate explained already both that it was addressed and the rationale for the wording in the proposal. I don't think my vote counts for much, but I'm a +1. ;) Well, the vote is on now. If I misunderstood your intentions I am sorry, but they are not very clear. Cheers, Hadrian - 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 On Thu, Feb 24, 2011 at 4:08 PM, Ate Douma a...@douma.nu 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 * inline widget rendering, like http://issues.apache.org/jira/browse/SHINDIG-1402 *
Re: [VOTE] Accept Rave into the Incubator
[X] +1 Accept Rave into the incubator - Arjé
Re: [VOTE] Accept Rave into the Incubator
+1 On Fri, Feb 25, 2011 at 5:30 AM, Arje Cahn a.c...@hippo.nl 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
+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]] Hub and Registry * space, page and Gadget based linking, navigation, coordination and collaboration * inline widget rendering, like
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 --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, coordination and collaboration * inline widget rendering, like
Re: [VOTE] Accept Rave into the Incubator
+1 Mike On Thu, Feb 24, 2011 at 7:08 PM, Ate Douma a...@douma.nu 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 * inline widget rendering, like http://issues.apache.org/jira/browse/SHINDIG-1402 *
Re: [VOTE] Accept Rave into the Incubator
+1 Woonsan --- On Fri, 2/25/11, Ate Douma a...@douma.nu wrote: From: Ate Douma a...@douma.nu 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 messaging, coordination and co-location support like using [[http://www.openajax.org|OpenAjax]] Hub and
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: [PROPOSAL] Apache Rave project
On 2/25/2011 4:25 AM, Troy Howard wrote: My point was: Bill made a statement, which though rather neutral and ambiguous, seemed to indicate that he (or perhaps a silent mass of others) did not think the proposal was such a good idea, due to the risks associated with a significant amount of corporate support and involvement. At least, that's how I interpreted it. Since then, the response has been fairly one sided, supporting the project, and unfortunately, Bill has not responded to fairly direct questions about his intent or reasoning. I'd much rather be hearing more from him about this issue than continuing to express my opinions. No, that's not what I meant at all. I was simply offering a small nudge to Ate that they frame this in terms of individual contributors (paid or otherwise) who will do the work of making the project a success, beyond initial code drops. Yes, it's unambiguous that this project will succeed based on the software contribution agreements and offers of code from all of the organizations who are championing this effort. But unlike many other valid, respected standards and open source project bodies, corporations aren't members in the Apache-style governance. Even when a corp withdraws from a project, as in the recent case of IBM retreating from Harmony to OpenJDK, the ASF doesn't measure the impact of IBM, but of individual contributors from IBM who no longer have time and/or perhaps interest. Several projects have come into the incubator on nothing but one or even two corporations interests, with contributors, only to disappear when the corporate interests shift, or the contributors realize how really difficult it can be to collaborate with your competitors. This particular proposal reads very similar to other Open* incubation efforts which were failures primarily from the same starting point, but had corporate pissing matches to derail the effort to collaborate. I would have liked to see more on the subject of collaboration, and I would liked to have seen more about how individuals were given work time to pursue their own interest in this collective software effort, vs the corporate business case that there is a (collective) business need for this software. The former can lead to a very successful project even when the corporate winds shift. All of the above are not enough to earn a -1 from me, I certainly would have said so in the first place. This was merely a suggestion to reread and potentially revise the proposal and ensure the participants were not coming at this effort as they might for a W3C or JCP effort, where the business case and corporate participation is usually the nexus. And I would have privately chided Ate about how organization-heavy versus what little detail about the contributors themselves was offered in the proposal. But we discuss the merits, risks and missteps of incubating projects on general@, because this is how we learn from each others successes and mistakes and to recognize ASF culture. Please read all posts to general@ incubator from all ASF folks here as simply ways to improve the chance of the proposal's or project's success, unless the message has an explicit +/-1 (and even those are often reversible if the concerns raised can be addressed). Bill - 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 On Fri, Feb 25, 2011 at 1:10 PM, Craig L Russell craig.russ...@oracle.comwrote: +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
+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]] Hub and Registry * space, page and Gadget based linking, navigation, coordination and collaboration *
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 Looks like a good project. - Henry On Thu, Feb 24, 2011 at 4:08 PM, Ate Douma a...@douma.nu 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 * inline widget rendering, like
