RE: [Discuss] The Future of Ripple as a Top Level ASF Project
The code is available at https://github.com/MSOpenTech/cordova-ripple https://github.com/MSOpenTech/cordova-lib/commits/platform-ripple Example plugin https://github.com/MSOpenTech/cordova-plugin-camera/tree/platform-ripple Set-up Instructions: 1. Get repositories: git clone https://github.com/apache/cordova-cli.git git clone https://github.com/MSOpenTech/cordova-ripple.git git clone -b platform-ripple https://github.com/MSOpenTech/cordova-lib.git git clone -b platform-ripple https://github.com/MSOpenTech/cordova-plugin-camera.git 2. Install cordova from git repos. Notes: a. mklink command require administrative privileges, b. on Mac OS mklink command should be replaced with ln -s mkdir cordova-cli/node_modules cd cordova-cli/node_modules && mklink /d cordova-lib ../../cordova-lib/cordova-lib cd .. && npm install cd ../cordova-lib/cordova-lib && npm install 3. Create and run app. cd ../.. && cordova-cli/bin/cordova create rippleApp cd rippleApp ../cordova-cli/bin/cordova platform add ../cordova-ripple ../cordova-cli/bin/cordova plugin add ../cordova-plugin-camera ../cordova-cli/bin/cordova run Thx! Sergey -Original Message- From: venkata kiran surapaneni [mailto:svkir...@gmail.com] Sent: Wednesday, July 23, 2014 11:13 AM To: dev@cordova.apache.org Subject: Re: [Discuss] The Future of Ripple as a Top Level ASF Project Hi Parashuram, I use Cordova and Ripple regularly and I am interested in checking out the prototypes. Where are they available ? Thanks, --Kiran On Wed, Jul 23, 2014 at 4:19 AM, Parashuram Narasimhan (MS OPEN TECH) < panar...@microsoft.com> wrote: > Hi Gorkem, > > We have produced a couple of prototypes to show how Ripple can be used > as a platform. We have been able to delegate most of the plugin > specific functionality to the plugin itself, that includes a ripple> tag in its plugin.xml. > We are definitely interested in supporting Ripple and do not have a > preference about it becoming a Cordova sub project, or staying a top > level project. > > Would love to hear your feedback on this prototype, and any > suggestions that you may have on taking this forward. > > -Original Message- > From: Gorkem Ercan [mailto:gorkem.er...@gmail.com] > Sent: Friday, July 18, 2014 9:06 AM > To: dev@cordova.apache.org > Subject: Re: [Discuss] The Future of Ripple as a Top Level ASF Project > > Did this discussion concluded? What was the conclusion? > > I would like to see Ripple to have a healthy future and if having it > as a sub-project on Cordova ensures it, I would like to help with that. > I think we can have one or two people from Red Hat assisting on the > maintenance of Ripple. This probably is not enough for a top-level > project but may be enough to continue as a sub-project. > > Also, I know there are tools (folks from MSFT, I am looking at you) > that use ripple, they may also be ultimately interested on the well > being of the project. > -- > Gorkem > > > > > On Tue, Apr 22, 2014 at 10:30 AM, Brent Lintner > > wrote: > > > Hey All, > > > > Since becoming an incubator project (being donated graciously by > > BlackBerry), Ripple has seen positive contributions. > > > > However, it is also apparent that the community does not seem large > > enough to sustain a project like this as a top level project (let > > alone an individual PMC). > > > > Three of the original contributors/creators of Ripple are now fully > > involved in a new technology startup in an unrelated field and > > therefore we no longer have the resources to support Ripple in ASF. > > Also, BlackBerry has given no resources to help since donating > > Ripple to the ASF (this might be due to a change in their internal > > priorities). > > > > Given this, I would like to propose: > > > > 1. We find more community members willing to lead committership of > > the project, and see how that goes. > > > > 2. We also consider the eventuality of folding Ripple into another > > ASF project, if possible. If so, it would seem Cordova is a > > candidate for this, especially given the project being one of > > Ripple's main focus and > support. > > If the community votes for this, we should involve the Cordova > > community to gage their interests as well (I've CC'd their mailing > > list > in this email). > > > > 3. If the above does not work out, I would then suggest we consider > > the most unfortunate (put perhaps prudent) eventuality, which is to > "fail" > > Ripple as an incubator project. "fail" is this case, not being negative. > > > > And, if it does fail incubation- what does ASF normally do with the > > project? > > > > Does it get donated back to the original party? Does it get moved to > > an open source project outside of ASF (under a different license)? > > > > Any insight would be appreciated! > > > > -- > > Brent Lintner > > > -- Thanks & Regards, -Kiran
Re: [Discuss] The Future of Ripple as a Top Level ASF Project
Hi Parashuram, I use Cordova and Ripple regularly and I am interested in checking out the prototypes. Where are they available ? Thanks, --Kiran On Wed, Jul 23, 2014 at 4:19 AM, Parashuram Narasimhan (MS OPEN TECH) < panar...@microsoft.com> wrote: > Hi Gorkem, > > We have produced a couple of prototypes to show how Ripple can be used as > a platform. We have been able to delegate most of the plugin specific > functionality to the plugin itself, that includes a tag > in its plugin.xml. > We are definitely interested in supporting Ripple and do not have a > preference about it becoming a Cordova sub project, or staying a top level > project. > > Would love to hear your feedback on this prototype, and any suggestions > that you may have on taking this forward. > > -Original Message- > From: Gorkem Ercan [mailto:gorkem.er...@gmail.com] > Sent: Friday, July 18, 2014 9:06 AM > To: dev@cordova.apache.org > Subject: Re: [Discuss] The Future of Ripple as a Top Level ASF Project > > Did this discussion concluded? What was the conclusion? > > I would like to see Ripple to have a healthy future and if having it as a > sub-project on Cordova ensures it, I would like to help with that. > I think we can have one or two people from Red Hat assisting on the > maintenance of Ripple. This probably is not enough for a top-level project > but may be enough to continue as a sub-project. > > Also, I know there are tools (folks from MSFT, I am looking at you) that > use ripple, they may also be ultimately interested on the well being of the > project. > -- > Gorkem > > > > > On Tue, Apr 22, 2014 at 10:30 AM, Brent Lintner > wrote: > > > Hey All, > > > > Since becoming an incubator project (being donated graciously by > > BlackBerry), Ripple has seen positive contributions. > > > > However, it is also apparent that the community does not seem large > > enough to sustain a project like this as a top level project (let > > alone an individual PMC). > > > > Three of the original contributors/creators of Ripple are now fully > > involved in a new technology startup in an unrelated field and > > therefore we no longer have the resources to support Ripple in ASF. > > Also, BlackBerry has given no resources to help since donating Ripple > > to the ASF (this might be due to a change in their internal priorities). > > > > Given this, I would like to propose: > > > > 1. We find more community members willing to lead committership of the > > project, and see how that goes. > > > > 2. We also consider the eventuality of folding Ripple into another ASF > > project, if possible. If so, it would seem Cordova is a candidate for > > this, especially given the project being one of Ripple's main focus and > support. > > If the community votes for this, we should involve the Cordova > > community to gage their interests as well (I've CC'd their mailing list > in this email). > > > > 3. If the above does not work out, I would then suggest we consider > > the most unfortunate (put perhaps prudent) eventuality, which is to > "fail" > > Ripple as an incubator project. "fail" is this case, not being negative. > > > > And, if it does fail incubation- what does ASF normally do with the > > project? > > > > Does it get donated back to the original party? Does it get moved to > > an open source project outside of ASF (under a different license)? > > > > Any insight would be appreciated! > > > > -- > > Brent Lintner > > > -- Thanks & Regards, -Kiran
RE: [Discuss] The Future of Ripple as a Top Level ASF Project
Hi Gorkem, We have produced a couple of prototypes to show how Ripple can be used as a platform. We have been able to delegate most of the plugin specific functionality to the plugin itself, that includes a tag in its plugin.xml. We are definitely interested in supporting Ripple and do not have a preference about it becoming a Cordova sub project, or staying a top level project. Would love to hear your feedback on this prototype, and any suggestions that you may have on taking this forward. -Original Message- From: Gorkem Ercan [mailto:gorkem.er...@gmail.com] Sent: Friday, July 18, 2014 9:06 AM To: dev@cordova.apache.org Subject: Re: [Discuss] The Future of Ripple as a Top Level ASF Project Did this discussion concluded? What was the conclusion? I would like to see Ripple to have a healthy future and if having it as a sub-project on Cordova ensures it, I would like to help with that. I think we can have one or two people from Red Hat assisting on the maintenance of Ripple. This probably is not enough for a top-level project but may be enough to continue as a sub-project. Also, I know there are tools (folks from MSFT, I am looking at you) that use ripple, they may also be ultimately interested on the well being of the project. -- Gorkem On Tue, Apr 22, 2014 at 10:30 AM, Brent Lintner wrote: > Hey All, > > Since becoming an incubator project (being donated graciously by > BlackBerry), Ripple has seen positive contributions. > > However, it is also apparent that the community does not seem large > enough to sustain a project like this as a top level project (let > alone an individual PMC). > > Three of the original contributors/creators of Ripple are now fully > involved in a new technology startup in an unrelated field and > therefore we no longer have the resources to support Ripple in ASF. > Also, BlackBerry has given no resources to help since donating Ripple > to the ASF (this might be due to a change in their internal priorities). > > Given this, I would like to propose: > > 1. We find more community members willing to lead committership of the > project, and see how that goes. > > 2. We also consider the eventuality of folding Ripple into another ASF > project, if possible. If so, it would seem Cordova is a candidate for > this, especially given the project being one of Ripple's main focus and > support. > If the community votes for this, we should involve the Cordova > community to gage their interests as well (I've CC'd their mailing list in > this email). > > 3. If the above does not work out, I would then suggest we consider > the most unfortunate (put perhaps prudent) eventuality, which is to "fail" > Ripple as an incubator project. "fail" is this case, not being negative. > > And, if it does fail incubation- what does ASF normally do with the > project? > > Does it get donated back to the original party? Does it get moved to > an open source project outside of ASF (under a different license)? > > Any insight would be appreciated! > > -- > Brent Lintner >
Re: [Discuss] The Future of Ripple as a Top Level ASF Project
Did this discussion concluded? What was the conclusion? I would like to see Ripple to have a healthy future and if having it as a sub-project on Cordova ensures it, I would like to help with that. I think we can have one or two people from Red Hat assisting on the maintenance of Ripple. This probably is not enough for a top-level project but may be enough to continue as a sub-project. Also, I know there are tools (folks from MSFT, I am looking at you) that use ripple, they may also be ultimately interested on the well being of the project. -- Gorkem On Tue, Apr 22, 2014 at 10:30 AM, Brent Lintner wrote: > Hey All, > > Since becoming an incubator project (being donated graciously by > BlackBerry), Ripple has seen positive contributions. > > However, it is also apparent that the community does not seem large enough > to sustain a project like this as a top level project (let alone an > individual PMC). > > Three of the original contributors/creators of Ripple are now fully > involved in a new technology startup in an unrelated field and therefore we > no longer have the resources to support Ripple in ASF. Also, BlackBerry has > given no resources to help since donating Ripple to the ASF (this might be > due to a change in their internal priorities). > > Given this, I would like to propose: > > 1. We find more community members willing to lead committership of the > project, and see how that goes. > > 2. We also consider the eventuality of folding Ripple into another ASF > project, if possible. If so, it would seem Cordova is a candidate for this, > especially given the project being one of Ripple's main focus and support. > If the community votes for this, we should involve the Cordova community to > gage their interests as well (I've CC'd their mailing list in this email). > > 3. If the above does not work out, I would then suggest we consider the > most unfortunate (put perhaps prudent) eventuality, which is to "fail" > Ripple as an incubator project. "fail" is this case, not being negative. > > And, if it does fail incubation- what does ASF normally do with the > project? > > Does it get donated back to the original party? Does it get moved to an > open source project outside of ASF (under a different license)? > > Any insight would be appreciated! > > -- > Brent Lintner >
Re: [Discuss] The Future of Ripple as a Top Level ASF Project
Although I agree completely that Ripple is awesome both underneath and in
the UI, it'd have to go up quite a length to reach what Chrome already
provides on mobile emulation. I'm talking about custom device
creation/emulation, touch emulation, viewport automatic sizing and custom
pixel-ratio, among some GPU related bugs regarding frames and lists that
I've seen using Ripple.
I think it's a very nice idea (the best, probably) to bring Ripple closer
to Cordova, and I'd like to see it and cordova-browser become very
intertwined to provide me with the hidden magic that's required to develop
and test a cordova application on desktop Chrome. It's the right way to do
what many of the long gone Cordova/Phonegap polyfills and mocks for desktop
browser tried to do a year or two ago.
Also, AFAIK, a great portion of what cordova-browser needs to be ready is
already done in Ripple, so it would be kind of a migration/import anyway.
I'm looking forward to this!
2014-04-28 15:26 GMT-03:00 Ross Gerbasi :
> Ripple is awesome and if we are thinking about really pushing the
> cordova-browser idea it really should consider all the things Ripple
> provides.
>
> Personally I would like to see all that stuff move into the individual
> plugins. For example the geolocation plugin should have a emulator in it.
> This way plugin developers can provide proper emulation. Maybe we could
> come up with a standard for a plugin to add emulation support. Something as
> simple as a emulation folder at the top level that has a JS file that would
> get hooked in to your app in the browser.
>
> This would allow for all plugin to provide either a UI to interface with or
> dummy data to supply to an app in dev mode. We can then let chrome deal
> with device emulation and we can worry about cordova emulation...
>
>
> On Mon, Apr 28, 2014 at 1:20 PM, Parashuram Narasimhan (MS OPEN TECH) <
> panar...@microsoft.com> wrote:
>
> > To clarify, I did not mean to diminish the value of Ripple, I was just
> > saying that Ripple is much more than valuable considering Cordova
> plugins.
> > Ripple specializes in "Cordova" like API - deviceready, cordova plugins,
> > etc.
> >
> >
> > -Original Message-
> > From: Ray Camden [mailto:rayca...@adobe.com]
> > Sent: Monday, April 28, 2014 11:16 AM
> > To: dev@cordova.apache.org
> > Subject: RE: [Discuss] The Future of Ripple as a Top Level ASF Project
> >
> > As just an FYI, I couldn't disagree more about your first point ("minimal
> > value"). Now that Ripple is working again, I find it to be *extremely*
> > helpful for prototyping, quick testing, and teaching as well. You mention
> > built in emulation in Chrome, and yep, that's nice, but consider
> > geolocation. In Chrome, you have to enter a long/lat value (and I don't
> > know about you, but I don't keep those values in my head), in Ripple, you
> > can use a much simpler map interface to pick your location. Hell, just
> > running deviceready for me automatically is helpful.
> >
> > Maybe I'm just too passionate about it - but I really don't want to
> > minimize the value of Ripple.
> >
> > Sorry - carry on. ;)
> >
> > From: Parashuram Narasimhan (MS OPEN TECH)
> > Sent: Monday, April 28, 2014 1:06 PM
> > To: dev@cordova.apache.org
> > Subject: RE: [Discuss] The Future of Ripple as a Top Level ASF Project
> >
> > So, should we start the formal proposal to the Apache Foundation to move
> > on making Ripple a part of Cordova? I am guessing that we would need
> > technical reasons on why that would make sense. I could help with
> drafting
> > the proposal.
> >
> > - Ripple is mostly used for Cordova development. Browsers already have
> > viewport/touch emulation built in and the value of ripple is minimal in
> > this space
> > - Ripple is very similar to other top level 'Cordova tools' like CLI,
> > Medic, etc. Hence, it makes sense to treat it as such and make it a part
> of
> > the Cordova like the other projects.
> >
> >
>
Re: [Discuss] The Future of Ripple as a Top Level ASF Project
Ripple is awesome and if we are thinking about really pushing the
cordova-browser idea it really should consider all the things Ripple
provides.
Personally I would like to see all that stuff move into the individual
plugins. For example the geolocation plugin should have a emulator in it.
This way plugin developers can provide proper emulation. Maybe we could
come up with a standard for a plugin to add emulation support. Something as
simple as a emulation folder at the top level that has a JS file that would
get hooked in to your app in the browser.
This would allow for all plugin to provide either a UI to interface with or
dummy data to supply to an app in dev mode. We can then let chrome deal
with device emulation and we can worry about cordova emulation...
On Mon, Apr 28, 2014 at 1:20 PM, Parashuram Narasimhan (MS OPEN TECH) <
panar...@microsoft.com> wrote:
> To clarify, I did not mean to diminish the value of Ripple, I was just
> saying that Ripple is much more than valuable considering Cordova plugins.
> Ripple specializes in "Cordova" like API - deviceready, cordova plugins,
> etc.
>
>
> -Original Message-
> From: Ray Camden [mailto:rayca...@adobe.com]
> Sent: Monday, April 28, 2014 11:16 AM
> To: dev@cordova.apache.org
> Subject: RE: [Discuss] The Future of Ripple as a Top Level ASF Project
>
> As just an FYI, I couldn't disagree more about your first point ("minimal
> value"). Now that Ripple is working again, I find it to be *extremely*
> helpful for prototyping, quick testing, and teaching as well. You mention
> built in emulation in Chrome, and yep, that's nice, but consider
> geolocation. In Chrome, you have to enter a long/lat value (and I don't
> know about you, but I don't keep those values in my head), in Ripple, you
> can use a much simpler map interface to pick your location. Hell, just
> running deviceready for me automatically is helpful.
>
> Maybe I'm just too passionate about it - but I really don't want to
> minimize the value of Ripple.
>
> Sorry - carry on. ;)
> ________
> From: Parashuram Narasimhan (MS OPEN TECH)
> Sent: Monday, April 28, 2014 1:06 PM
> To: dev@cordova.apache.org
> Subject: RE: [Discuss] The Future of Ripple as a Top Level ASF Project
>
> So, should we start the formal proposal to the Apache Foundation to move
> on making Ripple a part of Cordova? I am guessing that we would need
> technical reasons on why that would make sense. I could help with drafting
> the proposal.
>
> - Ripple is mostly used for Cordova development. Browsers already have
> viewport/touch emulation built in and the value of ripple is minimal in
> this space
> - Ripple is very similar to other top level 'Cordova tools' like CLI,
> Medic, etc. Hence, it makes sense to treat it as such and make it a part of
> the Cordova like the other projects.
>
>
RE: [Discuss] The Future of Ripple as a Top Level ASF Project
To clarify, I did not mean to diminish the value of Ripple, I was just saying
that Ripple is much more than valuable considering Cordova plugins.
Ripple specializes in "Cordova" like API - deviceready, cordova plugins, etc.
-Original Message-
From: Ray Camden [mailto:rayca...@adobe.com]
Sent: Monday, April 28, 2014 11:16 AM
To: dev@cordova.apache.org
Subject: RE: [Discuss] The Future of Ripple as a Top Level ASF Project
As just an FYI, I couldn't disagree more about your first point ("minimal
value"). Now that Ripple is working again, I find it to be *extremely* helpful
for prototyping, quick testing, and teaching as well. You mention built in
emulation in Chrome, and yep, that's nice, but consider geolocation. In Chrome,
you have to enter a long/lat value (and I don't know about you, but I don't
keep those values in my head), in Ripple, you can use a much simpler map
interface to pick your location. Hell, just running deviceready for me
automatically is helpful.
Maybe I'm just too passionate about it - but I really don't want to minimize
the value of Ripple.
Sorry - carry on. ;)
From: Parashuram Narasimhan (MS OPEN TECH)
Sent: Monday, April 28, 2014 1:06 PM
To: dev@cordova.apache.org
Subject: RE: [Discuss] The Future of Ripple as a Top Level ASF Project
So, should we start the formal proposal to the Apache Foundation to move on
making Ripple a part of Cordova? I am guessing that we would need technical
reasons on why that would make sense. I could help with drafting the proposal.
- Ripple is mostly used for Cordova development. Browsers already have
viewport/touch emulation built in and the value of ripple is minimal in this
space
- Ripple is very similar to other top level 'Cordova tools' like CLI, Medic,
etc. Hence, it makes sense to treat it as such and make it a part of the
Cordova like the other projects.
RE: [Discuss] The Future of Ripple as a Top Level ASF Project
As just an FYI, I couldn't disagree more about your first point ("minimal
value"). Now that Ripple is working again, I find it to be *extremely* helpful
for prototyping, quick testing, and teaching as well. You mention built in
emulation in Chrome, and yep, that's nice, but consider geolocation. In Chrome,
you have to enter a long/lat value (and I don't know about you, but I don't
keep those values in my head), in Ripple, you can use a much simpler map
interface to pick your location. Hell, just running deviceready for me
automatically is helpful.
Maybe I'm just too passionate about it - but I really don't want to minimize
the value of Ripple.
Sorry - carry on. ;)
From: Parashuram Narasimhan (MS OPEN TECH)
Sent: Monday, April 28, 2014 1:06 PM
To: dev@cordova.apache.org
Subject: RE: [Discuss] The Future of Ripple as a Top Level ASF Project
So, should we start the formal proposal to the Apache Foundation to move on
making Ripple a part of Cordova? I am guessing that we would need technical
reasons on why that would make sense. I could help with drafting the proposal.
- Ripple is mostly used for Cordova development. Browsers already have
viewport/touch emulation built in and the value of ripple is minimal in this
space
- Ripple is very similar to other top level 'Cordova tools' like CLI, Medic,
etc. Hence, it makes sense to treat it as such and make it a part of the
Cordova like the other projects.
RE: [Discuss] The Future of Ripple as a Top Level ASF Project
Oh - when I read your call for Ripple devs to 'switch', I had assumed it was something already done. From: agri...@google.com on behalf of Andrew Grieve Sent: Monday, April 28, 2014 11:49 AM To: dev Subject: Re: [Discuss] The Future of Ripple as a Top Level ASF Project Right, it doesn't exist yet (no one's picked up working on it). +Brian made the original pitch for it, but my understanding is that it is meant to be adding first-class support for testing Cordova apps in the browser, but do so by being a fully-supported cordova platform. Another way to look at this is to say that there's already a place for Ripple to go within Cordova. The core logic should go into cordova-browser. Plugin logic should go into each plugin repo under the "browser" platform. And the bridge interception piece should go into cordova-js. If there is still need for a ripple server after all of this, then that belongs inside of cordova-cli.
RE: [Discuss] The Future of Ripple as a Top Level ASF Project
So, should we start the formal proposal to the Apache Foundation to move on making Ripple a part of Cordova? I am guessing that we would need technical reasons on why that would make sense. I could help with drafting the proposal. - Ripple is mostly used for Cordova development. Browsers already have viewport/touch emulation built in and the value of ripple is minimal in this space - Ripple is very similar to other top level 'Cordova tools' like CLI, Medic, etc. Hence, it makes sense to treat it as such and make it a part of the Cordova like the other projects. -Original Message- From: brian.ler...@gmail.com [mailto:brian.ler...@gmail.com] On Behalf Of Brian LeRoux Sent: Monday, April 28, 2014 10:42 AM To: dev@cordova.apache.org Subject: Re: [Discuss] The Future of Ripple as a Top Level ASF Project Its not a bad idea but this takes Ripple out of 'gui simulator' into 'env simulator' territory. FWIW, we hope to have cycles this summer to put into cordova-browser but help from others would be VERY welcome. On Mon, Apr 28, 2014 at 9:49 AM, Andrew Grieve wrote: > Right, it doesn't exist yet (no one's picked up working on it). +Brian > made the original pitch for it, but my understanding is that it is > meant to be adding first-class support for testing Cordova apps in the > browser, but do so by being a fully-supported cordova platform. > > Another way to look at this is to say that there's already a place for > Ripple to go within Cordova. The core logic should go into cordova-browser. > Plugin logic should go into each plugin repo under the "browser" platform. > And the bridge interception piece should go into cordova-js. If there > is still need for a ripple server after all of this, then that belongs > inside of cordova-cli. > > > > On Sat, Apr 26, 2014 at 11:17 AM, Ray Camden wrote: > > > I am naturally inclined to *not* leave Ripple as I think it is a > > great tool, but I'll check out cordova-browser. You say it is very > > similar to Ripple, but where exactly is it? The github repo is mostly empty > > now. > > > > > > From: agri...@google.com on behalf of Andrew > Grieve < > > agri...@chromium.org> > > Sent: Thursday, April 24, 2014 3:17 PM > > To: dev > > Subject: Re: [Discuss] The Future of Ripple as a Top Level ASF > > Project > > > > For those passionate about Ripple, I'd like to try and woo you to > > two other avenues, as I don't see Ripple in the Cordova workflow in > > the future. > > > > cordova-app-harness for on-device testing (this is essentially the > > same as PhoneGap Developer App) cordova-browser CLI platform for > > local in-browser testing (very similar to Ripple, but fully > > supported by CLI & works with plugins in a generic way) > > > > >
Re: [Discuss] The Future of Ripple as a Top Level ASF Project
Its not a bad idea but this takes Ripple out of 'gui simulator' into 'env simulator' territory. FWIW, we hope to have cycles this summer to put into cordova-browser but help from others would be VERY welcome. On Mon, Apr 28, 2014 at 9:49 AM, Andrew Grieve wrote: > Right, it doesn't exist yet (no one's picked up working on it). +Brian made > the original pitch for it, but my understanding is that it is meant to be > adding first-class support for testing Cordova apps in the browser, but do > so by being a fully-supported cordova platform. > > Another way to look at this is to say that there's already a place for > Ripple to go within Cordova. The core logic should go into cordova-browser. > Plugin logic should go into each plugin repo under the "browser" platform. > And the bridge interception piece should go into cordova-js. If there is > still need for a ripple server after all of this, then that belongs inside > of cordova-cli. > > > > On Sat, Apr 26, 2014 at 11:17 AM, Ray Camden wrote: > > > I am naturally inclined to *not* leave Ripple as I think it is a great > > tool, but I'll check out cordova-browser. You say it is very similar to > > Ripple, but where exactly is it? The github repo is mostly empty now. > > > > > > From: agri...@google.com on behalf of Andrew > Grieve < > > agri...@chromium.org> > > Sent: Thursday, April 24, 2014 3:17 PM > > To: dev > > Subject: Re: [Discuss] The Future of Ripple as a Top Level ASF Project > > > > For those passionate about Ripple, I'd like to try and woo you to two > > other avenues, as I don't see Ripple in the Cordova workflow in the > > future. > > > > cordova-app-harness for on-device testing (this is essentially the > > same as PhoneGap Developer App) > > cordova-browser CLI platform for local in-browser testing (very > > similar to Ripple, but fully supported by CLI & works with plugins in > > a generic way) > > > > >
Re: [Discuss] The Future of Ripple as a Top Level ASF Project
Right, it doesn't exist yet (no one's picked up working on it). +Brian made the original pitch for it, but my understanding is that it is meant to be adding first-class support for testing Cordova apps in the browser, but do so by being a fully-supported cordova platform. Another way to look at this is to say that there's already a place for Ripple to go within Cordova. The core logic should go into cordova-browser. Plugin logic should go into each plugin repo under the "browser" platform. And the bridge interception piece should go into cordova-js. If there is still need for a ripple server after all of this, then that belongs inside of cordova-cli. On Sat, Apr 26, 2014 at 11:17 AM, Ray Camden wrote: > I am naturally inclined to *not* leave Ripple as I think it is a great > tool, but I'll check out cordova-browser. You say it is very similar to > Ripple, but where exactly is it? The github repo is mostly empty now. > > > From: agri...@google.com on behalf of Andrew Grieve < > agri...@chromium.org> > Sent: Thursday, April 24, 2014 3:17 PM > To: dev > Subject: Re: [Discuss] The Future of Ripple as a Top Level ASF Project > > For those passionate about Ripple, I'd like to try and woo you to two > other avenues, as I don't see Ripple in the Cordova workflow in the > future. > > cordova-app-harness for on-device testing (this is essentially the > same as PhoneGap Developer App) > cordova-browser CLI platform for local in-browser testing (very > similar to Ripple, but fully supported by CLI & works with plugins in > a generic way) > >
RE: [Discuss] The Future of Ripple as a Top Level ASF Project
I am naturally inclined to *not* leave Ripple as I think it is a great tool, but I'll check out cordova-browser. You say it is very similar to Ripple, but where exactly is it? The github repo is mostly empty now. From: agri...@google.com on behalf of Andrew Grieve Sent: Thursday, April 24, 2014 3:17 PM To: dev Subject: Re: [Discuss] The Future of Ripple as a Top Level ASF Project For those passionate about Ripple, I'd like to try and woo you to two other avenues, as I don't see Ripple in the Cordova workflow in the future. cordova-app-harness for on-device testing (this is essentially the same as PhoneGap Developer App) cordova-browser CLI platform for local in-browser testing (very similar to Ripple, but fully supported by CLI & works with plugins in a generic way)
Re: [Discuss] The Future of Ripple as a Top Level ASF Project
App Harness is here: https://github.com/apache/cordova-app-harness/. And there's a downstream version of it for Chrome Apps here: https://github.com/MobileChromeApps/harness Pre-built apks here: https://github.com/MobileChromeApps/harness/releases cordova-browser is here: https://github.com/apache/cordova-browser/ but it is nothing but a short README at the moment. On Thu, Apr 24, 2014 at 4:32 PM, venkata kiran surapaneni wrote: > Andrew, > > I just saw reference to these before I posted my earlier > reply. But I don't remember seeing any thing related to those on Cordova > site. Where can i get more information about the tools you mentioned ?
Re: [Discuss] The Future of Ripple as a Top Level ASF Project
Andrew, I just saw reference to these before I posted my earlier reply. But I don't remember seeing any thing related to those on Cordova site. Where can i get more information about the tools you mentioned ?
Re: [Discuss] The Future of Ripple as a Top Level ASF Project
For those passionate about Ripple, I'd like to try and woo you to two other avenues, as I don't see Ripple in the Cordova workflow in the future. cordova-app-harness for on-device testing (this is essentially the same as PhoneGap Developer App) cordova-browser CLI platform for local in-browser testing (very similar to Ripple, but fully supported by CLI & works with plugins in a generic way) On Thu, Apr 24, 2014 at 3:47 PM, venkata kiran surapaneni wrote: > I use Ripple a lot for my development and I would like to see it progress. > Actually I think developers are in need of such tool which simplifies their > development , it just didn't receive enough exposure. Once it receives good > exposure, I hope it will attract more committers and developers as well and > will make good progress.I think merging with Cordova will provide with the > exposure that it needs. But I expected Ripple to have good support for > WebWorks and other frameworks built on top of Cordova. I am not sure what > it means to the WebWorks support if Ripple is merged with Cordova ? > > I am willing to help on any clean up that is required and also work on > future road map. Count me in.
Re: [Discuss] The Future of Ripple as a Top Level ASF Project
I use Ripple a lot for my development and I would like to see it progress. Actually I think developers are in need of such tool which simplifies their development , it just didn't receive enough exposure. Once it receives good exposure, I hope it will attract more committers and developers as well and will make good progress.I think merging with Cordova will provide with the exposure that it needs. But I expected Ripple to have good support for WebWorks and other frameworks built on top of Cordova. I am not sure what it means to the WebWorks support if Ripple is merged with Cordova ? I am willing to help on any clean up that is required and also work on future road map. Count me in.
Re: [Discuss] The Future of Ripple as a Top Level ASF Project
On 24 Apr 2014, at 19:49, Brian LeRoux wrote: no, no…we fully plan on donating all that source back into apache (and it is open already [1][2]) these things serve different purposes and have different limitations. ripple works offline and only requires a web browser which is very useful. I only wish we had more capability to support the project. whether it is a TLP or a part of Cordova doesn't really matter Suggestion: - Cordova committers with interest just ask for commit access on the ripple podling - there is one or two persons who might be eligible for becoming ripple committers After that we just need to sort out all copyright related issues. As we have Cordovians as PMC on board, it should be possible to move out (no guarantees), even with no release made. Despite the recent discussions I trust a TLP project to know how releases are done and that there is no need to let the podling make a formal release before moving out. However the question is: who is willing to join as Ripple committer and dedicate some time to sort out the things we need to clean up? Hands up, Gents :-) [1] https://github.com/phonegap/phonegap-app-developer [2] https://github.com/phonegap/connect-phonegap On Thu, Apr 24, 2014 at 8:39 AM, Igor Costa wrote: That's good to be adopted by Apache, but turns out that conflicts directly to Phonegap App which does a better integration/development experience. That's my point of view. Igor Costa www.igorcosta.com www.igorcosta.org On Thu, Apr 24, 2014 at 11:22 AM, Ross Gerbasi wrote: I am also into this idea and would totally be into working on code to make that happen. Seems like we could just come up with a simple structure a plugin could follow to provide emulation in the browser? This could be through some UI panel or just simple dummy data being returned from calls. The plugin could really make that call. If we do go this route maybe we could rethink how ripple is integrated into the workflow? Is it possible to just make it another platform? Lastly now that Chrome has much stronger emulation support could we lean on it for Device, Screen, User Agent and basic sensor emulation then just have ripple (or this new platform) deal with cordova specific calls and plugins? On Wed, Apr 23, 2014 at 6:58 PM, Anis KADRI wrote: On Wed, Apr 23, 2014 at 8:41 AM, Parashuram Narasimhan (MS OPEN TECH) < panar...@microsoft.com> wrote: On a side note, does it make sense to make Ripple another platform, just like iOS, Android or Windows? Given that a lot of people use Ripple in projects that also have plugins, it may make sense for plugins to atleast provide some sort of mock data for Ripple, making Ripple useful with plugins that are not already supported. I like this idea. I like the idea of folding it into Cordova. --- http://www.grobmeier.de The Zen Programmer: http://bit.ly/12lC6DL @grobmeier GPG: 0xA5CC90DB
Re: [Discuss] The Future of Ripple as a Top Level ASF Project
no, no…we fully plan on donating all that source back into apache (and it is open already [1][2]) these things serve different purposes and have different limitations. ripple works offline and only requires a web browser which is very useful. I only wish we had more capability to support the project. whether it is a TLP or a part of Cordova doesn't really matter [1] https://github.com/phonegap/phonegap-app-developer [2] https://github.com/phonegap/connect-phonegap On Thu, Apr 24, 2014 at 8:39 AM, Igor Costa wrote: > That's good to be adopted by Apache, but turns out that conflicts directly > to Phonegap App which does a better integration/development experience. > > > That's my point of view. > > > Igor Costa > www.igorcosta.com > www.igorcosta.org > > > On Thu, Apr 24, 2014 at 11:22 AM, Ross Gerbasi wrote: > > > I am also into this idea and would totally be into working on code to > make > > that happen. Seems like we could just come up with a simple structure a > > plugin could follow to provide emulation in the browser? This could be > > through some UI panel or just simple dummy data being returned from > calls. > > The plugin could really make that call. > > > > If we do go this route maybe we could rethink how ripple is integrated > into > > the workflow? Is it possible to just make it another platform? > > > > Lastly now that Chrome has much stronger emulation support could we lean > on > > it for Device, Screen, User Agent and basic sensor emulation then just > have > > ripple (or this new platform) deal with cordova specific calls and > plugins? > > > > > > On Wed, Apr 23, 2014 at 6:58 PM, Anis KADRI > wrote: > > > > > On Wed, Apr 23, 2014 at 8:41 AM, Parashuram Narasimhan (MS OPEN TECH) < > > > panar...@microsoft.com> wrote: > > > > > > > On a side note, does it make sense to make Ripple another platform, > > just > > > > like iOS, Android or Windows? Given that a lot of people use Ripple > in > > > > projects that also have plugins, it may make sense for plugins to > > atleast > > > > provide some sort of mock data for Ripple, making Ripple useful with > > > > plugins that are not already supported. > > > > > > > > > I like this idea. I like the idea of folding it into Cordova. > > > > > >
Re: [Discuss] The Future of Ripple as a Top Level ASF Project
That's good to be adopted by Apache, but turns out that conflicts directly to Phonegap App which does a better integration/development experience. That's my point of view. Igor Costa www.igorcosta.com www.igorcosta.org On Thu, Apr 24, 2014 at 11:22 AM, Ross Gerbasi wrote: > I am also into this idea and would totally be into working on code to make > that happen. Seems like we could just come up with a simple structure a > plugin could follow to provide emulation in the browser? This could be > through some UI panel or just simple dummy data being returned from calls. > The plugin could really make that call. > > If we do go this route maybe we could rethink how ripple is integrated into > the workflow? Is it possible to just make it another platform? > > Lastly now that Chrome has much stronger emulation support could we lean on > it for Device, Screen, User Agent and basic sensor emulation then just have > ripple (or this new platform) deal with cordova specific calls and plugins? > > > On Wed, Apr 23, 2014 at 6:58 PM, Anis KADRI wrote: > > > On Wed, Apr 23, 2014 at 8:41 AM, Parashuram Narasimhan (MS OPEN TECH) < > > panar...@microsoft.com> wrote: > > > > > On a side note, does it make sense to make Ripple another platform, > just > > > like iOS, Android or Windows? Given that a lot of people use Ripple in > > > projects that also have plugins, it may make sense for plugins to > atleast > > > provide some sort of mock data for Ripple, making Ripple useful with > > > plugins that are not already supported. > > > > > > I like this idea. I like the idea of folding it into Cordova. > > >
Re: [Discuss] The Future of Ripple as a Top Level ASF Project
I am also into this idea and would totally be into working on code to make that happen. Seems like we could just come up with a simple structure a plugin could follow to provide emulation in the browser? This could be through some UI panel or just simple dummy data being returned from calls. The plugin could really make that call. If we do go this route maybe we could rethink how ripple is integrated into the workflow? Is it possible to just make it another platform? Lastly now that Chrome has much stronger emulation support could we lean on it for Device, Screen, User Agent and basic sensor emulation then just have ripple (or this new platform) deal with cordova specific calls and plugins? On Wed, Apr 23, 2014 at 6:58 PM, Anis KADRI wrote: > On Wed, Apr 23, 2014 at 8:41 AM, Parashuram Narasimhan (MS OPEN TECH) < > panar...@microsoft.com> wrote: > > > On a side note, does it make sense to make Ripple another platform, just > > like iOS, Android or Windows? Given that a lot of people use Ripple in > > projects that also have plugins, it may make sense for plugins to atleast > > provide some sort of mock data for Ripple, making Ripple useful with > > plugins that are not already supported. > > > I like this idea. I like the idea of folding it into Cordova. >
Re: [Discuss] The Future of Ripple as a Top Level ASF Project
On Wed, Apr 23, 2014 at 8:41 AM, Parashuram Narasimhan (MS OPEN TECH) < panar...@microsoft.com> wrote: > On a side note, does it make sense to make Ripple another platform, just > like iOS, Android or Windows? Given that a lot of people use Ripple in > projects that also have plugins, it may make sense for plugins to atleast > provide some sort of mock data for Ripple, making Ripple useful with > plugins that are not already supported. I like this idea. I like the idea of folding it into Cordova.
RE: [Discuss] The Future of Ripple as a Top Level ASF Project
Ripple is critical for the Windows eco system as it give us a great way to try our and build for multiple platforms. There are also multiple tools and IDEs for Cordova that use Ripple as a way to test the deployments. We have an open pull request and are also working on another set of pull requests for Ripple. Regardless of if it continues as a top level project of Apache or is folded into Cordova, Ripple would continue to be critical to us and we would like to continue contributing to the project. If you need help with reviewing pull requests or fixing bugs, we could take that up too. As Andrew mentions, we could also explore the possibility of how this could live in an ecosystem where we have things like the app harness and cordova browser. On a side note, does it make sense to make Ripple another platform, just like iOS, Android or Windows? Given that a lot of people use Ripple in projects that also have plugins, it may make sense for plugins to atleast provide some sort of mock data for Ripple, making Ripple useful with plugins that are not already supported. -Original Message- From: Christian Grobmeier [mailto:grobme...@gmail.com] Sent: Tuesday, April 22, 2014 10:52 AM To: d...@ripple.incubator.apache.org Cc: dev@cordova.apache.org Subject: Re: [Discuss] The Future of Ripple as a Top Level ASF Project hi folks, On 22 Apr 2014, at 16:30, Brent Lintner wrote: > However, it is also apparent that the community does not seem large > enough to sustain a project like this as a top level project (let > alone an individual PMC). ... > 1. We find more community members willing to lead committership of the > project, and see how that goes. possible this happens, but unlikely: if there is no activity it seems people are not attracted to help that much. > 2. We also consider the eventuality of folding Ripple into another ASF > project, if possible. If so, it would seem Cordova is a candidate for > this, especially given the project being one of Ripple's main focus > and support. > If the community votes for this, we should involve the Cordova > community to gage their interests as well (I've CC'd their mailing > list in this email). At the ASF we don't want umbrella projects. But in this case I really see the most interested party in Ripple is the Cordova project. It looks like Ripple can't succeed on a project on its, just because there are not enough PMC members available. Three are must, but its better to have 5 or 6. That said, the project is not dead so I would prefer to see the current active committers added to the Cordova committership. > 3. If the above does not work out, I would then suggest we consider > the most unfortunate (put perhaps prudent) eventuality, which is to > "fail" > Ripple as an incubator project. "fail" is this case, not being > negative. > > And, if it does fail incubation- what does ASF normally do with the > project? > > Does it get donated back to the original party? Does it get moved to > an open source project outside of ASF (under a different license)? In the incubator terminology there is no "fail", there is just a retirement :-) It would mean the project svn is put to read only and the websites are removed. A status page would indicate its current state. New committers can try to revive the project at any time. Everybody is welcome to fork the project - and even come back later to the ASF. However there is one restriction: usually the ASF keeps the trademark "Apache Ripple". There were a few exceptions in the past when the project could keep its trademark and continue outside the ASF (like Zeta Components). That being said, the community could surely decide to retire here, move the code to GitHub and continue there. The formal things (like reports) are gone then, but I am afraid GitHub is not the cure for Ripple. My personal preference is due to the fact that Cordova committers and Ripple committers already seem to overlap, to just move the project to Cordova. Of course the Cordova project would then still need to take care about the formal aspects of Ripple. In example, check if there are copyright protected images in there, or if everything is well with dependencies. This certainly requires some amount of work and if there is nobody willing to perform this work... This work would be necessary to do in GitHub as well, but well. Cheers Christian > > Any insight would be appreciated! > > -- > Brent Lintner --- http://www.grobmeier.de The Zen Programmer: http://bit.ly/12lC6DL @grobmeier GPG: 0xA5CC90DB
Re: [Discuss] The Future of Ripple as a Top Level ASF Project
hi folks, On 22 Apr 2014, at 16:30, Brent Lintner wrote: However, it is also apparent that the community does not seem large enough to sustain a project like this as a top level project (let alone an individual PMC). ... 1. We find more community members willing to lead committership of the project, and see how that goes. possible this happens, but unlikely: if there is no activity it seems people are not attracted to help that much. 2. We also consider the eventuality of folding Ripple into another ASF project, if possible. If so, it would seem Cordova is a candidate for this, especially given the project being one of Ripple's main focus and support. If the community votes for this, we should involve the Cordova community to gage their interests as well (I've CC'd their mailing list in this email). At the ASF we don't want umbrella projects. But in this case I really see the most interested party in Ripple is the Cordova project. It looks like Ripple can't succeed on a project on its, just because there are not enough PMC members available. Three are must, but its better to have 5 or 6. That said, the project is not dead so I would prefer to see the current active committers added to the Cordova committership. 3. If the above does not work out, I would then suggest we consider the most unfortunate (put perhaps prudent) eventuality, which is to "fail" Ripple as an incubator project. "fail" is this case, not being negative. And, if it does fail incubation- what does ASF normally do with the project? Does it get donated back to the original party? Does it get moved to an open source project outside of ASF (under a different license)? In the incubator terminology there is no "fail", there is just a retirement :-) It would mean the project svn is put to read only and the websites are removed. A status page would indicate its current state. New committers can try to revive the project at any time. Everybody is welcome to fork the project - and even come back later to the ASF. However there is one restriction: usually the ASF keeps the trademark "Apache Ripple". There were a few exceptions in the past when the project could keep its trademark and continue outside the ASF (like Zeta Components). That being said, the community could surely decide to retire here, move the code to GitHub and continue there. The formal things (like reports) are gone then, but I am afraid GitHub is not the cure for Ripple. My personal preference is due to the fact that Cordova committers and Ripple committers already seem to overlap, to just move the project to Cordova. Of course the Cordova project would then still need to take care about the formal aspects of Ripple. In example, check if there are copyright protected images in there, or if everything is well with dependencies. This certainly requires some amount of work and if there is nobody willing to perform this work... This work would be necessary to do in GitHub as well, but well. Cheers Christian Any insight would be appreciated! -- Brent Lintner --- http://www.grobmeier.de The Zen Programmer: http://bit.ly/12lC6DL @grobmeier GPG: 0xA5CC90DB
Re: [Discuss] The Future of Ripple as a Top Level ASF Project
Query - why would 3 be a fail per se? I mean - is there any reason why it couldn't be up on Github? That puts the ownership with one person (or org), which is perhaps risky, but, it could be simpler too, right? On Tue, Apr 22, 2014 at 9:30 AM, Brent Lintner wrote: > Hey All, > > Since becoming an incubator project (being donated graciously by > BlackBerry), Ripple has seen positive contributions. > > However, it is also apparent that the community does not seem large enough > to sustain a project like this as a top level project (let alone an > individual PMC). > > Three of the original contributors/creators of Ripple are now fully > involved in a new technology startup in an unrelated field and therefore we > no longer have the resources to support Ripple in ASF. Also, BlackBerry has > given no resources to help since donating Ripple to the ASF (this might be > due to a change in their internal priorities). > > Given this, I would like to propose: > > 1. We find more community members willing to lead committership of the > project, and see how that goes. > > 2. We also consider the eventuality of folding Ripple into another ASF > project, if possible. If so, it would seem Cordova is a candidate for this, > especially given the project being one of Ripple's main focus and support. > If the community votes for this, we should involve the Cordova community to > gage their interests as well (I've CC'd their mailing list in this email). > > 3. If the above does not work out, I would then suggest we consider the > most unfortunate (put perhaps prudent) eventuality, which is to "fail" > Ripple as an incubator project. "fail" is this case, not being negative. > > And, if it does fail incubation- what does ASF normally do with the > project? > > Does it get donated back to the original party? Does it get moved to an > open source project outside of ASF (under a different license)? > > Any insight would be appreciated! > > -- > Brent Lintner > -- === Raymond Camden, Web Developer for Adobe Email : raymondcam...@gmail.com Blog : www.raymondcamden.com Twitter: raymondcamden
Re: [Discuss] The Future of Ripple as a Top Level ASF Project
There is definitely overlap with cordova-browser. Chrome devtools has also added many mobile-emulation type features since Ripple was developed. There's also cordova-app-harness (and equivalent down-stream apps) that aid in a better dev. workflow). Not totally against having Cordova fold in Ripple, but I don't want to see it get added in and then unmaintained, and I think we're fairly spread-thin already. On Tue, Apr 22, 2014 at 11:49 AM, Shazron wrote: > +1 on absorbing Ripple > > > On Tue, Apr 22, 2014 at 8:16 AM, Joe Bowser wrote: > > > On Tue, Apr 22, 2014 at 7:30 AM, Brent Lintner > > wrote: > > > Hey All, > > > > > > Since becoming an incubator project (being donated graciously by > > > BlackBerry), Ripple has seen positive contributions. > > > > > > However, it is also apparent that the community does not seem large > > enough > > > to sustain a project like this as a top level project (let alone an > > > individual PMC). > > > > > > Three of the original contributors/creators of Ripple are now fully > > > involved in a new technology startup in an unrelated field and > therefore > > we > > > no longer have the resources to support Ripple in ASF. Also, BlackBerry > > has > > > given no resources to help since donating Ripple to the ASF (this might > > be > > > due to a change in their internal priorities). > > > > > > Given this, I would like to propose: > > > > > > 1. We find more community members willing to lead committership of the > > > project, and see how that goes. > > > > > > 2. We also consider the eventuality of folding Ripple into another ASF > > > project, if possible. If so, it would seem Cordova is a candidate for > > this, > > > especially given the project being one of Ripple's main focus and > > support. > > > If the community votes for this, we should involve the Cordova > community > > to > > > gage their interests as well (I've CC'd their mailing list in this > > email). > > > > I'd +1 this. I'd like to see Ripple live on in some form if people > > are still using it, even though I don't use it personally. > > > > > > > > 3. If the above does not work out, I would then suggest we consider the > > > most unfortunate (put perhaps prudent) eventuality, which is to "fail" > > > Ripple as an incubator project. "fail" is this case, not being > negative. > > > > > > > So, Incubator projects can't go into the Attic? That's what the ASF > > does with projects that become inactive after they leave incubator. > > I'm sure the ASF doesn't want to get into the habit of taking > > abandoned projects and shoving everything into the attic, so I'd > > rather see it get included in Cordova as one of the less active > > repositories. > > >
Re: [Discuss] The Future of Ripple as a Top Level ASF Project
+1 for moving to Cordova... JBoss IDE uses base Ripple and with some extensions to it. I will ping Red Hat committers if we can contribute some of that to Ripple. -- Gorkem On Tuesday, April 22, 2014, Shazron wrote: > +1 on absorbing Ripple > > > On Tue, Apr 22, 2014 at 8:16 AM, Joe Bowser > > wrote: > > > On Tue, Apr 22, 2014 at 7:30 AM, Brent Lintner > > > > > > wrote: > > > Hey All, > > > > > > Since becoming an incubator project (being donated graciously by > > > BlackBerry), Ripple has seen positive contributions. > > > > > > However, it is also apparent that the community does not seem large > > enough > > > to sustain a project like this as a top level project (let alone an > > > individual PMC). > > > > > > Three of the original contributors/creators of Ripple are now fully > > > involved in a new technology startup in an unrelated field and > therefore > > we > > > no longer have the resources to support Ripple in ASF. Also, BlackBerry > > has > > > given no resources to help since donating Ripple to the ASF (this might > > be > > > due to a change in their internal priorities). > > > > > > Given this, I would like to propose: > > > > > > 1. We find more community members willing to lead committership of the > > > project, and see how that goes. > > > > > > 2. We also consider the eventuality of folding Ripple into another ASF > > > project, if possible. If so, it would seem Cordova is a candidate for > > this, > > > especially given the project being one of Ripple's main focus and > > support. > > > If the community votes for this, we should involve the Cordova > community > > to > > > gage their interests as well (I've CC'd their mailing list in this > > email). > > > > I'd +1 this. I'd like to see Ripple live on in some form if people > > are still using it, even though I don't use it personally. > > > > > > > > 3. If the above does not work out, I would then suggest we consider the > > > most unfortunate (put perhaps prudent) eventuality, which is to "fail" > > > Ripple as an incubator project. "fail" is this case, not being > negative. > > > > > > > So, Incubator projects can't go into the Attic? That's what the ASF > > does with projects that become inactive after they leave incubator. > > I'm sure the ASF doesn't want to get into the habit of taking > > abandoned projects and shoving everything into the attic, so I'd > > rather see it get included in Cordova as one of the less active > > repositories. > > >
Re: [Discuss] The Future of Ripple as a Top Level ASF Project
+1 on absorbing Ripple On Tue, Apr 22, 2014 at 8:16 AM, Joe Bowser wrote: > On Tue, Apr 22, 2014 at 7:30 AM, Brent Lintner > wrote: > > Hey All, > > > > Since becoming an incubator project (being donated graciously by > > BlackBerry), Ripple has seen positive contributions. > > > > However, it is also apparent that the community does not seem large > enough > > to sustain a project like this as a top level project (let alone an > > individual PMC). > > > > Three of the original contributors/creators of Ripple are now fully > > involved in a new technology startup in an unrelated field and therefore > we > > no longer have the resources to support Ripple in ASF. Also, BlackBerry > has > > given no resources to help since donating Ripple to the ASF (this might > be > > due to a change in their internal priorities). > > > > Given this, I would like to propose: > > > > 1. We find more community members willing to lead committership of the > > project, and see how that goes. > > > > 2. We also consider the eventuality of folding Ripple into another ASF > > project, if possible. If so, it would seem Cordova is a candidate for > this, > > especially given the project being one of Ripple's main focus and > support. > > If the community votes for this, we should involve the Cordova community > to > > gage their interests as well (I've CC'd their mailing list in this > email). > > I'd +1 this. I'd like to see Ripple live on in some form if people > are still using it, even though I don't use it personally. > > > > > 3. If the above does not work out, I would then suggest we consider the > > most unfortunate (put perhaps prudent) eventuality, which is to "fail" > > Ripple as an incubator project. "fail" is this case, not being negative. > > > > So, Incubator projects can't go into the Attic? That's what the ASF > does with projects that become inactive after they leave incubator. > I'm sure the ASF doesn't want to get into the habit of taking > abandoned projects and shoving everything into the attic, so I'd > rather see it get included in Cordova as one of the less active > repositories. >
Re: [Discuss] The Future of Ripple as a Top Level ASF Project
On Tue, Apr 22, 2014 at 7:30 AM, Brent Lintner wrote: > Hey All, > > Since becoming an incubator project (being donated graciously by > BlackBerry), Ripple has seen positive contributions. > > However, it is also apparent that the community does not seem large enough > to sustain a project like this as a top level project (let alone an > individual PMC). > > Three of the original contributors/creators of Ripple are now fully > involved in a new technology startup in an unrelated field and therefore we > no longer have the resources to support Ripple in ASF. Also, BlackBerry has > given no resources to help since donating Ripple to the ASF (this might be > due to a change in their internal priorities). > > Given this, I would like to propose: > > 1. We find more community members willing to lead committership of the > project, and see how that goes. > > 2. We also consider the eventuality of folding Ripple into another ASF > project, if possible. If so, it would seem Cordova is a candidate for this, > especially given the project being one of Ripple's main focus and support. > If the community votes for this, we should involve the Cordova community to > gage their interests as well (I've CC'd their mailing list in this email). I'd +1 this. I'd like to see Ripple live on in some form if people are still using it, even though I don't use it personally. > > 3. If the above does not work out, I would then suggest we consider the > most unfortunate (put perhaps prudent) eventuality, which is to "fail" > Ripple as an incubator project. "fail" is this case, not being negative. > So, Incubator projects can't go into the Attic? That's what the ASF does with projects that become inactive after they leave incubator. I'm sure the ASF doesn't want to get into the habit of taking abandoned projects and shoving everything into the attic, so I'd rather see it get included in Cordova as one of the less active repositories.
