From: ng0@n0.is
To: Moonchild <moonchild@palemoon.org>
Cc: guix-devel@gnu.org
Subject: Re: Licensing question about Pale Moon Browser binary distribution
Date: Sun, 04 Feb 2018 14:40:43 +0000 [thread overview]
Message-ID: <877ersyg0k.fsf@abyayala.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <5A771999.1050509@palemoon.org> (moonchild@palemoon.org's message of "Sun, 4 Feb 2018 15:32:57 +0100")
Hi,
On Sun, 04 Feb 2018, Moonchild <moonchild@palemoon.org> wrote:
> 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.
Alright then. I should've asked this question earlier. Better
late than never.
Thanks for your reply!
> On 04/02/2018 12:58, ng0@n0.is 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
>>
>
>
--
ng0 :: https://ea.n0.is
A88C8ADD129828D7EAC02E52E22F9BBFEE348588 :: https://ea.n0.is/keys/
prev parent reply other threads:[~2018-02-04 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-04 11:58 Licensing question about Pale Moon Browser binary distribution ng0
2018-02-04 14:32 ` Moonchild
2018-02-04 14:40 ` ng0 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877ersyg0k.fsf@abyayala.i-did-not-set--mail-host-address--so-tickle-me \
--to=ng0@n0.is \
--cc=guix-devel@gnu.org \
--cc=moonchild@palemoon.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.