From c78625174b2dc2281260737efb43e1822fd71056 Mon Sep 17 00:00:00 2001 From: gorhgorh Date: Sun, 24 Apr 2016 21:44:50 +0200 Subject: [PATCH] closing cfp --- README.md | 11 ++--------- proposed/fuck-your-licence.md | 13 +++++++++++++ 2 files changed, 15 insertions(+), 9 deletions(-) create mode 100644 proposed/fuck-your-licence.md diff --git a/README.md b/README.md index c7c376e..9bffe0b 100644 --- a/README.md +++ b/README.md @@ -1,15 +1,10 @@ # SquatConf Call For Papers Berlin 2016 -Welcome to SquatConf CFP repository. you can also mail your submission to [talks@squatconf.eu] please copy this [model] and mail it. +Welcome to SquatConf CFP repository. ## Submit a talk -- Fork this repo -- `cp submitTalk.md proposed/my_talk.md` -- Edit your talk -- Submit a pull request - -or use the email submission (see paragraph above). +# CFP IS NOW CLOSED ## Disclaimer @@ -30,5 +25,3 @@ cool people. SquatConf is an experience, it is up to you to try it. -[talks@squatconf.eu]: mailto:talks@squatconf.eu -[model]: https://raw.githubusercontent.com/squatconf/talks/master/submitTalk.md diff --git a/proposed/fuck-your-licence.md b/proposed/fuck-your-licence.md new file mode 100644 index 0000000..40368d1 --- /dev/null +++ b/proposed/fuck-your-licence.md @@ -0,0 +1,13 @@ +# Fuck Your License: Communiques from the Copyfight + +name : Knoe Won +time: 30 minutes - 1 hour +need travel fee : yes +need room : yes +Location : no ? +note: can only be there for the 29th + +This workshop will present the myriad potentialities of unbridled data sharing emergent from non-legalist information liberation strategies. Starting off with an initial exposition of why copyleft licenses are not merely undesirable, but are in actuality far more cancerous to unbridled knowledge dissemination than copyright, the workshop will then present potential strategies for removing the various legal, technical, and cultural fetters enchaining various cultural bodies of work. In other words: how could one not only create open archives, but how can one do so safely without the possibility of adversarial reprisal? How could one integrate security considerations from the ground up to foster unimpeded data availability, irrespective of various potential impediments thereto? + + +NOTE: this talk need more info for us to process, it is still in flux right now.