Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CA+ULb+t0OMO1A0WwTYkwQpCC=+1RapZ__z7GV1A5nQxAiJOctQ@mail.gmail.com>
References: 
 <CAKBQfzSzq6hYP1CrdGLuUsmzf4ewRhAa6vqWo8niq+3rCZuGcw@mail.gmail.com>
 <56E7421B.6030808@shanecurcuru.org>
 <CA+ULb+t0OMO1A0WwTYkwQpCC=+1RapZ__z7GV1A5nQxAiJOctQ@mail.gmail.com>
From: Stian Soiland-Reyes <stain@apache.org>
Date: Mon, 21 Mar 2016 15:48:42 +0000
Message-ID: 
 <CAMBJEmUhZLwdtoWZt=W_=3TaORT4OVTdKugZhrohfUmPRYpOMA@mail.gmail.com>
Subject: Re: Hosting links to pre-Apache releases
To: general@incubator.apache.org
Cc: Greg Stein <gstein@gmail.com>
Content-Type: text/plain; charset=UTF-8

On 14 March 2016 at 23:52, Roman Shaposhnik <roman@shaposhnik.org> wrote:
> Agreed. The good news is that the previous license has an added benefit
> of being compatible with ALv2, but of course we still have to be crystal clear
> on that.
>
> Any good example of this that currently exist in ASF?

Here's an example of how we do the non-ASF download links for
Taverna Workbench (as we have not yet released the Workbench
repository under ASF):

https://taverna.incubator.apache.org/download/workbench/

(Comments welcome!)

To play safe we made it so the *.exe download links here actually
don't download directly, but go to a third-party legacy page where you
have to select again.   It could be that such a page could just be a
Launchpad, BinTray,  BitBucket or GitHub Releases, which should be
good alternatives for hosting the pre-Apache binaries.  So perhaps you
would be able to link to say
https://github.com/madlib/madlib/releases/tag/v1.7.0 ?

It should be easy for madlib's case as you don't have binary distributions.


>> Note we probably don't want to host the actual downloads themselves;
>> just point to the existing old download page.
> Actually, we'd rather move the bits to ASF infra (if that's ok).

Hmm... although their Apache license would permit this, those earlier
releases has not gone through IP review.

I think this would be confusing as then ASF would be hosting downloads
for non-ASF-vetted releases - which would also be against policy.
Technically ASF also uses the mirror network for downloads - do we
want to inject non-ASF releases there?


-- 
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons RDF (incubating)
http://orcid.org/0000-0001-9842-9718

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org