veyepar: Software Patents: Trolls and Other Bullies

Author(s):	Deb Nicholson
Location	Case Room 2
Date	jan Wed 14	Days Raw Files
Start	11:35	First Raw Start	11:32
Duration	0:45:00	Offset	0:02:34
End	12:20	Last Raw End	13:18
Chapters	00:00
Total cuts_time	45 min.

http://lca2015.linux.org.au/schedule/30247/view_talk
raw-playlist raw-mp4-playlist encoded-files-playlist host public tweet mp4 svg png

assets release.pdf Software_Patents_Trolls_and_Other_Bullies.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	Lots of small and medium free software projects are staffed by volunteers that don't have any money to tempt a patent aggression entity. There's been plenty of talk about patent trolls, but money isn't the only motive for a patent suit. Even if non-practicing entities are eventually curtailed, ill-intentioned practicing entities may not be affected. The free software community will still have to worry about anti-competitive suits, nuisance suits and suits designed to spread fear, uncertainty and doubt about the adoption of free software. So, what can we as free software builders, promoters and users do to protect the code we care about? Some solutions are only effective against non-practicing entities, while others may impact all kinds of bad actors. The strengths and weaknesses of proposed legislation, recent and ongoing campaigns and academic writings will be examined. If legislators and international trade negotiators won't take a stand against anti-competitive patent aggression, then we must do so as a community. Find out about some of the community solutions that are underway and how we can combat the threat of anti-FLOSS plaintiffs together. markdown
Comment:	production notes