$30 off During Our Annual Pro Sale. View Details »

From no OSS experience to the core team in 15 minutes a day (RubyConf 2016)

André Arko
November 13, 2016

From no OSS experience to the core team in 15 minutes a day (RubyConf 2016)

Using and contributing to open source has been a cornerstone of the Ruby community for many years. Despite this strong tradition, it’s hard to find anything collecting the likely advantages and costs of working on open source. This talk will introduce open source work, the benefits and costs of doing that work, and then provide a straightforward list of activities that can be done by anyone, no matter their level of experience with programming. Pick a project, schedule at least 15 minutes per day, join the core team. It’s your destiny!

André Arko

November 13, 2016
Tweet

More Decks by André Arko

Other Decks in Technology

Transcript

  1. FROM NO OSS EXPERIENCE
    TO THE CORE TEAM
    IN 15 MINUTES PER DAY

    View Slide

  2. André Arko
    @indirect

    View Slide

  3. View Slide

  4. The Ruby Way
    therubyway.io

    View Slide

  5. View Slide

  6. View Slide

  7. how to start
    contributing to open source

    View Slide

  8. what exactly is
    contributing to open source

    View Slide

  9. you
    are experienced enough

    View Slide

  10. “real programmers”
    do not exist

    View Slide

  11. GitHub is not
    your resume

    View Slide

  12. what are
    your goals?

    View Slide

  13. your time
    is your own

    View Slide

  14. what even is
    contributing

    View Slide

  15. benefits!
    there are some

    View Slide

  16. should you
    do this thing?

    View Slide

  17. can you work
    for free?

    View Slide

  18. making money
    is a valid choice

    View Slide

  19. open source means
    losing control of your work

    View Slide

  20. choose a license
    carefully

    View Slide

  21. we made it!
    here’s the plan

    View Slide

  22. 1. wtf

    View Slide

  23. 2. answer questions

    View Slide

  24. 3. help with issues

    View Slide

  25. 4. reproduce bugs

    View Slide

  26. 5. writing patches

    View Slide

  27. 6. improve everything

    View Slide

  28. 7. you’re doing it!

    View Slide

  29. 8. now you’re in charge

    View Slide

  30. what did we learn?

    View Slide

  31. thanks for listening!
    (also thanks to @ashedryden @mountain_ghosts for writing about
    these topics previously, and @sailorhg for many ideas in this talk)

    View Slide