Introduction: Slides ready
parent
16cf83d92e
commit
dc82dc74f9
27
slides.org
27
slides.org
|
@ -117,7 +117,7 @@
|
|||
- [ ] =vim=
|
||||
- [ ] =screen=
|
||||
|
||||
* LACKING Slides [2/6]
|
||||
* LACKING Slides [3/6]
|
||||
:PROPERTIES:
|
||||
:ID: slides
|
||||
:END:
|
||||
|
@ -125,14 +125,14 @@
|
|||
#+BEGIN: columnview :hlines 2 :maxlevel 3 :indent t :id slides
|
||||
| ITEM | DURATION | TODO | ENVIRONMENT |
|
||||
|-------------------------------------------------------+----------+----------+-------------|
|
||||
| Slides | 0:40:59 | LACKING | |
|
||||
| Slides | 0:40:53 | LACKING | |
|
||||
|-------------------------------------------------------+----------+----------+-------------|
|
||||
| \_ Summary | | | |
|
||||
|-------------------------------------------------------+----------+----------+-------------|
|
||||
| \_ Introduction | 0:01:55 | REVIEWED | |
|
||||
| \_ Spoken Intro | 0:00:50 | REVIEWED | note |
|
||||
| \_ Choreographed Workflows | 00:00:20 | REVIEWED | fullframe |
|
||||
| \_ Practical Freedom | 0:00:45 | REVIEWED | fullframe |
|
||||
| \_ Introduction | 0:01:50 | READY | |
|
||||
| \_ Spoken Intro | 0:00:50 | READY | note |
|
||||
| \_ Choreographed Workflows | 00:00:20 | READY | fullframe |
|
||||
| \_ Practical Freedom | 0:00:40 | READY | fullframe |
|
||||
|-------------------------------------------------------+----------+----------+-------------|
|
||||
| \_ Practical Example: Web Browser | 0:07:03 | READY | |
|
||||
| \_ Browser Topics | | | |
|
||||
|
@ -190,8 +190,8 @@
|
|||
| \_ Thank You | 00:00:01 | | fullframe |
|
||||
#+END:
|
||||
|
||||
** REVIEWED Introduction [0/3]
|
||||
*** REVIEWED Spoken Intro :B_note:
|
||||
** READY Introduction [3/3]
|
||||
*** READY Spoken Intro :B_note:
|
||||
:PROPERTIES:
|
||||
:BEAMER_env: note
|
||||
:DURATION: 0:00:50
|
||||
|
@ -222,7 +222,7 @@ My hope is that the examples I have chosen will be useful not just to
|
|||
but to lightly technical users as well.
|
||||
|
||||
|
||||
*** REVIEWED Choreographed Workflows :B_fullframe:
|
||||
*** READY Choreographed Workflows :B_fullframe:
|
||||
:PROPERTIES:
|
||||
:BEAMER_env: fullframe
|
||||
:DURATION: 00:00:20
|
||||
|
@ -244,7 +244,7 @@ And I don't deny that this has been a useful method for making computers
|
|||
But it's important to understand where this trend falls short.
|
||||
|
||||
|
||||
*** REVIEWED Practical Freedom :B_fullframe:
|
||||
*** READY Practical Freedom :B_fullframe:
|
||||
:PROPERTIES:
|
||||
:BEAMER_env: fullframe
|
||||
:END:
|
||||
|
@ -255,18 +255,17 @@ Practical Freedom
|
|||
**** Notes :B_noteNH:
|
||||
:PROPERTIES:
|
||||
:BEAMER_env: noteNH
|
||||
:DURATION: 00:00:45
|
||||
:DURATION: 00:00:40
|
||||
:END:
|
||||
|
||||
This is a talk about /practical/ freedoms---an
|
||||
issue separate from but /requiring/ software freedom.
|
||||
How can we be empowered to do /anything we might imagine/ with our machines?
|
||||
If developers are thinking /for/ us and guiding us in our computing,
|
||||
then we're limited to preconceived workflows.
|
||||
This leaves immense power in the hands of developers even if software is
|
||||
free,
|
||||
because average users are stuck begging them to implement changes,
|
||||
or need to have money to pay someone to do so.
|
||||
because average users are stuck asking them to implement changes,
|
||||
or footing the bill for someone else to do so.
|
||||
|
||||
My goal here is to blur those lines between ``user'' and ``programmer'' and
|
||||
show you how users can be empowered to take control of their computing in
|
||||
|
|
Loading…
Reference in New Issue