PyCom choose GPL3

Discussion and questions about boards that can run MicroPython but don't have a dedicated forum.
Target audience: Everyone interested in running MicroPython on other hardware.
User avatar
Posts: 342
Joined: Mon May 05, 2014 9:13 am
Location: Germany

Re: PyCom choose GPL3

Post by kfricke » Mon Nov 14, 2016 12:55 pm

Lysenko wrote:Besides, I rather suspect they may have no choice. They may be dependent on something (A)GPL3 licensed themselves.
Suspicious!!! :twisted:
Lets see what their repository will reveal! Their estimated time of arrival for the open-sources repository was last friday. Nothing 100% concrete showed yet. Only the weekly news from today are picking up exactly what Lysenko did assume.

Posts: 6
Joined: Sat Dec 10, 2016 3:46 pm

Re: PyCom choose GPL3

Post by smurfendrek123 » Sun Dec 11, 2016 1:14 am

Can they re-licence some files that don't use gplv3 code and then use the code in those files to help out the micropython project? Or does everything have to become gpl3 because some files in the project are gpl3?

User avatar
Posts: 1385
Joined: Thu May 28, 2015 5:54 pm

Re: PyCom choose GPL3

Post by deshipu » Mon Dec 12, 2016 12:49 pm

The license applies to "the work" -- in this case, the whole thing, and all of its parts.

User avatar
Posts: 154
Joined: Tue Aug 16, 2016 10:10 am
Location: СССР

Re: PyCom choose GPL3

Post by kamikaze » Mon Dec 12, 2016 4:18 pm

don't see any problem with PyCom license... also what do people mean when saying GPLv3 doesn't allow to use code for something more serious than hobby stuff? It looks like someone wants to have an open source code between "the chosen developers" and still be able to close end result from customers? Eh? :| GPLv3 forces people not to be hypocrites who play with words "open source" )

User avatar
Posts: 342
Joined: Tue Sep 30, 2014 7:20 am

Re: PyCom choose GPL3

Post by danicampora » Thu Apr 06, 2017 6:18 pm


We have revamped the GPL V3 licence to make it easier for you to build applications using Pycom boards WITHOUT having to share the code or indeed make the application source code available to others.

There is a comprehensive FAQ which can be found here: ... 20v2.2.pdf

In essence the rule is the following:

For customers building an application using a Pycom Board: You can do what you want with the application and decide to close source / Open source. You do not need to share the code.
For customers interested in ONLY using Pycom firmware on NON-Pycom boards then you can do so without requiring a license from Pycom however you will need to comply with the obligations of GPL V3 which means making the source code available etc. There are also some legal requirements around acknowledgements of other licensees whose firmware we have used such as Espressif, TI etc. Should a customer in this scenario choose to close source the application then that is possible however they must enter into a separate licence agreement with Pycom.
I hope that clarifies the licensing aspect however feel free to shoot over more questions etc.


User avatar
Posts: 54
Joined: Sun Sep 17, 2017 12:10 am

Re: PyCom choose GPL3

Post by tuupola » Sun Sep 17, 2017 12:35 am

Do I understand correctly if I want to do a MIT licensed open source project utilising Pycom board, only way to do it is to use avoid both the Pycom firmware and the Pycom MicroPython Libraries?

Post Reply