Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Michael Miller
@Makuna
Micro switches are more reliable. Search, you will find this to be common issue. Some people use steppers instead of servos.
geman220
@geman220
okay ty
Ivan Grokhotkov
@igrr
@/all I'm planning to ask each person who contributed to this esp8266 core for a permission to relicense the code under Apache 2.0 license.
This obviously excludes any code inherited from arduino.cc, and any libraries which were not originally written in the scope of this project.
The reason behind this request is to reuse esp8266 code in the upcoming ESP32 core. I would like to make it easier for people to use this new core in commercial projects.
If anyone has some thoughts/questions/objections, please follow up :)
andig
@andig
@igrr for the purpose of being able to distribute derived work without making he sources available? I wouldn't object to that as it doesn't hinder the core development in any way and may attract new talent.
Ivan Grokhotkov
@igrr
Yes, for that purpose. From the emails i get, i see there is interest for using the core in commercial projects. But LGPL terms mean that you have to publish your object files at the very least. Since we have flash memory encryption in the ESP32 for the purpose of readback protection, it would be nice to give people an option not to publish their code, even in the form of object files.
Michael Miller
@Makuna
While my contribution is not as great as some here, I have issues with people making a profit off work I have given to the community without themselves giving back to community. But I know of no way to police such contributions without licensing contracts which currently I don't believe is possible. As long as the accreditation is followed so at least it points people back to the community then as far as this project, I am ok with it.
Ivan Grokhotkov
@igrr
@Makuna noted! I will think more about this.
Michael Miller
@Makuna
Also, I don't have ANY concerns over someone selling a 100 units of something; They are more doing it for passion at those numbers and these kinds of people tend to contribute back.
Ivan Grokhotkov
@igrr
The best (IMO) thing which i came up with goes like this.
Companies which want this core in their project and want to get some support while doing that, pay Espressif for the support. Espressif then gives back to the community by paying someone to work on the core.
So while they don't pay the people who contributed to the project directly, they do help the project as whole
Michael Miller
@Makuna
Can you add something about them paying someone "competent" to work on the core ;-)
(that was a joke if it wasn't obvious)
seclorum
@seclorum
greetings platformio'ers .. is there any word on when pio will catch up with the Espressif SDK .. which seems to be quite a few versions ahead of things ..
Testato
@Testato
Whit the new licence the arduino API remain in the core ?
So we will have analogRead(); or Serial.print ?
Ivan Grokhotkov
@igrr
@Makuna if you ever decide to switch jobs, then this can be arranged ;)
@Testato LGPL (and GPL as well) permit the use of header files which contain function prototypes, enumerations, and structure layouts, without having to license all the work under LGPL. So the plan is to take header files of Arduino core classes, and do a TDD-based clean-room implementation of them, under new license.
this isn't an awful lot of work, there are only a few classes (String, Stream, Print, IPAddress)
Me No Dev
@me-no-dev
@igrr I would like to switch jobs :D
and what about all of the code I have written so far for the esp32?
Ivan Grokhotkov
@igrr
if you can relicense the peripheral drivers you've written for the 32, that would be cool.
Me No Dev
@me-no-dev
yes I can :) i believe we have talked about it before
don't i need to relicense the ones in this core too?
Ivan Grokhotkov
@igrr
That's what i meant about peripheral drivers :)
i.e. "hal"
other stuff like bootloader, main, and some other things have to be done slightly in a different way...
Me No Dev
@me-no-dev
do you have any info if anything that we have so far in the esp31b hat will chhange in the final?
Ivan Grokhotkov
@igrr
I have. Yeah, a bunch of things will change. But I can't tell which ones exactly :)
Me No Dev
@me-no-dev
i have not done any bootloader stuff on the esp32 ;)
it will be sad to see huge changes in the hardware rendering the code obsolete
Ivan Grokhotkov
@igrr
Not huge, no. At least not in the peripheral domain.
Me No Dev
@me-no-dev
that is good to hear :)
gitter really needs to add a smiley face ;) it looks like I'm laughing all of the time
Baruch Even
@baruch
@igrr I'll cook up a patch and send a pull request
Baruch Even
@baruch
How do you folks test a repository change? I don't want to replace the environment I use normally in platformio but I want to compile some code with the delay modification to make sure everything else compiles and works as usual.
Me No Dev
@me-no-dev
when you make a PR the system will run a check :)
if it fails, a slightly embarassing message will pop up on the right of the chat to let you know that you failed
message is visible in the PR as well (and you can see what failed where)
Baruch Even
@baruch
:-P
That sounds dirty...
Me No Dev
@me-no-dev
it's pretty good actually ;) because it compiles all examples in the core against your patch
Ivan Grokhotkov
@igrr
You can run the tests locally as well. See .travis.yml for the commands to run tests
Also there is a pull request for the setup to run tests on ESP, which i haven't merged yet.
Baruch Even
@baruch
@igrr I have the patch ready. I can also put forth the cooperative threading code I made, still without making use of the delay override though.
If someone wants to take a look at this it can be seen at https://github.com/baruch/esp8266_smart_home/tree/master/arduino/lib/CooperativeThread
Ivan Grokhotkov
@igrr
@baruch could you take a stab at pulling this into the core, and replacing g_cont with an instance of that thread?
Baruch Even
@baruch
and for comparison you can look at the same directory for the node_soilsensor code which is still a state machine
Not sure what you mean, you want the threading to jump back right to the new coop thread?