Question Regarding Permission to Distribute a Repackaged Firefox Build

I'd redirect you directly to https://wiki.mozilla.org/Matrix — you'll find folks with the postmarketOS experience there, and also staff aware of the history of packaging, if not directly involved.

Are there any docs behind the process? I was only able to find https://gitlab.com/debclick/uFirefox which, working with existing packages in CI, might be "fine" — but wasn't able to verify the mentioned adjustment script though.

What's the path from a CI artifact to the store listing, verification and artifact hosting? Is there any provenance kept as it moves between download surfaces? Who would be the "publisher" in the store? What changes does that distribution warrant, how they're applied, who will be responsible for the source code of that and how is access to such "supply chain" handled?

You probably want to file a bug in the Packaging bugzilla component https://bugzilla.mozilla.org/buglist.cgi?product=Firefox%20Build%20System&component=Third%20Party%20Packaging&resolution=--- or similar to have a canonical tracking ticket to refer to as well.

I'd redirect you directly to https://wiki.mozilla.org/Matrix — you'll find folks with the postmarketOS experience there, and also staff aware of the history of packaging, if not directly involved. Are there any docs behind the process? I was only able to find https://gitlab.com/debclick/uFirefox which, working with existing packages in CI, might be "fine" — but wasn't able to verify the mentioned adjustment script though. What's the path from a CI artifact to the store listing, verification and artifact hosting? Is there any provenance kept as it moves between download surfaces? Who would be the "publisher" in the store? What changes does that distribution warrant, how they're applied, who will be responsible for the source code of that and how is access to such "supply chain" handled? You probably want to file a bug in the Packaging bugzilla component https://bugzilla.mozilla.org/buglist.cgi?product=Firefox%20Build%20System&component=Third%20Party%20Packaging&resolution=--- or similar to have a canonical tracking ticket to refer to as well.

Development

git clone git submodule update --init --recursive virtualenv venv --system-site-packages source venv/bin/activate pip install clickable-ut --upgrade clickable build

The clickable.yaml specifies to use crackle as a custom build command. For debugging the crackle command it can be helpful to enter the clickable docker container. E.g.:

clickable run ./crackle/crackle bump-version firefox

I am not a developer, nor do i know how this works but the person working on ( https://gitlab.com/debclick/uFirefox ) Can explain all in detail

I believe all it does is take the latest upstream firefox and bumps it into a "clickable" so that we can install it on our devices. i joined the mozilla space on Element, not sure where to go since there is no "ubuntu touch" on mozilla ;-)

Well then please have someone representing the UBports with the above knowledge get in touch — answers to the questions mostly depend on if that's derivative work and how it's being distributed. (Normally when you build from a fork, you can't use trademarked branding for distribution; here it's taking already built official distribution and does some tweaks in the filesystem IIUC — might be worth partnering for maintaining the official package for UBports.)

You still want to go through legal, see contacts in https://www.mozilla.org/en-US/foundation/licensing/ — but figured going the packaging route would be more productive for now;) On the Matrix chat ask in the #general room for redirection. Danny, Pascal or Sylvestre will be able to tell you more and point you towards the right direction.

This is the component for filing a bug in the official licensing docs:

https://www.mozilla.org/en-US/MPL/license-policy/#Filing_Bugs

This is the closest to this question:

• https://www.mozilla.org/en-US/foundation/trademarks/distribution-policy/

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,

I forwarded it towards representing people for "ubuntu touch" and "ufirefox" itself.

I see this as an opportunity that goes beyond Ubuntu Touch itself. As the Linux mobile ecosystem continues to evolve, Ubuntu Touch has the potential to take a leading role alongside postmarketOS in building a more mature and user-friendly alternative mobile platform. Ensuring that Firefox can be distributed through the OpenStore would be a meaningful contribution toward that goal, helping to provide users with familiar, trusted applications while strengthening the long-term viability of Linux on mobile devices.