Including People (Ruby on Ales 2016)

Including People (Ruby on Ales 2016)

This talk is about the twin open source project goals of, on the one hand, increasing participation and contribution to an open source project, and on the other hand including everyone while eliminating discrimination and harassment (whether deliberate or accidental). I'll talk about different approaches to reducing discrimination, including better documentation, better development tooling, explicit onboarding process, and codes of conduct. I'll also cover concrete steps that anyone can take to help increase inclusion and participation in the teams, communities, and open source projects that they are involved in.

4c3ed917e59156a36212d48155831482?s=128

André Arko

March 31, 2016
Tweet

Transcript

  1. Including people

  2. Including people

  3. Including people !"#$%&

  4. André Arko @indirect

  5. None
  6. The Ruby Way therubyway.io

  7. None
  8. stickers!

  9. None
  10. stickers!

  11. wait, why is a white dude talking about diversity and

    inclusion
  12. including people in projects & communities

  13. experiences and suggestions some

  14. “diversity” let’s talk about

  15. how to start increasing inclusion in tech: s/diversity/inclusion/g — @rockbot

  16. diversity is being asked to sit inclusivity is being asked

    your opinion at the table — @taylor_atx
  17. bias & exclusion we have a problem

  18. is a lie told by meritocracy rich white men

  19. leads straight to the pipeline a sewage plant

  20. the economic argument for inclusion is diversionary bullshit

  21. including people is an attitude and a philosophy of interaction

  22. projects need to include their teams

  23. projects need to include contributors

  24. projects need to include users

  25. users pay more attention than you think they do

  26. code of conduct makes it clear your project will not

    tolerate harassment
  27. documentation first point of contact with your project for most

    people
  28. write tutorials topic guides an API reference troubleshooting docs

  29. write tutorials topic guides an API reference troubleshooting docs

  30. accept issue reports gracefully

  31. listen and speak respectfully

  32. contributors are like users, but more helpful

  33. ask for help people like helping

  34. write docs just for potential or current contributors

  35. pull requests are just issues with work done for you

  36. your team is people

  37. respect and empathy

  38. are why you’re here respect & empathy

  39. are all that matters. respect & empathy

  40. I want to hear from you @indirect andre@arko.net