Hey, Yeah it's confusing... Pom says mit, Readme says Apache 2 and some files have netty license header :)
Let's see what he answers. Julian Von meinem Mobiltelefon gesendet -------- Ursprüngliche Nachricht -------- Betreff: Re: Usage of Netty - JSerialcom-Bridge Von: Christofer Dutz An: dev@plc4x.apache.org Cc: Hi Julian, It seems the files am have apache headers, but the pom says mit license. Perhaps Justin can help us with what's allowed and what's not. It would be cool to have it in a location we can update and release it on our own. Cause even if the maintainer is accepting PRs, we don't know how often he releases. We could put it alongside the raw socket stuff. It's only one contributor, so he could donate everything without too much effort. Chris Holen Sie sich Outlook für Android<https://aka.ms/ghei36> ________________________________ From: Julian Feinauer <j.feina...@pragmaticminds.de> Sent: Wednesday, August 7, 2019 3:13:33 PM To: dev@plc4x.apache.org <dev@plc4x.apache.org> Subject: Usage of Netty - JSerialcom-Bridge Hi all, as we use in our DF1 Code (and also fort he Modbus Code, I think) the library: https://github.com/Ziver/Netty-Transport-jSerialComm which is under netty license. But it quite outdated and only “maintained” by one guy. I contacted him asking if he accepts PRs and also suggested, that we probably move / replicate the code in our code in a tools module (or integrate it in the Serial-Netty Stuff somewhere). What do you think? The best way, if he agrees, would be to have him sign an ICLA and we could simply take the code as is and refactor it perhaps a bit and adapt it to newer versions. Otherwise, I think it will be hard to use this lib and we would need to come up with an alternative. Julian
