[liblouis-liblouisxml] Re: Google code project downloads
- From: Christian Egli <christian.egli@xxxxxx>
- To: Michael Whapples <mwhapples@xxxxxxx>
- Date: Wed, 02 Oct 2013 10:50:04 +0200
Michael Whapples <mwhapples@xxxxxxx> writes:
> Google Code will not be offering the ability to create new downloads
> after 15 January 2014. So my question is, how do we plan to provide
> liblouis and liblouisutdml release downloads after that point?
I saw that and wondered myself. Thanks for bringing this up.
> do people find release downloads useful? This could include binary
> builds as well as source tarballs, or would just having release tags
> in the repository be sufficient?
If you look at the numbers you'll see that people do actually use the
tarballs and the windows binaries. If we just had release tags that
would mean that the users would have to fetch the code from svn and
build it using autotools. Release tarballs and windows binaries make it
much easier for the user, so I think we need to provide those.
> Do we want to provide these through another website/FTP server or
> shall we look at other project hosting services like SourceForge,
> BitBucket or GitHub?
Basically I think we are (were) quite happy with Google Code. It
provided us with code repo (svn), a basic web site, downloads, a minimal
bug tracker and hosting of the online manual. I see the following
options:
- Just forget about downloads. No longer provide them. As I said above,
I think we should have downloads.
- While I like GitHub and use it for all my other stuff it also doesn't
provide downloads (the downloads are only snapshots of the repo and
not binaries). Don't know how we'd do the online manual.
- SourceForge would be an option, has svn, web site, issues and
downloads, but is a bit too cluttered for my taste. Don't know how
we'd do the online manual.
- I don't know BitBucket. From a cursory glance it seems to have it all
(downloads, minimal website, issues and repo). The big issue here is
that liblouis would have to move to hg or git. Again don't know how
we'd do the online manual. And god knows when they are disabling
downloads (you get what you pay for just like with Google).
- Self hosting. Have a minimal static web site that allows for web site,
downloads and online manual. Keep the rest as is (repo and issues on
Google or some other place). As far as I know John (or viewplus) has
the liblouis.org domain, so this might be an option.
- Use Google drive for downloads as they suggest. Seems a bit of a
makeshift solution.
- Become a GNU project. We could then use the GNU infrastructure for
projects, i.e. web site, download, online manual, code repo and
issues. This would be safe long term but would probably involve some
politics (we would not have to change the license but the GNU label
might scare some people).
Thanks
Christian
--
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zürich, Switzerland
-----
Die neue Online-Bibliothek der SBS: Mit wenigen Klicks zum Buch unter
http://online.sbs.ch
For a description of the software, to download it and links to
project pages go to http://www.abilitiessoft.com
Other related posts:
