Slide 1

Slide 1 text

The next generation of contributors is not on IRC. https://speakerdeck.com/mbbroberg Matt Broberg @mbbroberg

Slide 2

Slide 2 text

Hi, I’m Matt Technical Editor for Opensource.com at Red Hat Member of OSI, PSF Contributor to Kubernetes, CHAOSS Graduate of OSI-approved Brandeis course on the Business of Open Source @mbbroberg

Slide 3

Slide 3 text

@mbbroberg Where were you When you first chat with an open source community?

Slide 4

Slide 4 text

< empty space > < empty space > < empty space > < empty space > @mbbroberg IRC (circa 1990)

Slide 5

Slide 5 text

Yahoo (18 million in 2005) < empty space > @mbbroberg MSN Messenger (115 million in 2004) IRC (240k in 2005) ICQ (20 million in 2004)

Slide 6

Slide 6 text

< empty space > @mbbroberg IRC ICQ MSN Yahoo < empty space > < empty space >

Slide 7

Slide 7 text

Slack (44 million) Element (Riot.im) (18 million) @mbbroberg IRC Gitter (100k)

Slide 8

Slide 8 text

Telegram (400 million) Twitter (326 million) Reddit (430 million) Slack (44m) G Discord (100 million) GitHub (44m) @mbbroberg Element (18m) irc

Slide 9

Slide 9 text

* Twitter (126 million) Slack (12m) Telegram (200 million) Goo g Discord (250 million) GitHub (40 m) @mbbroberg MSFT (13m) Riot (13m) Facebook / WhatsApp (2.6 billion)

Slide 10

Slide 10 text

@mbbroberg Where were you When you first chat with an open source community?

Slide 11

Slide 11 text

My impression You @mbbroberg

Slide 12

Slide 12 text

My impression You Me @mbbroberg

Slide 13

Slide 13 text

My impression You 1) Seasoned open source participant 2) Can recite the OSD from heart 3) Contributed before git was cool 4) Are still active on IRC 5) Care about this community GitHub generation of open source Recently learned FSF & OSI are different See git as the lingua franca of tech Just joined IRC via Element Care about this community Me @mbbroberg

Slide 14

Slide 14 text

New users and IRC What’s with the wizard-like syntax? Where is my chat history? Why does NAMESERV hate me? What clients consistently work? Why can’t I @ anyone? @mbbroberg

Slide 15

Slide 15 text

The bar is higher than ever Modern sign up experience Mobile access by default In-app onboarding and guide Advanced moderation options Shared discussion history Multi-media support Notifications options IRC | Slack | Element (Riot.im) @mbbroberg

Slide 16

Slide 16 text

IRC continues to shrink from +400,000 in 2004 to < 100,000 in 2020 At a time when open source is more popular than ever

Slide 17

Slide 17 text

But IRC has principles! Point License is (at least) open source Decentralized (Federated) End-to-end encryption

Slide 18

Slide 18 text

But IRC has principles! Point License is (at least) open source Decentralized (Federated) End-to-end encryption

Slide 19

Slide 19 text

The bar is higher than ever Modern sign up experience Mobile access by default In-app onboarding and guide Advanced moderation options Shared discussion history Multi-media support Notifications options IRC | Rocket | Element (Riot.im) @mbbroberg

Slide 20

Slide 20 text

IRC is not the right tool @mbbroberg

Slide 21

Slide 21 text

Choosing community channels @mbbroberg

Slide 22

Slide 22 text

Sync For casual, high throughput discussion Async For a definitive, recorded answer News To stay informed and empowered F2F To build a formidable bond @mbbroberg

Slide 23

Slide 23 text

Sync For casual, high throughput discussion Async For a definitive, recorded answer News To stay informed and empowered F2F To build a formidable bond @mbbroberg

Slide 24

Slide 24 text

Async Sync F2F News User groups & Conferences @mbbroberg

Slide 25

Slide 25 text

