 Hello everyone, thanks for being here And we will be talking today about how to develop more welcoming behaviors and environments and situations You can see the slides on the pros version of this talk the longer version because I had to trim it down so much yesterday In github.com slash to test slash talk welcoming people with dashes in the middle This will be all published. I will tell you what did and I will tweet about it, too I will start with two quotes, which thankfully I have heard already in this conference It's good that we are coming to a bit of a convergence of the things we are caring about the first one is from a book that was published 30 years ago almost and It's in the preface. It says the major problems of our of our work are not so much technical as they are human and sociological They developed this idea over the course of that book these two authors were flying to Australia for consulting And they were like we just discovered this and they developed all this content in dust in that flight And we still are getting surprised because we still didn't learn the lesson. Thankfully. We are starting to do that in conferences like this one The other one is from humane development org. We are humans working with humans Developing software for the benefit of humans. So those are two quotes to set the tone of this talk We'll be talking about why should we care about welcoming we'll be talking about Feedback how to give the feedback in a productive way and how to receive it, too We'll be taking talking about onboarding to open source projects We'll be talking about how to work with our flood rains We already know about cognitive biases But I will mention too that I think we don't discuss so often and I will really relate them To our work as contributors and maintainers of open source projects I was going to talk about microaggressions where I removed all that content we don't need to talk it again and Then we'll talk about how to make this expected and normal and common instead of something special that a few people care about So why should we care as professionals? There's a very Concrete reason why we should be caring and it's more different people see more different aspects of the single product We are building Concrete examples examples about this are the glass staircases that we had in the Apple stores No women were there wearing skirts and knowing what problem would arise from glass staircases How did that get through these architects and engineers and our example where they crash them is until 2011 They were not required to have female damage. This was a problem with designing airbites. This was a Quite heavy problem and not so dramatic example is the Apple watch if you have tattoos in your wrist It won't sense that accurately your pulse But there's another more relevant More relevant in my opinion As relevant at least reason why we should care and it's because we are humans and there's morals that we can follow I will quote child by tell the developer and CEO of thought but which I didn't mention yet But but is the company I work for and I thank them for letting me speak here about the things that we consider important He said in a podcast when someone has been discriminated against or is in a minority The status quo is in and on itself wrong We should do more not doing wrong in a state of status quo, which is unfair is not acceptable It's just morally wrong. We should be challenging the things that are making our communities less welcoming and That's a moral reason why we should be caring about diversity not only because we are professionals Trying to build the best product we can So let's talk about feedback Let me go to my notes. There is a lot of feedback everywhere constantly feedback We are not conscious about There's implicit feedback on who speaks up and who stays quiet There is implicit feedback in who is invited to certain threads and discussions who gets mentioned to get Opinions in an open source project What is not sell what is very considered very important? What jokes do we allow to happen in our interfaces and documentation all of that is implicit feedback? And if we become conscious about it, we can make sure that we can keep the humor without offending people I think that's quite important another interesting aspect of feedback is how creative people tend to Identify themselves with the work they produce and so Recently for example, I saw this quote in the slag room of my work We were making fun of legacy code, which was so terrible in our opinion and somebody said instead of laughing about this code why don't we study how they come to be and What do we not like about it and how can we avoid from happening it again in the future if that's what the client wants? This person was conscious and was sharing that consciousness that code is the result of a system Nobody's guilty and we should be talking about it that way so as to not offend the teams working behind of it Pixar has this concept of blessing. They came up with a great flow to discuss creative ideas. They said They're bringing this from improvisation if you do theater, you might recognize this Accept all ideas. Don't reject any idea. Don't use language like yes, but use language like yes, and Only challenge an idea when you have something better to propose You can't say this is not a good idea and just be done with it They said that this been this has been very successful in making people feel comfortable in rather awkward situations And they said that they managed to make this a requirement and a flow that everyone follows Because the leaders in the organization were vocal about following it and were actively disencouraging People not following this flow So the flow was important for them, but the practical Practically to implement it. They say that the leaders doing what they say they wanted to do was key so That's important open source maintainers probably So the feedback is actionable specific it's kind for example if you say something like you always do that thing That's bad for a team That's not none of those things But if you say something like when extra happened you did why what do you think about doing see instead? Then that's all of those things Feedback should be encouraging and should be within the scope of the of skills of the recipient Every one idea that I constantly keep in mind While having any human conversation really not only about feedback and code reviews and in the office is that everywhere? Every person knows something that I don't every person is unique every person has a unique set of experiences and Information and interests that make them particularly interesting to me to learn from so this has been very important for me it's like It's like a long-term vision that allows me to apply many of the little rules that we study Automatically everyone has something new to say to us So that's about feedback. Let's talk about how to onboard people and in our open source projects The first interaction that a user will have with our project is a landing page or a with me Read me documents in github. Those are the landing pages of our project in start up in terms There we should be saying how do we communicate where do we conduct these discussions and how do we contribute? What's our code of conduct and so on and they it should be all verbatim in the with me Or it should be linked to those resources But it should certainly be in that first page so that the new cameras don't get confused a new open source project It's an enormous bag of things which are interrelated like documentation and code and Communication channels and and services like CI and so on and it can feel very daunting for something starting a bootcamp to go into it But if we have this real me document and if we tag our issues Then we are giving them more of a breadcrumbs more of breadcrumbs to follow so that they can Use the skills they have in the best way for that project Mm-hmm Another good thing to do is to give fast code reviews in this comic somebody says to another person How are you doing and their person says well? Let me think how to answer that question and your person is like what's going on? How are you doing? Oh, sorry? I'm fine. I was just like coming up with the best answer The same can happen in pull requests if somebody sends a sizeable pull request We might want to wait until we can give them a thoughtful code review or a thoughtful answer But then that person Mozilla has been conducting experiments if that person has to wait for a week It's highly probable that they won't come back that they will just forget that they won't continue contributing They will feel like we left them without an answer when they were contributing work to our projects So something good to do is to say thank you so much your contribution is great I didn't ask for it and I have it here I will leave you now this one comment and in one week when I have more time I will give you a more proper code review. Thank you again something like that So that we don't leave this out for silence in the middle that can't draw people out Especially people who are new By definition when you're new you have much to learn you don't know how things work and you have lower confidence So if somebody's not answering it might feel that they left you without an answer that they ignored you We don't want to convey that feeling to newcomers Actually, I'm thinking of a robot now That you'd answer automatically in our names. Thank you. I've become back to you in two days. Can you take a note of that place? I like that idea During code reviews try to respond to every comment same thing a PR can have like 50 comments with little questions in each line If you don't respond to one of them It can feel like that try to respond to everything even if it's just a plus one or or I don't agree with that or whatever If you disagree strongly and you feel strongly about something consider giving yourself some time yesterday We heard like that in Twitter. You can actually think and breathe before you write same happens with github Don't you assume people know your context using words like obviously when it's not obvious to you because you're starting is terrible It harms directly your self-confidence Something that should be obvious for everyone. It's not for myself. What's wrong with me? Well, nothing What's wrong is with the language? We shouldn't use those words in places where we expect new cameras New cameras that we don't know their background for And the previous comments on feedback apply as well Another Thing that I'd like to talk about he said took that fat gave in a conference a few years ago He released Twitter Woodstrap a few years ago. He was so happy. He said I created this front-end framework I love it so much. It's my little puppy. I'm proud of it I will publish it and let the world use it and fall in love with it and certainly happened Everyone started using this project and so So this little beautiful puppy growing into an enormous dog that didn't even fit in his apartment And so he was like I have to go for a walk with a dog and I have to feel it But I don't have enough food for it and people are waiting on me for issues and poor requests and so on I just don't have time. I feel so guilty and I'm starting to burn out. I don't know what to do He started a great conversation about guilt and expectations and open source His case is an outlier for for more sane cases I have a little rule that I learned that was useful and we are playing at that but which is having canned responses Let's think let's say that you woke up today Saturday morning Seattle. You get a beautiful morning coffee You're in a good mood. You are well rested. You're coming from the east. So you have extra hours to sleep. That's beautiful somebody Somebody sends a PR an issue to your project, but it's not very well written. It's not clear what you're asking You need more information. It might be a bug in your project. It might be a bug in their system You don't really know it might be a bug in another related project. And so you write down you say, thank you so much for your submission This is useful. Now. We need more information. Can you please give me steps to reproduce them? you link to your bug report needs more info and so this person can follow some steps and You say I need to reproduce to be able to fix it So let's work through it. Give me the version number of the libraries you're using and so on and you're proud of yourself You're like I hit this person so much. I give them such a thoughtful answer How can I beat this person always having a morning's here and coffee after over sleeping and We can't we really can't as humans But we can have little tricks that allow us to behave that way always and even spending less time That answer we save it in a text file somewhere and I get have repo or whatever and then we just copy paste it whenever Somebody sends a bug report with not enough information, which is 99% of the cases We can be answering that way every time Without spending more than a minute and we can do this for every other case that this happens So if the issue is not a bug and so it doesn't belong here But it's that cover flow can be real to say that in just 10 words. So let's let's write two paragraphs Issues to a specific to your app. It's not the library Issues tail and it's up and down we close it. It's an unclear request that I just spoke about all of those can have their own kind responses I've been maintaining a few very popular projects at thought Bob since I started and I wrote the things that I learned in this book Maintaining open source projects. It might be useful for you. It would have been so useful for me two years ago I wish it helped existed before because it didn't say I started working on it It's in better so now it's cheaper and the two part chapter that I need to write will be there by January the winter is a good time to write I'll speak now about how I'm a doing with time. I'm already over time. I won't talk about biases We all will know about that and it's in the internet. I will speak about how to make this Normal how to make this something that we expect and happens every day I recently received a visit from a person who said when you're on stage I pitch the talk to them when you're on stage tell them that the community the tech community is not diverse because it's Because it's it's all right because it should be we're all hypocrites We don't want to change things and it made me think a lot I certainly disagree but it made me think if we all think that way doesn't make sense to work on this Should I be giving the stock should we be worrying or should we accept that we are just a lot humans? But I remembered slavery and I remembered women's suffrage and I remembered same-sex marriage and equal pay and all of this seemed like impossible changes of consciousness society-wide but Work happens and seemingly people changed opinions from one day to the other But it's not opinions that changed people knew that this was wrong what changed I believe is that it became common knowledge that these things were going on a great story to speak about common knowledge Common knowledge is the idea that we know something but we also all know that we all know that something So now it's comfortable to speak about it For example when Lauren yesterday said talking pays good Not only did we already know it was obvious to us that we should be talking pay We now know that we all know that so we can now all go on the 1st of May or tomorrow or whenever Talk about it safely without incurring risk. I have two other examples, but I won't have time to quote them I love this this topic There's a naked emperor example, you might know that story. It's the same thing So common knowledge the idea is that stating something publicly even when it's obvious can change how people think and Behave and what I want us to do is to start talking out these things so openly with conferences like this one So that we share as much as Lauren shared the top pay thing We shared how the microaggressions that we just did to and the gender and race Bias ratios are just wrong and we should be improving them and we should take pride when we improve them and broadcast that So that instead of how poor topics, they are as comfortable as now slavery is slavery seems like something from the past But sometimes it was a staboo as pay. I want to do that I want us to keep calm and have these difficult conversations constantly. Thank you for this conference and thank you for coming