Kevin P. Fleming dixit: >For the vast majority of OSI-approved licenses, the activities you >noted above do not trigger any license obligations because you are >only using the software and not distributing it. A notable exception >is the AGPL family of licenses, which extend the 'distribution' >definition to include 'providing access to the functionality of the
And, of course, anything that *is* distributed to the user. This usually encompasses all frontend code (ECMAscript), but also if the backend code exposes copyrightable parts of itself, such as large help messages. In general, making available a list of shoulders you stand on is considered good code provenance hygiene. bye, //mirabilos -- I believe no one can invent an algorithm. One just happens to hit upon it when God enlightens him. Or only God invents algorithms, we merely copy them. If you don't believe in God, just consider God as Nature if you won't deny existence. -- Coywolf Qi Hunt _______________________________________________ The opinions expressed in this email are those of the sender and not necessarily those of the Open Source Initiative. Official statements by the Open Source Initiative will be sent from an opensource.org email address. License-discuss mailing list License-discuss@lists.opensource.org http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org
