Legal and Policy Issues

COLLAB: The optics of the policy

And vice-versa
UA2.220 (Guillissen)
Nathan Willis
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 the public. This session will be an open discussion about photo and video-recording policies, online tagging policies, and related personal-privacy policies, with the goal of clarifying the requirements, needs, and intents of all stakeholders in the FOSS community, so that future event organizers have a solid framework from which to draft clear policies that fit their situations.
Free-software events, like free-software projects, have to maintain a delicate balance between openness as a broad principle and privacy as an individual concern. In the past few years, more and more free-software events and community projects have developed "photo policies" that are intended to define when and how individuals and groups should be captured in media from the event and when and how those same people should be identified in the media. But a haphazard approach to policy writing can create unintentional ambiguities, such as how to define when an individual is the "subject' of a photograph or merely in the background. And free-software communities must also take care to write policies that do not come into conflict with local law, especially when events take place in public spaces. Finally, event organizers need to ensure that their photo policies, real-name policies, press policies, and session-recording consent policies work in concern with one another, not in conflict. This session will be a broad discussion of photography policies and how they interact with other policy concerns. The intent will be to enumerate the concerns of all stakeholders, identify potential areas of confusion, note best practices, and — most importantly — establish resources and spaces for further discussion for project and community members creating photo policies in the future.

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
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.
2/1/20
Legal and Policy Issues
UA2.220 (Guillissen)
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?