I believe this should not be a problem if one is writing python application scripts on RPi. GPL applies for the operating system but not on the apps written on the OS.Hove wrote: I beleive copyright / licensing (GPL) is the main hurdle if the RPi is to be integrated into another product for commercial purposes.
What's to stop you providing links to raspbian/debian, which will satisfy almost everyone? If anyone is still really insistent *you* send them the code, you could just post them a DVD, although I don't know if that's actually required.Heater wrote:helpme,
The problem with the GPL and Pi based products is this:
1) You ship a product to me that includes a Pi and Raspian and your application.
2) Most of that Raspian is GPLed.
3) Therefore under the terms of the GPL you have to be able to provide me, if I ask, with all the source code needed to build that Raspian.
You see, you will have shipped binaries of GPLed code to me and you need to abide by the license they are under.
Are you prepared to do that?
This nothing to do with your application which you can licence how you like.
So for the least faff you could just stick a CD/DVD in with the box. But I don't see why you couldn't provide links to debian to satisfy people who actually want the code and provide a written offer to post a DVD to satisfy the letter of the GPL.3b of the GPLv3 wrote:for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code
I think you would need your own FCC/CE since the other components you use may radiate. Although it may depend on quantity.williegeorge wrote:I would like to post what I think is the same question very specifically in hopes of a similarly specific response. If no one here is sure of the correct answer, hopefully someone will at least be able to point me in the right direction.
I am working on developing a commercial product that will consist of a RPi in a plastic box. All of the value-add on my part will be in the software. I check with the developers of the software I'm using about licensing issues once I figure this part out. Would my device need separate FCC/CE since I am not modifying the physical RPi at all?
In a related note, would I have to admit to my customers that it is a RPi inside the mystery box?
The government agencies don't perform certification testing, independent labs do which are certified by the agencies, ironically often with the assistance of yet-more third-party contractors, generally known as independent verification and validation (IV&V) entities. Yes, there are auditors who check the IV&V folks as well as the others ... the government contracting gravy train never endsLob0426 wrote:Ok time to be a smart Aleck;
How else would CE and the FCC make money?
UL is probably a better tester of any product than either of those are!
AIUI true development boards are not considered finished products and therefore not subject to FCC and CE (IANAL this is not legal advice)helpme wrote:I am very pleased with Raspberry Pi. I am even more pleasantly surprised that RPi has passed FCC and CE certifications. Is it necessary to have a development board to pass FCC/CE?