Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Maintaining a big open source project: lessons ...

Maintaining a big open source project: lessons learned

About a year ago, I started to maintain Devise - one of the most popular Ruby Gems available. I had no knowledge of the code and a little experience with open source from a side project I developed myself.

Obviously, this was a very challenging task and I made a lot of mistakes in the process. The good thing is I learned a lot too.

In this talk, I will share with you some of the lessons I learned that I think can be valuable not only for open source but for our day-to-day work too.

Leonardo Tegon

May 02, 2019

Transcript

130 slides
  1. The future of the Ruby community is brilliant but it

    depends on us — Rafael França
  2. TRIAGE The process of examining problems in order to decide

    which ones are the most serious and must be dealt with first
  3. Include a title and a clear description, as much relevant

    information as possible and either a test case or a sample Rails app that replicates the issue — Devise's contribution guide
  4. Avoid opening new issues to ask questions[...]. Please go through

    the project wiki, documentation and source code first, or try to ask your question on Stack Overflow. — Devise's contribution guide
  5. Once we read a piece of code for the very

    first time, we’re immersed in a long learning curve and a continuous cycle of questionings, doubts, and insights. — Rondy Sousa
  6. IMAGE CREDITS •Helena Lopes: https://unsplash.com/photos/1m2LQEonm2A •Pawel Janiak: https://unsplash.com/photos/WtRuYJ2EPMA •Alejandro Escamilla:

    https://unsplash.com/photos/BbQLHCpVUqA •Sharon McCutcheon: https://unsplash.com/photos/8lnbXtxFGZw •Alexis Brown: https://unsplash.com/photos/-Xv7k95vOFA •Angelina Kichukova: https://unsplash.com/photos/AjaOjlImLjM •GIFs: https://giphy.com/brooklynninenine

More Decks by Leonardo Tegon

Other Decks in Programming