ripple-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Speed, Derek" <derek.sp...@intel.com>
Subject RE: Ripple retirement? (Re: Incubator PMC/Board report for Oct 2014 ([ppmc]))
Date Tue, 21 Oct 2014 16:41:37 GMT
Hi Raymond,

I am trying to get my head around the Cordova browser platform concept and came across your
very informative blog post here: http://www.raymondcamden.com/2014/9/24/Browser-as-a-platform-for-your-PhoneGapCordova-apps

In the comments to your blog post, you stated that you thought that the browser as a platform
concept in Cordova felt like a better approach than Ripple - could you please elaborate a
little on this?

Just so folks understand where I am coming from, here is a little background. Our product,
the Intel XDK, uses Ripple as the basis of our device emulator. We have been putting some
effort into a proof-of-concept that involves refactoring Ripple such that the implementation
of the emulation is provided via  Cordova plug-ins rather than built into Ripple itself. 
This seems to have a fair amount of overlap conceptually with the Cordova browser as a platform
effort so we are trying to form an opinion on which approach makes more sense for us to look
at investing in for the longer term. 

Any insight/advice you or anyone else on the Ripple list can provide that compares the pros/cons
of the two approaches is greatly appreciated.

Thanks,
Derek

-----Original Message-----
From: Raymond Camden [mailto:raymondcamden@gmail.com] 
Sent: Wednesday, October 15, 2014 8:00 PM
To: dev@ripple.incubator.apache.org
Subject: Re: Ripple retirement? (Re: Incubator PMC/Board report for Oct 2014 ([ppmc]))

Actually, the Browser platform can be tested now and will be released very soon. If I had
to guess, at PhoneGap Day in a week. It is definitely *not*
6 months out.

On Wed, Oct 15, 2014 at 6:14 PM, Parashuram Narasimhan (MS OPEN TECH) < panarasi@microsoft.com>
wrote:

