GPLv3 explained

GPLv3.md

GPL3 LICENSE SYNOPSIS

TL;DR* Here's what the license entails:

1. Anyone can copy, modify and distribute this software.
2. You have to include the license and copyright notice with each and every distribution.
3. You can use this software privately.
4. You can use this software for commercial purposes.
5. If you dare build your business solely from this code, you risk open-sourcing the whole code base.
6. If you modify it, you have to indicate changes made to the code.
7. Any modifications of this code base MUST be distributed with the same license, GPLv3.
8. This software is provided without warranty.
9. The software author or license can not be held liable for any damages inflicted by the software.

More information on about the LICENSE can be found here

One question, does it matter if I use a library that is not licensed with the GPL?

You must obey any licensing conditions of any library you use. If the library has a license that conflicts with the GPL then you can’t add it to the gpl source unless you don’t distribute the binary.  I do not know what the library is.Sent from my iPhoneOn Nov 26, 2024, at 6:14 PM, BluePy ***@***.***> wrote:Re: ***@***.*** commented on this gist.One question, does it matter if I use a library that is not licensed with the GPL?—Reply to this email directly, view it on GitHub or unsubscribe.You are receiving this email because you commented on the thread.Triage notifications on the go with GitHub Mobile for iOS or Android.                                                           

zaphod77
I'm asking all these questions because I DO HOPE for my design to be the basis of a start-up company and to manufacture and sell the resultant 3D printers. It's really quite a unique design. It should print much faster and create much stronger prints (fingers crossed).
But it does seem like my code that runs on the separate processor can be kept as the company's trade secret, with no requirement that its source code has to be made available as Open Source.
So, that's a relief. :)

Thank you.

Note that you won't be able to stop people from reverse engineering the coprocessor based on what your open source part does to talk to it, but they would have to clean room the replacement, and if they didn't do that, major bucks for you.

…

On Tue, Nov 26, 2024 at 9:13 PM RogerInHawaii ***@***.***> wrote: ***@***.**** commented on this gist. ------------------------------ zaphod77 I'm asking all these questions because I DO HOPE for my design to be the basis of a start-up company and to manufacture and sell the resultant 3D printers. It's really quite a unique design. It should print much faster and create much stronger prints (fingers crossed). But it does seem like my code that runs on the separate processor can be kept as the company's trade secret, with no requirement that its source code has to be made available as Open Source. So, that's a relief. :) Thank you. — Reply to this email directly, view it on GitHub <https://gist.github.com/kn9ts/cbe95340d29fc1aaeaa5dd5c059d2e60#gistcomment-5302917> or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQL7ZOO7L33CEOUOO7I3JL2CVIH7BFKMF2HI4TJMJ2XIZLTSKBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDHNFZXJJDOMFWWLK3UNBZGKYLEL52HS4DFVRZXKYTKMVRXIX3UPFYGLK2HNFZXIQ3PNVWWK3TUUZ2G64DJMNZZDAVEOR4XAZNEM5UXG5FFOZQWY5LFVAZTKNZTGYYTONFHORZGSZ3HMVZKMY3SMVQXIZI> . You are receiving this email because you commented on the thread. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> .

The libraries in question are in my Cobalt repo under bot_code.py, it needs A LOT of work, it's concept is being a programming assistant that you can configure to only make answers to certain languages, this would be beneficial if for example, you ran the bot offline, so you don't download useless data you won't need.

@RogerInHawaii

https://www.gnu.org/licenses/gpl-faq.en.html#MereAggregation (my emphasis):

... pipes, sockets and command-line arguments are communication mechanisms normally used between two separate programs. So when they are used for communication, the modules normally are separate programs. But if the semantics of the communication are intimate enough, exchanging complex internal data structures, that too could be a basis to consider the two parts as combined into a larger program.

So it seems you actually need to provide the source code for your firmware to the users under the GPL license.

@MasterKia , I don't know how one defines the phrase "intimate enough". In my case the only communication between the Firmware and the program running on the additional microprocessor is commands from the Firmware to the additional microprocessor telling it to perform some operation (e.g. turning a light on having it drive a stepper motor), and for the additional microprocessor to respond with a "DONE" or "FAILED" message back to the Firmware. No "complex data structures" are communicated.

I agree here. I don't believe that statement would apply.

Functionality is added to the open source firmware that sends instructions to the closed source microprocessor. Those instructions are not obfuscated, and no other communication is done. It's essentially one open source program giving a closed source ones simple command line switches, and reading the return code.

This seems like a legitimate aggregate, based on the description.

Now if there were secret undocumented actions caused by activating commands in a specific sequence, then things would be a bit more questionable. If there is data encoded into the sequence of commands that the coprocessor detects (and affects it's ability to succeed or fail), then that would be abuse, unless the required sequences themselves were documented in the open source side. If you have undocumented magic sequences, then you are concealing some of the source.

From the way it's described, there is no issue.