I agree completely with Philippe; a statement such as you proposed does not
modify the license, but it indicates to downstream consumers the scenarios
under which they could expect you to (potentially) enforce the attribution
requirement, and situations under which you do not intend to enforce the
On Fri, May 20, 2016 at 4:06 AM, Andi McClure wrote:
> I am working on some projects (a programming language, a game library) for
> which I wish to use a "source attribution" license-- for example, the zlib
> license, or the 2-clause BSD license if I could somehow delete
cess by You for as long as Licensor
continues to distribute the Original Work.
OSL 3.0 <https://opensource.org/licenses/osl-3.0> § 3.
/Larry
From: Andi McClure [mailto:andi.m.mccl...@gmail.com]
Sent: Thursday, May 19, 2016 7:06 PM
To: license-discuss@opensource.org
Subject:
On 20/05/16 03:06, Andi McClure wrote:
"For purposes of the above license, 'source' is defined as the
preferred form for making modifications to the code. In other words,
minified Javascript which is not intended to be modified does not count
as a 'source distribution'."
…and if I included
Andi McClure scripsit:
> The zlib license refers to "source distributions". The BSD license refers
> to "redistributions of source code". Neither license defines "source code".
[...]
> The Apache and MPL licenses *do* define "source code" (both say something
> like "the form of the work
I am working on some projects (a programming language, a game library) for
which I wish to use a "source attribution" license-- for example, the zlib
license, or the 2-clause BSD license if I could somehow delete the second
clause. I want people redistributing or reusing source code from my
6 matches
Mail list logo