Legal and Policy Issues
DEBATE: Does Careful Inventory of Licensing Bill of Materials Have Real Impact on FOSS License Compliance?
February 1, 2020
12:00 PM – 12:50 PM Add to calendar
12:00 PM – 12:50 PM Add to calendar
UA2.220 (Guillissen)
Projects today often have thousands of FOSS dependencies. Since risk
flows downstream in the supply chain; projects inherit and pass on the
risks of all their dependencies. In response, licensing bill of
materials tools often seek to push well-formed licensing inventory
data upstream in an effort to ease downstream compliance
challenges. At the same time, there has been a stark increase in
license violations, especially, though not exclusively, on copyleft
licenses. Is this approach to improving compliance working?
Affirmative position: Compliance at scale through tool-driven assembly of bills of materials is essential for FOSS
First Affirmative Constructive (1AC) = 7 minutes
a. Cross-examination of First Affirmative by Second Negative = 3 minutes
First Negative Constructive (1NC) = 7 minutes
a. Cross-examination of First Negative by First Affirmative = 3 minutes
Second Affirmative Constructive (2AC) = 7 minutes
a. Cross-examination of Second Affirmative by First Negative = 3 minutes
Second Negative Constructive (2NC) = 7 minutes
a. Cross-examination of Second Negative by Second Affirmative = 3 minutes
First Negative Rebuttal (1NR) = 3 minutes
First Affirmative Rebuttal (1AR) = 3 minutes
Second Negative Rebuttal (2NR) = 3 minutes
Second Affirmative Rebuttal (2AR) = 3 minutes
Additional information
| Type | devroom |
|---|
More sessions
| 2/1/20 |
Welcome to the Legal & Policy Issues DevRoom including and overview of how the new Collaboration and Debate sessions will work.
|
| 2/1/20 |
As decentralized social media gathers more users, the privacy by design and default principles from the GDPR are in accordance to the design model it proposes. This talk is going to tackle the main advantages and challenges this approach brings, from the perspective of the data protection legislation and privacy architectural strategies.
|
| 2/1/20 |
In a perfect world, lawyers (and the entire legal system) should not be necessary. And in a perfect FOSS world, everyone respects each and every provision of every license. The reality is, however, very different, and enforcement may be a necessary evil. This need does not mean we have to open the gates to be flooded by "copyleft trolls", but to establish a sound enforcement policy, in order to unleash the lawyers only for the most blatant and repeated violations
|
| 2/1/20 |
How can we give users standing in free/open software/hardware? How can we motivate end users to care about FOSS if they can't express their preference? What tools do we have beyond the "court of public opinion"? Can we invent a NEW legal hack?
|
| 2/1/20 |
Photography policies have begun to appear at free-software events in recent years. These policies typically seek to address personal privacy concerns for event attendees, but they sometimes conflict with the event's desire to record talks, Q&A periods, and social gatherings in public spaces. If not drafted with care, photo policies also run the risk of creating ambiguities for journalists, other attendees making personal photo or video recordings, and members of event-hosting organizations or ...
|
| 2/1/20 |
Are the FSF's 4 Freedoms and the OSI's Open Source Definition out of date in 2020 and should be replaced.
|
| 2/1/20 |
We have seen several licenses proposed as "open source" that carry some obligation or restriction related to ethics or other social goals. Is this a good direction for FOSS license drafting?
|
