Return to Video

Keynote: Mary Gardiner

  • 0:06 - 0:08
    Okay, so as Richard said,
  • 0:08 - 0:13
    I am the co-founder of The Ada Initiative,
  • 0:13 - 0:15
    which is a US non-profit,
  • 0:15 - 0:18
    aiming to increase the participation
  • 0:18 - 0:20
    of women in open source
  • 0:20 - 0:22
    and other open technology and culture areas,
  • 0:22 - 0:26
    and I'm also a PhD student at Macquarie University,
  • 0:26 - 0:29
    trying to finish up that last 10%
  • 0:29 - 0:32
    that takes so much time of any major project.
  • 0:32 - 0:35
    I'm not really going to be talking about
  • 0:35 - 0:38
    either of those things in today's keynote.
  • 0:38 - 0:40
    Perhaps a little bit university.
  • 0:40 - 0:41
    We'll get to that.
  • 0:41 - 0:42
    What I am talking about
  • 0:42 - 0:45
    is changing the world with Python.
  • 0:45 - 0:47
    So I know not everyone here
  • 0:47 - 0:52
    considers themselves an open source developer.
  • 0:52 - 0:54
    You don't release your code into the public, and so forth.
  • 0:54 - 0:55
    But I'm one of those people who started out
  • 0:55 - 0:59
    learning about open source culture and ideals
  • 0:59 - 1:03
    probably several years before I started writing
  • 1:03 - 1:05
    any kind of code that ever worked.
  • 1:05 - 1:08
    And when you start out like that,
  • 1:08 - 1:12
    this is kind of what you think open source is like.
  • 1:12 - 1:14
    (laughter)
  • 1:14 - 1:17
    That -- yeah, that you will single-handedly save the world
  • 1:17 - 1:20
    and wear tight tops.
  • 1:20 - 1:23
    And a stern expression.
  • 1:23 - 1:24
    Yeah, so you think of it
  • 1:24 - 1:27
    as a pretty heroic endeavor, sometimes,
  • 1:27 - 1:29
    that you're making code that will be used
  • 1:29 - 1:34
    outside of people who can afford proprietary software,
  • 1:34 - 1:38
    outside of people who have resources
  • 1:38 - 1:42
    to get boutique code developed for them.
  • 1:42 - 1:44
    Maybe you don't think of yourself exactly like this guy.
  • 1:44 - 1:45
    I mean, there's alternatives.
  • 1:45 - 1:47
    You know, you could think of yourself
  • 1:47 - 1:49
    as one of these people.
  • 1:53 - 1:57
    I think of myself as wooden spoon girl over there.
  • 1:59 - 2:01
    So that's sort of -- you know, all.
  • 2:01 - 2:05
    Depending on where you're coming to open source culture,
  • 2:05 - 2:07
    in particular, people who --
  • 2:07 - 2:09
    so I started reading about
  • 2:09 - 2:11
    the Hacker's Dictionary and so forth,
  • 2:11 - 2:14
    when I started University, at the end of the 1990s.
  • 2:14 - 2:18
    If you come across Jamie Zawinski's writings too soon,
  • 2:18 - 2:20
    you think open source development is more like this.
  • 2:20 - 2:22
    (laughter)
  • 2:22 - 2:25
    For people who don't know of Jamie Zawinsky,
  • 2:25 - 2:27
    he was one of the original Netscape developers,
  • 2:27 - 2:31
    and he was behind a large part of the push
  • 2:31 - 2:34
    to get what is now Firefox open sourced.
  • 2:34 - 2:37
    And then he promptly left Netscape
  • 2:37 - 2:40
    and bought a nightclub, which he runs to this day.
  • 2:40 - 2:41
    And I think this is actually a photograph
  • 2:41 - 2:42
    from the DNA Lounge.
  • 2:42 - 2:45
    Anyway, so that's kind of where you might have
  • 2:45 - 2:47
    come to open source from, thinking --
  • 2:47 - 2:48
    okay, I'm gonna be a hero,
  • 2:48 - 2:50
    and I'm gonna party all night.
  • 2:50 - 2:54
    And I guess, if you're Anthony, that might be true.
  • 2:54 - 2:57
    But for the rest of us, there's this disappointing realization
  • 2:57 - 3:00
    when suddenly you realize you're spending a lot of time
  • 3:00 - 3:04
    more in this kind of environment.
  • 3:07 - 3:09
    And then every so often --
  • 3:11 - 3:13
    I'll just take a second to adjust the mic properly.
  • 3:23 - 3:25
    >> Do you want to use the lectern mic?
  • 3:25 - 3:27
    We'll see how it goes this time.
  • 3:27 - 3:29
    If it falls off again, I'll use the lectern mic.
  • 3:29 - 3:31
    Yeah, so you're spending a lot of time
  • 3:31 - 3:33
    in environments like this,
  • 3:33 - 3:36
    and every so often, you take a weekend off,
  • 3:36 - 3:40
    and you spend time doing this.
  • 3:44 - 3:46
    So what I'm talking about in --
  • 3:46 - 3:50
    maybe it is better to use the lectern mic.
  • 3:53 - 3:55
    Okay.
  • 4:02 - 4:04
    Switch that off.
  • 4:06 - 4:07
    Okay.
  • 4:07 - 4:11
    Right, so I'm talking about restoring your heroism
  • 4:11 - 4:15
    with a touch of Python.
  • 4:18 - 4:19
    So I'm gonna talk about four projects
  • 4:19 - 4:22
    in the Python space today.
  • 4:22 - 4:24
    For people who were in Brianna's talk,
  • 4:24 - 4:26
    this is maybe a little bit like that,
  • 4:26 - 4:29
    except four projects instead of one.
  • 4:29 - 4:31
    Basically, projects you might want to consider
  • 4:31 - 4:33
    contributing to, or investigating further,
  • 4:33 - 4:35
    if you want a little bit more of the wooden spoon
  • 4:35 - 4:37
    and less of the cube farm
  • 4:37 - 4:40
    in your Python development.
  • 4:40 - 4:42
    The first one I'm gonna talk about --
  • 4:42 - 4:44
    and probably devote the most time to --
  • 4:44 - 4:45
    is a project called Plover.
  • 4:45 - 4:49
    Probably the least well known of these projects.
  • 4:51 - 4:55
    Has anybody here actually heard of the Plover Project?
  • 4:56 - 4:57
    Yeah, okay.
  • 4:57 - 5:02
    So that was about three people, for the benefit of the audio.
  • 5:02 - 5:05
    Right, so, for the rest of you...
  • 5:07 - 5:08
    A little bit of background on this.
  • 5:08 - 5:10
    So what you see right at the top there
  • 5:10 - 5:15
    is a standard -- what's called steno keyboard layout.
  • 5:15 - 5:19
    So steno is the typing mechanism
  • 5:19 - 5:22
    that people use for extremely fast speech transcripts,
  • 5:22 - 5:25
    like people who transcribe court proceedings,
  • 5:25 - 5:30
    and people who closed caption television live to air.
  • 5:30 - 5:35
    The mechanism you use to type is called chording.
  • 5:35 - 5:36
    You hold down multiple keys at once.
  • 5:36 - 5:40
    Each key press -- it depends on the dictionary you use,
  • 5:40 - 5:42
    but each key press corresponds to
  • 5:42 - 5:44
    usually about a syllable,
  • 5:44 - 5:46
    rather than a single letter.
  • 5:46 - 5:48
    Each combination key press, that is.
  • 5:48 - 5:50
    You can customize the dictionary,
  • 5:50 - 5:52
    so in court reporting,
  • 5:52 - 5:53
    where there's a lot of jargon and so forth,
  • 5:53 - 5:56
    you might have a single chord
  • 5:56 - 5:58
    that you've defined to be as much as
  • 5:58 - 6:00
    an entire sentence.
  • 6:00 - 6:02
    It's arbitrary.
  • 6:02 - 6:05
    So traditionally, this is taught
  • 6:05 - 6:09
    in quite expensive technical courses, stenotyping.
  • 6:09 - 6:11
    And the entry-level machines
  • 6:11 - 6:14
    to do it cost something, I believe --
  • 6:14 - 6:16
    something along the lines of $3,000.
  • 6:16 - 6:20
    But, in principle, there's no reason why you can't do it --
  • 6:20 - 6:21
    assuming that you have a keyboard
  • 6:21 - 6:23
    that can register enough presses,
  • 6:23 - 6:26
    which luckily have been developed a lot for gamers,
  • 6:26 - 6:28
    who have similar kinds of styles --
  • 6:28 - 6:30
    (laughter)
  • 6:30 - 6:31
    so the cheapest --
  • 6:31 - 6:35
    the requirement is called an n-key rollover.
  • 6:35 - 6:38
    Sometimes called anti-ghosting, I believe.
  • 6:38 - 6:42
    The cheapest is the Microsoft Sidewinder X4,
  • 6:42 - 6:45
    which is about -- I think I've seen it for under $60
  • 6:45 - 6:46
    in Australia.
  • 6:46 - 6:49
    Undoubtedly 10 cents in the United States, maybe.
  • 6:49 - 6:51
    (laughter)
  • 6:51 - 6:55
    So Plover is an attempt to bring stenotyping
  • 6:55 - 6:57
    to standard keyboards.
  • 6:57 - 7:01
    So that is -- making both the entry open source,
  • 7:01 - 7:06
    and making the equipment extremely cheap.
  • 7:06 - 7:08
    So the reason this helps save the world
  • 7:08 - 7:14
    is that extremely fast typing is --
  • 7:14 - 7:16
    so it's a benefit for a lot of us.
  • 7:16 - 7:20
    So to give you a sense of what I mean by extremely fast,
  • 7:20 - 7:22
    unless you do a lot of dedicated
  • 7:22 - 7:23
    sitting in front of your computer
  • 7:23 - 7:25
    for multiple hours,
  • 7:25 - 7:26
    over multiple weeks,
  • 7:26 - 7:28
    most people, I think, plateau --
  • 7:28 - 7:30
    who here knows their qwerty typing speed,
  • 7:30 - 7:34
    and it's faster than 60 words a minute?
  • 7:35 - 7:38
    Maybe 15, 20 people.
  • 7:38 - 7:42
    Anyone faster than 100 words a minute?
  • 7:42 - 7:44
    Okay, I see one.
  • 7:44 - 7:50
    So it's a little bit hard for the steno people to tell,
  • 7:50 - 7:53
    because mostly it's taught full-time in technical colleges.
  • 7:53 - 7:55
    You take a two-year course,
  • 7:55 - 7:56
    where you do nothing but do this.
  • 7:56 - 7:58
    And that brings your typing speed
  • 7:58 - 8:00
    up above 200 words a minute.
  • 8:00 - 8:02
    I think the world record is somebody
  • 8:02 - 8:05
    who can type 350 words a minute.
  • 8:05 - 8:08
    But the estimate of the woman
  • 8:08 - 8:09
    who founded the Plover Project,
  • 8:09 - 8:11
    a woman called Mirabai Knight,
  • 8:11 - 8:13
    is that most people with the kind of effort
  • 8:13 - 8:15
    that a lot of us put into learning qwerty,
  • 8:15 - 8:19
    which is a few weeks to a few months
  • 8:19 - 8:21
    with typing exercises,
  • 8:21 - 8:24
    and not eight-hour days --
  • 8:24 - 8:25
    but, you know, an hour here and there,
  • 8:25 - 8:27
    over six months,
  • 8:27 - 8:30
    that most people could reach 100 words a minute.
  • 8:30 - 8:31
    That's around about the speed
  • 8:31 - 8:32
    that most people reach when they drop out
  • 8:32 - 8:34
    of steno courses,
  • 8:34 - 8:35
    because they realize there's a big difference
  • 8:35 - 8:37
    between 100 words a minute
  • 8:37 - 8:38
    and the 220 you need
  • 8:38 - 8:41
    to be a certified court reporter.
  • 8:41 - 8:43
    But on the other hand, for the people in the room
  • 8:43 - 8:44
    who didn't raise their hand,
  • 8:44 - 8:45
    except for that person up there,
  • 8:45 - 8:47
    100 words a minute
  • 8:47 - 8:49
    would be faster for your typing.
  • 8:49 - 8:50
    So there's that.
  • 8:50 - 8:54
    But one more changing the world aspect for that,
  • 8:54 - 8:56
    aside from making typing faster,
  • 8:56 - 9:00
    is that for people who rely on text for communication --
  • 9:00 - 9:02
    so people who are entering stuff
  • 9:02 - 9:03
    in order to be able to speak,
  • 9:03 - 9:05
    who need to enter text
  • 9:05 - 9:08
    in order to produce text-to-speech output,
  • 9:08 - 9:09
    the faster the better, basically.
  • 9:09 - 9:11
    It's really, really hard
  • 9:11 - 9:13
    to reach conversational speed.
  • 9:13 - 9:18
    I think -- so I don't know what I'm speaking right now.
  • 9:18 - 9:22
    It could be as much as 300 words a minute.
  • 9:22 - 9:27
    So for anybody who needs to take down my speech,
  • 9:27 - 9:28
    which is court reporters,
  • 9:28 - 9:31
    or anybody who'd like to talk to me by typing,
  • 9:31 - 9:32
    and having it read out,
  • 9:32 - 9:37
    fast typing is a hell of a benefit.
  • 9:37 - 9:39
    So I'm just gonna have...
  • 9:39 - 9:41
    This is one of those moments where I have a video,
  • 9:41 - 9:45
    and it could be a problem.
  • 9:51 - 9:53
    So this is Mirabai Knight,
  • 9:53 - 9:55
    who is a trained stenotypist,
  • 9:55 - 9:59
    who has a typing speed of over 220 words a minute,
  • 9:59 - 10:01
    so she's using the Plover tool,
  • 10:01 - 10:03
    and she's using
  • 10:03 - 10:05
    one of the Microsoft Sidewinder keyboards here.
  • 10:05 - 10:08
    So she's not using the very high end hardware
  • 10:08 - 10:10
    that she would use professionally.
  • 10:10 - 10:14
    And she's entered an online typing race.
  • 10:18 - 10:22
    Okay, so it counts down, and go.
  • 10:22 - 10:24
    (reading text aloud)
  • 10:46 - 10:49
    213 words a minute.
  • 10:52 - 10:54
    So that's steno.
  • 10:54 - 10:57
    And that's Plover.
  • 11:02 - 11:03
    She has a number of YouTube videos.
  • 11:03 - 11:07
    Five or six, demonstrating herself using Plover.
  • 11:07 - 11:09
    Sometimes you can see her hands on the keys
  • 11:09 - 11:11
    and so forth.
  • 11:11 - 11:14
    Okay, so the thing about Plover is --
  • 11:14 - 11:15
    so first of all, most of you have never heard of it.
  • 11:15 - 11:17
    Second of all,
  • 11:17 - 11:19
    Mirabai funded it out of her own pocket.
  • 11:19 - 11:21
    She found a guy who programs Python
  • 11:21 - 11:23
    living downstairs from her in New York.
  • 11:23 - 11:25
    (laughter)
  • 11:25 - 11:27
    And she paid him all the money she had,
  • 11:27 - 11:29
    because she had this vision of open source steno.
  • 11:29 - 11:32
    So they've gotten it to the point where it works
  • 11:32 - 11:34
    as an input mechanism on Ubuntu.
  • 11:34 - 11:36
    You install this Python program,
  • 11:36 - 11:38
    and you get your Microsoft Sidewinder
  • 11:38 - 11:41
    or other n-key rollover keyboard,
  • 11:41 - 11:43
    and you can do steno.
  • 11:43 - 11:46
    So there's some obvious holes in that.
  • 11:46 - 11:48
    For starters, not everyone uses Ubuntu.
  • 11:48 - 11:53
    There's also a great deal of learning curve to go.
  • 11:53 - 11:57
    So me telling you about this is very cool,
  • 11:57 - 11:58
    but I've known this for a year,
  • 11:58 - 12:00
    and I haven't gone out yet
  • 12:00 - 12:01
    and learned how to enter steno.
  • 12:01 - 12:03
    Even though I have a PhD thesis to write.
  • 12:03 - 12:06
    (laughter)
  • 12:06 - 12:09
    So there's a hell of a lot of work left to do,
  • 12:09 - 12:10
    and as far as I'm aware,
  • 12:10 - 12:12
    Mirabai has run out of funding.
  • 12:12 - 12:15
    So the kind of stuff they need as well --
  • 12:15 - 12:16
    it needs to be ported
  • 12:16 - 12:18
    to more operating systems.
  • 12:18 - 12:21
    There is a competing tool already for iPad,
  • 12:21 - 12:26
    but tablets in general are an obvious next candidate,
  • 12:26 - 12:30
    because typing on them is particularly horrible.
  • 12:30 - 12:35
    At the moment, you can edit the dictionary by opening up --
  • 12:35 - 12:36
    so the dictionary of chords
  • 12:36 - 12:40
    is a giant text file in a particular format,
  • 12:40 - 12:43
    and you can edit it in a text editor, if you want to.
  • 12:43 - 12:45
    What would be really nice
  • 12:45 - 12:47
    is some tools that make that slightly more pleasant,
  • 12:47 - 12:49
    as in you don't open it up,
  • 12:49 - 12:51
    scroll down to where you want to put in your new chord,
  • 12:51 - 12:54
    put it in, put in the letters it translates to,
  • 12:54 - 12:58
    and then have to test it to see if it conflicts
  • 12:58 - 13:00
    with other chords that have been entered
  • 13:00 - 13:02
    elsewhere in the dictionary.
  • 13:02 - 13:06
    Because it's a very good idea not to have ambiguity.
  • 13:06 - 13:09
    So there's a whole bunch of tools
  • 13:09 - 13:11
    that need to be developed around editing the dictionary.
  • 13:11 - 13:13
    One thought I had was actually
  • 13:13 - 13:16
    that they could stand to have something
  • 13:16 - 13:18
    that suggests: "You appeared to enter the sequence..."
  • 13:18 - 13:20
    I guess...
  • 13:20 - 13:23
    "My research is -- convincingly argues that...
  • 13:23 - 13:25
    A lot of times.
  • 13:25 - 13:28
    You could stand to make a chord for it."
  • 13:28 - 13:31
    So something that actually logs your key strokes
  • 13:31 - 13:32
    and recommends that you turn
  • 13:32 - 13:35
    certain commonly typed sequences into a chord
  • 13:35 - 13:37
    would be a really nice tool.
  • 13:37 - 13:40
    And finally, in order to get people over that hump
  • 13:40 - 13:42
    of, "Oh, I have to learn to type
  • 13:42 - 13:43
    in a whole new way,
  • 13:43 - 13:46
    even though I heard about it in this Python keynote
  • 13:46 - 13:48
    and it sounded kind of cool,"
  • 13:48 - 13:50
    it needs to have teaching tools.
  • 13:50 - 13:54
    It needs have at least the equivalent of TuxTypist
  • 13:54 - 13:56
    for Linux, which is a standard teaching tool.
  • 13:56 - 13:58
    And Mirabai is sort of hoping that something like
  • 13:58 - 14:02
    Frets on Fire will eventually have a steno version,
  • 14:02 - 14:03
    where you have to type
  • 14:03 - 14:06
    in order to get the music to play.
  • 14:06 - 14:10
    So that's one way you could save the world with Python.
  • 14:10 - 14:14
    By contributing to letting people type faster.
  • 14:14 - 14:16
    And not just programmers,
  • 14:16 - 14:19
    but people who use their computers to talk,
  • 14:19 - 14:22
    and people who use their computers and typing
  • 14:22 - 14:26
    as their only means of interpersonal communication.
  • 14:26 - 14:28
    Okay, and that's the URL.
  • 14:28 - 14:30
    There's a development mailing list already.
  • 14:30 - 14:33
    There's a blog, including some relatively elementary,
  • 14:33 - 14:35
    at this stage, introduction to how to learn steno,
  • 14:35 - 14:37
    and how to read your dictionary,
  • 14:37 - 14:41
    and that sort of thing.
  • 14:41 - 14:43
    I think Mirabai must have spent a fair bit of money
  • 14:43 - 14:46
    on it at this point.
  • 14:46 - 14:49
    I guess, as sort of a side note,
  • 14:49 - 14:51
    I believe that the people who can do this
  • 14:51 - 14:52
    at over 200 words a minute
  • 14:52 - 14:56
    often command seven figure -- no, not seven figure.
  • 14:56 - 14:59
    Six figure salaries.
  • 14:59 - 15:02
    You can easily earn, I think, $150,000, US,
  • 15:02 - 15:04
    because there's just not a lot of people
  • 15:04 - 15:06
    who spent three years in technical college
  • 15:06 - 15:08
    learning to type at 240 words a minute.
  • 15:08 - 15:11
    So that's where she got the money from.
  • 15:11 - 15:13
    Okay.
  • 15:13 - 15:18
    The Software Carpentry Course.
  • 15:18 - 15:19
    I'll do this at the beginning of every one.
  • 15:19 - 15:21
    Who's heard of the Software Carpentry?
  • 15:21 - 15:23
    Again, a fairly small number of people.
  • 15:23 - 15:26
    But more than Plover.
  • 15:26 - 15:28
    Okay.
  • 15:28 - 15:29
    So this time you'd be saving the world
  • 15:29 - 15:31
    by helping scientists.
  • 15:31 - 15:33
    So there's a little bit of that going on
  • 15:33 - 15:35
    at this PyCon, in fact.
  • 15:35 - 15:38
    People talking about scientific programming in Python.
  • 15:38 - 15:40
    That's not quite what Software Carpentry is doing.
  • 15:40 - 15:45
    So Software Carpentry is headed by a guy
  • 15:45 - 15:47
    called Greg Wilson.
  • 15:47 - 15:49
    In his latest introduction to Software Carpentry,
  • 15:49 - 15:52
    he says that he talked to scientists about --
  • 15:52 - 15:56
    they estimate that they spend about 40% of their time --
  • 15:56 - 15:58
    this is non-computational scientists, so --
  • 15:58 - 16:02
    people who are doing massive data analysis, and so on.
  • 16:02 - 16:05
    They spend about 40% of their time working with computers
  • 16:05 - 16:08
    to try and get at their data somehow,
  • 16:08 - 16:10
    often programming now.
  • 16:10 - 16:12
    And 96% of them say
  • 16:12 - 16:13
    that they largely taught themselves
  • 16:13 - 16:15
    everything they know about software engineering.
  • 16:15 - 16:19
    Or everything they don't know.
  • 16:19 - 16:23
    Why not write unit tests?
  • 16:23 - 16:25
    Why not use version control systems?
  • 16:25 - 16:27
    The physicist answers...
  • 16:27 - 16:29
    What's a version control system?
  • 16:29 - 16:31
    Okay, so to be fair,
  • 16:31 - 16:32
    you can have these conversations
  • 16:32 - 16:34
    with working software engineers as well.
  • 16:34 - 16:40
    And as somebody who's a computer scientist,
  • 16:40 - 16:43
    you can definitely have this with computer scientists a lot.
  • 16:43 - 16:44
    Computer scientists are really bad --
  • 16:44 - 16:46
    largely; not all of them --
  • 16:46 - 16:48
    are very bad software engineers.
  • 16:48 - 16:54
    So Software Carpentry is basically
  • 16:54 - 16:56
    a giant curriculum on the --
  • 16:56 - 17:01
    they call it the 90% of software engineering
  • 17:01 - 17:05
    that gets you 90% of the way there, essentially.
  • 17:05 - 17:07
    So it introduces version control.
  • 17:07 - 17:09
    It introduces unit tests.
  • 17:09 - 17:12
    It introduces useful languages, including Python,
  • 17:12 - 17:15
    but also simple spreadsheet programming and so on.
  • 17:15 - 17:18
    To get people that --
  • 17:18 - 17:20
    to get people working in science, you know,
  • 17:20 - 17:24
    using tools that have been developed
  • 17:24 - 17:26
    in the last 40 years or so in terms of software engineering,
  • 17:26 - 17:28
    rather than either reinventing them,
  • 17:28 - 17:30
    or, much more commonly,
  • 17:30 - 17:35
    simply not having anything of the kind.
  • 17:35 - 17:36
    So you get people
  • 17:36 - 17:37
    who can't replicate their experiments,
  • 17:37 - 17:38
    because they don't have the code,
  • 17:38 - 17:40
    or they don't have that version of the code anymore.
  • 17:43 - 17:44
    You get people who can't replicate --
  • 17:44 - 17:47
    who can't work out why their experiment
  • 17:47 - 17:48
    doesn't work this week,
  • 17:48 - 17:50
    because they can't revert to last week,
  • 17:50 - 17:51
    and they don't have any unit tests
  • 17:51 - 17:53
    to guarantee that their code works the same
  • 17:53 - 17:55
    as last week.
  • 17:55 - 17:59
    So saving the world with the Software Carpentry Project
  • 17:59 - 18:01
    mostly involves contributing to their lessons,
  • 18:01 - 18:05
    which are distributed free,
  • 18:05 - 18:08
    open online, and are open source.
  • 18:08 - 18:11
    So you can simply debug the lessons.
  • 18:11 - 18:12
    Watch the videos
  • 18:12 - 18:13
    and work through the worksheets,
  • 18:13 - 18:15
    and send Greg Wilson errors
  • 18:15 - 18:17
    whenever you discover a problem.
  • 18:17 - 18:22
    They also are keen to have other people produce lessons.
  • 18:22 - 18:25
    So they like them to be three-minute videos, essentially.
  • 18:25 - 18:25
    You write a script.
  • 18:25 - 18:28
    You make a short video.
  • 18:28 - 18:29
    They'll edit it for you.
  • 18:29 - 18:31
    Cut it all together.
  • 18:31 - 18:33
    Put up a transcript.
  • 18:33 - 18:38
    And you can give any variation of the course at --
  • 18:38 - 18:40
    well, it's aimed at university people.
  • 18:40 - 18:44
    Sometimes the course is accessible to undergrads.
  • 18:44 - 18:47
    Most likely aimed at introductory --
  • 18:47 - 18:48
    people who are entering grad school.
  • 18:48 - 18:52
    The full course, I think,
  • 18:52 - 18:55
    probably is aimed at an entire semester.
  • 18:55 - 18:57
    They have a compressed one-week version
  • 18:57 - 18:59
    and a compressed three-day version, and so on.
  • 18:59 - 19:01
    And they're also keen to have people
  • 19:01 - 19:04
    offer to give that course.
  • 19:04 - 19:07
    That's probably more accessible to academics.
  • 19:07 - 19:09
    Universities are, in my experience,
  • 19:09 - 19:11
    not overly friendly to people turning up,
  • 19:11 - 19:12
    and saying, "I'd like to give a course."
  • 19:12 - 19:14
    Nice as that would be sometimes.
  • 19:14 - 19:17
    Anyway, Software Carpentry, there.
  • 19:17 - 19:19
    Producing tools --
  • 19:19 - 19:25
    Python community-associated tools for scientists
  • 19:25 - 19:27
    to learn software engineering.
  • 19:27 - 19:29
    Okay.
  • 19:29 - 19:31
    Next tool.
  • 19:31 - 19:32
    Okay, Calibre.
  • 19:32 - 19:34
    More of you have heard of Calibre?
  • 19:34 - 19:36
    Yeah, we're getting there.
  • 19:36 - 19:39
    I'm hoping this is a linear increase.
  • 19:39 - 19:42
    So Calibre is an ebook manager.
  • 19:42 - 19:49
    It won't literally help you save books from the fire.
  • 19:49 - 19:51
    We'll get to saving books in a second.
  • 19:51 - 19:53
    I have a special for Richard there.
  • 19:53 - 19:58
    What Calibre does is simply make managing your ebooks
  • 19:58 - 20:00
    a bit easier, and get you a little bit more out of the clutches
  • 20:00 - 20:04
    of individual ebook vendors.
  • 20:04 - 20:08
    The core Calibre, for obvious legal reasons,
  • 20:08 - 20:12
    does not actually break digital rights management
  • 20:12 - 20:13
    on your books,
  • 20:13 - 20:16
    but it does allow you to centralize them in one place.
  • 20:16 - 20:18
    It does the rather nice thing of converting
  • 20:18 - 20:23
    epub format ebooks to mobi, and vice versa.
  • 20:23 - 20:28
    Mostly in order to counter some of Kindle's evilness,
  • 20:28 - 20:31
    that it doesn't read the most common format.
  • 20:31 - 20:34
    So contributing to Calibre...
  • 20:34 - 20:38
    It's mostly straight out.
  • 20:38 - 20:43
    This is -- you like to fix bugs involving strings, basically.
  • 20:43 - 20:48
    If you're one of those people who has always --
  • 20:48 - 20:50
    always dreamed they could wake up in the morning,
  • 20:50 - 20:52
    thinking, "Gosh, I hope I come across a Unicode bug today,
  • 20:52 - 20:54
    because I love those ones,"
  • 20:54 - 20:57
    you should be contributing to Calibre.
  • 20:57 - 21:00
    They also --
  • 21:00 - 21:03
    I don't think they actually call for this
  • 21:03 - 21:05
    on their own website, I have to say,
  • 21:05 - 21:06
    but almost everyone I know
  • 21:06 - 21:08
    who's had something to do with Calibre
  • 21:08 - 21:10
    says they release constantly,
  • 21:10 - 21:12
    they release every week,
  • 21:12 - 21:13
    they have more features
  • 21:13 - 21:14
    for pulling data out of some ebooks
  • 21:14 - 21:17
    and stuffing it into other ebooks, and so forth.
  • 21:17 - 21:21
    What a shame that some of the buttons --
  • 21:21 - 21:24
    the selection of buttons across the top
  • 21:24 - 21:25
    actually scrolls off the right hand of your screen.
  • 21:25 - 21:27
    So if you've got a small screen,
  • 21:27 - 21:29
    you can only use half the functionality.
  • 21:29 - 21:32
    And things like that.
  • 21:32 - 21:34
    So if you're interested, also,
  • 21:34 - 21:37
    in GUI development and user interface design,
  • 21:37 - 21:40
    you could help save the world and contribute to Calibre.
  • 21:40 - 21:43
    Okay, that's the website.
  • 21:43 - 21:45
    Definitely worth using,
  • 21:45 - 21:49
    if you're doing any ebook reading at all.
  • 21:49 - 21:53
    Okay, a very brief non-Pythonic interlude.
  • 21:53 - 21:55
    Rich is not even paying attention.
  • 21:55 - 21:57
    This has a picture of a cat, especially for him.
  • 21:57 - 22:00
    Yeah, right?
  • 22:00 - 22:01
    We have a picture of a cat,
  • 22:01 - 22:04
    to go for Richard, as requested on Twitter last night.
  • 22:04 - 22:07
    So a project that's not written in Python, very quickly.
  • 22:07 - 22:09
    Distributed Proofreaders.
  • 22:09 - 22:10
    People have heard of it?
  • 22:10 - 22:12
    A little bit?
  • 22:12 - 22:16
    They basically do Project Gutenberg now.
  • 22:16 - 22:20
    They provide maybe 90% or 95% of books
  • 22:20 - 22:22
    coming into Project Gutenberg.
  • 22:22 - 22:23
    Basically, people scan books,
  • 22:23 - 22:26
    they upload the scan to distribute to proofreaders,
  • 22:26 - 22:29
    heaps and heaps of people
  • 22:29 - 22:31
    go to the Distributed Proofreaders site.
  • 22:31 - 22:33
    So the acronym there
  • 22:33 - 22:37
    is Project Gutenberg Distributed Proofreaders.net.
  • 22:37 - 22:38
    PGDP.
  • 22:38 - 22:40
    Not easy to remember.
  • 22:40 - 22:45
    People check the optical character recognition.
  • 22:45 - 22:48
    I think they do five separate passes now.
  • 22:48 - 22:51
    So five separate dedicated proofreaders
  • 22:51 - 22:52
    have to read every ebook.
  • 22:52 - 22:53
    At the end of that,
  • 22:53 - 22:55
    it gets uploaded to Project Gutenberg.
  • 22:55 - 22:57
    I stuck this in here,
  • 22:57 - 22:59
    because it is a little bit more directly
  • 22:59 - 23:00
    saving books from the fire,
  • 23:00 - 23:04
    where the fire is copyright claims by people
  • 23:04 - 23:07
    who have released new editions.
  • 23:07 - 23:11
    So Project Gutenberg distributes books
  • 23:11 - 23:13
    that were published before 1923,
  • 23:13 - 23:15
    and by far the easiest way to prove that
  • 23:15 - 23:18
    is to get a copy that was printed before 1923,
  • 23:18 - 23:20
    and those are slowly disappearing,
  • 23:20 - 23:22
    for obvious reasons.
  • 23:22 - 23:23
    Okay.
  • 23:23 - 23:25
    So if you literally -- or more literally
  • 23:25 - 23:27
    want to save books from the fire,
  • 23:27 - 23:28
    you can drop into Distributed Proofreaders.
  • 23:28 - 23:31
    But the code that drives the site,
  • 23:31 - 23:33
    while it's open source, is written in PHP.
  • 23:33 - 23:35
    So that's why the cat was angry.
  • 23:35 - 23:38
    (laughter)
  • 23:38 - 23:40
    Okay, last of all: Sugar.
  • 23:40 - 23:43
    People who have heard of Sugar?
  • 23:43 - 23:47
    Sugar, the learning environment,
  • 23:47 - 23:50
    originally for the One Laptop Per Child Project.
  • 23:50 - 23:55
    Right?
  • 23:55 - 23:56
    So this is helping children,
  • 23:56 - 23:57
    which is obviously helping save the world.
  • 23:57 - 23:59
    I don't know whether I need to develop
  • 23:59 - 24:00
    that argument any further.
  • 24:00 - 24:02
    We have a cute child on the screen, ladies and gentlemen.
  • 24:09 - 24:10
    Anthony would like to save the cat.
  • 24:13 - 24:15
    Okay, cute children.
  • 24:15 - 24:19
    So Sugar is an innovative collaboration-oriented
  • 24:19 - 24:23
    learning environment for, sort of, children
  • 24:23 - 24:25
    up to primary school age.
  • 24:25 - 24:30
    It's very focused on collaboratively editing documents.
  • 24:30 - 24:36
    It has the cute feature that you can access the --
  • 24:36 - 24:37
    while you're actually using your --
  • 24:37 - 24:39
    it's not only for OLPC now.
  • 24:39 - 24:41
    You can get it on a USB stick,
  • 24:41 - 24:43
    and stick it in any laptop.
  • 24:43 - 24:45
    That you can actually click on something,
  • 24:45 - 24:48
    and there's the source code that's running on your laptop
  • 24:48 - 24:49
    in Python,
  • 24:49 - 24:50
    and you can actually edit Sugar
  • 24:50 - 24:52
    if you're a small child,
  • 24:52 - 24:54
    and you have small enough fingers for those keyboards.
  • 24:54 - 24:58
    You can actually edit the code as you go.
  • 24:58 - 25:01
    So it's a pretty big project.
  • 25:01 - 25:03
    It's basically a window manager,
  • 25:03 - 25:06
    on up through an incredible number of applications,
  • 25:06 - 25:07
    which they call activities.
  • 25:07 - 25:10
    So it's got a wide range of stuff you can do for them.
  • 25:10 - 25:14
    They still have a lot of core environment development,
  • 25:14 - 25:16
    so if you're interested in hacking on window manager level,
  • 25:16 - 25:18
    display level kind of stuff,
  • 25:18 - 25:21
    there's a fair bit of that going on.
  • 25:21 - 25:23
    There's activities, which is the writing and chatting
  • 25:23 - 25:28
    and web surfing and doing maths collaboratively tools.
  • 25:28 - 25:32
    In particular, they have a little project called Math 4,
  • 25:32 - 25:36
    which is teaching grade 4 level mathematics.
  • 25:36 - 25:40
    And they have infrastructure, which is running their website,
  • 25:40 - 25:42
    and all that sort of thing.
  • 25:42 - 25:44
    It's a big enough project that they have a dedicated team
  • 25:44 - 25:45
    of volunteers working on their website,
  • 25:45 - 25:47
    and working on their presentation, and so on.
  • 25:47 - 25:49
    Okay.
  • 25:49 - 25:51
    And that's where they are.
  • 25:51 - 25:52
    They're at Sugar Labs.
  • 25:52 - 25:58
    And then, at some point,
  • 25:58 - 25:59
    somebody will consider you cool enough
  • 25:59 - 26:01
    to invite you to their special party
  • 26:01 - 26:02
    at their open source nightclub.
  • 26:02 - 26:06
    Okay, so that brings me
  • 26:06 - 26:09
    to the end of my four projects
  • 26:09 - 26:11
    you could contribute to in Python,
  • 26:11 - 26:13
    in order to do your bit in saving the world.
  • 26:13 - 26:15
    I just have some quick thanks.
  • 26:15 - 26:17
    I wrote this on the Ada Initiative's time.
  • 26:17 - 26:21
    So their sponsors are listed there.
  • 26:21 - 26:25
    The high level sponsors were Linux Australia,
  • 26:25 - 26:28
    Puppet Labs, and Dreamhost web hosting.
  • 26:28 - 26:31
    And last of all, my husband, Andrew Bennetts,
  • 26:31 - 26:36
    who dug up, I think, two of these projects for me,
  • 26:36 - 26:41
    and criticized my choice of images for the talk.
  • 26:41 - 26:45
    Okay.
  • 26:45 - 26:46
    All right.
  • 26:46 - 26:47
    Thank you.
  • 26:47 - 26:54
    (applause)
  • 26:57 - 26:59
    >> We have time for two or three questions.
  • 26:59 - 27:01
    (inaudible)
  • 27:01 - 27:03
    >> Do we have a microphone?
  • 27:09 - 27:11
    >> Push the power button.
  • 27:11 - 27:23
    (inaudible)
  • 27:23 - 27:25
    >> Okay.
  • 27:25 - 27:27
    At the risk of possibly turning this
  • 27:27 - 27:29
    into a yak-shaving exercise,
  • 27:29 - 27:31
    you've mentioned four projects here
  • 27:31 - 27:33
    which would benefit from having Python hackers
  • 27:33 - 27:36
    join in and contribute.
  • 27:36 - 27:38
    There are 300-odd of us here,
  • 27:38 - 27:40
    and the 270-odd who aren't already
  • 27:40 - 27:42
    contributors to a large open source project
  • 27:42 - 27:46
    would possibly flood those four,
  • 27:46 - 27:48
    if they all turned up tomorrow to contribute.
  • 27:48 - 27:49
    There is, obviously,
  • 27:49 - 27:50
    a lot of open source contributors
  • 27:50 - 27:52
    who aren't in this room.
  • 27:52 - 27:54
    What's the best way to coordinate effort here?
  • 27:54 - 27:56
    You said that your husband had to bring you
  • 27:56 - 27:57
    two of those projects.
  • 27:57 - 27:58
    I'm sure there are, for every one on there,
  • 27:58 - 28:01
    another thousand of people who would like help
  • 28:01 - 28:04
    doing their thing who aren't Python technical
  • 28:04 - 28:06
    and want the assistance.
  • 28:06 - 28:08
    How do we coordinate that effort better?
  • 28:08 - 28:09
    MARY: Yeah.
  • 28:09 - 28:11
    So I have to say I'm suspicious
  • 28:11 - 28:13
    that not everyone in this room
  • 28:13 - 28:15
    is immediately gonna join one of these projects.
  • 28:15 - 28:19
    So I'm hoping that that will save...
  • 28:19 - 28:22
    So I think, just to give you an example --
  • 28:22 - 28:24
    so Sugar could probably absorb everyone in this room,
  • 28:24 - 28:26
    if you all suddenly turn up.
  • 28:26 - 28:28
    It might be a little bit of a thing for them,
  • 28:28 - 28:29
    but they could probably absorb you.
  • 28:29 - 28:31
    I wouldn't recommend that everyone goes
  • 28:31 - 28:33
    and volunteers for Plover,
  • 28:33 - 28:36
    because they had 10 posts to their mailing list last month,
  • 28:36 - 28:39
    and 300 of them might scare them a little bit.
  • 28:39 - 28:43
    In terms of recruiting people to projects,
  • 28:43 - 28:46
    I have to say that's a really good question.
  • 28:46 - 28:51
    I don't know of any really good mechanism
  • 28:51 - 28:55
    at the moment to identify --
  • 28:55 - 28:58
    somebody turns up,
  • 28:58 - 29:00
    and they say, "I want to be an open source hacker.
  • 29:00 - 29:02
    What project should I join?"
  • 29:02 - 29:05
    And that is kind of the eternal mentoring question
  • 29:05 - 29:08
    in open source, because it's really hard to answer.
  • 29:08 - 29:09
    You want a project --
  • 29:09 - 29:11
    I'm reasonably sure all of these projects are living,
  • 29:11 - 29:13
    and actually accept patches.
  • 29:13 - 29:15
    That's the first thing you need to check.
  • 29:15 - 29:17
    That they all actually want contributors
  • 29:17 - 29:19
    who aren't the main author
  • 29:19 - 29:22
    is another thing you need to check.
  • 29:22 - 29:25
    But it would be really nice to have kind of
  • 29:25 - 29:28
    an edited clearinghouse of open source projects
  • 29:28 - 29:30
    that need contributors,
  • 29:30 - 29:32
    matching them up with skills.
  • 29:32 - 29:33
    I know Sourceforge has tried, and --
  • 29:33 - 29:38
    >> Another one.
  • 29:38 - 29:39
    Fresh Meat or someone -- one or the other.
  • 29:39 - 29:41
    MARY: Yeah.
  • 29:41 - 29:42
    But if anyone -- so yeah.
  • 29:42 - 29:44
    My email address is there.
  • 29:44 - 29:45
    And we want this for the Ada Initiative too,
  • 29:45 - 29:47
    because we want to be able to provide
  • 29:47 - 29:48
    this kind of stuff to women.
  • 29:48 - 29:50
    If anyone is aware of a good mechanism
  • 29:50 - 29:52
    of joining enthusiastic people
  • 29:52 - 29:54
    with projects that have holes in them,
  • 29:54 - 29:57
    that would be -- or wants to develop one --
  • 29:57 - 29:59
    that would be really cool.
  • 29:59 - 30:01
    >> Time for one more question.
  • 30:01 - 30:03
    >> Yes, you said that Software Carpentry --
  • 30:03 - 30:06
    >> The mic needs to be green.
  • 30:15 - 30:16
    >> Just ask and repeat.
  • 30:16 - 30:21
    >> You said that Software Carpentry wanted videos.
  • 30:21 - 30:25
    Say hypothetically that I'm not either an aspiring actor
  • 30:25 - 30:28
    or an aspiring producer.
  • 30:28 - 30:30
    What sort of videos do they want?
  • 30:30 - 30:31
    Is it just talking heads?
  • 30:31 - 30:32
    Or somebody with a whiteboard?
  • 30:32 - 30:34
    MARY: So the question is:
  • 30:34 - 30:37
    what kind of videos does Software Carpentry want,
  • 30:37 - 30:40
    given that most of us aren't actors
  • 30:40 - 30:42
    or video professionals, and so on.
  • 30:42 - 30:46
    What they mostly want is two things.
  • 30:46 - 30:48
    They want short lectures,
  • 30:48 - 30:50
    so that is a bit talking head.
  • 30:50 - 30:52
    Like, they want you to point a camera at yourself
  • 30:52 - 30:53
    while you talk for three minutes
  • 30:53 - 30:57
    about the Software Carpentry issue of your choice.
  • 30:57 - 30:59
    They will edit it for you,
  • 30:59 - 31:01
    and you're supposed to write a script in advance.
  • 31:01 - 31:07
    So the idea is that effectively you're following your script.
  • 31:07 - 31:10
    You make a mistake, you just pause for five seconds,
  • 31:10 - 31:12
    so that they can cut the video appropriately,
  • 31:12 - 31:14
    and then you just resume.
  • 31:14 - 31:15
    That's one type.
  • 31:15 - 31:17
    The other type that they want is screencasts.
  • 31:17 - 31:20
    So pictures of yourself typing a Python program
  • 31:20 - 31:21
    or using a spreadsheet,
  • 31:21 - 31:23
    while talking about what you're doing.
  • 31:23 - 31:26
    And so that second one,
  • 31:26 - 31:28
    especially given that you write the script in advance,
  • 31:28 - 31:30
    is probably something easier to contribute,
  • 31:30 - 31:32
    if you're not really comfortable
  • 31:32 - 31:35
    doing a head-to-camera kind of video.
  • 31:35 - 31:37
    But that's the kind of thing.
  • 31:37 - 31:39
    They want people talking about software development
  • 31:39 - 31:41
    for short periods of time.
  • 31:41 - 31:44
    But one of the options is screencasting yourself,
  • 31:44 - 31:46
    using a tool.
  • 31:52 - 31:55
    >> Thank you, Mary, for that keynote.
  • 31:55 - 31:58
    (applause)
Title:
Keynote: Mary Gardiner
Description:

Keynote.

more » « less
Video Language:
English
Duration:
31:59

English subtitles

Revisions