[MEI-L] Google Code deprecating downloads

Roland, Perry (pdr4h) pdr4h at eservices.virginia.edu
Tue Nov 19 16:10:34 CET 2013

This is a possible solution --

Comment by bperry... at gmail.com, Aug 13, 2013

The reasoning of eliminating the Downloads totally escapes me. The proposed solution by Google is pretty silly and solves nothing given that you can access files in your repository through direct links to the files - EXACTLY the same way links to the Downloads files works. All that has changed is that maintaining the downloadable files and using direct links to downloadable files is now much less convenient for the project maintainers and there is not a way to get the total download count.

So here is a better solution than Google's proposed solution that does not involve using Google Drive AND still keeps the download files in your project repository so they can be easily managed by all the project team.

Simply create a "Downloads" directory in your repository. Then create a wiki page for downloading your files. You can then place any files you want to make available in your new "Downloads" directory (which is now part of the Repo). You can add whatever text you want to the wiki "Downloads" page and put in the direct link in your repo to the download file. If you don't know how to get the link, then simply browse your source tree until you get to the file, click on it, then look over on the right and copy the link location for the "View raw file" link. If you are ambitious enough you can even add the SHA1 checksum to the wiki page.

You now have a wiki page that allows downloading your files. You can even put links to your wiki "Downloads" wiki page on your Project Summary/Home page or add it as link to your links section on the Summary/Home page. The downside is you have update that wiki page each time you add a file to the "Downloads" directory if you want to provide a direct download link to the file.

So there you have it. A way to continue offering Downloads and direct links that keeps the download files with the project, that all project administrators can use, and no messing with Google Drive.

--- bill

We already have the schemas in the repo, just not the Guidelines PDF, so this could work for us.  I just created a "Download Test" page in the Wiki that appears to work fine.



> -----Original Message-----

> From: mei-l [mailto:mei-l-bounces at lists.uni-paderborn.de] On Behalf Of Peter

> Stadler

> Sent: Tuesday, November 19, 2013 6:12 AM

> To: Music Encoding Initiative

> Subject: [MEI-L] Google Code deprecating downloads


> From January 15, 2014, Google will no longer offer the ability to create new

> downloads:


> http://google-opensource.blogspot.de/2013/05/a-change-to-google-code-<http://google-opensource.blogspot.de/2013/05/a-change-to-google-code-download-service.html>

> download-service.html<http://google-opensource.blogspot.de/2013/05/a-change-to-google-code-download-service.html>


> As far as I can see, the MEI schema files (and more?) are served from there, so

> we should look for another download location and move the files there. One

> could as well move to GitHub with the whole repository ...


> Best

> Peter



> --

> Peter Stadler

> Carl-Maria-von-Weber-Gesamtausgabe

> Arbeitsstelle Detmold

> Gartenstr. 20

> D-32756 Detmold

> Tel. +49 5231 975-665

> Fax: +49 5231 975-668

> stadler at weber-gesamtausgabe.de

> www.weber-gesamtausgabe.de<http://www.weber-gesamtausgabe.de>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20131119/89a3b75f/attachment.html>

More information about the mei-l mailing list