From: Christopher Lemmer Webber <cwebber@dustycloud.org>
To: Carlo Zancanaro <carlo@zancanaro.id.au>
Cc: guix-devel@gnu.org
Subject: Re: Vanilla Firefox recipe?
Date: Wed, 27 May 2020 07:53:22 -0400 [thread overview]
Message-ID: <87a71twq4t.fsf@dustycloud.org> (raw)
In-Reply-To: <87a71u5751.fsf@zancanaro.id.au>
Carlo Zancanaro writes:
> Hey Chris,
>
> On Wed, May 27 2020, Christopher Lemmer Webber wrote:
>> However, I wonder if, with a matter of just two patches, this could be
>> resolved:
>>
>> - Patch out the automatic download of Cisco's h.264 plugin.
>> - Add a warning banner *above* the extensions page, or simply switch it
>> to the same one that Icecat already uses.
>>
>> Is that all that's necessary, then, to get "vanilla Firefox" in Guix?
>> It strikes me that with those two changes, the criteria would be met.
>
> We would need to watch out for Mozilla's requirements to use the
> "Firefox" trademark[1]. Of particular note is the section titled
> "Modified Versions Require Prior Written Permission":
>
> The open source nature of Firefox and other Mozilla software allows
> you to freely download and modify the source code. However, if you
> make any changes to Firefox or other Mozilla software, you may not
> redistribute that product using any Mozilla trademark without
> Mozilla’s prior written consent and, typically, a distribution
> agreement with Mozilla. For example, you may not distribute a
> modified form of Firefox and continue to call it Firefox.
>
> Changes requiring Mozilla’s prior written permission include (but are not limited to):
> - Changing the default home page or adding bookmarks,
> - Adding, modifying, or deleting source files,
> - Adding, modifying, or deleting content from installer files,
> - File location changes,
> - Adding extensions, add-ons or plugins, or
> - Installing themes other than those available in the most recent
> stable version of Firefox available at Mozilla.org.
>
> If you wish to distribute a modified version of Firefox or other
> Mozilla software with Mozilla trademarks please contact us with your
> request at trademark-permissions@mozilla.com.
>
> Carlo
>
> [1]: https://www.mozilla.org/en-US/foundation/trademarks/distribution-policy/
I agree this is a concern and is in the list of things to address.
I forget, but I remember reading somewhere that Firefox's codebase does
ship in such a way where rebranding it isn't as hard as it used to be,
or that the development version already did have some of this branding
stripped out.
Am I misremembering?
- Chris
next prev parent reply other threads:[~2020-05-27 11:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 19:10 Vanilla Firefox recipe? Christopher Lemmer Webber
2020-05-11 20:31 ` Guillaume Le Vaillant
2020-05-12 19:23 ` Efraim Flashner
2020-05-24 13:54 ` Adonay Felipe Nogueira via
2020-05-25 20:17 ` Christopher Lemmer Webber
2020-05-26 17:27 ` Christopher Lemmer Webber
2020-05-26 17:34 ` Christopher Lemmer Webber
2020-05-26 17:45 ` Leo Famulari
2020-05-27 4:33 ` Carlo Zancanaro
2020-05-27 11:53 ` Christopher Lemmer Webber [this message]
2020-05-26 20:27 ` Ludovic Courtès
2020-05-27 5:16 ` Why Mozilla Firefox is nonfree? (was: Vanilla Firefox recipe?) Dmitry Alexandrov
2020-05-27 17:31 ` Adonay Felipe Nogueira via
2020-05-28 5:11 ` X-Content-Filtered-By: Mailman/MimeDel 2.1.23 Dmitry Alexandrov
2020-05-27 14:26 ` Vanilla Firefox recipe? Tobias Geerinckx-Rice
2020-05-25 20:44 ` Tobias Geerinckx-Rice
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=87a71twq4t.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=carlo@zancanaro.id.au \
--cc=guix-devel@gnu.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.