Am 08/04/2011 01:57 AM, schrieb Dave Fisher:
On Aug 3, 2011, at 4:31 PM, Gavin McDonald wrote:
-----Original Message-----
From: Marcus (OOo) [mailto:marcus.m...@wtnet.de]
Sent: Thursday, 4 August 2011 8:54 AM
To: ooo-dev@incubator.apache.org
Subject: Re: How to handle the downloads?
Am 08/04/2011 12:38 AM, schrieb Gavin McDonald:
-----Original Message-----
From: Marcus (OOo) [mailto:marcus.m...@wtnet.de]
Sent: Wednesday, 3 August 2011 6:45 PM
To: ooo-dev@incubator.apache.org
Subject: Re: How to handle the downloads?
Am 08/03/2011 02:17 AM, schrieb Gavin McDonald:
-----Original Message-----
From: Marcus (OOo) [mailto:marcus.m...@wtnet.de]
Sent: Wednesday, 3 August 2011 9:40 AM
To: ooo-dev@incubator.apache.org
Subject: Re: How to handle the downloads?
Am 08/02/2011 11:03 PM, schrieb Gavin McDonald:
-----Original Message-----
From: Marcus (OOo) [mailto:marcus.m...@wtnet.de]
Sent: Wednesday, 3 August 2011 12:55 AM
To: ooo-dev@incubator.apache.org
Subject: Re: How to handle the downloads?
Thanks for you note. Then we should implement adownload method
withthe fllowing order:
1. User clicks on the One-Click-Download URL and get the software
(like today on "download.openoffice.org").
2. If not, he can use alternative download links (like today on
"download.openoffice.org/pther.html").
3. If a special mirror has to be used, the list of all available
mirrors
will help
(like today on
"http://distribution.openoffice.org/mirrors/#mirrors";).
Latest with step 3 all users should be able to download something.
Yep, all possible here at the ASF right now.
See www.apache.org/mirrors for our equiv of step 3.
I've already understood that you don't want the OOo mirrors but
that we should use the Apache ones. ;-)
Hi Marcus,
don't count me as 100% on that yet, I want to know more about the
OOo mirrors too.
OK, if you have already questions just ask and I will try to give
answers.
not yet, working on it,
I just didn't want to be maintaining 150+ projects on one mirror
system and
1 project
on another mirror system. maintaining one mirror system is easier,
so If that is possible and our mirroring system can cope, and we can
maybe coax a few more mirrors our way all the better. Some of our
existing mirrors may decide that bandwidth is too much and leave, so
we need replacements.
I don't know about bandwidth but to get an impression about size and
amount please have a look here. This mirror has rsync'ed everything
that
was
released by Sun and Oracle:
http://ftp5.gwdg.de/pub/openoffice/
thanks,
If it makes sense to try and merge these somehow, I want to pursue
that avenue.
A first step should be to look for doubles.
yep,
We may need both for some time, we can not put non ASF releases on
our mirroring system anyway so what we are trying to resolve is from
our first ASF release onwards.
Hm, when looking at this mirror it is already hosting non-Apache
software:
ftp://ftp.uni-erlangen.de/pub/mirrors/
Software from Apache and, e.g., OpenOffice.org is just a subset
within
many
other projects.
Sorry, that isn't what I meant. The mirrors get their content from us
right, we can not provide them with non-asf released software to put
on their mirror copy of our dist tree [1] . They are of course welcome
to provide non-asf mirrors as most of them already do.
[1] - http://apache.org/dist/
Gav...
OK, let me try again. The mirrors can distribute what ever they want but
within the Apache subdirs only ASF licensed software is allowed. Have a
got it
right now?
Spot on.
And the only way non ASF licenses software will get into the Apache subdirs
is
if we put it there in the first place.
A project makes a release and puts the files of that release into a specific
area of
svn. That then syncs up with our main dist area, mirrors then sync up from
there.
Do we have to commit our binary files into SVN? I hope not. ;-)
IOW, the pre-existing mirror system for OOo needs to continue and be
referred to
in documentation and 'older releases' page so that folks can get pre-asf
released
versions of OOo from there. Only new releases from now onwards developed
here
at ASF will be put into our release/dist areas.
Yes, sounds a reasonable separation.
However, when we don't migrate our Mirrorbrain load balancer, then we
need a new method to choose an appropriate mirror as the current
"download.cgi" works only for ASF mirrors.
Here is the big question.
As long as the Apache hosted version of download.openoffice.org points to
mirrors with already existing OOo releases that were put on the mirrors by
Oracle/Sun then we are A-OK? Correct?
If so, then I think we are good to go as long as it is clear what is AL2.0 and
what is not.
Then the implication is that the magic on the download pages should clearly
indicate AL2.0 or legacy - maybe with color, a title change and an Apache
feather icon.
Is that enough for us to keep JFDI?
Regards,
Dave
Marcus
Am 08/02/2011 04:38 PM, schrieb Donald Whytock:
A consideration...I for one have a need to be able to select my
mirror. My office's firewall blocks certain domains and
websites, especially those recognized as "hosting" or
"file-sharing"
sites.
It does not, however, block .edu sites, so when I download an
Apache product I select a university mirror.
Other users may have similar constraints. If OOo's download
process is going to tie into Apache mirroring, please don't
completely eliminate the capacity to select the mirror.
Don
