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.

Transcript

1. Including
   people
   

   View Slide

2. Including
   people
   

   View Slide

3. Including
   people
   !"#$%&
   

   View Slide

4. André Arko
   @indirect
   

   View Slide

5. View Slide

6. The Ruby Way
   therubyway.io
   

   View Slide

7. View Slide

8. stickers!
   

   View Slide

9. View Slide

10. stickers!
    

    View Slide

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

    View Slide

12. including
    people
    in
    projects &
    communities
    

    View Slide

13. experiences
    and
    suggestions
    some
    

    View Slide

14. “diversity”
    let’s talk about
    

    View Slide

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

    View Slide

16. diversity
    is being asked to sit
    inclusivity
    is being asked your
    opinion at the table
    — @taylor_atx
    

    View Slide

17. bias & exclusion
    we have a
    problem
    

    View Slide

18. is a lie told by
    meritocracy
    rich white men
    

    View Slide

19. leads straight to
    the pipeline
    a sewage plant
    

    View Slide

20. the
    economic argument
    for inclusion
    is diversionary
    bullshit
    

    View Slide

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

    View Slide

22. projects
    need to include
    their teams
    

    View Slide

23. projects
    need to include
    contributors
    

    View Slide

24. projects
    need to include
    users
    

    View Slide

25. users
    pay more
    attention than
    you think they do
    

    View Slide

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

    View Slide

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

    View Slide

28. write
    tutorials
    topic guides
    an API reference
    troubleshooting docs
    

    View Slide

29. write
    tutorials
    topic guides
    an API reference
    troubleshooting docs
    

    View Slide

30. accept
    issue reports
    gracefully
    

    View Slide

31. listen
    and speak
    respectfully
    

    View Slide

32. contributors
    are like users,
    but more helpful
    

    View Slide

33. ask for help
    people like helping
    

    View Slide

34. write docs
    just for potential or
    current contributors
    

    View Slide

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

    View Slide

36. your team
    is people
    

    View Slide

37. respect
    and
    empathy
    

    View Slide

38. are why
    you’re here
    respect & empathy
    

    View Slide

39. are all that
    matters.
    respect & empathy
    

    View Slide

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

    View Slide