ripple-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ross Gardler (MS OPEN TECH)" <>
Subject RE: Why no releases?
Date Tue, 11 Nov 2014 18:10:59 GMT
Can anyone explain how it is that there is no ASF release yet the readme says:

"To install:

    npm install -g ripple-emulator"

Inspecting ripple-emulator on npm I see lots of mentions of Apache Ripple and no clear indication
that this is an incubating project. It looks to any uninformed user that this is an Apache
release, but it is not.  NPM was last updated a month ago.

More importantly the foundation is unable to provide appropriate legal protection for contributors
unless these release approved by the ASF.

This needs to be fixed, and quickly. Apache projects must conform to our release policy. This
is fundamentally important to the foundation and shoule be equally important to contributors
who hope to receive the legal protection that the foundation has been created to provide.

The overhead in making a release is minimal (at least once the initial due diligence has been
done on entry into the incubator).

Thanks for the input on the current status of the IP review. It is great that it seems it's
pretty much complete. Lets finish the job and get a release out.


-----Original Message-----
From: Gord Tanner [] 
Sent: Thursday, October 30, 2014 12:48 PM
To: dev
Subject: Re: Why no releases?

AFAIK The images that were the problem were removed with that commit.

There still is the notice file here [0].

I am wondering if [1] needs to be cleaned up too.

[0] -
[1] -

On Thu, Oct 30, 2014 at 1:44 PM, Horn, Julian C <>

> This may or may not be a real problem.  Note the following commit comment:
> commit c317ffb1446d821727a453b317fdaf0a7d634d4f
> Author: Gord Tanner <>
> Date:   Sun Oct 20 22:37:34 2013 -0400
>     Remove Images that were not able to licence apache.
>     When BlackBerry first opensourced Ripple there was some problems
>     with them open sourcing the images of their phones.  I have removed
>     all the images that BlackBerry put in of their phones and removed the
>     notice and Readme.
>     This should help us get closer to being able to do an Apache 
> release
> Here's a little more background.  Originally there was a file named 
> NOTICE in the assets/client/images folder containing the following text:
> The images and logos provided in this project are proprietary to their 
> owners, excluded from the Apache 2.0 license, and cannot be used for 
> any other purpose.
> Note that this wording does not indicate which images are considered 
> proprietary.  Based on Gord's comment, I'm going to guess that he has 
> reason to believe that it's only the device skins that were actually 
> considered proprietary.
> Later this NOTICE file was copied to assets/server/images.  Later 
> still the device skins were removed, and the NOTICE file was removed 
> from assets/client/images, presumably by the above commit.
> Today the NOTICE file remains in assets/server/images, but I believe 
> this is an oversight.  There are no phone images in that folder, only 
> the Ripple logo.  There is a Ripple logo in asserts/client/server, so 
> it follows that if the files in assets/client/server are now OK then 
> the files in asserts/server/images are also OK.  Therefore the NOTICE 
> file should be removed from assets/server/images.
> I don't know of my own knowledge whether this removes the last barrier 
> to doing an Apache release.  Gord's comment says his change "gets us 
> closer", so perhaps that means he has in mind some other cleanup.
>     Julian
> -----Original Message-----
> From: Christian Grobmeier []
> Sent: Thursday, October 30, 2014 12:00 PM
> To:
> Subject: Re: Why no releases?
> I haven't it right here, but I asked before ages on this list.
> I think its pretty much everything which is an image used for letting 
> the browser look like a phone
> If nobody else here can comment, I will try to find the email from the 
> archives
> --
>   Christian Grobmeier
> On Thu, Oct 30, 2014, at 16:46, Ross Gardler (MS OPEN TECH) wrote:
> > Thanks Christian. I guess that is something we need to fix. Is there 
> > a list of these resources that need replacing anywhere handy?
> >
> > Microsoft Open Technologies, Inc.
> > A subsidiary of Microsoft Corporation
> >
> > -----Original Message-----
> > From: Christian Grobmeier []
> > Sent: Thursday, October 30, 2014 8:34 AM
> > To:
> > Subject: Re: Why no releases?
> >
> > One of the issues I am aware of is that we are not having the right 
> > to redistribute some images. We need to replace them
> >
> > --
> >   Christian Grobmeier
> >
> >
> > On Thu, Oct 30, 2014, at 16:30, Ross Gardler (MS OPEN TECH) wrote:
> > > I note that Ripple has not made any releases as yet. Why is this?
> > >
> > > Sent from my Windows Phone
View raw message