MicroPython Forum (Archive)

on4aa wrote: ↑

Tue Jan 30, 2018 7:54 pm

I now changed the subject to attend to your concerns, whilst remaining as correctly informative as is humanly possible.

@pfalcon It indeed looks like I do not share your godlike powers to change thread titles!

@pfalcon I understand your concern. I tend to chose my subject wording very carefully. However, this thread indeed took another turn along the way, which may give the wrong impressions about uasyncio on its own. I now changed the subject to attend to your concerns, whilst remaining as correctly info...

Uh, that does not sound good. I will install their firmware to peek around what is happening. It is not that dramatic and probably not done with bad intention. There are without doubt also cultural differences in sensitivity for such matters. Removing import m5cloud from boot.py should stop this be...

tuupola wrote: ↑

Sun Jan 28, 2018 6:09 am

Answering to myself here, yes it seems it does. Thanks to viral nature of GPL my understanding is this makes the whole project effectively GPL licensed.

By consequence, M5Stack is affected as well.

tuupola wrote: ↑

Mon Jan 29, 2018 4:17 am

Or is the problem that the M5Stack version of MicroPython firmware uploads the code stored in flash to the cloud without user consent even if you are not using the cloud editor to edit the code?

Exactly.

@cefn Thank you very much for amending my code to the point where it behaves itself on CPU. Bear with me for a moment, I would like to recapitulate one step earlier to make sure all is well understood. Correct me if I am wrong. loop.create_task(sample(data_ready)) #loop.create_task(update_lcd(data_r...

@loboris Thank you for your clarification. This inspires a lot of confidence. As you suggest, it would indeed be wise to list the items that are not licensed under the MIT terms in a file in the root, together with their license type. This would allow users who intend on using your software in a com...

Dear loboris, First off, thank you for all your efforts. However, to leave out any legal conundrums; Would you mind putting your software licensing terms in the root folder of your GitHub repository? As it currently stands, it looks like the MIT license only applies to certain parts of your software...

This discussion is related to the following loboris MicroPython for ESP32 issue.

The confidentiality of your application code might actually also be at risk by virtue of the firmware and certain libraries. I am absolutely not saying that this is happening, but just to put an example: closed source firmware could be leaking your application code to an off-site server as soon as W...