Monday was a big day for the Open IoT Challenge participants. It was the day they had to submit their final solution after 3 months of hard work! 10 teams came through with some great solutions. Here are their final reports:
All third party content must be taken through the Eclipse Foundation’s Intellectual Property (IP) Due Diligence Process before being used by an open source project hosted by the Eclipse Foundation. This includes all third party content that is incorporated into project code, included in builds, or otherwise required by the project code to provide functionality.
The Eclipse Foundation’s Intellectual Property (IP) Policy was recently updated and we’re in the process of updating our processes and support infrastructure to accommodate the changes. With the updated IP Policy, we introduced the notion of Type A (license certified) and Type B (license certified, provenance checked, and scanned) due diligence types for third-party dependencies that projects can opt to adopt.
Long-time Eclipse Committer, Ian Bull initiated a interesting short chat on Twitter yesterday about one big challenge when it comes to intellectual property (IP) management. Ian asked about the implications of somebody forking an open source project, changing the license in that fork, and then distributing the work under that new license.
With the changes in the Eclipse Intellectual Property (IP) Policy made in 2016, the Eclipse Foundation now offers two types of IP Due Diligence for the third-party software used by a project. Our Type A Due Diligence involves a license certification only and our Type B Due Diligence provides our traditional license certification, provenance check, and code scan for various sorts of anomalies.
2016 has been an incredible year for the IoT industry and the pace of innovation looks like it will accelerate in 2017. Last week I participated in a webinar, organized by Canonical, on the IoT trends to watch in 2017. It was a really good discussion, so feel free to listen to the recording. I think it would also be interesting to summarize some of the 2017 trends I see in the IoT industry and specifically in the Eclipse IoT community.