A product to be sold commercially is built around the Raspberry Pi. There is a proprietary hardware running its own software connected to the Pi, and a GUI application runs on the Pi itself.
What licensing conditions do I have to take care about?
This blog implies that I should print "Powered by Raspberry Pi" on the packaging, but it's not clear whether it's a strict requirement or only a recommendation.
If, like Brian, you’re making a product which requires a Raspberry Pi to run, we don’t ask you to buy special permission or licenses from us to use it. All we ask is that you include the words “Powered by Raspberry Pi” somewhere on your packaging.
However, it's on a blog within the website, and is not as strictly formulated as the various lawyer-style trademarks rules.
2. Operating system
The product is planned to be shipped as described below:
- I download and write the Raspbian image to an SD card.
- I install my software on it.
- I uninstall everything which I don't need for my product, to make more space on the SD card and to make loading times shorter
- I ship clones of that SD card with my product.
As Raspbian is licensed with GPL, I will have to redistribute the source. Does this mean that I have to download the corresponding source from here, and either put it on the SD card, or store it myself in case someone requests it from me and the Raspbian repository is somehow off-line? Is it a problem that as I uninstalled several things from it, the source does not correspond to the binary I shipped?
If, instead of step 3, I modify the source or the makefiles to only build the necessary components, I will have to supply the source as well, especially if I modified it, and the makefiles as well, with all the help (what compiler I used with what settings) someone needs to do it by themselves?
3. Additional packages
The Raspbian images contain several non-free packages, like Java SE, Mathematica, and Wolfram. Do I have to remove all traces of them from my deployment, even if my software doesn't use any of them at all?
This question is not about
- how available is the Raspberry Pi and what technical related disadvantages does it have in a commercial product.
- how to protect the software from being copied or reverse-engineered.
These questions are already answered elsewhere, some of them being severely out of date.