Chris Nighswonger <cnighswonger@foundations.edu> wrote:
Given that this discussion has been somewhat carried on through the wiki (http://wiki.koha-community.org/wiki/General_Meeting,_June_2_2010), I thought it would be good to keep it on list as well.
I only added a link back to this thread. No new discussion was raised there. I agree that it's good to keep it nearly all on list. Small update on the above from the meeting: thd will be emailing the list with a summary of discussions he's had with SFLC.
[...] A vendor would have to deliberately remove or disable this functionality to prevent a client from retrieving a full copy of their database.
Of course any vendor locking clients in will disable that!
(Of course any client who contracts with a vendor *without* writing data protection assurances into their contract is asking for trouble to start with.)
I feel that any client who contracts with a vendor without writing code access assurances in to their contract is asking for trouble to start with. AGPLv3 is unnecessary with good vendors and does not prevent lock-in vendors from locking clients in. Basically, it's much pain for no gain.
The matter of "onerous burdens on friendly hosters" has been addressed in previous communications and so those arguments are not repeated here.
Yes, it's been addressed, not answered. Let's see what thd reports. Regards, -- MJ Ray (slef) Webmaster and LMS developer at | software www.software.coop http://mjr.towers.org.uk | .... co IMO only: see http://mjr.towers.org.uk/email.html | .... op