On 20/08/10 01:22, Ben Bucksch wrote:
You can always offer a download on your own server and cite the URL in
the app. All you need to do is guarantee that it stays live (the old MPL
even specced how long).
And that was one of its most annoying provisions. When you are doing
daily builds on 3 platforms in 75 languages, do you have any idea how
much disk space it requires to keep source available for 6 months?
generally speaking even GPL only creates obligations to people whom
you've distributed executables to, rather than to the entire world.
Frankly, I don't see why, given that these receivers can then freely
redistribute, so there's little point.
The point is that you don't place unnecessary burdens on the
redistributor. Limiting it to the number of copies of the binary
distributed bases an upper bound on e.g. the amount of money you need to
spend on bandwidth and your FTP server. Mandating you make it available
to the whole world opens you up to unlimited costs. That's unreasonable,
IMO.
I don't know what would happen if a company sold commercial software
based on Gecko, and in the license for the software mandated that the
MPL source is not re-distributed. The customer could then get the
source, and the MPL would allow them to give it to me, but the other
contract would forbid it. Essentially close-sourcing the MPL changes. I
don't think we want that.
That's not possible, either under the MPL 1.1 or 2.0. Quoting from 2.0:
3.3.b): "You may distribute such Executable form under the terms of this
License or under different terms, provided that the license for the
Executable form does not attempt to limit or alter the recipient’s
rights in the Source Code form under this License."
Gerv
_______________________________________________
legal mailing list
[email protected]
https://lists.mozilla.org/listinfo/legal