> Microsoft also has an interest in Ripple given that our Multi-Device 
> Development offering leverages Ripple in the development workflow. We 
> use Ripple only for Cordova-related workflows. However, we plan to 
> start using cordova-browser when it is finalized and replace Ripple 
> with that. However, cordova-browser is at least 6 months away.
>
> Can this project continue in its current state for the next 6 months ? 
> I can volunteer to help with releases, reports and bug fixes if that 
> is a concern. Can we revisit this decision after 6 months?
>
> -----Original Message-----
> From: Speed, Derek [mailto:derek.speed@intel.com]
> Sent: Thursday, October 9, 2014 12:02 PM
> To: dev@ripple.incubator.apache.org
> Subject: RE: Ripple retirement? (Re: Incubator PMC/Board report for 
> Oct
> 2014 ([ppmc]))
>
> As many of you on this list know, the device emulator in the Intel XDK 
> is based on Ripple so we have a strong interest in the future 
> direction of Ripple. However, most of our focus within the Intel XDK 
> team on Ripple development has been on adapting it to meet our 
> specific needs in the Intel XDK and we have, regrettably, not spent 
> much effort on contributing to the upstream project.
>
> Recently, we have been discussing some collaboration opportunities 
> between Cordova and Ripple that Brent mentioned below. We're very 
> close to having something worth sharing with the community for 
> feedback. So, stay tuned for an e-mail on the early results of the 
> technical work we have been doing together.
>
> Thanks,
> Derek
>
> -----Original Message-----
> From: Brent Lintner [mailto:brent.lintner@gmail.com]
> Sent: Thursday, October 9, 2014 11:35 AM
> To: dev@ripple.incubator.apache.org
> Subject: Re: Ripple retirement? (Re: Incubator PMC/Board report for 
> Oct
> 2014 ([ppmc]))
>
> Pending the voice call that went on yesterday about Ripple/Cordova 
> collaboration (of which I did not make):
>
> IMO: I find GitHub projects (even from my direct experience) develop 
> and sustain active communities without well defined governance (that 
> develops on demand), and (ideally) provides a truly central (and 
> familiar) channel of communication, contribution, and community. I.e 
> Issues, PRs, Wikis, etc- all the tools you need in one place.
>
> FWIW, we were on GitHub when open sourced by Blackberry in the first 
> place, and I felt it was sufficient, and easier to coordinate.
>
> Given that, I feel the project has the best chance of continuing on 
> outside of the ASF, because freeing up the process of development and 
> releasing versions might very well reignite contribution, community, 
> and admin management. Things like Cordova adoption or trademark issues 
> can still be worked out there.
>
> +1 to Github.
>
> PS: If a specific user account is needed to host the fork, I can volunteer.
> While I am less in the space than others, I can benevolently manage 
> the project by giving read/write access and name maintainers to any 
> who are willing or currently committers, and we could go from there (as a thought).
>
> On Wed, Oct 8, 2014 at 11:10 AM, Christian Grobmeier <cg@grobmeier.de>
> wrote:
>
> > The project is AL 2.0 licensed so to my understanding the Github 
> > project would be a "fork" of the original Ripple.
> > The owners of the fork would "own" it then.
> >
> > Please note that to my knowledge a few things are not sorted out 
> > license wise, in example some images. Like we would have needed to 
> > sort this out here, it would be wise to sort it out on GitHub as well.
> >
> > There are some cases when the name could be taken to GitHub. Please 
> > note this requires discussion with the trademark folks.
> > As there is almost no community so far, it might be difficult to 
> > argue if a single person would be able to get the name.
> > However, I defer you to the trademarks@apache list if any questions 
> > in that direction.
> >
> > On Wed, Oct 8, 2014, at 16:51, Raymond Camden wrote:
> > > Would would "own" the project?
> > >
> > > On Wed, Oct 8, 2014 at 9:47 AM, Christian Grobmeier 
> > > <grobmeier@gmail.com
> > >
> > > wrote:
> > >
> > > > It's not necessary to move to GitHub if nobody wants.
> > > > My main point is that there is almost zero community here and 
> > > > it's unlikely to change. If Brent or Raymond want to apply a fix 
> > > > or so in the future, they could go to GitHub.
> > > >
> > > > --
> > > >   Christian Grobmeier
> > > >   grobmeier@gmail.com
> > > >
> > > > On Wed, Oct 8, 2014, at 16:39, Ross Gardler (MS OPEN TECH) wrote:
> > > > > How does it going to GitHub help?
> > > > >
> > > > > Sent from my Windows Phone
> > > > > ________________________________
> > > > > From: Raymond Camden<mailto:raymondcamden@gmail.com>
> > > > > Sent: ‎10/‎8/‎2014 7:26 AM
> > > > > To:
> > > > > dev@ripple.incubator.apache.org<mailto:
> > dev@ripple.incubator.apache.org>
> > > > > Subject: Re: Ripple retirement? (Re: Incubator PMC/Board 
> > > > > report for
> > Oct
> > > > > 2014 ([ppmc]))
> > > > >
> > > > > As much as I like Ripple, I know I don't have a lot of time to
> > devote to
> > > > > it. I'd be fine with it going to GitHub.
> > > > >
> > > > >
> > > > > On Wed, Oct 8, 2014 at 3:46 AM, Christian Grobmeier <
> > grobmeier@gmail.com
> > > > >
> > > > > wrote:
> > > > >
> > > > > > Hello all,
> > > > > >
> > > > > > we need to report soon, and I have made a few observations.
> > > > > >
> > > > > > We are actually not active in any kind. This is very sad, 
> > > > > > because
> > most
> > > > > > of us here
> > > > > > want Ripple to survive, but it's the truth.
> > > > > >
> > > > > > We don't have commit activity. Only two of us where 
> > > > > > discussing a
> > new
> > > > > > committer
> > > > > > to join, without managing to finally start the vote (reminder:
> > this is
> > > > a
> > > > > > dev list, new
> > > > > > committers are discussed on the private list).
> > > > > > Usually I have to push the report further to the Ripple 
> > > > > > lists and
> > its
> > > > > > hard to get a report
> > > > > > done any time.
> > > > > >
> > > > > > I was wondering if we have a serious chance to change this.
> > > > > >
> > > > > > Yes, we discussed to join Cordova as subproject. But it 
> > > > > > won't help
> > if
> > > > > > there are no
> > > > > > volunteers from that place taking over.
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > >
> > > >
> > ====================================================================
> > ==
> > =====
> > > > > Raymond Camden, Web Developer for Adobe
> > > > >
> > > > > Email : raymondcamden@gmail.com Blog : 
> > > > > www.raymondcamden.com<http://www.raymondcamden.com>
> > > > > Twitter: raymondcamden
> > > >
> > >
> > >
> > >
> > > --
> > >
> > ====================================================================
> > ==
> > =====
> > > Raymond Camden, Web Developer for Adobe
> > >
> > > Email : raymondcamden@gmail.com
> > > Blog : www.raymondcamden.com
> > > Twitter: raymondcamden
> >
>
>
>
> --
> Brent Lintner
>



--
===========================================================================
Raymond Camden, Web Developer for Adobe

Email : raymondcamden@gmail.com
Blog : www.raymondcamden.com
Twitter: raymondcamden
Mime
View raw message