The next generation of contributors is not on IRC
Broberg, Matthew
There is some combination of a turf war and a diaspora happening in the open source communities I participate in. There are synchronous and async channels galore. Every one of them has fans and haters with firmly held opinions on how it's the best or worst thing in the world. Let's take a step back and take a look at the landscape together. What are our communities searching for when they hop into communication channels? How do we meet new members where they are comfortable in order to be more welcoming? As a self-defined GitHub generation of open source enthusiast, I'd like to start a conversation from my personal experience and then jump into research on the options available to us today. I hope we can leave with a view of the world spanning across channels with a focus on our contributors. Topics to be discussed: -Defining new contributors - where are they coming from and why -Empathize with an inexperienced contributor trying to jump right in -Introduce the concept of "a third place" -The challenges of synchronous communication (IRC, Slack, Gitter, others) -Options to focus on asynchronous channels (Email, Discourse, others) -Understanding when you need which -A pitch for why IRC could be great with Matrix.org (Riot.im) -Bringing it back to the new contributor with specific examples -An optimistic conclusion of our collective efforts to improve
 Good morning. Good morning. So yeah, I'm excited to talk to you about the next generation of contribution. It's a little tongue-in-cheek title, hopefully, to get your attention and wake you up this morning on a bright Sunday after some lovely lambic beers all weekend. For those of you who would prefer to follow along if it's easier for you to read on a local tablet or device, I've uploaded these slides on speaker deck slash mbbroberg. Also tweeted it out, so I'll give you a second to find that if you need to. But yeah, while I give that introduction, hi. I'm Matt. I'm a full-time technical editor for opensource.com. We're a really small team that produce a lot of content. I'd love for all of you to consider being authors. If you are at this event, you absolutely have an open source story to share. I can tell you more about that. I also want to give a plug to Brandeis University in collaboration with the Open Source Institute who is running a really interesting master's course on the business of open source. I'm taking it right now and learning a ton about all the things I don't know about open source that a lot of this community, I believe, does. So just to level set with you how I'm walking into this, I'm assuming you are a seasoned open source participant while I am of the GitHub generation of open source. Tell you more of what that means. You could possibly, maybe not, recite the SFF for freedoms off the top of your head. Anyone willing to do that right now? Okay, never mind. Well, I recently learned that OSI and FSF are different. I kind of definitely conflated them more than I'd like to admit. You think you've had a contribute before Git. I think that Git is basically Latin in technology. It's the only thing. It's the language of Franca. So anything before that didn't exist. We're all just oral tradition. You're probably active on IRC. I'm active everywhere but IRC. And lastly, you care about your community as do I. I think if we can all create communities where we care about each other and people feel welcome, we'll be on the same page. But I just figured I'd level set with you also. You knew where I was coming from. Because I'm going to just jump right in and say I don't get IRC. When I was, every time I try to log into it, I end up getting into a bit of a tit for tat with name serve. I'm not quite sure who I'm talking to. I'm not logged into the right place. I feel a little like a wizard, which is kind of cool because I'm a little behind on my CIS admin skills these days, but ultimately I end up seeing a stream of offensive spam and I'm confused as to what channel I'm in and what's going on. And that has led in the communities that participated in where IRC is a default channel. I'm always told to go check the manual, the friendly manual that will explain in great detail how to use the tooling more appropriately. But I've always left this with the sense that I don't get it and I feel kind of ashamed about it. I've got a degree in computer science, been in the tech industry for 10 years after four years of IT work beforehand. And I don't say that to brag. It's actually out of embarrassment that like, oh, how can this technology continue to elude me on a day-to-day basis when I have this foundation behind me? But I think it comes from where what my point of origin was that like, for me, open source started the day I made a GitHub user and a user account and logged in to do something. And I wanted to participate for the first time. I was very excited, pretty nervous about it. And I was using Homebrew on Mac for those that know the package manager. And I opened my very first issue only eight years ago with a bunch of junk about why the package wasn't working for me and me being confused about it. And to my absolute surprise and delight, immediately I hear from these people who are really big names in that community in my sense. They actually told me I didn't install Git correctly on Mac. It was a totally trivial issue. No one made me feel stupid at all, though. They immediately pointed me towards helpful documentation. And I felt like I had done something. Like somebody else has definitely felt that silly going into the Homebrew community. And when they look through issues, they will find that path, ideally get to the same positive conclusion and see the welcoming people along the way. And I love that experience, and it really set me up for the success as I slowly iterated towards an open source community and an open source career focus. Because my pathway is all through proprietary. I started with a proprietary hardware vendor. I found communities that are surrounding proprietary technology that live on a proprietary platform of Twitter. And I eventually joined a proprietary code sharing site and found that to be really open source and fun to me. And I got into open core startups. That is a different conversation. We can talk about whether that works or doesn't and the many ways in which it doesn't. And so on and so forth. Now I'm very much centered around open source communities as a focus of my career. I've got the joy of working at opensource.com to get those stories out further and to coach people through that experience. And I continue to learn about why we obsess about licenses by coming to FOSM and by taking courses like I am. But my pathway is not the same as I know many others have gone through. That started with IRC just being a logical simple thing. But for me it's still this. Even though I understand where it comes from and I understand that had its place in time I feel as if it's not as inviting as that incredible GitHub issue that didn't shame me or make me feel stupid. Ultimately whether that's the sign of my posture syndrome or not is between me and my therapist. But as somebody who's as I like to say on the easy setting of contribution in this world a concept taken from straight white male the lowest difficulty setting there is by John here. I understand I have already a bunch of easy ways in which I can be involved and not feel too ashamed of things when they don't go well. That said if I can feel that awkward I can definitely imagine other people who have a more difficult path towards open source who don't want to be as out there will have more of a challenge. Also I want to talk about this because I'm doing as they continue to read a lot more about the inclusivity and diversity challenges in the technology space and try to inform myself while I don't feel ever informed enough to give a full lecture on it I do know I need to start making changes in my own behavior in order to improve this for those that are going to be coming forward now that are in their teens and their 20s and their 30s or are people that are pivoting from other parts and other industries and want to participate. I do a lot of mentoring on the side for people who are confused as to how they can get involved in technology and consistently ask the same question of where do I get involved what do I do how do I do this open source thing that all these companies are looking to hire for and I can't in good conscience say jump on IRC and see how to get involved it's confusing it and it ultimately could make some people feel like they shouldn't be pivoting into technology that they shouldn't be there and quite honestly it's not where their community is the one that they're going to pursue that they're going to feel welcome in. So I think about how we can start to change that and one of the talks that really influenced me recently is by KK creator of Jenkins he had an incredible talk at Monctober Fest about the that underrepresented people are underestimated but he also brought up this amazing concept thank you for Margaret for tweeting it so I could quote it about the curb cutting principle that if you think about cutting the curb so that people in wheelchairs can go up it it actually helps a number of other people along the way it helps people with strollers or with heavy luggage bags or anyone with any form of walking disability people who have sight difficulties by creating an easier on ramp for a specific target people you have a halo effect you end up positively impacting all these other people and I think about what we're doing as community leaders to do that for our early onboarding for people who maybe don't it can't just quite get up that ledge right away how do we make it easy from the beginning we may have a greater impact than we even realize. So to put it in some context I understand when IRC came out and became the de facto standard it's because there's a lot of empty space around it was IRC or nothing to communicate I guess telnetting and reading each other's things is something that I've read about as well but I'll just put that aside I don't know it very well but if we fast forward to today the stats I've been able to find is that IRC is hovering around 400,000 active users in the last year or so and we look at some of the other synchronous communication channels that people are talking about we've got Microsoft teams as much as people have to use that for work and don't necessarily love it there's 13 million people on that Slack people love it open source communities hate it 12 million users Riot.i am very impressive that they've grown to well over 11 million users Google chat it's like slowly waning in the background but at 4 million and that's just synchronous communication channels and that's just recently we zoom out even further and think about like the ways in which we interact with communities in the technology space that's an interesting noise I'm gonna keep talking while somebody figures that out so if we think about where communities are talking across the industry you've got Twitter which is my default place to come conversate with community members at 126 million users Telegram is way more massive than I ever realized at 200 million and a lot more open source communities are talking there Discord is humongous Reddit is a complete beast when we think about it is that getting pretty distracting true all right jazz hands for a moment and I'll just leave this fear curiosity not that one don't don't I touch the cables that's exciting the electricity is strange everybody yeah yeah I know I definitely at Fossum that does feel appropriate to video guy that was amazing cool okay so there is a lot more competition there's a lot more places people are conversing about open source than ever before and that that can be quite it's quite exciting but it's also it starts to make that little dot of IRC in the middle look maybe less to be centric even though it's center of the picture it's definitely not the dominant place people are talking now oh man I'm gonna like so just a quick side-by-side by no means inclusive of everything that's important to setting up a healthy community a healthy place for people to converse we think about just the sign-up experience the mobile access the inboard on the in-app onboarding of users accessibility options just comparing IRC to yes the hated but often used slack it starts to look like okay I can understand why people aren't jumping on the platform that's existed for the longest there are other options that are definitely maturing but the default option is shifting and I'd like us all to shift with it in quite honestly one of the more important parts is why are we using synchronous communication I am not always on and I doubt you want to be too it's rarely the right place to start so I want to take a take a moment and talk about why I mean just to list five I think we can go through a hundred each one of us has at least one that it requires that always on participation there's this expectation that it sets a default of immediacy there's no continuity of knowledge when you use synchronous communication if I answer a question today three days later yes the same one you get the same question it's often not a place that is building the type of community that we're trying to foster or maybe it is but it's not alone there are other pieces to the puzzle so I'm gonna pivot to talking about community channels and my theory of operation it's a model that's worked for me all models are wrong some are more helpful than others this one is mine well this one actually isn't to start this is somebody else's so in the great good place there's this wonderful concept of your third place where like traditionally your first place being home where you have a certain sense of identity and purpose and meaning your second place being your work which is in our culture is just as dominant if not the dominant place that you live in and there is this magical third place that we're all searching for it's a place where we feel comfortable and feel connected it's where you relax in public encounter familiar faces and make new acquaintances take a moment it think of some community you participate in and doesn't it check all those boxes right away that sense of feeling comfortable and connected to other people there are a bunch of other reasons that it's interesting it's a great theory of operation and I think we're all building third places as we build open source communities and places where our communities interact so to take that in mind I kind of break it into this quadrant that works for me where I think about the synchronous communication which I don't think is the greatest default but it is fantastic for casual and high throughput conversations it's the place of banter where you start to build some sort of connection while asynchronous is really the definitive record of what is the right answer and what is the wrong answer we all end up making these static web pages for things like this there are a bunch of other tools that are useful there's also the power and importance of face to face connection many of us flew drive took a train to be here to make face to face connections with each other because no matter how much we work fully remotely no matter how much we connect with each other as much as I love that over the internet experience we still need this there's something special about this this space lastly I think it's important to think intentionally about your news channel like how are you feeding information and distributing that context to people that care about what you're doing it's cathedral in the bizarre like that you need someplace where I'm being regularly updated with information so that I know I'm making an impact on what I'm doing so what are some default ones synchronous we've talked about asynchronous you know Google groups that's the logo for it that no one knows about there's GitHub is actually pretty decent at asynchronous communication people kind of bend the way you use issues to me be more about collaboration discourse is absolutely fantastic whether you like the creator or not it's a really powerful conversation and threading platform that's open source and you can deploy yourself or use their service stack overflows another form of it and they have their ability to branch off and use your own face to face we all go to them we're at a conference right now user groups and local meetups are important news for better or worse Twitter is where a lot of us hang out it's certainly what been my my choice and this where I know a lot of you from but then there are infinite number of newsletters and other places where we get our news so to see this in practice I just want to give a couple examples some Mozilla recently did a huge renovation of how they communicate internally and externally with their community they landed on riot which I think is really telling that it's a maturing technology it's it's a there's great research if you look up Mozilla's synchronous communication conversation why they chose riot they also want to discourse for their asynchronous so if you join the Mozilla community they have a whole platform you can jump on they have incredible MOSFest and then their Mozilla blog is really really detailed they are always pushing information out and I think it's so interesting they do a great job of having syndicated channels so they push it out to Twitter they push it out to their newsletter subscribers it's like a really tight way of staying connected to this broad and diverse open source community if we look at go the go programming language for instance they've defaulted to Slack there are many many thousands of people talking about go on Slack on a regular basis they use Google groups quite a bit as well as GitHub GitHub issues to communicate with each other for asynchronous there's a ton there's go for con which is the unofficial official place to be it's where people go year round and go meetups are all over the world and then they have the go blog but what's interesting about them they have more of an unofficial presence on Twitter and email and newsletters they have great podcasts and newsletters to distribute it out go times one from change log that's not an official part of the go language but it is an unofficial place that the community circles last but not least let's talk about Kubernetes because everybody else is they are also on Slack and it's really interesting default channel is more GitHub it's a lot GitHub centric while then the newsletter excuse me the discussion lists are a little bit of a back channel while the face to face is really interesting they do so many videos online so they're using Zoom and they're using YouTube to extend that face to face it doesn't quite substitute the in person because that community is getting so big they've added this virtual element as well I think video chats can be really powerful in that way in these distributed communities in their news is just as deep just as distributed people filling in the gaps that they don't but the official channel is always their blog so if you're looking for some same defaults if you're building a community and you find this framework kind of useful I'd say if you're starting from scratch I'd really recommend not going with synchronous from the start and trying to build a place where you answer questions for people and you can create some dialogue amongst the frequent visitors start to get that sense of belonging building and then once people really start to know each other you and you need that side channel you need that conversation you can do that through synchronous but wait until the time zones aren't a factor and that you have a sense of culture already discourse is a great asynchronous communication channel I'm really enjoying using it highly customizable it's really easy relatively easy to run on your own or they have a very reasonable cost structure if you want to pay for it if you're looking to do face to face from the start look at Kubernetes way in which they do the community meetups they're really interesting ways to get people connected was on one recently with 40 people from around the world we're all talking about the bugs that they had squashed that week and ways in which they made contributor experience a little easier I can't talk about many communities that have that level of scale and that number of people that during the day are jumping in and talking to each other and not all of them were paid to do it there's a lot of volunteers a lot of people who are trying to grow their career and the news whether you love it or not the centralization of Twitter is really effective I look forward to understanding mastodon a little bit more to see if that is a collaborative place but I think it's going to be an and not an or and then newsletters are really powerful it's a great place to be if you're interested in running your own website having a blog that then syndicates to those is really effective so that all matters because contribution matters so just to pivot back into the conversation of what are we all trying to do we're trying to build communications of practice because the actual footage of people trying to recruit contributors is like a hungry hungry hippo's game no idea if that reference works internationally but I love it anyway it's a great game just to look at one of the hundreds of sites that try to say good first contributors first contributors that get hub.io these are just some of the amazing organizations who are desperate for new contribution to give a shout out exorcism is one of the best place to learn a programming language and is run by brilliant people all of these others are great too but everyone is very interested in getting new contributions so clearly there's a lot of demand which means we need to meet people where their expectations are not ask them to meet meet us where we already are because if we think about the contributor experience early on back in the IRC only days like almost everyone who is contributing or who is talking about what they're doing was also contributing to something because it was one of the same you had to have that level of skill but now it's kind of shifted that the contributors is a very small peak and the potential contributor field and if we think about it there's like a little dot that's ready to roll off in either direction of the actual maintainers of the software thank you so I just want to reinforce that communication channels are exceptionally important and they said an expectation and we want that expectation to be something where people feel incredibly welcome and don't feel like they're being told to try harder and maybe one day they'll be worthy of being an open source contributor it's going to be multi-channel it's just that's the new standard that everybody is using multiple channels if you try to break it into this grid I think it gets a little bit more sane so you don't have a half a dozen synchronous communication channels and no place for the right and wrong answers like a discourse but lastly I just want to make a shout out to the idea that any place that is contributing to open source is an open source community so whether they're using Slack or otherwise you may not like that choice but it is not necessarily the wrong choice we can try to grow people towards an all open source community and understand the nuances of it but it's taken me eight years to get there and I'm finally starting to get it and I'd like to grow that way but I don't want to shame or make anyone else feel unwelcome because they're not where I am today so I hope we can all meet people where they are today and help them grow into being open source advocates and understand the nuance of it. I really thank you for your time and I look forward to hearing more of your talks as well. Thanks. That was super easy. Yeah. Hello. So distinction being async and synchronized. What I have experienced is that most time when a community have an asynchronous community is that they demand that people install the app on the phone and use personalization which then become a synchronized communication method anyway and if you don't want to install the app you more or less get frozen out. Okay so I'm hearing that the question is like is notifications in that sense that asynchronous converts into synchronous in most cases. I completely understand what you're saying there. There is a level that all technology these days is trying to steal our attention all the time and trying to get us to turn notifications on and be as real time as possible. I think it's not a requirement. I'm part of about a dozen different discourse services right now and I just kind of schedule out time. Well I turned off notifications and I log into the web apps and go in there on my own time. So I think it does take more mental effort than it should. I don't think it's a necessity to think of it that way and if you think about the experience like let's say the same strategy where like I just logged in three days later and looked for updates but I do that in a synchronous communication channel I've got to scroll back infinitely and try to thread in my head the conversations that happened while in like a discourse or stack overflow experience they're all spread out with Q&As in their own separate categories. So more advocating for that structure as opposed to the unstructured. If your goal is to get to a simple yes no definitive answer if your goal is to get people to banter with each other like choose a synchronous channel that is definitely the place to do it. Leslie, how am I doing on time? You're going to take two more questions. Oh cool. Well you got the mic. Go for it. You didn't mention mailing lists. I did not mention mailing lists. I would highly recommend so I did mention Google lists but I didn't give mailman the respect that deserves I'm on an infinite number I'd prefer not to be quite honestly with all due respect. Discourse has a great built in feature where you can use it like a multi-threaded mailing list. It will so I think it's a one to one replacement with a better user experience for those less familiar with it while also providing a mailman like experience mailing lists. So I'd love for you a disagreement that where we could learn a lot from it but yeah that's my current stance on it especially for the expectations that there are today of just a full-fledged friendly experience I'd say discourse is a better choice to start. I've just seen the hand up there. I don't really want to throw this. Hi. It's just in regards to dealing with actually setting up all these channels and form of communication. As a community manager for example how would you install perhaps unique code of conduct for each of these channels or would it be a blanket all channels how you interact with each other. So like for example if it was the synchronous you would have to perhaps say no spamming no doing X, Y and Z that kind of aspect. Yeah absolutely so I'm hearing the question is that like do you have a per channel code of conduct and per channel documentation or is it centralized. Firm believer you have to have one URL to rule them all. That's kind of a different conversation but like by default like your documentation should lead to one place and give as brief an overview as possible and then link to other things. So I think a default code of conduct for across the spectrum because that's you're all still participating in one community across the channels is really important and then yes there may be some specific nuance like what's our reddit versus how we use discourse and those instructions can be in those different channels. Everybody round of applause for Matthew please.
 Good morning.  Good morning.  So yeah, I'm excited to talk to you about the next generation of contribution.  It's a little tongue-in-cheek title, hopefully, to get your attention and wake you up this  morning on a bright Sunday after some lovely lambic beers all weekend.  For those of you who would prefer to follow along if it's easier for you to read on a  local tablet or device, I've uploaded these slides on speaker deck slash mbbroberg.  Also tweeted it out, so I'll give you a second to find that if you need to.  But yeah, while I give that introduction, hi.  I'm Matt.  I'm a full-time technical editor for opensource.com.  We're a really small team that produce a lot of content.  I'd love for all of you to consider being authors.  If you are at this event, you absolutely have an open source story to share.  I can tell you more about that.  I also want to give a plug to Brandeis University in collaboration with the Open Source Institute  who is running a really interesting master's course on the business of open source.  I'm taking it right now and learning a ton about all the things I don't know about open  source that a lot of this community, I believe, does.  So just to level set with you how I'm walking into this, I'm assuming you are a seasoned  open source participant while I am of the GitHub generation of open source.  Tell you more of what that means.  You could possibly, maybe not, recite the SFF for freedoms off the top of your head.  Anyone willing to do that right now?  Okay, never mind.  Well, I recently learned that OSI and FSF are different.  I kind of definitely conflated them more than I'd like to admit.  You think you've had a contribute before Git.  I think that Git is basically Latin in technology.  It's the only thing.  It's the language of Franca.  So anything before that didn't exist.  We're all just oral tradition.  You're probably active on IRC.  I'm active everywhere but IRC.  And lastly, you care about your community as do I.  I think if we can all create communities where we care about each other and people feel welcome,  we'll be on the same page.  But I just figured I'd level set with you also.  You knew where I was coming from.  Because I'm going to just jump right in and say I don't get IRC.  When I was, every time I try to log into it, I end up getting into a bit of a tit for tat  with name serve.  I'm not quite sure who I'm talking to.  I'm not logged into the right place.  I feel a little like a wizard, which is kind of cool because I'm a little behind on my  CIS admin skills these days, but ultimately I end up seeing a stream of offensive spam  and I'm confused as to what channel I'm in and what's going on.  And that has led in the communities that participated in where IRC is a default channel.  I'm always told to go check the manual, the friendly manual that will explain in great  detail how to use the tooling more appropriately.  But I've always left this with the sense that I don't get it and I feel kind of ashamed  about it.  I've got a degree in computer science, been in the tech industry for 10 years after four  years of IT work beforehand.  And I don't say that to brag.  It's actually out of embarrassment that like, oh, how can this technology continue to elude  me on a day-to-day basis when I have this foundation behind me?  But I think it comes from where what my point of origin was that like, for me, open source  started the day I made a GitHub user and a user account and logged in to do something.  And I wanted to participate for the first time.  I was very excited, pretty nervous about it.  And I was using Homebrew on Mac for those that know the package manager.  And I opened my very first issue only eight years ago with a bunch of junk about why the  package wasn't working for me and me being confused about it.  And to my absolute surprise and delight, immediately I hear from these people who are really big  names in that community in my sense.  They actually told me I didn't install Git correctly on Mac.  It was a totally trivial issue.  No one made me feel stupid at all, though.  They immediately pointed me towards helpful documentation.  And I felt like I had done something.  Like somebody else has definitely felt that silly going into the Homebrew community.  And when they look through issues, they will find that path, ideally get to the same positive  conclusion and see the welcoming people along the way.  And I love that experience, and it really set me up for the success as I slowly iterated  towards an open source community and an open source career focus.  Because my pathway is all through proprietary.  I started with a proprietary hardware vendor.  I found communities that are surrounding proprietary technology that live on a proprietary  platform of Twitter.  And I eventually joined a proprietary code sharing site and found that to be really open  source and fun to me.  And I got into open core startups.  That is a different conversation.  We can talk about whether that works or doesn't and the many ways in which it doesn't.  And so on and so forth.  Now I'm very much centered around open source communities as a focus of my career.  I've got the joy of working at opensource.com to get those stories out further and to coach  people through that experience.  And I continue to learn about why we obsess about licenses by coming to FOSM and by taking  courses like I am.  But my pathway is not the same as I know many others have gone through.  That started with IRC just being a logical simple thing.  But for me it's still this.  Even though I understand where it comes from and I understand that had its place in time  I feel as if it's not as inviting as that incredible GitHub issue that didn't shame  me or make me feel stupid.  Ultimately whether that's the sign of my posture syndrome or not is between me and my  therapist.  But as somebody who's as I like to say on the easy setting of contribution in this world  a concept taken from straight white male the lowest difficulty setting there is by John  here.  I understand I have already a bunch of easy ways in which I can be involved and not feel  too ashamed of things when they don't go well.  That said if I can feel that awkward I can definitely imagine other people who have a  more difficult path towards open source who don't want to be as out there will have more  of a challenge.  Also I want to talk about this because I'm doing as they continue to read a lot more  about the inclusivity and diversity challenges in the technology space and try to inform myself  while I don't feel ever informed enough to give a full lecture on it I do know I need  to start making changes in my own behavior in order to improve this for those that are  going to be coming forward now that are in their teens and their 20s and their 30s or  are people that are pivoting from other parts and other industries and want to participate.  I do a lot of mentoring on the side for people who are confused as to how they can get involved  in technology and consistently ask the same question of where do I get involved what do  I do how do I do this open source thing that all these companies are looking to hire for  and I can't in good conscience say jump on IRC and see how to get involved it's confusing  it and it ultimately could make some people feel like they shouldn't be pivoting into  technology that they shouldn't be there and quite honestly it's not where their community  is the one that they're going to pursue that they're going to feel welcome in.  So I think about how we can start to change that and one of the talks that really influenced  me recently is by KK creator of Jenkins he had an incredible talk at Monctober Fest about  the that underrepresented people are underestimated but he also brought up this amazing concept  thank you for Margaret for tweeting it so I could quote it about the curb cutting principle  that if you think about cutting the curb so that people in wheelchairs can go up it it  actually helps a number of other people along the way it helps people with strollers or with  heavy luggage bags or anyone with any form of walking disability people who have sight  difficulties by creating an easier on ramp for a specific target people you have a halo  effect you end up positively impacting all these other people and I think about what  we're doing as community leaders to do that for our early onboarding for people who maybe  don't it can't just quite get up that ledge right away how do we make it easy from the  beginning we may have a greater impact than we even realize.  So to put it in some context I understand when IRC came out and became the de facto  standard it's because there's a lot of empty space around it was IRC or nothing to communicate  I guess telnetting and reading each other's things is something that I've read about as  well but I'll just put that aside I don't know it very well but if we fast forward to  today the stats I've been able to find is that IRC is hovering around 400,000 active  users in the last year or so and we look at some of the other synchronous communication  channels that people are talking about we've got Microsoft teams as much as people have  to use that for work and don't necessarily love it there's 13 million people on that  Slack people love it open source communities hate it 12 million users Riot.i am very impressive  that they've grown to well over 11 million users Google chat it's like slowly waning  in the background but at 4 million and that's just synchronous communication channels and  that's just recently we zoom out even further and think about like the ways in which we  interact with communities in the technology space that's an interesting noise I'm gonna  keep talking while somebody figures that out so if we think about where communities are  talking across the industry you've got Twitter which is my default place to come conversate  with community members at 126 million users Telegram is way more massive than I ever  realized at 200 million and a lot more open source communities are talking there Discord  is humongous Reddit is a complete beast when we think about it is that getting pretty distracting  true all right jazz hands for a moment and I'll just leave this fear curiosity not that  one don't don't I touch the cables that's exciting  the electricity is strange everybody yeah yeah I know I definitely at Fossum that does  feel appropriate to video guy that was amazing cool okay so there is a lot more competition  there's a lot more places people are conversing about open source than ever before and that  that can be quite it's quite exciting but it's also it starts to make that little dot  of IRC in the middle look maybe less to be centric even though it's center of the picture  it's definitely not the dominant place people are talking now oh man I'm gonna like so just  a quick side-by-side by no means inclusive of everything that's important to setting  up a healthy community a healthy place for people to converse we think about just the  sign-up experience the mobile access the inboard on the in-app onboarding of users accessibility  options just comparing IRC to yes the hated but often used slack it starts to look like  okay I can understand why people aren't jumping on the platform that's existed for the longest  there are other options that are definitely maturing but the default option is shifting  and I'd like us all to shift with it in quite honestly one of the more important parts is  why are we using synchronous communication I am not always on and I doubt you want to  be too it's rarely the right place to start so I want to take a take a moment and talk  about why I mean just to list five I think we can go through a hundred each one of us  has at least one that it requires that always on participation there's this expectation  that it sets a default of immediacy there's no continuity of knowledge when you use synchronous  communication if I answer a question today three days later yes the same one you get  the same question it's often not a place that is building the type of community that  we're trying to foster or maybe it is but it's not alone there are other pieces to  the puzzle so I'm gonna pivot to talking about community channels and my theory of operation  it's a model that's worked for me all models are wrong some are more helpful than others  this one is mine well this one actually isn't to start this is somebody else's so in the  great good place there's this wonderful concept of your third place where like traditionally  your first place being home where you have a certain sense of identity and purpose and  meaning your second place being your work which is in our culture is just as dominant  if not the dominant place that you live in and there is this magical third place that  we're all searching for it's a place where we feel comfortable and feel connected it's  where you relax in public encounter familiar faces and make new acquaintances take a moment  it think of some community you participate in and doesn't it check all those boxes right  away that sense of feeling comfortable and connected to other people there are a bunch  of other reasons that it's interesting it's a great theory of operation and I think we're  all building third places as we build open source communities and places where our communities  interact so to take that in mind I kind of break it into this quadrant that works for  me where I think about the synchronous communication which I don't think is the greatest default  but it is fantastic for casual and high throughput conversations it's the place of banter where  you start to build some sort of connection while asynchronous is really the definitive  record of what is the right answer and what is the wrong answer we all end up making these  static web pages for things like this there are a bunch of other tools that are useful  there's also the power and importance of face to face connection many of us flew drive took  a train to be here to make face to face connections with each other because no matter how much  we work fully remotely no matter how much we connect with each other as much as I love  that over the internet experience we still need this there's something special about  this this space lastly I think it's important to think intentionally about your news channel  like how are you feeding information and distributing that context to people that care about what  you're doing it's cathedral in the bizarre like that you need someplace where I'm being  regularly updated with information so that I know I'm making an impact on what I'm doing  so what are some default ones synchronous we've talked about asynchronous you know Google groups  that's the logo for it that no one knows about there's GitHub is actually pretty decent at  asynchronous communication people kind of bend the way you use issues to me be more about  collaboration discourse is absolutely fantastic whether you like the creator or not it's a  really powerful conversation and threading platform that's open source and you can deploy  yourself or use their service stack overflows another form of it and they have their ability  to branch off and use your own face to face we all go to them we're at a conference right  now user groups and local meetups are important news for better or worse Twitter is where  a lot of us hang out it's certainly what been my my choice and this where I know a lot of  you from but then there are infinite number of newsletters and other places where we get  our news so to see this in practice I just want to give a couple examples some Mozilla  recently did a huge renovation of how they communicate internally and externally with  their community they landed on riot which I think is really telling that it's a maturing  technology it's it's a there's great research if you look up Mozilla's synchronous communication  conversation why they chose riot they also want to discourse for their asynchronous so  if you join the Mozilla community they have a whole platform you can jump on they have  incredible MOSFest and then their Mozilla blog is really really detailed they are always  pushing information out and I think it's so interesting they do a great job of having  syndicated channels so they push it out to Twitter they push it out to their newsletter  subscribers it's like a really tight way of staying connected to this broad and diverse  open source community if we look at go the go programming language for instance they've  defaulted to Slack there are many many thousands of people talking about go on Slack on a regular  basis they use Google groups quite a bit as well as GitHub GitHub issues to communicate  with each other for asynchronous there's a ton there's go for con which is the unofficial  official place to be it's where people go year round and go meetups are all over the  world and then they have the go blog but what's interesting about them they have more of an  unofficial presence on Twitter and email and newsletters they have great podcasts and  newsletters to distribute it out go times one from change log that's not an official  part of the go language but it is an unofficial place that the community circles last but  not least let's talk about Kubernetes because everybody else is they are also on Slack and  it's really interesting default channel is more GitHub it's a lot GitHub centric while  then the newsletter excuse me the discussion lists are a little bit of a back channel while  the face to face is really interesting they do so many videos online so they're using  Zoom and they're using YouTube to extend that face to face it doesn't quite substitute  the in person because that community is getting so big they've added this virtual element  as well I think video chats can be really powerful in that way in these distributed communities  in their news is just as deep just as distributed people filling in the gaps that they don't  but the official channel is always their blog so if you're looking for some same defaults  if you're building a community and you find this framework kind of useful I'd say if  you're starting from scratch I'd really recommend not going with synchronous from the start  and trying to build a place where you answer questions for people and you can create some  dialogue amongst the frequent visitors start to get that sense of belonging building and  then once people really start to know each other you and you need that side channel you  need that conversation you can do that through synchronous but wait until the time zones  aren't a factor and that you have a sense of culture already discourse is a great asynchronous  communication channel I'm really enjoying using it highly customizable it's really easy  relatively easy to run on your own or they have a very reasonable cost structure if you  want to pay for it if you're looking to do face to face from the start look at Kubernetes  way in which they do the community meetups they're really interesting ways to get people  connected was on one recently with 40 people from around the world we're all talking about  the bugs that they had squashed that week and ways in which they made contributor experience  a little easier I can't talk about many communities that have that level of scale and that number  of people that during the day are jumping in and talking to each other and not all of  them were paid to do it there's a lot of volunteers a lot of people who are trying to grow their  career and the news whether you love it or not the centralization of Twitter is really  effective I look forward to understanding mastodon a little bit more to see if that is a collaborative  place but I think it's going to be an and not an or and then newsletters are really powerful  it's a great place to be if you're interested in running your own website having a blog  that then syndicates to those is really effective so that all matters because contribution matters  so just to pivot back into the conversation of what are we all trying to do we're trying  to build communications of practice because the actual footage of people trying to recruit  contributors is like a hungry hungry hippo's game no idea if that reference works internationally  but I love it anyway it's a great game just to look at one of the hundreds of sites that  try to say good first contributors first contributors that get hub.io these are just some of the amazing  organizations who are desperate for new contribution to give a shout out exorcism is one of the  best place to learn a programming language and is run by brilliant people all of these  others are great too but everyone is very interested in getting new contributions so clearly there's  a lot of demand which means we need to meet people where their expectations are not ask  them to meet meet us where we already are because if we think about the contributor experience  early on back in the IRC only days like almost everyone who is contributing or who is talking  about what they're doing was also contributing to something because it was one of the same  you had to have that level of skill but now it's kind of shifted that the contributors  is a very small peak and the potential contributor field and if we think about it there's like  a little dot that's ready to roll off in either direction of the actual maintainers of the  software thank you so I just want to reinforce that communication channels are exceptionally  important and they said an expectation and we want that expectation to be something where  people feel incredibly welcome and don't feel like they're being told to try harder and maybe  one day they'll be worthy of being an open source contributor it's going to be multi-channel  it's just that's the new standard that everybody is using multiple channels if you try to break  it into this grid I think it gets a little bit more sane so you don't have a half a dozen  synchronous communication channels and no place for the right and wrong answers like  a discourse but lastly I just want to make a shout out to the idea that any place that  is contributing to open source is an open source community so whether they're using  Slack or otherwise you may not like that choice but it is not necessarily the wrong choice  we can try to grow people towards an all open source community and understand the nuances  of it but it's taken me eight years to get there and I'm finally starting to get it and  I'd like to grow that way but I don't want to shame or make anyone else feel unwelcome  because they're not where I am today so I hope we can all meet people where they are today  and help them grow into being open source advocates and understand the nuance of it.  I really thank you for your time and I look forward to hearing more of your talks as well.  Thanks.  That was super easy.  Yeah.  Hello.  So distinction being async and synchronized.  What I have experienced is that most time when a community have an asynchronous community  is that they demand that people install the app on the phone and use personalization which  then become a synchronized communication method anyway and if you don't want to install the  app you more or less get frozen out.  Okay so I'm hearing that the question is like is notifications in that sense that asynchronous  converts into synchronous in most cases.  I completely understand what you're saying there.  There is a level that all technology these days is trying to steal our attention all  the time and trying to get us to turn notifications on and be as real time as possible.  I think it's not a requirement.  I'm part of about a dozen different discourse services right now and I just kind of schedule  out time.  Well I turned off notifications and I log into the web apps and go in there on my own  time.  So I think it does take more mental effort than it should.  I don't think it's a necessity to think of it that way and if you think about the experience  like let's say the same strategy where like I just logged in three days later and looked  for updates but I do that in a synchronous communication channel I've got to scroll back  infinitely and try to thread in my head the conversations that happened while in like a  discourse or stack overflow experience they're all spread out with Q&As in their own separate  categories.  So more advocating for that structure as opposed to the unstructured.  If your goal is to get to a simple yes no definitive answer if your goal is to get people  to banter with each other like choose a synchronous channel that is definitely the place to do  it.  Leslie, how am I doing on time?  You're going to take two more questions.  Oh cool.  Well you got the mic.  Go for it.  You didn't mention mailing lists.  I did not mention mailing lists.  I would highly recommend so I did mention Google lists but I didn't give mailman the  respect that deserves I'm on an infinite number I'd prefer not to be quite honestly with all  due respect.  Discourse has a great built in feature where you can use it like a multi-threaded mailing  list.  It will so I think it's a one to one replacement with a better user experience for those less  familiar with it while also providing a mailman like experience mailing lists.  So I'd love for you a disagreement that where we could learn a lot from it but yeah that's  my current stance on it especially for the expectations that there are today of just  a full-fledged friendly experience I'd say discourse is a better choice to start.  I've just seen the hand up there.  I don't really want to throw this.  Hi.  It's just in regards to dealing with actually setting up all these channels and form of  communication.  As a community manager for example how would you install perhaps unique code of conduct  for each of these channels or would it be a blanket all channels how you interact with  each other.  So like for example if it was the synchronous you would have to perhaps say no spamming  no doing X, Y and Z that kind of aspect.  Yeah absolutely so I'm hearing the question is that like do you have a per channel code  of conduct and per channel documentation or is it centralized.  Firm believer you have to have one URL to rule them all.  That's kind of a different conversation but like by default like your documentation should  lead to one place and give as brief an overview as possible and then link to other things.  So I think a default code of conduct for across the spectrum because that's you're all still  participating in one community across the channels is really important and then yes  there may be some specific nuance like what's our reddit versus how we use discourse and  those instructions can be in those different channels.  Everybody round of applause for Matthew please.
