Davide Ricci

OpenHarmony's journey to Oniro - One year on

We introduced Openharmony at SFSCon 2020. One year has passed and with it much water under the project’s bridge. The project is now officially an Eclipse project, with its own brand. Members and industry partners are joining and the version 1.0 release is behind the corner. This talk provides an update of the vision, objectives, ecosystem, governance model, technology, standards, compliance processes, and all progress made in one intense year of work inside the Oniro project.

Compliance with Open Source and Free Software licenses remains a perennial topic of discussion among policy makers in our community. However, little attention is paid to the motivations why these licenses have specific requirements. Specifically, at least for copyleft licenses, the licenses seek to bestow specific rights and freedoms to the users who receive the software integrated into the devices they use. This panel, containing a group of industry experts, consultants, and license enforcement experts, discusses the challenges and importance of assuring downstream can actually utilize the compliance artifacts they receive with products as intended by the license.

Compliance with Open Source and Free Software licenses remains a perennial topic of discussion among policy makers in our community. However, little attention is paid to the motivations why these licenses have specific requirements. Specifically, at least for copyleft licenses, the licenses seek to bestow specific rights and freedoms to the users who receive the software integrated into the devices they use. This panel, containing a group of industry experts, consultants, and license enforcement experts, discusses the challenges and importance of assuring downstream can actually utilize the compliance artifacts they receive with products as intended by the license.

Other people: Bradley M. Kuhn John Sullivan Miriam Ballhausen Eilís Ní Fhlannagáin

Leveraging FOSS is an attractive proposition, yet managing FOSS and licensing obligations is often an after thought. Business risks and negative branding impacts are ignored, or willingly glimpsed upon, when an organization is in startup mode, however in larger companies and organizations, no lines of code should be pushed upstreamed or shipped with product unless, development shouldn’t even begin unless a comprhensive and state of the art FOSS license compliance policy and practice is in place. So do you go about building a new one, when none exists yet. Which standard do you look at? Which best practices do you follow? What processes do you build to make sure that the policy ultimately folllows the busines needs while mitigating risks as opposed to blocking business completely?