<div class="gmail_quote">On Sun, May 9, 2010 at 10:37 PM, Lars Wirzenius <span dir="ltr"><<a href="mailto:lars@catalyst.net.nz">lars@catalyst.net.nz</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
* AGPLv3 is a variant of GPLv3. As Chris said, the main difference is<br>
that users of the program will need be given access to the source of the<br>
actual running program. That includes anyone using the OPAC, not just<br>
librarians. Anyone running unmodified Koha can just point people at the<br>
<a href="http://download.koha-community.org" target="_blank">download.koha-community.org</a> (or Debian or wherever they installed it<br>
from). Anyone running a modified Koha will need to provide the source<br>
themselves, although it might be possible to do that as a patch, to<br>
avoid excessive bandwidth costs. However, bandwidth costs can probably<br>
be reduced by, say, using bittorrent.<br></blockquote></div><br>Paragraph 13 of the AGPLv3 reads, in part, thus:<br>
<br>
"Notwithstanding any other provision of this License, if you modify<br>
the Program, your modified version must prominently offer all users<br>
interacting with it remotely through a computer network (if your<br>
version supports such interaction) an opportunity to receive the<br>
Corresponding Source of your version by providing access to the<br>
Corresponding Source from a network server at no charge, through some<br>
standard or customary means of facilitating copying of software."<br>
<br>
The wording used here is "a network server" (emphasis on the indefinite<br>article and broad terminology) which does not necessarily<br>
imply either the server running the software, or even any server<br>
located on the network of the entity running the software. A public<br>
git server containing a repository kept current with the changes made<br>
by that entity would clearly qualify as "a network server." in this<br>
context. Ie. github or some other hosting repository could be used<br>which represents little to no cost on the part of the entity. Or<br>(better yet) simply ensuring that all such modified code is immediately<br>contributed to the main code base would also seem to satisfy this <br>
requirement.<br><br>Kind Regards,<br>Chris<br>