Susan Bugher said:
The web pages on the CD will be created *once* expecially for the CD.
They will not be the same as the online pages.
Okay.
PL2005 will have 200-300 programs, say 400-600 files. I gather you are
suggesting a script with direct DL links (difficult or unwelcome in
many instances).
The list of direct download links does not have to be in the same file as
the script. The script could use an external list to download the program
files and put them in a suitable folder structure.
You are right that direct download links can be difficult to find in many
cases. I wonder how many percents of them?
Maybe 5 % ?
We could predict that the script would not be used by so many, so there
is no need for spreading the load. So we can bypass mirror systems and
give the script a direct link when the problem is mirror arrangements.
So I don't agree about the "unwelcome" idea.
I don't think the script will be used by enough people to make it
"unwelcome".
An update would require checking *all* the URLs. IMO
Let me just point out that links can be checked by running the script.
So a script would simplify link checking.
at least 70-80 percent of the URLs would have to be revised for a
mid-year update.
ACF participants will be asking the authors for permission to do
certain things. The CD goals and procedures spell out what we intend to
do and how we intend to do it. The authors will be asked to consent to
that.
A script for downloading needs no consent, as far as I can understand.
If we as a group are involved in organising volunteers creating physical
CD's and distribution of them we should of course ask for permission in
the cases where the license does not allow it to begin with.
I just meant that there is a possibility, in the future maybe, if needed,
to change the level of responsibility by only creating the script and let
others use it.