Don’t default to synchronous Synchronous chat is rarely the right place for your community (at first) @mbbroberg

Slide 26

Slide 26 text

Don’t default to synchronous 1. Requires always-on participation 2. Difficult to follow multiple discussions 3. Sets expectation of immediacy in response 4. Divides participation by time zone 5. No continuation of knowledge @mbbroberg

Slide 27

Slide 27 text

Don’t default to synchronous If synchronous is the right place for your community... @mbbroberg

Slide 28

Slide 28 text

Advanced Sync Setup @mbbroberg #where-you-prefer-to-be

Slide 29

Slide 29 text

Advanced Sync Setup @mbbroberg Community #contributors #where-you-prefer-to-be Bridges (Element) #maintainers

Slide 30

Slide 30 text

Advanced Sync Setup @mbbroberg Community #contributors #where-you-prefer-to-be #announcements (rename #general) #contributors #maintainers Bridges (Element) #maintainers #announcements Bots #social

Slide 31

Slide 31 text

Advanced Sync Setup @mbbroberg Community #contributors #where-you-prefer-to-be #announcements (rename #general) #contributors #maintainers Bridges (Element) #maintainers #announcements Bots #social Be where future contributors are

Slide 32

Slide 32 text

Because community is not always open ● Proprietary hardware community ● Proprietary virtualization community ● Joining a proprietary code sharing site ● Open source on a proprietary OS ● Open core startups ● Growing communities on GitHub ● Open source communities ● Opensource.com ● A maturing obsession with licenses ● Maintainer and contributor @mbbroberg

Slide 33

Slide 33 text

Communication channels matter They imply who is welcome and who needs to “try harder” to be welcome. @mbbroberg

Slide 34

Slide 34 text

Advanced Sync Setup @mbbroberg Community #contributors #where-you-prefer-to-be #announcements (rename #general) #contributors #maintainers Bridges (Element) #maintainers #announcements Bots (Slack) #social Be multichannel

Slide 35

Slide 35 text

Be inclusive first, educate on open values along the way @mbbroberg

Slide 36

Slide 36 text

Don’t love these types of problems? Recruit contributors that do. @mbbroberg

Slide 37

Slide 37 text

All communities that contribute to open source are open source communities @mbbroberg

Slide 38

Slide 38 text

Thank you And thanks: ◂ To Open Source Initiative! This is such an honor. ◂ To the Mozilla team for inspiring research on this topic. ◂ To the Opensource.com team for their support. If you’re interested in sharing your open source story there, I’m mbbroberg online. ◂ Presentation template by Slidesgo, icons by Flaticon. @mbbroberg

Slide 39

Slide 39 text

1. Daily publication with over 3 million articles read a month 2. Publishing articles on anything with a strong open source story 3. Staff available to coach authors on telling great stories 4. Top articles in Linux, Python, Rust, Kubernetes, and open source news 5. An ever-evolving community of active participants Interested in writing with us? Go to Opensource.com/writers (or at me! @mbbroberg)

Slide 40

Slide 40 text

* Your current users/contributors Potential contributors @mbbroberg

Slide 41

Slide 41 text

* Potential contributors @mbbroberg Maintainers Your current users/contributors

Slide 42

Slide 42 text

Async Sync F2F News MozFest @mbbroberg Mozilla The Mozilla Blog

Slide 43

Slide 43 text

Async Sync F2F News GopherCon & Go Meetups @mbbroberg Go The Go Blog

Slide 44

Slide 44 text

Async Sync F2F News KubeCon & Cloud Native Meetups @mbbroberg Kubernetes The Kubernetes Blog ++

Slide 45

Slide 45 text

Async Sync F2F News & Add-on events @mbbroberg Defaults &

Slide 46

Slide 46 text

Async Sync F2F News All Things Open & Fosdem @mbbroberg Open Defaults &

Slide 47

Slide 47 text

Async Sync F2F News All Things Open & Fosdem @mbbroberg Open Defaults &