So assuming all the code is dual licensed GPL/BSD and not a mixture of licenses then we’re fine to use it. We would need to note its license in our LICENSE file.
Great! So I am proposing to assist the parties that are interested in the development by creating a SocketCAN branch and contributing the basic socket layer support. I would ask them to contribute the ported SocketCAN implementation in a form compatible with the NuttX network architecture, compatible with the NuttX coding standard, and fully verified. There are several parties involved here and I don't know who, if anyone, has committed to the implementation: NXP, PX4, UAVCAN, VW, all or some of the above. VW is very supportive of this effort they are the owners of the SocketCAN code so even in the worst case licensing scenario, I think we should be able to work things out.
We can be careful with the licensing throughout this and we can ask for a thorough license review before any move to master is considered.
I don't plan to do anything, however, until I have a firm commitment for the development.
Greg
