How should you choose a license for your project? What's the difference between different FOSS licenses? Why do these dull legal documents make some people so angry? In this talk, an experienced FOSS lawyer will talk about the basics of FOSS licensing. We'll cover license types, copyleft's complexities, CLAs and DCOs, relicensing, and more.
This talk will explore the process of building and deploying the first Linux Foundation ISO standard in fourteen years in collaboration with the Joint Development Foundation. It will explain why the evolution from de facto industry standard to formal standardization was important for open source compliance in the context of areas like sale, procurement and M&A. An equal amount of time will be spent providing a guide to the journey itself, as the lessons learned are applicable to all projects building out specifications or code that seek worldwide, lasting adoption across multiple industries. The standardization process will be framed in the context of timely engagement, with SPDX queued to be the second Joint Development Foundation PAS submission behind OpenChain, and everyone involved ready to support more projects undertaking a similar journey in the months and years ahead. In practical terms, this talk will allow the audience to come away with a clear understanding of how we will take open source and standards to the next level.
While the situation around licensing in software is always worth a debate and not quite as settled as it could be the situation for hardware is much worse. There are a lot of misconceptions out there about how to license hardware designs. This talk will show you some of the common misunderstandings, highlight the open questions, propose some collective action to fix the situation and yes - of course - also explain how things are done the right way.
The talk will be a summary and extended version of the public FAQ "Why are Creative Commons Non Commercial licenses not Open Source and a big problem in hardware and product design".
University based hackers are some of the most prolific and participative open source contributors. Many University and other public R+D centres have little idea how much FOSS they are producing, nor how much they are using. This has two implications: inbound compliance with third party open source, particularly on subsequent tech transfer (distribution); and outbound license choice and the impacts in terms of licensing, confidentiality, community building, and university processes. R+D proyects have certain characteristics (how they are developed, university rights, ownership, etc,) that make governance and compliance "interesting" to say the least. I, open source lawyer for nigh on 20 years, will tell you some horror (and success) stories.
Given the nature of collaborative development of Open Source Software (OSS) in projects, projects must ensure that technical development occurs along with legal cooperation between developers and users. Participation in technology development through OSS requires that we look to community solutions for patent risk mitigation.
Participants will be introduced to the Open Invention Network and develop an understanding of the organization’s mission, free membership, community initiatives, and support of OSS innovation through projects.
Are you trying to build the brand of your community-led project? Is your community struggling to keep vendor marketing teams out of your project's governance? Do you need a lawyer before you can "trademark" something, or can you do it yourself? (Tip: you can do it yourself!)
This AMA is here to help answer basic trademark law questions in practical, everyday terms for FOSS projects and the companies that contribute to them. Legal advice can only come from your own lawyer - but most community questions have practical answers that can get you started without a lawyer. Trademarks are all about the public's association of a brand with a product - and most of that happens in the real world, not a lawyer's office.
Bring your simple community questions about how trademarks work, and we'll try to get you some practical advice on what to do. Similarly, corporate questions are welcome - for how you can effectively partner with a Foundation or community-led project without stepping on toes.
Trademark education for engineers and community members.