Re: meaning of Php.XPath license?

[Francis F. <fra...@vi...>]

Well I don't know if this is because of Mozilla 1.1 or because of the 
triple license, but in my book they said that modification can be kept 
private, but I find this on Mozilla.org 
(http://mozilla.org/MPL/MPL-1.0-annotated-fs.html):

What that said is that you have to make the source code public to whom 
you give/sale executable too, but you don't need to give it back to 
Mozilla.org


It's in the MOzilla license

3.2. Availability of Source Code.
Any Modification which You create or to which You contribute must be 
made available in Source Code form under the terms of this License 
either on the same media as an Executable version or via an accepted 
Electronic Distribution Mechanism to anyone to whom you made an 
Executable version available; and if made available via Electronic 
Distribution Mechanism, must remain available for at least twelve (12) 
months after the date it initially became available, or at least six (6) 
months after a subsequent version of that particular Modification has 
been made available to such recipients. You are responsible for ensuring 
that the Source Code version remains available even if the Electronic 
Distribution Mechanism is maintained by a third party.

if you want an explnation here it is:
at 
http://mozilla.org/MPL/annotations-1.0.html#Public_Availability_of_Source_Code

``Availability of Source Code''
This provision is intended to ensure availability of code, while 
minimizing the burden on each Contributor. It is based on the principle 
of ``code follows the executable'' that is found in the GPL. It does not 
require that you return Modifications to mozilla.org or any other named 
organization. However, you may do so if you choose, and we hope that you 
wish to participate in the development community that mozilla.org is 
chartered to foster.



Nigel Swinson wrote:
>>As for relicensing, well I think that this is a long debate, the only
>>license that I know that modification has to come back to the developper
>>is GPL/LGPL.
> 
> 
> http://mozilla.org/MPL/relicensing-faq.html#why-grant-permission
> The new Mozilla license scheme (i.e., the MPL/GPL/LGPL triple license) is
> arguably consistent with the prior schemes: It too requires that people make
> source code available for modifications to Mozilla code (this is required
> whether licensees use the code under MPL, GPL, or LGPL terms), and it too
> allows Mozilla code to be used in proprietary programs (this is allowed by
> the MPL, and also allowed by the LGPL in certain cases).
> 
> Nigel
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Phpxpath-users mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpxpath-users
> 


-- 
Francis Fillion, BAA SI
Broadcasting live from his linux box.
And the maintainer of http://www.windplanet.com