< Return to Video

2022 Q&A - Caption/Subtitle File

  • 0:02 - 0:06
    I'm moving around, so I'm masking. I am
    our mobile microphone, but we have a
  • 0:06 - 0:09
    standard microphone also. We have
    people all over the place in the world
  • 0:09 - 0:14
    at home and we also have a resident
    question asker right here.
  • 0:14 - 0:17
    So he's going to represent the
    online questions right?
  • 0:17 - 0:18
    - Yes, correct.
    Also, so you all know
  • 0:18 - 0:22
    I do not know what any of the
    questions are in advance. I will be
  • 0:22 - 0:25
    hearing them all for the first time,
    which also means I might not know the
  • 0:25 - 0:29
    answer or I might pass it to someone
    in the audience, or sometimes I
  • 0:29 - 0:31
    just don't know. So that's what
    happens with these.
  • 0:31 - 0:33
    That's my job. The passing.
  • 0:33 - 0:37
    All right, so we can kind of start
    wherever you want. We can start
  • 0:37 - 0:42
    with in-person. We can start with some
    pre-submitted. We can start with some
  • 0:42 - 0:44
    currently submitted. We have an
    in-person -
  • 0:44 - 0:46
    Looks like we have a hand right here.
    You mind coming over to the
  • 0:46 - 0:52
    microphone? Just so folks on the livestream
    can hear. And if you have also a
  • 0:52 - 0:57
    question, feel free to go up and line
    up. We're going to prioritize, of course,
  • 0:57 - 1:03
    those of you who came on a train for two
    and a half days to be here and then I
  • 1:03 - 1:06
    think Paul will be reading some of the
    ones that are coming in via the social
  • 1:06 - 1:11
    channels. YouTube, Twitter, etc. So
    we'll have a mix of both.
  • 1:11 - 1:13
    Then we'll have food and drinks.
  • 1:15 - 1:18
    Thanks so much for the presentation.
    Very exciting stuff. Looking forward to
  • 1:18 - 1:23
    the future. My question is about Openverse.
    And I wonder if you could speak a
  • 1:23 - 1:28
    little bit about the safety measures
    that have been thought about or will
  • 1:28 - 1:33
    need to be thought about in terms of the
    content that is uploaded there? Will
  • 1:33 - 1:38
    EXIF data be removed from photos that
    are uploaded? That's my question.
  • 1:39 - 1:44
    That's a great question, actually. So
    first, I do not know if we've thought of
  • 1:44 - 1:49
    EXIF before. So you actually just raised
    something really great that we should
  • 1:49 - 1:57
    write down and look at later. I will say
    that - so there's two things there.
  • 1:57 - 2:01
    There's Openverse, which is - think of it
    like a search engine. So it's crawling
  • 2:01 - 2:04
    literally the whole web, and looking for
    things that are Creative Commons
  • 2:04 - 2:08
    licensed and providing a directory of
    them. So what people publish to their own
  • 2:08 - 2:12
    websites is kind of the state of
    responsibility there. But it's kind of
  • 2:12 - 2:17
    like a Google but for Creative Commons
    licensed content. That is separate from
  • 2:17 - 2:22
    the WordPress.org/Photos directory that
    we've created, which is kind of like a
  • 2:22 - 2:26
    Getty or an Unsplash or everything
    but all CC0 licensed forever and
  • 2:26 - 2:29
    ever. By the way, we're not going to
    change that on you like some other photo
  • 2:29 - 2:39
    directories have. That goes to
    moderation. If you want to submit to
  • 2:39 - 2:43
    something there, you'll see that right
    now, it says, "Hey" - one of the checkboxes
  • 2:43 - 2:47
    it certifies, of course, one, that
    you have rights to the photo. Please
  • 2:47 - 2:51
    don't upload other people's photos to it,
    only your own. But, two, that it doesn't
  • 2:51 - 2:58
    have any human faces or other copy
    written material in the photo itself. So
  • 2:58 - 3:02
    this first phase of the photo directory
    really focused on things that can truly be
  • 3:02 - 3:07
    CC0 all the way. Something we've all
    been learning - and it's a little
  • 3:07 - 3:14
    complicated - is with humans and, like, a
    picture of - let's say you had a picture
  • 3:14 - 3:19
    of a piece of art that might have a
    copyright embedded. So even if the image
  • 3:19 - 3:24
    is CC0, something in it might be
    copywritten. And so we're
  • 3:24 - 3:30
    working on - what is an open
    source, GPL, CC0 model release?
  • 3:30 - 3:38
    What does that look like? And that is a
    very open set of lawyers working on
  • 3:38 - 3:43
    things. But once we have it, I think
    that's actually really exciting. Maybe
  • 3:43 - 3:49
    someone could license their likeness as
    well to be in the Openverse. Maybe
  • 3:49 - 3:54
    we generate something with GPT-3
    that replaces faces and then that's the
  • 3:54 - 3:58
    thing that's open. Or maybe someone even
    says, "Maybe while I'm alive, I don't want
  • 3:58 - 4:03
    my likeness used. But maybe on my death, I
    bequeath my likeness to this open
  • 4:03 - 4:06
    commons that belongs to humanity."
    There's lots of different ways this
  • 4:06 - 4:10
    could work, kind of is fun to think
    about and imagine. But that's how that's
  • 4:10 - 4:16
    working right now. We'll probably, you know,
    what makes sense is something that maybe
  • 4:16 - 4:20
    shows the EXIF data you upload before it
    goes into the thing, at least for a
  • 4:20 - 4:22
    photo directory. So you're just aware of
    everything that's being put in there.
  • 4:23 - 4:27
    Location is actually fantastic to have.
    Like if I have a picture of Stonehenge
  • 4:28 - 4:32
    the location where I took that picture
    is kind of awesome. But other metadata,
  • 4:32 - 4:36
    which could be contained in EXIF,
    probably people should just be aware of.
  • 4:36 - 4:40
    Right? So we'll work on getting that
    added to the photo uploader. And by the
  • 4:40 - 4:43
    way, awesome question. Thank you.
    - Thank you very much for the answer.
  • 4:43 - 4:44
    Strong open.
  • 4:45 - 4:49
    No problem. Did we cover everything you think
    is important there? Anything else?
  • 4:49 - 4:54
    Okay, awesome. Bob, before you
    ask your question
  • 4:54 - 4:56
    can you share how you got here?
  • 4:59 - 5:03
    By train, from Seattle
    - From Seattle?
  • 5:03 - 5:06
    Yeah, Seattle.
    - That's on the other side of the country, right?
  • 5:06 - 5:12
    On the other side of the country, and
    spending about six days on the train, two
  • 5:12 - 5:18
    days here. And yeah, it's been an
    adventure. So I've come all this way.
  • 5:19 - 5:21
    Give me some Woo for 2022.
  • 5:22 - 5:24
    - Some moo?
    Woo.
  • 5:24 - 5:28
    I want to hear what WooCommerce is going
    to do in 2022 in your eyes.
  • 5:28 - 5:35
    Sure. So Woo, spelled W-O-O for those who don't
    know, is a plugin for WordPress, which
  • 5:36 - 5:42
    creates commerce functionality in
    WordPress. It's one of the 55,000
  • 5:42 - 5:45
    plugins that exist. But it is a very
    popular one, an important one,
  • 5:45 - 5:50
    especially as we look at things like - you
    saw Shopify coming up on that usage
  • 5:50 - 5:55
    graph. WooCommerce is an open source
    Shopify, and we hope that it can do to
  • 5:55 - 6:01
    democratizing commerce what WordPress
    has done to democratizing publishing.
  • 6:01 - 6:07
    In terms of what's coming for WooCommerce
    in 2022, the thing I'm most excited
  • 6:07 - 6:12
    about that's most relevant for this
    audience is, I would say, embracing
  • 6:12 - 6:17
    Gutenberg and the block interfaces for
    everything with Woo. So right now, Woo still
  • 6:17 - 6:23
    has some ways of doing things which are
    more tied to the Classic Editor, or
  • 6:23 - 6:27
    shortcodes, or other ways of creating,
    like, check out blocks, products,
  • 6:27 - 6:32
    everything like that. There are some
    plugins and experiments around
  • 6:32 - 6:37
    Gutenberg and blocks. And I think that I
    would love if Woo was one of the best
  • 6:37 - 6:42
    plugins in the world for embracing how
    to use Gutenberg. And I think the team's
  • 6:42 - 6:47
    been working really hard on that. It is
    an amazing team. That both includes a
  • 6:47 - 6:51
    lot of community and a lot of the folks
    sponsored by Automattic to work on that.
  • 6:51 - 6:56
    And I'd say that's what 2022 - the thing
    that's most relevant for this audience
  • 6:56 - 6:59
    I'm excited about is more Gutenberg in Woo.
  • 6:59 - 7:02
    And we also have the CEO of WooCommerce
    here. Does that sound -
  • 7:02 - 7:08
    Giving me a thumbs up? That sounds good?
    All right. Sounds good.
  • 7:08 - 7:11
    So more Gutenberg? That's kind of
    the answer to everything is more
  • 7:11 - 7:17
    Gutenberg. It's like cowbell. You can
    always have more cowbell.
  • 7:17 - 7:19
    You can always have more Gutenberg.
  • 7:19 - 7:21
    Thank you. Well, that was worth 6000
    miles.
  • 7:30 - 7:36
    Cool. Alright, should we move to an online
    question or - wait, we got one in
  • 7:36 - 7:39
    person. And then next, let's do an
    online one, just to make sure we have
  • 7:39 - 7:40
    everything from those folks.
  • 7:40 - 7:46
    Sweet. So my question is about styles. I
    think, you know, the theme styles and - or
  • 7:46 - 7:50
    variants, I think they were called
    initially, is a very innovative idea that
  • 7:50 - 7:53
    lets people paint their sites. It's
    great for developers, designers, and
  • 7:53 - 7:58
    everyday users. So I understand that. I
    think, what could be interesting, and I
  • 7:58 - 8:01
    wonder if you've thought about this, is
    perhaps there's a Style Directory like
  • 8:01 - 8:06
    we have a Pattern Directory. Is that
    something we're in the thought of?
  • 8:06 - 8:09
    I know that there's a couple other
    concerns, you know, we'd have to have a
  • 8:09 - 8:12
    standardized way that themes are being
    made, which we're moving towards
  • 8:12 - 8:16
    already. So I don't know, I think that's
    an interesting way to empower people to
  • 8:16 - 8:20
    also give back to the Directory or into
    WordPress, just like patterns. Like if
  • 8:20 - 8:24
    you can save a pattern, can you save a style?
    And then anybody can save a style?
  • 8:24 - 8:26
    Is that something on the docket?
  • 8:27 - 8:32
    I'm going to fast-forward a little bit here
    into basically science fiction. But if
  • 8:32 - 8:37
    you could imagine us getting a really
    great repository of truly CC0
  • 8:37 - 8:44
    Creative Commons, zero license stuff,
    around images, fonts, etc. That opens up
  • 8:44 - 8:48
    a lot of possibilities for creating
    essentially GPL compatible styles, like
  • 8:48 - 8:53
    you talked about. If you've ever watched
    or helped a friend set up WordPress, or
  • 8:53 - 8:58
    watched a user test or something, one of
    the most hard - most heartbreaking things
  • 8:58 - 9:04
    is when someone chooses a theme based
    on the image in the demo. And I learned
  • 9:04 - 9:08
    this myself. So in one of the previous
    themes, like Twenty Ten or Twenty Eleven
  • 9:08 - 9:12
    there wasn't a lot of open source licensed
    imagery in the world and so I just took
  • 9:12 - 9:16
    all my photos and GPL-licensed them. So one
    of these old themes - I think it's Twenty Ten
  • 9:16 - 9:23
    there's a picture from Ireland of some
    sheep on a road. And we would literally
  • 9:23 - 9:30
    do user tests where people were like, "I like the
    sheep, so I chose this theme." And it's
  • 9:30 - 9:35
    like, "Yes, I like the sheep too, but you can
    put any image in the world there. It
  • 9:35 - 9:40
    doesn't just have to be a sheep theme."
    It's really, it's a - yeah, you know what
  • 9:40 - 9:46
    I'm talking about. Styles right now are
    tied to themes and it's tied to theme.json
  • 9:46 - 9:53
    And so I think theme.json is - theme
    dot J-S-O-N, which I call JSON. I don't
  • 9:53 - 9:56
    know how you pronounce it, but that's
    how I call it - it's the number one thing. If
  • 9:56 - 10:01
    you're a theme developer or interested in
    developing themes, look up that. Learn as much
  • 10:01 - 10:04
    about theme.json as possible. So
    right now, it's specific to the
  • 10:04 - 10:09
    theme. But over time, particularly for
    things like typography, which is a
  • 10:09 - 10:13
    passion of mine. Actually, my very first
    open source code I ever created,
  • 10:14 - 10:18
    which was a contribution to b2, the
    predecessor to WordPress, was texturize.
  • 10:19 - 10:25
    Which was - I'd learned a ton about
    typography and I wanted all posts to
  • 10:25 - 10:29
    have proper typography. So instead of a
    prime mark in between a word like
  • 10:29 - 10:34
    that's - between the that and the s - I
    wanted to be a proper curly quote. And
  • 10:34 - 10:38
    so this first code I ever contributed to
    open source was texturized. I'm very
  • 10:38 - 10:42
    passionate about this. I would love for
    people to be able to see the incredible
  • 10:42 - 10:46
    transformations that can happen to a
    site through updating the typography
  • 10:46 - 10:50
    and particularly pairings of type where
    you have might have like, a really
  • 10:50 - 10:54
    awesome serif paired with a really
    awesome sans serif for the body text or
  • 10:54 - 10:59
    something like that. And I think how
    themes evolve a little bit - actually
  • 10:59 - 11:06
    I'm not sure entirely how themes evolve but -
    to be honest - but it's pretty
  • 11:06 - 11:11
    exciting that the theme can almost be a
    little bit like - honestly it reminds me of
  • 11:11 - 11:17
    jazz. I grew up playing jazz. It's why
    we name every WordPress release after a
  • 11:17 - 11:23
    jazz musician. Jazz are often based on
    something called standards. So like a
  • 11:23 - 11:28
    good chunk of all popular jazz songs are
    built on rhythm changes, which is a set of
  • 11:28 - 11:32
    chord changes, actually from I think, a
    musical song called "I Got Rhythm."
  • 11:32 - 11:36
    [sings] I got rhythm, I got music.
  • 11:36 - 11:38
    Really cool chord changes there.
    Really awesome bridge.
  • 11:38 - 11:43
    And people have written lots of other songs
    on top of that. What's cool
  • 11:43 - 11:47
    is the chord changes - I think I'm a
    little outside of my realm of expertise
  • 11:47 - 11:51
    here - but the chord changes themselves
    are essentially open source, meaning
  • 11:51 - 11:55
    anyone can use those chord changes. Now
    the melody right on top of it
  • 11:55 - 11:59
    might be proprietary, might belong to a
    specific thing. But that kind of
  • 11:59 - 12:03
    underlying structure is open. And so I
    think themes become that kind of
  • 12:03 - 12:06
    underlying structure. And then what
    people take on top of it - it's the chord
  • 12:06 - 12:10
    changes. And then what people create on
    top of it could be as varied and unique
  • 12:10 - 12:15
    as all the things written, people have
    written on top of the rhythm changes
  • 12:15 - 12:17
    as they're called in jazz
  • 12:17 - 12:25
    which is incredible. Thousands of songs,
    countless millions of, like, performances
  • 12:25 - 12:31
    and solos. So that's my hope for what
    happens with themes. And hopefully, we
  • 12:31 - 12:36
    can get more - like, we don't have a ton of
    CC0 licensed fonts yet. So hopefully,
  • 12:36 - 12:41
    we can develop more and more of that
    content in the Openverse/metaverse
  • 12:41 - 12:45
    that is available to all WordPress
    users. And the cool thing
  • 12:45 - 12:49
    about Openverse, as well, is the API is
    totally open. So that's available to Drupal
  • 12:49 - 12:53
    users, Joomla users, everyone else -
    Wix users, Squarespace users. Anyone
  • 12:53 - 12:58
    who wants to access this content, it is
    something the WordPress community is
  • 12:58 - 13:04
    creating for benefit to the world. So if
    you contribute to that you're
  • 13:04 - 13:10
    essentially contributing to humanity's
    repository of cool open stuff that's
  • 13:10 - 13:14
    available for anyone to use in any way. So
    I'm very excited about what the
  • 13:14 - 13:19
    future of Openverse will be. We have
    the very first - we basically just got the
  • 13:19 - 13:22
    code ported over and the search engine
    ported over, and not even the audio yet,
  • 13:22 - 13:27
    that's coming in January. And I cannot
    believe more in the mission of that.
  • 13:28 - 13:30
    Thank you.
    - Thank you.
  • 13:33 - 13:37
    Cool, and you can line up behind her
    if you also have a question.
  • 13:37 - 13:40
    But come on in. What's your name,
    by the way?
  • 13:40 - 13:41
    Ali.
    - Hi Ali.
  • 13:41 - 13:47
    Hi Matt. So I create a lot of content
    around WordPress for the people who are
  • 13:47 - 13:51
    looking at WordPress in front of them
    for the first time looking to, you know,
  • 13:51 - 13:55
    build something with it having never
    used it before. And I think a lot about
  • 13:55 - 14:01
    the young people who are looking at
    WordPress as a path to something, as a
  • 14:01 - 14:05
    path to improving their life or
    brightening their future whatever that
  • 14:05 - 14:08
    might be. And I know that we have in the
    live stream right now a lot of young
  • 14:08 - 14:15
    people watching, listening, and being inspired
    by this. What advice would you have to
  • 14:15 - 14:22
    those young people who are looking to
    inherit this world that we're leaving
  • 14:22 - 14:29
    them? And what advice can you give
    them as far as using WordPress as a tool
  • 14:29 - 14:34
    to improve what we're leaving them?
    No pressure.
  • 14:36 - 14:38
    That's a cool one.
  • 14:45 - 14:48
    In my life, one of the most influential
    things I ever realized
  • 14:48 - 14:53
    was that everything I was using, every
    piece of technology, every piece
  • 14:53 - 14:59
    of furniture, every chair, everything
    was created by someone who wasn't that
  • 14:59 - 15:05
    much different from me or people I
    knew. And so there's crafts that can be
  • 15:05 - 15:11
    developed when you focus on an area. And
    in fact, with the internet, there's more
  • 15:11 - 15:17
    and more of this through YouTube,
    Wikipedia, online blogs, etc. There's so
  • 15:17 - 15:22
    much you can learn about pretty much any
    area that you're passionate about. And I
  • 15:22 - 15:26
    think, for me, and it might be Steve Jobs or
    someone else who talks about this, but
  • 15:26 - 15:31
    just this idea that the things that I use and
    love are created by people
  • 15:31 - 15:36
    not that much different from me was
    really powerful. And that's part of
  • 15:36 - 15:41
    what got me contributing to open source
    in the beginning. When I was - again, I got
  • 15:41 - 15:49
    started on the forums of b2. So b2 is
    the predecessor to WordPress. It had some
  • 15:49 - 15:53
    forums, probably run by like phpBB or
    something. And I just, at first, I was
  • 15:53 - 15:57
    asking questions and then, later, I saw
    questions I had already asked being
  • 15:57 - 16:01
    asked by other people. And I started
    answering them. I didn't know anything.
  • 16:02 - 16:10
    I couldn't - I cannot overemphasize how
    ignorant I was, as a 17, 18, 19 year old
  • 16:10 - 16:15
    kid in Houston, Texas, who had no formal
    training, no university courses, etc. So
  • 16:16 - 16:23
    I think what's exciting about the
    digital economy is that, in this
  • 16:23 - 16:28
    Openverse that we're trying to create
    together, it doesn't matter who you are,
  • 16:28 - 16:31
    where you're from, or anything like
    that. It matters what you contribute.
  • 16:31 - 16:38
    And learning to contribute has never been
    more accessible and more open source
  • 16:38 - 16:48
    more open. The other advice I'd give is
    that, when you're younger, you have a
  • 16:48 - 16:54
    lot more time than you realize. And to
    try to invest that time - if there's
  • 16:54 - 17:01
    anyone young listening to this - in what
    your passion is, you know. If you
  • 17:01 - 17:06
    feel drawn to a particular area - I was
    actually shocked both in my own
  • 17:06 - 17:12
    experience, and in seeing many other
    successful folks since then, in how
  • 17:13 - 17:22
    being a world expert in XYZ - whatever
    XYZ is - is maybe 100 hours of work in
  • 17:22 - 17:28
    some areas. Maybe 200 hours of work. But
    when you're young, you have a lot more
  • 17:28 - 17:33
    hours than folks who maybe are providing
    for the family or full-time jobs or
  • 17:33 - 17:40
    other things. So really embrace that
    opportunity of both school, education,
  • 17:40 - 17:45
    literature available to you, etc. to try to
    consume and absorb as much of it
  • 17:45 - 17:58
    as possible. I feel so much - one of my only
    regrets as a almost 38 year old is that
  • 17:58 - 18:03
    I didn't pay as much attention when I
    was in school. And I went to all public
  • 18:03 - 18:08
    schools in Houston. But I had some
    amazing teachers, like the text I was
  • 18:08 - 18:16
    given, the literature, etc. was free
    or inexpensive, and was really
  • 18:16 - 18:19
    passion from these teachers of some
    of the best things that humanity has
  • 18:19 - 18:23
    created so far. So check that out. And
    the code equivalent of that is
  • 18:23 - 18:29
    WordPress in a lot of ways. Meaning
    that, again, you can think of the other
  • 18:29 - 18:34
    largest Internet services in the world -
    Amazon, Microsoft, Facebook, etc. You
  • 18:34 - 18:42
    can't go and look at how they work. You
    can't suggest a change to how the Google
  • 18:42 - 18:45
    homepage works or the Facebook
    algorithm or anything like that. Those
  • 18:45 - 18:48
    are all proprietary. With things like
    Wikipedia and WordPress, it's all open
  • 18:48 - 18:55
    source. Which means that you could
    suggest a change of the WP admin
  • 18:55 - 19:01
    homepage, which hundreds of thousands
    of millions of people see and impacts a
  • 19:01 - 19:06
    lot of folks. So open source for me was
    a huge enabler - again, not growing up in
  • 19:06 - 19:10
    the Bay area or the traditional, like,
    Seattle or other traditional
  • 19:10 - 19:16
    centers of technology. It was really
    exciting for me. So I'll start with
  • 19:16 - 19:20
    that. Hopefully, I guess folks and maybe
    younger folks like something to start
  • 19:20 - 19:23
    with. And I saw Josepha raise her hand, so
    maybe you have something to add there.
  • 19:23 - 19:26
    - I do. I also have an additional thing.
    Can I introduce you really quick?
  • 19:26 - 19:33
    - Of course.
    So Josepha is the lead of WordPress.org. So she -
  • 19:39 - 19:44
    she is - all of the cool things we talked
    about around like the Directories, etc.
  • 19:45 - 19:48
    Josepha is in charge of that. So she
    really leads the community development of
  • 19:48 - 19:53
    WordPress.org. Everything around that. So
    thank you, Josepha. And now -
  • 19:54 - 19:58
    And now this. So I think also one of the
    most important things - where am I
  • 19:58 - 20:04
    looking? I'm going to look at you, Matt.
    Also, one really important thing to
  • 20:04 - 20:07
    remember for people who are getting
    started with WordPress for the first
  • 20:07 - 20:11
    time is that the open source nature of
    it does mean that we also have really
  • 20:11 - 20:17
    active and passive ways to learn some of
    the most vital 21st century skills that
  • 20:17 - 20:21
    the workforce of the future will need.
    We need it now. But not all of us
  • 20:21 - 20:25
    actually are any good at it in the world.
    WordPressers are generally really
  • 20:25 - 20:27
    really good at it. And there's a
    reason for it. It's because we do it
  • 20:27 - 20:33
    every day. And so like that, in the
    immediate - in my immediate advice that I
  • 20:33 - 20:36
    can give to people, that is the number
    one thing. Like, observe the way that
  • 20:36 - 20:41
    this works, because it's going to be
    relevant from here until they're done
  • 20:41 - 20:42
    wanting to work.
  • 20:44 - 20:49
    Anything else in the audience? Because
    we have an unusual audience here.
  • 20:49 - 20:51
    Here we go. Do you mind introducing
    yourself really quick?
  • 20:51 - 20:56
    I'm Michelle Frechette and I'm with Stellar WP,
    but I also do a whole bunch
  • 20:56 - 21:03
    of other stuff in the community, which
    is fun. So my question is actually off of those
  • 21:03 - 21:07
    two responses as well. We have a ton
    of education out there, right? So
  • 21:07 - 21:12
    whether it's through Learn WordPress,
    whether it's people on YouTube, all these
  • 21:12 - 21:16
    opportunities to learn about it. What
    are we doing to bring the next
  • 21:16 - 21:21
    generation in to help continue to grow?
    I'm watching the age of people I see at
  • 21:21 - 21:25
    WordPress continue to grow, but not a
    ton of people coming in with us?
  • 21:26 - 21:29
    I don't know, I'm looking around. This is
    a very youthful group.
  • 21:30 - 21:34
    Well, I'm one of the older here. I admit
    that. But what are we doing to bring -
  • 21:34 - 21:39
    I mean, I tweeted last week. Olivia
    Bisset - she's in middle school - had a
  • 21:39 - 21:44
    hackathon. I think I tagged you in my
    tweet. And she herself, with her sister
  • 21:44 - 21:49
    put on a huge hackathon of all middle
    schoolers, but that's unusual. So what
  • 21:49 - 21:53
    are we doing to make sure that the next
    generation of kids is going to want to
  • 21:53 - 21:55
    contribute the way that the people in
    this room do?
  • 21:55 - 22:00
    You stole my answer because I was going
    to talk about David and Olivia Bisset.
  • 22:02 - 22:10
    David Bisset, one of the most prolific
    tweeters about WordPress, Hi, David.
  • 22:10 - 22:17
    Will post a lot of gifs from this talk.
    Olivia is his daughter and already
  • 22:17 - 22:21
    started to be really active in the
    WordPress community. I would put that
  • 22:21 - 22:27
    back to everyone in this room and
    everyone listening here as well. You
  • 22:27 - 22:31
    know the old adage, like you teach a
    person to fish or you teach a person -
  • 22:31 - 22:35
    you give a person a fish, you feed him
    for a day. Teach a person to fish, you
  • 22:35 - 22:41
    feed them for their lifetimes. I think
    you just give a person a blog or, even
  • 22:41 - 22:46
    worse, a social media account, you feed
    him for a day. You teach them how to
  • 22:46 - 22:53
    create the web, which is, in many ways,
    in my opinion, the most amazing
  • 22:55 - 23:01
    actualization of shared humanity and
    knowledge. Like how do we create
  • 23:01 - 23:06
    something that lasts beyond our own
    individual lifetimes? It's the web. How
  • 23:06 - 23:10
    do we create something that lasts beyond
    us? A legacy, a true legacy? It's adding
  • 23:10 - 23:14
    to the information that's part of what
    hopefully goes forward for future
  • 23:14 - 23:18
    generations. And then becomes - allows us
    to sort of fast - skip all the
  • 23:18 - 23:23
    mistakes, skip all the learnings to
    what's latest. It's upgrading the clock
  • 23:23 - 23:31
    speed and version of humanity. So for
    anyone who's listening, mentoring and
  • 23:31 - 23:37
    guiding someone younger than yourself
    into participating in the WordPress
  • 23:37 - 23:48
    community is - you get like. What is it?
    A mitzvah? You get like an extra
  • 23:48 - 23:55
    special bonus and, sort of like the
    history of open source in the world, if
  • 23:55 - 23:59
    you bring someone new into it. So I'd
    highly encourage you - and there's so
  • 23:59 - 24:02
    many, if you look at some of the biggest
    contributors to WordPress over the
  • 24:02 - 24:09
    years, a Ryan Boren or a Nacin, etc. part
    of their legacy, beyond just all the code
  • 24:09 - 24:16
    they wrote, is all the people they
    brought in. And the folks who felt like
  • 24:16 - 24:19
    you know, they knew a lot but they
    weren't able to contribute or something.
  • 24:19 - 24:25
    And they said, "No, you got it. You can
    be a Core committer. You can be someone
  • 24:25 - 24:30
    who patches a Core bug. You can be
    someone who translates WordPress
  • 24:30 - 24:33
    into an entirely new language, or
    preserves a language for posterity."
  • 24:33 - 24:40
    Like there's so much you can do using
    WordPress as the launchpad for
  • 24:40 - 24:44
    contributing something positive to
    humanity. And so that is, I think, a real
  • 24:44 - 24:54
    key. So I don't know what is perfect for
    the young people because I'm not one of
  • 24:54 - 25:00
    them anymore. I was when WordPress
    started. But to the extent you have anyone
  • 25:00 - 25:05
    in your lives, both here in the audience
    or broader to the folks watching this
  • 25:06 - 25:12
    that has that desire to have an impact,
    teach them how to be involved with open
  • 25:12 - 25:16
    source and whether that's WordPress or
    some other open source project, I think
  • 25:16 - 25:22
    is the best way to contribute to the
    future of humanity. Thank you.
  • 25:22 - 25:24
    What's that?
    - More KidsCamps?
  • 25:24 - 25:27
    More KidsCamps? Yeah, we do have some
    KidCamps. So very specifically
  • 25:27 - 25:30
    we have KidsCamps at places
    like WordCamp - was it
  • 25:30 - 25:38
    Orlando? Miami, Miami. Yeah. Which David
    Bisset helped organize. Let's all be
  • 25:38 - 25:45
    more like David. If you have kids, why
    aren't they contributing? I wouldn't
  • 25:45 - 25:48
    put that on anyone because kids do
    the opposite of what you ask them. So
  • 25:48 - 25:53
    like, tell them don't contribute to
    WordPress. And then maybe they will.
  • 25:53 - 25:56
    - Take your kids to WordPress day.
    Take your kids to WordPress day actually is
  • 25:56 - 26:01
    an awesome idea.
    - We'll talk later.
  • 26:02 - 26:05
    Cool. Should we do one from online?
  • 26:08 - 26:13
    This is a question from - I lost the name.
    But it was essentially - there were a couple
  • 26:13 - 26:16
    of references to the metaverse in, I
    think, sort of a joking way, but
  • 26:17 - 26:19
    one's on WordPress in virtual reality.
  • 26:21 - 26:23
    WordPress in virtual reality.
  • 26:28 - 26:30
    Let's pass the mic really quick.
    Do you want to say something?
  • 26:30 - 26:34
    Hey, no, we got one. We
    got one. Here you go. Again, the
  • 26:34 - 26:38
    intelligence in this audience is far
    greater than what I have so I want to
  • 26:38 - 26:40
    push this back as much as possible.
    - I just wanted to say
  • 26:40 - 26:44
    WordCamp Boston did do that, if not
    earlier this year - it was last year.
  • 26:44 - 26:46
    They had a virtual reality WordCamp
    - Oh, cool.
  • 26:46 - 26:50
    And it was last year. Thank you. Just yeah.
  • 26:54 - 26:58
    That's a tricky one. I don't know how to
    answer that, to be totally honest.
  • 26:58 - 27:03
    Because like, the internet is virtual
    reality. It's just kind of text-based.
  • 27:03 - 27:08
    And then when you think of other ways of
    interfacing with virtual reality, like
  • 27:08 - 27:15
    VR headsets, or AR, etc. One good thing
    WordPress - WordPress is great at dealing
  • 27:15 - 27:21
    with content. So don't build on top of
    WordPress if you're building like
  • 27:21 - 27:25
    a messaging system or real time game or
    something like that. But if you're
  • 27:25 - 27:30
    making something that essentially
    is people inputting content and
  • 27:30 - 27:34
    outputting that to the world, you should
    probably be building it on WordPress.
  • 27:34 - 27:40
    Whether it's real estate, records, almost
    anything. If it's content going in and out
  • 27:40 - 27:50
    that should be on WordPress. When
    companies - nameless - should talk about
  • 27:50 - 27:56
    this idea of a metaverse, they often
    talk about the interoperability. This
  • 27:56 - 28:02
    idea that contents or items that you
    create in one metaverse is available in
  • 28:02 - 28:09
    all of them. If I imagine my most sci-fi
    thoughts of the future - science fiction
  • 28:11 - 28:18
    it's hard for me to imagine that if humanity
    interacts more and more in a
  • 28:18 - 28:23
    virtual space, that will be controlled
    by one company. I really think it'll
  • 28:23 - 28:29
    look more like the web. Like a place
    where people can register domains. We
  • 28:29 - 28:36
    actually had a joke in here, I forgot to
    tell. So you get it now. What if there
  • 28:36 - 28:43
    were something like a DAO, a distributed
    autonomous organization, that
  • 28:43 - 28:48
    manage a namespace, which you could pay
    to own a part of, and in fact, there's
  • 28:48 - 28:54
    no gas fees for owning part of it.
    The fees are borne by the merchant.
  • 28:54 - 28:58
    That would essentially be buying a
    domain with a credit card on any
  • 28:58 - 29:07
    registrar. So we have things already
    that any person listening to this can
  • 29:07 - 29:13
    have true ownership of, like a domain.
    That's their, like, home on the internet.
  • 29:14 - 29:17
    Internet is the best metaverse we've
    created so far. And part of that's
  • 29:17 - 29:21
    because of the interoperability, and the
    open standards that these things are
  • 29:21 - 29:28
    built on. Patent-free standards as well,
    which I'll emphasize. So to the extent
  • 29:28 - 29:32
    that things will be - I don't know exactly
    what it'll look like. Nothing I've seen
  • 29:32 - 29:37
    so far is that compelling. But to the extent
    that there are fun, content-driven things
  • 29:37 - 29:40
    that are going to be part of the next
    generations of the web? Web3, Web4
  • 29:40 - 29:45
    Web5, Web10 - I expect WordPress
    will be at the center of it.
  • 29:48 - 29:51
    We've got an in-person question. Okay.
    Please introduce yourself.
  • 29:51 - 29:55
    Hi, my name is Bud Kraus. We've never had the
    pleasure to meet but I've heard you
  • 29:55 - 29:57
    speak at several of these.
    - Thank you.
  • 29:57 - 30:00
    And welcome to New York. So all
    I want to know
  • 30:00 - 30:05
    is this is a brand new space. Sorry
    for the people who aren't here, but
  • 30:05 - 30:08
    this is a brand new space. What are you
    going to be doing here? And can we use
  • 30:08 - 30:10
    it too, the people who live in this area?
  • 30:12 - 30:21
    Yeah. So for those who are watching
    online, we're in this cool space in the
  • 30:21 - 30:26
    Noho - which means north of Houston,
    which is a New York incorrect way to
  • 30:26 - 30:37
    pronounce Houston, which is the city
    where I'm from - neighborhood. And it's
  • 30:37 - 30:43
    a cool neighborhood, it's near a lot of
    public transit. And it's a cool space. A
  • 30:43 - 30:47
    company I'm involved in, CEO of
    Automattic, when we purchased the
  • 30:47 - 30:56
    company called Tumblr, got this space.
    And so we have this until 2025. Not
  • 30:56 - 31:00
    coincidentally, a lot more of the people
    working on Tumblr and everything we do
  • 31:00 - 31:03
    have gone more distributed. So there's
    not as many people in this particular
  • 31:03 - 31:08
    space as there used to be. But we tried to
    create this in a way that, much like
  • 31:08 - 31:13
    tonight, could be a place that people use
    for events and other community things.
  • 31:13 - 31:18
    So if you're interested in doing that,
    for something particularly open source
  • 31:18 - 31:22
    driven within the community, we're happy
    to open up this space for anything in
  • 31:22 - 31:27
    the future. And a cool kind of aside is
    all the art in the space, including
  • 31:27 - 31:34
    what's behind me, is from people on
    Tumblr. And so these are all publishers
  • 31:34 - 31:38
    on Tumblr. So all the art that will be
    in the space and eventually - right now
  • 31:38 - 31:42
    we have this wall covered. We're going
    to cover every single wall here. So we
  • 31:42 - 31:47
    have many thousands of square feet to cover
    still. It's all going to be people who
  • 31:47 - 31:50
    publish on WordPress and Tumblr. And in
    the future, Tumblr will be powered by
  • 31:50 - 31:55
    WordPress, so that'll happen. So it'll
    all be the same thing. So it's kind of
  • 31:55 - 31:59
    cool that it'll all be artists that use
    open source publishing to put their
  • 31:59 - 32:06
    content into the Openverse. Alright.
  • 32:07 - 32:12
    Hi, Matt. My name is Anil, and I have a
    curiosity question. You mentioned about
  • 32:12 - 32:18
    Gutenberg Phase Three, which will be
    collaboration. So I'm curious, what can
  • 32:18 - 32:23
    we expect at that phase of
    Gutenberg and collaboration?
  • 32:23 - 32:28
    That's a good question. Because I talked
    twice as long as last year, but maybe
  • 32:28 - 32:35
    missed that particular point. So that
    Collaboration Phase - collaboration?
  • 32:35 - 32:40
    Sorry. Phase Three of Gutenberg is -
    imagine Google Docs. It's probably the
  • 32:40 - 32:43
    best analogy. You know how when you're
    in a Google Doc, when someone
  • 32:43 - 32:46
    else is editing at the same time, you
    see exactly what they're doing, what
  • 32:46 - 32:50
    they're changing. So imagine every single
    thing on WordPress updating in real
  • 32:50 - 32:56
    time, as other people edit it. So
    there's no more version conflicts or
  • 32:56 - 33:01
    anything like that. Literally, WordPress
    represents the kind of real-time source
  • 33:01 - 33:07
    of truth for whatever the content -
    whether it's, again, posts, pages, or
  • 33:07 - 33:13
    other in real-time. And then there's
    both a real-time awareness and workflows
  • 33:13 - 33:18
    around editing that. And so the real-time
    awareness is kind of the easy part
  • 33:18 - 33:21
    actually. It's that part where when
    someone else is editing at the same
  • 33:21 - 33:25
    time, and you're editing it, you see
    what's happening. So there's no
  • 33:25 - 33:29
    conflicts. The workflow is a little
    trickier and that's what I'm
  • 33:29 - 33:35
    actually more excited about working on.
    Where workflow is a word we use for
  • 33:36 - 33:40
    someone edits it, someone approves it,
    someone like - there's different stages of
  • 33:40 - 33:44
    different forms of content. Which is
    also very relevant for translation.
  • 33:46 - 33:50
    Someone writes the content, let's say
    in English, and then maybe it gets
  • 33:50 - 33:55
    translated into another language. I
    realized this personally, to share
  • 33:55 - 34:00
    another weird story like the economics
    thing. On WordPress.com, we use
  • 34:00 - 34:04
    GlotPress and allowed anyone to
    translate any string on WordPress.com.
  • 34:05 - 34:10
    And for a while, on every - I forget which
    language it was, but let's just call it
  • 34:10 - 34:15
    Italian. Instead of saying "Leave a
    Comment" on every Italian blog hosted on
  • 34:15 - 34:22
    WordPress.com, it said "Happy Birthday." So
    someone obviously was like trolling us
  • 34:22 - 34:25
    and said, like, instead of "Leave a
    Comment," it'll say "Happy Birthday."
  • 34:25 - 34:32
    That was actually pretty funny. Whoever
    did that, I'll buy you a beer. But
  • 34:32 - 34:36
    ideally, there would have been a
    workflow or someone else who speaks
  • 34:36 - 34:42
    Italian would have said, "This says 'Happy
    Birthday.'" How do you even say that
  • 34:42 - 34:48
    in Italian? Does anyone know? I know you say
    "Feliz navidad." How do you say like
  • 34:48 - 34:51
    happy birthday and merry Christmas. What
    is happy birthday?
  • 34:51 - 34:54
    - Buon natale? I'm guessing
  • 34:54 - 35:00
    Buon natale? Okay, okay. We'll go there.
    Someone would have seen that and said,
  • 35:00 - 35:04
    "That doesn't mean 'Leave a Comment.'
    And we shouldn't put this on the
  • 35:04 - 35:10
    homepage of every single Italian
    WordPress in the world." So that
  • 35:10 - 35:15
    workflow, I think, is key to Phase Four
    of Gutenberg, which is why it's part of
  • 35:15 - 35:22
    Phase Three. So collaboration is the fun
    part, which will be easy and hard to do
  • 35:22 - 35:25
    at the same time, which is that kind of
    real time co-editing. And there's some
  • 35:25 - 35:29
    cool new standards in browsers that
    allow us to do this in a decentralized
  • 35:29 - 35:33
    way, which I'm really excited about,
    using essentially features built into
  • 35:33 - 35:37
    Chrome and others that allow us to, like
    connect multiple people editing a
  • 35:37 - 35:41
    page or post at the same time, using
    just a browser and open source
  • 35:41 - 35:47
    technology. But the more like, approval,
    etc, is a little bit more of the later
  • 35:47 - 35:53
    Phase Three. So 2023, we'll work on
    that. For now, contribute to Openverse,
  • 35:53 - 36:00
    block patterns, blocks, and block themes.
    That is the key for 2022. Again, if I
  • 36:00 - 36:04
    get on stage next year, and say there's
    30 - we've gone to 40 block themes?
  • 36:05 - 36:12
    Utter failure. Please throw fruit at me
    or something else. I hope that we have
  • 36:12 - 36:18
    300, or ideally 3000, of these block-
    enabled themes and that's - both that's
  • 36:18 - 36:22
    updating existing themes and creating
    new ones to allow people to express their
  • 36:22 - 36:27
    creativity online through the Gutenberg
    editor. Again, right now, if you look at
  • 36:27 - 36:36
    what social networks do, they try to
    really narrow you into a very limited
  • 36:36 - 36:40
    expression of creativity. Why? Because
    they want to serve ads against your
  • 36:40 - 36:44
    profile and what you're creating. They
    want to target you. That's not what
  • 36:44 - 36:48
    we're trying to do with WordPress. So we
    want you to create the most unique, cool
  • 36:48 - 36:53
    stuff online as possible. And blocks
    enable people to do that. And I'm
  • 36:53 - 36:56
    looking forward to more and more of it.
    Does that answer the question?
  • 36:56 - 36:58
    - Yes, thank you.
    Cool, thank you.
  • 37:03 - 37:08
    I saw someone stand up over here. Was that? Okay.
  • 37:11 - 37:15
    You have preempted so many of the
    questions that were submitted.
  • 37:15 - 37:18
    Oh!
    - We're getting you one, though.
  • 37:20 - 37:24
    Somewhat related to what you were just
    speaking to, the question is:
  • 37:24 - 37:28
    soon we'll have blocks that allow you to
    drag everything everywhere. We'll soon
  • 37:28 - 37:32
    have a ton of free images, patterns,
    etc. How are we going to make all that
  • 37:32 - 37:35
    easy to understand and use for users?
  • 37:39 - 37:44
    Yeah, that's our problem. So this is
    what is going to be, I think, the focus
  • 37:44 - 37:55
    of Core WordPress iterations over
    5.9, 6.0, 6.1, and beyond. I'll say it in
  • 37:55 - 37:59
    an abstract sense, which is things like
    user tests. And we do run these and we
  • 37:59 - 38:03
    publish them on our Make WordPress blogs,
    which is where we'll ask someone
  • 38:04 - 38:08
    who has never used WordPress before,
    "Please try it out." And this is something
  • 38:08 - 38:12
    proprietary software companies do all
    the time. But in WordPress, we actually
  • 38:12 - 38:15
    publish these. And so you can see them
    and you can learn from them. And you can
  • 38:15 - 38:19
    see what someone who's never used
    WordPress before has trouble with using
  • 38:19 - 38:23
    and not using. Things that might be very,
    very intuitive to people in this room
  • 38:23 - 38:26
    because we've been using WordPress for
    five or 10 years, might be very
  • 38:26 - 38:30
    challenging to someone entirely new to the
    concepts or the abstractions that we
  • 38:30 - 38:35
    use. The other example, which I hope
    everyone listening to this does - because
  • 38:35 - 38:40
    if you're listening to this, you're like
    a WordPress OG - is helping a friend use
  • 38:40 - 38:46
    WordPress. Right? I hear a laugh in the
    front row. It's like that whole thing
  • 38:46 - 38:52
    like, "Friends don't let friends publish on
    Wix." Take someone who's
  • 38:52 - 38:57
    building a website, you say, "All right,
    I'm going to help you set this up." And
  • 38:57 - 39:00
    while you're doing that, you're probably
    going to learn a lot of things that are
  • 39:00 - 39:06
    tough in WordPress. And hopefully, that
    helps you then contribute a bug or an
  • 39:06 - 39:09
    improvement or something into the Core
    software that makes it easier for
  • 39:09 - 39:14
    everyone else to use. By the way, to the extent
    WordPress - again, that's what's amazing
  • 39:14 - 39:20
    about it to me. When you look at that
    10 times larger than the second in the
  • 39:20 - 39:26
    marketplace - by the way, Shopify is a
    company valued at like $140 billion. How
  • 39:26 - 39:32
    did we do that? How do we be 10 times
    larger than that? It's just people
  • 39:32 - 39:37
    helping other people. I can't put it
    more simply than that. It's how
  • 39:37 - 39:41
    WordPress has had basically no marketing
    dollars through its whole history. Its
  • 39:41 - 39:46
    friends telling friends, like, "Hey, you
    want a website? Let me help you set it
  • 39:46 - 39:52
    up." And then when they have trouble,
    coming back to a cool WordPress Make
  • 39:52 - 39:58
    site or something else and saying, "Hey,
    my friend had trouble with XYZ. Can - I
  • 39:58 - 40:02
    think if we move this around or change
    this widget or make this button more prominent
  • 40:02 - 40:09
    or something like that - that would be
    more intuitive for folks." And the beauty
  • 40:09 - 40:12
    of a project like WordPress, and there's
    a few other open source projects which
  • 40:12 - 40:18
    are similar, is we can simultaneously
    become more intuitive for new users at
  • 40:18 - 40:24
    the same time that we become more
    powerful for power users. That's not
  • 40:24 - 40:29
    easy. I think it can only happen in the
    digital realm. Like an SLR camera with
  • 40:29 - 40:34
    like 80 buttons can't also become
    simultaneously easier for people
  • 40:34 - 40:38
    just taking their first photo. But in the
    digital world, we can do that. And
  • 40:38 - 40:42
    that's actually really, really exciting.
    So that's part of what excites me about
  • 40:42 - 40:46
    WordPress, and I hope is a part of what
    people contribute in the future.
  • 40:54 - 40:59
    Another from the off site questions?
    Let's see. This is from Sarah Gooding.
  • 40:59 - 41:02
    What can WordPress do to protect small
    publishers from the threat of big tech
  • 41:02 - 41:05
    companies' greed and hostility to the
    open web?
  • 41:06 - 41:08
    Oh, my goodness.
  • 41:12 - 41:17
    Big tech companies - was it
    hostility to the open web?
  • 41:17 - 41:18
    Greed and hostility to the open web.
  • 41:18 - 41:21
    Greed and hostility. Oh, my goodness,
    we're dealing with one of the
  • 41:21 - 41:32
    seven deadly sins. First, I'll say that
    there's some giant tech companies whose
  • 41:32 - 41:38
    greed and hostility is somewhat aligned
    with the open web. Meaning that a Google
  • 41:38 - 41:44
    who is indexing the web, is probably more
    aligned with the mission of WordPress
  • 41:45 - 41:50
    than a Facebook, which is trying to
    create an alternative to the open web or
  • 41:50 - 41:56
    other companies. Fill in the blank there.
    So that's something to keep in mind. The
  • 41:56 - 42:05
    number one thing I think we can do is
    create an alternative. So it's easy to
  • 42:05 - 42:10
    forget that someone starting a WordPress
    might not want - the thing they
  • 42:10 - 42:14
    wake up in the morning and think about is
    not like, "I want to make more open source
  • 42:14 - 42:19
    software in the world." They might be
    thinking, "Hey, I want more customers in
  • 42:19 - 42:27
    my restaurant" or "I want more visitors,
    to my salon" or "I want more readers of
  • 42:27 - 42:32
    my novel I'm working on." Like, whatever
    it might be. And the beauty of WordPress
  • 42:32 - 42:36
    is there's so many things you can do on
    top of it. It's that WordPress is a means
  • 42:36 - 42:42
    to an end. And this is our strength and
    our weakness. On third-party measuring
  • 42:42 - 42:48
    services, like a Quantcast or a Nielsen
    or something like that, like
  • 42:48 - 42:53
    a facebook.com or a google.com shows up as
    one domain. And WordPress is, in many
  • 42:53 - 42:57
    ways, like the dark matter of the web
    in that it's the thing that comprises
  • 42:57 - 43:01
    the majority of the universe, but
    doesn't show up on one domain by
  • 43:01 - 43:05
    definition. It's across millions, tens -
    hundreds of millions of different
  • 43:05 - 43:10
    domains and represents each person on
    the domain owning a piece of the web.
  • 43:10 - 43:16
    It belongs to them. Literally domains,
    I'm not - I'm going to pitch domains
  • 43:16 - 43:21
    here. Domains are like the most Web3
    thing you could create. It really
  • 43:21 - 43:30
    belongs to you far more than almost
    anything else. So I think what we can do
  • 43:30 - 43:34
    is - well, I'll tell you the biggest
    thing I've learned, which goes a little
  • 43:34 - 43:39
    back to your question on what is a
    thing to talk about to the youth or
  • 43:39 - 43:45
    people that create things. Early on, I
    was like a Slashdot reading zealot.
  • 43:46 - 43:50
    Meaning like, I was like, "Ah, Microsoft
    and Bill Gates are evil." I had a very
  • 43:50 - 43:55
    like, black and white view of the world
    where I saw open source as good and
  • 43:55 - 44:03
    anything proprietary as bad. And it was
    binary. As you mature, you learn that
  • 44:03 - 44:12
    things are not binary. It's grayscale.
    It's duotone. And there's things that
  • 44:12 - 44:15
    are both simultaneously good and bad,
    and things that exist on the
  • 44:15 - 44:20
    spectrum. And over time, I've chosen to
    devote more of my life to things that I
  • 44:20 - 44:24
    feel like are on the side of the
    spectrum that I want future generations -
  • 44:24 - 44:31
    if I ever have children or grandchildren -
    them to experience of the web. But that
  • 44:31 - 44:42
    the - everything exists on the spectrum. I
    would say that for - pure philosophy does
  • 44:42 - 44:48
    not win. Meaning that for folks, maybe
    like here in the room, or some of the
  • 44:48 - 44:53
    folks watching the livestream, the idea of
    owning your content, owning the software
  • 44:53 - 44:57
    that powers it and everything like that,
    is very compelling. That's probably
  • 44:57 - 45:05
    compelling for like 1 or 2% of humanity.
    We're at the very end of the bell curve
  • 45:05 - 45:10
    of folks who care about those
    things. For the rest, if we want a
  • 45:10 - 45:15
    majority of the web - hopefully, I hope a
    majority, or even like 85 or 90% of the
  • 45:15 - 45:20
    web to be powered by open source. For them,
    we need to create the best user experience.
  • 45:20 - 45:25
    Meaning it needs to be the easiest. It needs
    to be the most intuitive. And it needs to be
  • 45:25 - 45:28
    the thing that gets them towards
    their goals the fastest. For many
  • 45:28 - 45:33
    people, that means WordPress will be
    invisible. And that's okay. We don't
  • 45:33 - 45:37
    need people to even know what WordPress
    is. If they're using WordPress, open
  • 45:37 - 45:42
    source, open API, open data, everything
    to get to where they're going, that is
  • 45:42 - 45:47
    infinitely better than using proprietary
    software to get from A to B. So we need
  • 45:47 - 45:49
    to create as many use cases, as many -
  • 45:51 - 45:57
    work on usability as much as possible to
    create that. So that is my learning. And
  • 45:57 - 46:01
    something I hope we can all work together
    great, because even if someone
  • 46:01 - 46:05
    doesn't realize that using open source
    and making the web more open. If by
  • 46:05 - 46:09
    creating their website, creating their
    restaurant, creating their online service
  • 46:09 - 46:13
    selling something online, they are doing
    so in a way that makes the web even just
  • 46:13 - 46:17
    a smidgen more open. That's cool. That's
    good for humanity. That's the part I
  • 46:17 - 46:21
    want future generations to grow up in.
    Thank you.
  • 46:26 - 46:27
    Okay, we got two minutes.
  • 46:27 - 46:31
    - No, no. Two questions.
    Two questions! Okay.
  • 46:31 - 46:34
    Well, how I talk, that could take 20
    minutes.
  • 46:35 - 46:39
    - Okay, we're down to 20 minutes, so I'm
    giving you five for each.
  • 46:39 - 46:42
    Okay, five minutes per for each question,
    apparently. So.
  • 46:49 - 46:53
    Hi Matt, my name is Aaron Jorbin. I
    probably came the shortest distance
  • 46:53 - 46:59
    because I live, like, three blocks away.
    A couple of times, tonight, you've
  • 46:59 - 47:04
    talked about the GPL, the importance of
    the GPL, the importance of the Four
  • 47:04 - 47:09
    Freedoms of the GPL. Over the last year,
    there's been an effort to dual license
  • 47:09 - 47:16
    the Gutenberg repository, and thus allow
    people to use the WordPress code in ways
  • 47:16 - 47:20
    that would not confer those four
    freedoms on to future users of
  • 47:20 - 47:26
    WordPress. I'm wondering how that lines up
    with your ideas of the four freedoms and
  • 47:26 - 47:33
    why I, as a contributor to WordPress,
    should support my code being re-licensed
  • 47:33 - 47:36
    to remove the four freedoms from future
    users?
  • 47:37 - 47:41
    That's such a good question. So thank
    you, Aaron, for asking that. And also,
  • 47:41 - 47:44
    thank you for being someone else who
    makes me not the only person in the room
  • 47:44 - 47:52
    with a suit. And Aaron looks great. So
    thank you very much for that. Hopefully,
  • 47:52 - 48:00
    we get that on camera. So this is
    interesting. So the GPL was created in
  • 48:00 - 48:07
    the 80s and 90s, and had no concept of,
    essentially, delivery over the web. So
  • 48:07 - 48:13
    the GPL says that if you share something,
    distribute it, which was - historically
  • 48:13 - 48:18
    means, distributed the source code over
    like floppy disk, or CDs, or things like
  • 48:18 - 48:24
    that, you must confer the same freedoms.
    But it didn't count if you were just
  • 48:24 - 48:29
    running your website, which is good and
    bad. It's good in that, like, your
  • 48:29 - 48:36
    password file on your WordPress site is
    not GPL. Right? You don't need to share
  • 48:36 - 48:40
    that to the world. There are licenses
    like the Affero GPL and others that say
  • 48:40 - 48:44
    like you need to share everything, but it
    also creates a loophole. So technically,
  • 48:44 - 48:49
    like WordPress.com doesn't need to share
    any of its code back to the world. It
  • 48:49 - 48:52
    does. Those folks work really hard on
    putting improvements back into
  • 48:52 - 48:57
    WordPress, but they're not required to because
    delivery and distribution through SaaS
  • 48:57 - 49:04
    services does not confer the distribution
    in which the GPL was intended.
  • 49:04 - 49:14
    In practice, we do it but in letter of
    law, it's not required. Mobile apps
  • 49:15 - 49:22
    are whole new worlds. And again, there
    is the ideal thing and there's the
  • 49:22 - 49:30
    pragmatic thing. Practical - ideally, I
    would love to use a mobile device which
  • 49:30 - 49:36
    had firmer hardware, and everything
    involved with it was fully open source.
  • 49:38 - 49:44
    Pragmatically, I need to use an Android
    or iOS device, probably from Apple or
  • 49:44 - 49:51
    Samsung, that works. That has good
    battery life and everything like that.
  • 49:51 - 49:59
    So I've always thought of myself as a
    pragmatic, open source evangelist.
  • 50:00 - 50:06
    Gutenberg. Now how do we bring this to
    Gutenberg? So, Gutenberg is trying to
  • 50:06 - 50:17
    create a pan-CMS or pan-creation
    standard for things like blocks. We
  • 50:17 - 50:22
    think, or I think, that in Gutenberg,
    if we can create a standard interface for
  • 50:22 - 50:27
    things like adding an image or the
    basic things that you do within a block
  • 50:27 - 50:34
    interface, that is good for the web and
    humanity. So part of that is that I
  • 50:34 - 50:38
    would really like to see even
    proprietary systems adopt Gutenberg
  • 50:38 - 50:44
    blocks. I think that would be a win. You
    know, I've made fun of some systems like
  • 50:44 - 50:49
    Wix and Squarespace or Mailchimp or
    others. I think they - I would love
  • 50:49 - 50:54
    I would be thrilled if they all used
    Gutenberg. And Gutenberg is licensed
  • 50:54 - 50:58
    under a way that, if you use it, you
    don't have to make the rest of your
  • 50:58 - 51:04
    software also open source. So the way
    the GPL is, is it's what's called a
  • 51:04 - 51:10
    "viral license." So if you use part of it,
    everything else that links it also has
  • 51:10 - 51:15
    to be open source. Which I like for
    WordPress. I like for everything I do.
  • 51:15 - 51:22
    But I also recognize that maybe, in
    let's say, a mobile app, I might want to
  • 51:22 - 51:26
    have an open source-based editor that
    uses the standards and code of
  • 51:26 - 51:32
    Gutenberg, but the rest of the app might
    not be open source. Maybe it's the
  • 51:32 - 51:36
    Mailchimp app. Let's use Mailchimp as an
    example. I don't have any relation to
  • 51:36 - 51:42
    Mailchimp. So I can talk about that.
    Mailchimp's awesome, very successful, just
  • 51:42 - 51:46
    sold to Intuit for like $10 billion or
    whatever. If you look at what they're
  • 51:46 - 51:50
    doing with their newsletter creator,
    it's blocks. If you look at what they're
  • 51:50 - 51:54
    doing and like - and they don't actually
    have a great mobile app yet, so it'd be
  • 51:54 - 51:58
    cool. So when we took our mobile apps -
    which means developing Gutenberg three
  • 51:58 - 52:03
    times. We have to develop for the web,
    iOS, and Android, which is a lot of
  • 52:03 - 52:11
    work. We are re-licensing the mobile
    versions of Gutenberg as MIT, which
  • 52:11 - 52:15
    means that they can be embedded in
    mobile apps, which are not also open
  • 52:15 - 52:22
    source. This gets into another weird
    thing, which is all mobile apps are
  • 52:22 - 52:29
    mediated by app stores. I don't love
    that, for the record. But it's the
  • 52:29 - 52:32
    reality. You're either going through
    Google or Apple to distribute on an app
  • 52:32 - 52:35
    store to the majority of humans in the
    world.
  • 52:36 - 52:40
    And you have to - when you distribute your
    app, you kind of have to - you don't kind of,
  • 52:40 - 52:46
    you have to agree to their terms of
    services and licenses, which are sort of
  • 52:46 - 52:50
    compatible with open source. Actually,
    WordPress has been a pioneer there.
  • 52:51 - 52:56
    Apple originally did not allow GPL
    applications to be distributed on the
  • 52:56 - 53:03
    Apple Store. And WordPress fought for
    that. And we won it, essentially. And, in
  • 53:03 - 53:09
    fact, Apple has used WordPress code in
    demos. So we kind of got the unofficial
  • 53:09 - 53:13
    blessing that like, our GPL app was okay
    to be on the Apple store. But like,
  • 53:13 - 53:19
    that's still a process, which we fight
    and we go for. Most famously - was it
  • 53:19 - 53:21
    last year that it happened?
  • 53:21 - 53:24
    Either last year or earlier this year,
    it all blends together.
  • 53:24 - 53:29
    It all blends together. I don't know.
    Post-COVID, everything's a real mix.
  • 53:29 - 53:38
    But that Apple issued an incredibly rare apology,
    which Apple never does, where they had
  • 53:38 - 53:44
    sort of told the WordPress open source
    app they needed to do something that
  • 53:44 - 53:49
    seemed a little outside of the
    requirements and the license. And they -
  • 53:50 - 53:56
    someone higher up realized that and
    walked it back. So not often that
  • 53:56 - 54:00
    happens with a $2 trillion company. But
    it happened with WordPress and Apple.
  • 54:00 - 54:05
    And that was exciting. So we will
    continue fighting wherever we can for
  • 54:05 - 54:09
    getting these app stores to open up a
    little bit. We will also be pragmatic in
  • 54:09 - 54:14
    that in reality, everyone who has an
    Apple or iOS device means you go to the
  • 54:14 - 54:20
    app stores to reach them. And I think
    it's actually a flaw of - if we think of why
  • 54:20 - 54:24
    Drupal or Joomla hasn't done as well, I
    think they need apps. And I've
  • 54:24 - 54:28
    encouraged those communities to create
    great apps because they need them.
  • 54:28 - 54:36
    Why we're expanding the license of Gutenberg,
    in particular, to be both GPL and MIT
  • 54:36 - 54:41
    is that I would like WordPress blocks - or
    Gutenberg blocks to become standards
  • 54:41 - 54:47
    that are larger than just WordPress. And
    there is a Drupal version of Gutenberg
  • 54:47 - 54:52
    etc. But I think part of that is that if
    blocks can become standards across every
  • 54:52 - 54:59
    proprietary system. I make fun of Wix - I
    think it's fair, they've earned it. But
  • 54:59 - 55:07
    if they adopted Gutenberg, I would toast
    them and take them out to beers.
  • 55:07 - 55:12
    I think that'd be awesome. Gutenberg is
    something even bigger than WordPress,
  • 55:12 - 55:17
    which is basically saying how do we edit
    and create the web? And can we get as
  • 55:17 - 55:22
    many people - both proprietary and open
    source - collaborating on that as possible?
  • 55:22 - 55:26
    So that is the bet we've made. Maybe it's
    correct, maybe it's incorrect. I hope
  • 55:26 - 55:30
    that you, as a contributor, still are
    excited about being part of Gutenberg,
  • 55:31 - 55:35
    even though it's Gutenberg and MIT,
    which are both open source licenses. But
  • 55:35 - 55:41
    MIT, of course, allows proprietary
    licensing. I understand that. The
  • 55:41 - 55:46
    majority of open source software in the
    world is, well, I think majority is GPL.
  • 55:46 - 55:53
    But there's a big chunk that's non-GPL.
    I think, what we're doing - folks in this
  • 55:53 - 55:57
    room, you and I - are creating more that
    open source stuff. And if proprietary people
  • 55:57 - 56:01
    use it along the way to creating more open
    source, I think that's great and okay.
  • 56:01 - 56:04
    Thank you.
    - And thank you for wearing a suit.
  • 56:04 - 56:06
    And thank you for coming tonight.
  • 56:10 - 56:16
    Someone asked me earlier why I wear a
    suit. And it's actually - one of my
  • 56:16 - 56:22
    favorite folks is Frank Sinatra. And he
    talked about - someone asked why they
  • 56:22 - 56:27
    wore a tux every night to perform. And
    he said to the other band members, he
  • 56:27 - 56:32
    said, "Well, if we were performing for
    the king or queen, what would we wear?
  • 56:33 - 56:37
    We'd dress up. We'd wear a tux to perform
    for them." And he said, "Well, every
  • 56:37 - 56:42
    single night that this band performs,
    there might be someone in the audience
  • 56:42 - 56:46
    who saved up two months to be there, or
    a waitress or someone like that, who
  • 56:46 - 56:50
    really worked to be there. And so, guess
    what? We're gonna dress up for them and
  • 56:50 - 56:56
    perform for them like they are the King or
    Queen of England." Royalty. Every person
  • 56:56 - 56:58
    in the audience is royalty. So that's
    why I wear a suit every year. If you're
  • 56:58 - 57:05
    wondering. This is like the only suit I wear
    during the year, but I wear it because I
  • 57:05 - 57:10
    consider every member of the WordPress
    community to be royalty. And I dress up for
  • 57:10 - 57:12
    y'all. So thank you.
  • 57:17 - 57:20
    Alright, this is the last question.
    I'm so excited.
  • 57:20 - 57:21
    Bring us home.
  • 57:21 - 57:23
    I think it's a short question. Hopefully
    it wasn't already asked.
  • 57:23 - 57:24
    Can you introduce yourself?
  • 57:24 - 57:30
    Hi, I'm Rachel Winchester. Most people
    know me as Win. I'm here for representing
  • 57:30 - 57:36
    DigitalCube. And I'm just curious if
    the topic of internet art has made it on
  • 57:36 - 57:38
    your radar. And if it's something of
    interest to you.
  • 57:39 - 57:41
    Tell me more about internet art.
    How do you define it?
  • 57:41 - 57:46
    Well, internet art is browser art or web-based
    art. But it's art that uses the Internet
  • 57:46 - 57:52
    as a medium. So it works with WordPress,
    because WordPress is that paintbrush.
  • 57:52 - 57:53
    Hmm.
  • 57:53 - 57:57
    I will also call out that you have an amazing
    Issey Miyake purse, who's one of my
  • 57:57 - 58:04
    favorite designers of all time. Thank
    you for bringing that to the microphone
  • 58:04 - 58:11
    as well. What do you think about the
    Openverse and internet art? Like this idea
  • 58:11 - 58:14
    that people could maybe even contribute
    internet art to the Openverse?
  • 58:14 - 58:19
    Oh, I love the idea of making publicly accessible
    images more accessible.
  • 58:19 - 58:20
    I love that idea.
  • 58:22 - 58:30
    That this is - it's an interesting
    tension, right? Because artists create
  • 58:30 - 58:37
    things, and they want to earn a living
    from the things they create. And people
  • 58:37 - 58:42
    create things and want to contribute it
    to the commons of humanity. That becomes
  • 58:42 - 58:46
    part of what we remix, part of what we
    build on, part of the foundation of what
  • 58:46 - 58:50
    creates the next generations, next
    versions of what happens. And in
  • 58:50 - 58:55
    copyright law, which I would say is
    popularly epitomized - since in United
  • 58:55 - 59:00
    States copyright law, you have an
    ability to do that. You know, rest in
  • 59:00 - 59:05
    peace for Joe Ablow. Like, would talk
    about his 3% rule where he would take an
  • 59:05 - 59:12
    existing thing, modify 3%, and create
    something new. Incredible, right? One of
  • 59:12 - 59:17
    the great artists of our generations, in
    so many ways, that affected popular
  • 59:17 - 59:23
    culture, that affected art, that affected so
    many things through that taking something
  • 59:23 - 59:28
    that exists and modifying it. So I don't
    know. I think that's the epitome
  • 59:28 - 59:34
    of open source. I would say that
    WordPress' limitation is, before, that
  • 59:34 - 59:38
    was basically all in the code and
    language realm. It was all about the
  • 59:38 - 59:42
    plugins, the themes - a little bit of
    design, and the translations that were
  • 59:42 - 59:47
    open source. If you had to define what's
    next for us, it's expanding through the
  • 59:47 - 59:52
    Openverse, through things that are
    more content-driven: images, video,
  • 59:52 - 59:59
    audio, art. I'm a photographer. My
    username is Photomatt. So I consider
  • 59:59 - 60:06
    photographs to be art and I hope to put
    more and more of the art I create and
  • 60:06 - 60:11
    hopefully others into that commons, so
    that is the basis for what generations
  • 60:11 - 60:17
    create in the future. So, thank you so
    much. I appreciate the question.
  • 60:22 - 60:26
    And with that, I think we might be -
    I mean, Josepha's coming up.
  • 60:26 - 60:28
    I've got two notes for everyone,
    because I would, naturally.
  • 60:28 - 60:30
    Number one, there were a lot of questions
  • 60:30 - 60:34
    that were asked beforehand and
    also in the livestream chat that we
  • 60:34 - 60:38
    did not get to. But just like last year,
    we will have a blog post up where we can
  • 60:38 - 60:43
    get those answered for you all. Don't
    worry. And my final, final thing, let's
  • 60:43 - 60:47
    have a round of applause for the folks
    who put this event together and for our
  • 60:47 - 60:48
    excellent slide makers.
Title:
2022 Q&A - Caption/Subtitle File
Video Language:
English
Duration:
01:00:53

English subtitles

Revisions