nextgencontributors_0_155.png nextgencontributors_156_875.png nextgencontributors_876_1679.png nextgencontributors_1680_3095.png nextgencontributors_3096_3755.png nextgencontributors_3756_4679.png nextgencontributors_4680_5099.png nextgencontributors_5100_5447.png nextgencontributors_5448_6335.png nextgencontributors_6336_7727.png nextgencontributors_7728_8183.png nextgencontributors_8184_9227.png nextgencontributors_9228_10139.png nextgencontributors_10140_10799.png nextgencontributors_10800_11231.png nextgencontributors_11232_12443.png nextgencontributors_12444_12851.png nextgencontributors_12852_13775.png nextgencontributors_13776_16259.png nextgencontributors_16260_16571.png nextgencontributors_16572_17159.png nextgencontributors_17160_18359.png nextgencontributors_18360_19427.png nextgencontributors_19428_20171.png nextgencontributors_20172_20867.png nextgencontributors_20868_22451.png nextgencontributors_22452_23699.png nextgencontributors_23700_27227.png nextgencontributors_27228_29687.png nextgencontributors_29688_29879.png nextgencontributors_29880_29927.png nextgencontributors_29928_29975.png nextgencontributors_29976_30047.png nextgencontributors_30048_30131.png nextgencontributors_30132_30887.png nextgencontributors_30888_31655.png nextgencontributors_31656_32099.png nextgencontributors_32100_32291.png nextgencontributors_32292_32519.png nextgencontributors_32520_33383.png nextgencontributors_33384_39875.png nextgencontributors_39876_39923.png nextgencontributors_39924_40048.png
Good morning. Good morning. So yeah, I'm excited to talk to you about the next generation of contribution. It's a little tongue-in-cheek title, hopefully, to get your attention and wake you up this morning on a bright Sunday after some lovely lambic beers all weekend. For those of you who would prefer to follow along if it's easier for you to read on a local tablet or device, I've uploaded these slides on speaker deck slash mbbroberg. Also tweeted it out, so I'll give you a second to find that if you need to. But yeah, while I give that introduction, hi. I'm Matt. I'm a full-time technical editor for opensource.com. We're a really small team that produce a lot of content. I'd love for all of you to consider being authors. If you are at this event, you absolutely have an open source story to share. I can tell you more about that. I also want to give a plug to Brandeis University in collaboration with the Open Source Institute who is running a really interesting master's course on the business of open source. I'm taking it right now and learning a ton about all the things I don't know about open source that a lot of this community, I believe, does. So just to level set with you how I'm walking into this, I'm assuming you are a seasoned open source participant while I am of the GitHub generation of open source. Tell you more of what that means. You could possibly, maybe not, recite the SFF for freedoms off the top of your head. Anyone willing to do that right now? Okay, never mind. Well, I recently learned that OSI and FSF are different. I kind of definitely conflated them more than I'd like to admit. You think you've had a contribute before Git. I think that Git is basically Latin in technology. It's the only thing. It's the language of Franca. So anything before that didn't exist. We're all just oral tradition. You're probably active on IRC. I'm active everywhere but IRC. And lastly, you care about your community as do I. I think if we can all create communities where we care about each other and people feel welcome, we'll be on the same page. But I just figured I'd level set with you also. You knew where I was coming from. Because I'm going to just jump right in and say I don't get IRC. When I was, every time I try to log into it, I end up getting into a bit of a tit for tat with name serve. I'm not quite sure who I'm talking to. I'm not logged into the right place. I feel a little like a wizard, which is kind of cool because I'm a little behind on my CIS admin skills these days, but ultimately I end up seeing a stream of offensive spam and I'm confused as to what channel I'm in and what's going on. And that has led in the communities that participated in where IRC is a default channel. I'm always told to go check the manual, the friendly manual that will explain in great detail how to use the tooling more appropriately. But I've always left this with the sense that I don't get it and I feel kind of ashamed about it. I've got a degree in computer science, been in the tech industry for 10 years after four years of IT work beforehand. And I don't say that to brag. It's actually out of embarrassment that like, oh, how can this technology continue to elude me on a day-to-day basis when I have this foundation behind me? But I think it comes from where what my point of origin was that like, for me, open source started the day I made a GitHub user and a user account and logged in to do something. And I wanted to participate for the first time. I was very excited, pretty nervous about it. And I was using Homebrew on Mac for those that know the package manager. And I opened my very first issue only eight years ago with a bunch of junk about why the package wasn't working for me and me being confused about it. And to my absolute surprise and delight, immediately I hear from these people who are really big names in that community in my sense. They actually told me I didn't install Git correctly on Mac. It was a totally trivial issue. No one made me feel stupid at all, though. They immediately pointed me towards helpful documentation. And I felt like I had done something. Like somebody else has definitely felt that silly going into the Homebrew community. And when they look through issues, they will find that path, ideally get to the same positive conclusion and see the welcoming people along the way. And I love that experience, and it really set me up for the success as I slowly iterated towards an open source community and an open source career focus. Because my pathway is all through proprietary. I started with a proprietary hardware vendor. I found communities that are surrounding proprietary technology that live on a proprietary platform of Twitter. And I eventually joined a proprietary code sharing site and found that to be really open source and fun to me. And I got into open core startups. That is a different conversation. We can talk about whether that works or doesn't and the many ways in which it doesn't. And so on and so forth. Now I'm very much centered around open source communities as a focus of my career. I've got the joy of working at opensource.com to get those stories out further and to coach people through that experience. And I continue to learn about why we obsess about licenses by coming to FOSM and by taking courses like I am. But my pathway is not the same as I know many others have gone through. That started with IRC just being a logical simple thing. But for me it's still this. Even though I understand where it comes from and I understand that had its place in time I feel as if it's not as inviting as that incredible GitHub issue that didn't shame me or make me feel stupid. Ultimately whether that's the sign of my posture syndrome or not is between me and my therapist. But as somebody who's as I like to say on the easy setting of contribution in this world a concept taken from straight white male the lowest difficulty setting there is by John here. I understand I have already a bunch of easy ways in which I can be involved and not feel too ashamed of things when they don't go well. That said if I can feel that awkward I can definitely imagine other people who have a more difficult path towards open source who don't want to be as out there will have more of a challenge. Also I want to talk about this because I'm doing as they continue to read a lot more about the inclusivity and diversity challenges in the technology space and try to inform myself while I don't feel ever informed enough to give a full lecture on it I do know I need to start making changes in my own behavior in order to improve this for those that are going to be coming forward now that are in their teens and their 20s and their 30s or are people that are pivoting from other parts and other industries and want to participate. I do a lot of mentoring on the side for people who are confused as to how they can get involved in technology and consistently ask the same question of where do I get involved what do I do how do I do this open source thing that all these companies are looking to hire for and I can't in good conscience say jump on IRC and see how to get involved it's confusing it and it ultimately could make some people feel like they shouldn't be pivoting into technology that they shouldn't be there and quite honestly it's not where their community is the one that they're going to pursue that they're going to feel welcome in. So I think about how we can start to change that and one of the talks that really influenced me recently is by KK creator of Jenkins he had an incredible talk at Monctober Fest about the that underrepresented people are underestimated but he also brought up this amazing concept thank you for Margaret for tweeting it so I could quote it about the curb cutting principle that if you think about cutting the curb so that people in wheelchairs can go up it it actually helps a number of other people along the way it helps people with strollers or with heavy luggage bags or anyone with any form of walking disability people who have sight difficulties by creating an easier on ramp for a specific target people you have a halo effect you end up positively impacting all these other people and I think about what we're doing as community leaders to do that for our early onboarding for people who maybe don't it can't just quite get up that ledge right away how do we make it easy from the beginning we may have a greater impact than we even realize. So to put it in some context I understand when IRC came out and became the de facto standard it's because there's a lot of empty space around it was IRC or nothing to communicate I guess telnetting and reading each other's things is something that I've read about as well but I'll just put that aside I don't know it very well but if we fast forward to today the stats I've been able to find is that IRC is hovering around 400,000 active users in the last year or so and we look at some of the other synchronous communication channels that people are talking about we've got Microsoft teams as much as people have to use that for work and don't necessarily love it there's 13 million people on that Slack people love it open source communities hate it 12 million users Riot.i am very impressive that they've grown to well over 11 million users Google chat it's like slowly waning in the background but at 4 million and that's just synchronous communication channels and that's just recently we zoom out even further and think about like the ways in which we interact with communities in the technology space that's an interesting noise I'm gonna keep talking while somebody figures that out so if we think about where communities are talking across the industry you've got Twitter which is my default place to come conversate with community members at 126 million users Telegram is way more massive than I ever realized at 200 million and a lot more open source communities are talking there Discord is humongous Reddit is a complete beast when we think about it is that getting pretty distracting true all right jazz hands for a moment and I'll just leave this fear curiosity not that one don't don't I touch the cables that's exciting the electricity is strange everybody yeah yeah I know I definitely at Fossum that does feel appropriate to video guy that was amazing cool okay so there is a lot more competition there's a lot more places people are conversing about open source than ever before and that that can be quite it's quite exciting but it's also it starts to make that little dot of IRC in the middle look maybe less to be centric even though it's center of the picture it's definitely not the dominant place people are talking now oh man I'm gonna like so just a quick side-by-side by no means inclusive of everything that's important to setting up a healthy community a healthy place for people to converse we think about just the sign-up experience the mobile access the inboard on the in-app onboarding of users accessibility options just comparing IRC to yes the hated but often used slack it starts to look like okay I can understand why people aren't jumping on the platform that's existed for the longest there are other options that are definitely maturing but the default option is shifting and I'd like us all to shift with it in quite honestly one of the more important parts is why are we using synchronous communication I am not always on and I doubt you want to be too it's rarely the right place to start so I want to take a take a moment and talk about why I mean just to list five I think we can go through a hundred each one of us has at least one that it requires that always on participation there's this expectation that it sets a default of immediacy there's no continuity of knowledge when you use synchronous communication if I answer a question today three days later yes the same one you get the same question it's often not a place that is building the type of community that we're trying to foster or maybe it is but it's not alone there are other pieces to the puzzle so I'm gonna pivot to talking about community channels and my theory of operation it's a model that's worked for me all models are wrong some are more helpful than others this one is mine well this one actually isn't to start this is somebody else's so in the great good place there's this wonderful concept of your third place where like traditionally your first place being home where you have a certain sense of identity and purpose and meaning your second place being your work which is in our culture is just as dominant if not the dominant place that you live in and there is this magical third place that we're all searching for it's a place where we feel comfortable and feel connected it's where you relax in public encounter familiar faces and make new acquaintances take a moment it think of some community you participate in and doesn't it check all those boxes right away that sense of feeling comfortable and connected to other people there are a bunch of other reasons that it's interesting it's a great theory of operation and I think we're all building third places as we build open source communities and places where our communities interact so to take that in mind I kind of break it into this quadrant that works for me where I think about the synchronous communication which I don't think is the greatest default but it is fantastic for casual and high throughput conversations it's the place of banter where you start to build some sort of connection while asynchronous is really the definitive record of what is the right answer and what is the wrong answer we all end up making these static web pages for things like this there are a bunch of other tools that are useful there's also the power and importance of face to face connection many of us flew drive took a train to be here to make face to face connections with each other because no matter how much we work fully remotely no matter how much we connect with each other as much as I love that over the internet experience we still need this there's something special about this this space lastly I think it's important to think intentionally about your news channel like how are you feeding information and distributing that context to people that care about what you're doing it's cathedral in the bizarre like that you need someplace where I'm being regularly updated with information so that I know I'm making an impact on what I'm doing so what are some default ones synchronous we've talked about asynchronous you know Google groups that's the logo for it that no one knows about there's GitHub is actually pretty decent at asynchronous communication people kind of bend the way you use issues to me be more about collaboration discourse is absolutely fantastic whether you like the creator or not it's a really powerful conversation and threading platform that's open source and you can deploy yourself or use their service stack overflows another form of it and they have their ability to branch off and use your own face to face we all go to them we're at a conference right now user groups and local meetups are important news for better or worse Twitter is where a lot of us hang out it's certainly what been my my choice and this where I know a lot of you from but then there are infinite number of newsletters and other places where we get our news so to see this in practice I just want to give a couple examples some Mozilla recently did a huge renovation of how they communicate internally and externally with their community they landed on riot which I think is really telling that it's a maturing technology it's it's a there's great research if you look up Mozilla's synchronous communication conversation why they chose riot they also want to discourse for their asynchronous so if you join the Mozilla community they have a whole platform you can jump on they have incredible MOSFest and then their Mozilla blog is really really detailed they are always pushing information out and I think it's so interesting they do a great job of having syndicated channels so they push it out to Twitter they push it out to their newsletter subscribers it's like a really tight way of staying connected to this broad and diverse open source community if we look at go the go programming language for instance they've defaulted to Slack there are many many thousands of people talking about go on Slack on a regular basis they use Google groups quite a bit as well as GitHub GitHub issues to communicate with each other for asynchronous there's a ton there's go for con which is the unofficial official place to be it's where people go year round and go meetups are all over the world and then they have the go blog but what's interesting about them they have more of an unofficial presence on Twitter and email and newsletters they have great podcasts and newsletters to distribute it out go times one from change log that's not an official part of the go language but it is an unofficial place that the community circles last but not least let's talk about Kubernetes because everybody else is they are also on Slack and it's really interesting default channel is more GitHub it's a lot GitHub centric while then the newsletter excuse me the discussion lists are a little bit of a back channel while the face to face is really interesting they do so many videos online so they're using Zoom and they're using YouTube to extend that face to face it doesn't quite substitute the in person because that community is getting so big they've added this virtual element as well I think video chats can be really powerful in that way in these distributed communities in their news is just as deep just as distributed people filling in the gaps that they don't but the official channel is always their blog so if you're looking for some same defaults if you're building a community and you find this framework kind of useful I'd say if you're starting from scratch I'd really recommend not going with synchronous from the start and trying to build a place where you answer questions for people and you can create some dialogue amongst the frequent visitors start to get that sense of belonging building and then once people really start to know each other you and you need that side channel you need that conversation you can do that through synchronous but wait until the time zones aren't a factor and that you have a sense of culture already discourse is a great asynchronous communication channel I'm really enjoying using it highly customizable it's really easy relatively easy to run on your own or they have a very reasonable cost structure if you want to pay for it if you're looking to do face to face from the start look at Kubernetes way in which they do the community meetups they're really interesting ways to get people connected was on one recently with 40 people from around the world we're all talking about the bugs that they had squashed that week and ways in which they made contributor experience a little easier I can't talk about many communities that have that level of scale and that number of people that during the day are jumping in and talking to each other and not all of them were paid to do it there's a lot of volunteers a lot of people who are trying to grow their career and the news whether you love it or not the centralization of Twitter is really effective I look forward to understanding mastodon a little bit more to see if that is a collaborative place but I think it's going to be an and not an or and then newsletters are really powerful it's a great place to be if you're interested in running your own website having a blog that then syndicates to those is really effective so that all matters because contribution matters so just to pivot back into the conversation of what are we all trying to do we're trying to build communications of practice because the actual footage of people trying to recruit contributors is like a hungry hungry hippo's game no idea if that reference works internationally but I love it anyway it's a great game just to look at one of the hundreds of sites that try to say good first contributors first contributors that get hub.io these are just some of the amazing organizations who are desperate for new contribution to give a shout out exorcism is one of the best place to learn a programming language and is run by brilliant people all of these others are great too but everyone is very interested in getting new contributions so clearly there's a lot of demand which means we need to meet people where their expectations are not ask them to meet meet us where we already are because if we think about the contributor experience early on back in the IRC only days like almost everyone who is contributing or who is talking about what they're doing was also contributing to something because it was one of the same you had to have that level of skill but now it's kind of shifted that the contributors is a very small peak and the potential contributor field and if we think about it there's like a little dot that's ready to roll off in either direction of the actual maintainers of the software thank you so I just want to reinforce that communication channels are exceptionally important and they said an expectation and we want that expectation to be something where people feel incredibly welcome and don't feel like they're being told to try harder and maybe one day they'll be worthy of being an open source contributor it's going to be multi-channel it's just that's the new standard that everybody is using multiple channels if you try to break it into this grid I think it gets a little bit more sane so you don't have a half a dozen synchronous communication channels and no place for the right and wrong answers like a discourse but lastly I just want to make a shout out to the idea that any place that is contributing to open source is an open source community so whether they're using Slack or otherwise you may not like that choice but it is not necessarily the wrong choice we can try to grow people towards an all open source community and understand the nuances of it but it's taken me eight years to get there and I'm finally starting to get it and I'd like to grow that way but I don't want to shame or make anyone else feel unwelcome because they're not where I am today so I hope we can all meet people where they are today and help them grow into being open source advocates and understand the nuance of it. I really thank you for your time and I look forward to hearing more of your talks as well. Thanks. That was super easy. Yeah. Hello. So distinction being async and synchronized. What I have experienced is that most time when a community have an asynchronous community is that they demand that people install the app on the phone and use personalization which then become a synchronized communication method anyway and if you don't want to install the app you more or less get frozen out. Okay so I'm hearing that the question is like is notifications in that sense that asynchronous converts into synchronous in most cases. I completely understand what you're saying there. There is a level that all technology these days is trying to steal our attention all the time and trying to get us to turn notifications on and be as real time as possible. I think it's not a requirement. I'm part of about a dozen different discourse services right now and I just kind of schedule out time. Well I turned off notifications and I log into the web apps and go in there on my own time. So I think it does take more mental effort than it should. I don't think it's a necessity to think of it that way and if you think about the experience like let's say the same strategy where like I just logged in three days later and looked for updates but I do that in a synchronous communication channel I've got to scroll back infinitely and try to thread in my head the conversations that happened while in like a discourse or stack overflow experience they're all spread out with Q&As in their own separate categories. So more advocating for that structure as opposed to the unstructured. If your goal is to get to a simple yes no definitive answer if your goal is to get people to banter with each other like choose a synchronous channel that is definitely the place to do it. Leslie, how am I doing on time? You're going to take two more questions. Oh cool. Well you got the mic. Go for it. You didn't mention mailing lists. I did not mention mailing lists. I would highly recommend so I did mention Google lists but I didn't give mailman the respect that deserves I'm on an infinite number I'd prefer not to be quite honestly with all due respect. Discourse has a great built in feature where you can use it like a multi-threaded mailing list. It will so I think it's a one to one replacement with a better user experience for those less familiar with it while also providing a mailman like experience mailing lists. So I'd love for you a disagreement that where we could learn a lot from it but yeah that's my current stance on it especially for the expectations that there are today of just a full-fledged friendly experience I'd say discourse is a better choice to start. I've just seen the hand up there. I don't really want to throw this. Hi. It's just in regards to dealing with actually setting up all these channels and form of communication. As a community manager for example how would you install perhaps unique code of conduct for each of these channels or would it be a blanket all channels how you interact with each other. So like for example if it was the synchronous you would have to perhaps say no spamming no doing X, Y and Z that kind of aspect. Yeah absolutely so I'm hearing the question is that like do you have a per channel code of conduct and per channel documentation or is it centralized. Firm believer you have to have one URL to rule them all. That's kind of a different conversation but like by default like your documentation should lead to one place and give as brief an overview as possible and then link to other things. So I think a default code of conduct for across the spectrum because that's you're all still participating in one community across the channels is really important and then yes there may be some specific nuance like what's our reddit versus how we use discourse and those instructions can be in those different channels. Everybody round of applause for Matthew please.
I am of the GitHub generation of open source. I'm going to just jump right in and say I don't behavior in order to improve this for those that right away how do we make it easy from the year or so and we look at some of the other synchronous communication channels that people think about where communities are talking across lot more open source communities are talking understand why people aren't jumping on the the default option is shifting and I'd like us place to start so I want to take a take a moment of knowledge when you use synchronous great good place there's this wonderful concept third place that we're all searching for it's a community you participate in and doesn't it check our communities interact so to take that in mind cathedral in the bizarre like that you need the world we're all talking about the bugs that going to be an and not an or and then newsletters the conversation of what are we all trying to do is one of the best place to learn a programming experience early on back in the IRC only days contributor it's going to be multi-channel it's just that's the new standard that everybody is am today so I hope we can all meet people where they are today and help them grow into being open distinction being async and synchronized. What I saying there. There is a level that all honestly with all due respect. Discourse has a form of communication. As a community manager for