Author(s):	Michael Cordover
Location	OGGB4
Date	jan Wed 14	Days Raw Files
Start	15:40	First Raw Start	15:06
Duration	0:45:00	Offset	0:33:31
End	16:25	Last Raw End	16:29
Chapters	00:00
Total cuts_time	42 min.

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

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

State:	--------- borked edit encode push to queue post richard review 1 email review 2 make public tweet to-miror conf done
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:	Unknown Yes No has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	Most modern discussions about open government focus on "Gov 2.0" initiatives like open data licensing, release of data in machine readable formats and enabling online access to government. However, these mostly rely on pro-active governments providing that access voluntarily. This opening up of government information is in part due to the excellent work done in the 1990s and 2000s pushing for the adoption of open data standards. This has enabled a greater adoption of open source software by governments. What we don't see is much government contribution back to open source projects. With only a few exceptions, most software developed for and by government remains closed source. In fact, these projects are often shrouded in secrecy. The origins of open government policy can be traced to the passage of Freedom of Information (FOI) acts in the 1980s. These provide individuals with a statutory right of access to information produced by government. The basic idea behind FOI was that people should be able to see what their taxpayer dollars were funding. So, can FOI be used to open up source code for these secretive projects? Perhaps - but not fully, and certainly not easily. The software used in Australia’s notoriously complicated Senate elections was developed in-house at the Australian Electoral Commission (AEC) and is called EasyCount. In October 2013 I submitted a FOI request asking for the source code for EasyCount and associated documentation. Access was refused on the basis that the code was a trade secret. The AEC has fought hard to prevent the source code being seen by the public, or even scrutineers from political parties. They even refused to provide me with a list of documents identified. I’m currently appealing the AEC’s decision through the courts, thanks to more than $10,000 in crowd funding. In return the AEC has sought to have me declared a vexatious applicant. In the middle of it all the Senate passed a motion ordering the responsible minister to table the source code in Parliament, but the government refused to comply. Even if I win in court (which is far from certain), the code will still be protected by copyright. While the code might be available for inspection, none of the 260,000 lines of code will able to be reused for anything else. There’s a strong argument that major public investments in software development should result in code released under an open licence. I think FOI can be part of this process, but that we're only seeing the beginning of some major developments in open government policy. Ultimately I hope this will culminate in more government-created software released as open source. markdown
Comment:	production notes