Session
Schedule FOSDEM 2020
Legal and Policy Issues

Oracle v. Google: What are the implications for FOSS?

UA2.220 (Guillissen)
Van Lindberg
All the merits briefs for Oracle v. Google will be filed a couple weeks before FOSDEM 2020. This will be a rundown of the positions argued by various groups - how are the parties positioning the questions presented? What are the various amici arguing? Are there any positions that will be particularly impactful for FOSS groups and users?

On Friday, Nov. 15, the U.S. Supreme Court agreed to hear Oracle v. Google. It is hard to overstate how impactful this decision will be on FOSS. For the first time in a generation, the Supreme Court will be evaluating how copyright and software interact - and they will be discussing it in the context of GPL-licensed Java.

Right before FOSDEM, all the briefs by all parties will be due. As we sit in Brussels, the court clerks will be reading the various briefs and creating a "bench memo" for each justice, summarizing the arguments being advanced by both Oracle and Google, as well as the points raised by different amici.

This presentation will be a verbal "bench memo" for those in the FOSS community. Rather than advance a particular view, we will try to understand the scope of issues being argued, and how they may affect Free and Open Source Software in the United States - and worldwide.

Additional information

Type devroom

More sessions

2/1/20
Legal and Policy Issues
Tom Marble
UA2.220 (Guillissen)
Welcome to the Legal & Policy Issues DevRoom including and overview of how the new Collaboration and Debate sessions will work.
2/1/20
Legal and Policy Issues
Cristina DeLisle
UA2.220 (Guillissen)
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
Legal and Policy Issues
UA2.220 (Guillissen)
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
Legal and Policy Issues
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 ...
2/1/20
Legal and Policy Issues
Italo Vignoli
UA2.220 (Guillissen)
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
Legal and Policy Issues
Nathan Willis
UA2.220 (Guillissen)
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
Legal and Policy Issues
UA2.220 (Guillissen)
Are the FSF's 4 Freedoms and the OSI's Open Source Definition out of date in 2020 and should be replaced.