[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Licensing question about Pale Moon Browser binary distribution
From: |
Moonchild |
Subject: |
Re: Licensing question about Pale Moon Browser binary distribution |
Date: |
Sun, 4 Feb 2018 15:32:57 +0100 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:3.4) Gecko/20100101 Goanna/20171226 FossaMail/38.6.2a1 |
Hi!
You've read the exception point correctly:
Using New Moon (=unofficial) branding, you are allowed to do whatever
you wish with your distribution, including reconfiguration, different
home page, etc. Go right ahead!
If you make source code changes, you should also supply your modified
source code to stay within the requirements of the MPL source code license.
Moonchild.
On 04/02/2018 12:58, address@hidden wrote:
>>From re-reading item 12:
>
>> Unofficial branding ("New Moon") as supplied in the source code
>> may be used for unendorsed binaries at all times. Thusly
>> branded binaries with the New Moon logo and product name are
>> not subject to the endorsement and exception rules as set out
>> in previous points of this license and may be freely
>> distributed in altered or unaltered form, subject to the
>> Mozilla Public License as regards source code changes and
>> availability. This permission does, however, not include any
>> rights or license to the Pale Moon name and logo that may still
>> be present in the resulting unofficially branded binaries.
>
> in the above mentioned policy I understand that we will be
> allowed to distribute the resulting binaries. Is my understanding
> of your policy exception correct or did I miss anything?
>
> Regards,
> ng0
>
0x6DA5F2AC.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature