[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Berkeley DB 6.0 license change to AGPLv3

On 03/07/13 16:34, Bradley M. Kuhn wrote: [...]
> I know that some have complained that compliance with AGPLv3 may require
> more work by Debian redistributors.  That is a reasonable concern, but I
> think the issue can be mitigated. [...seems to continue to other topics...]

OK, how?

My preferred method at the moment is to grant or request from copyright
holders the following additional permissions:

    * Developers need publish their modifications only (not the whole
application source code with all unusual libraries), as long as it
provides a URL or link back to complete upstream source code repository/ies.

    * The running application need not check if the source code is
currently on-line (so long as it is usually and can be requested).

But I doubt Oracle will grant additional permissions, so how can the
issue be mitigated?

MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op
http://koha-community.org supporter, web and library systems developer.
In My Opinion Only: see http://mjr.towers.org.uk/email.html
Available for hire (including development) at http://www.software.coop/

Reply to: