Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
@nayafia How to be a Good Open Source Citizen @nayafia for Devmonth
@nayafia
@nayafia RubyGems.org
@nayafia Hi everyone, a full post-mortem is coming, but here's what happened from my perspective. I got mentioned on twitt...
@nayafia Nick. I don’t support today's PoC, I don't, really. But I told you. Twice in a week. I feel deeply sad now. --bla...
@nayafia RubyGems.org
@nayafia Ruby Together http://rubytogether.org
@nayafia Ruby Together http://rubytogether.org (you should totally sponsor!)
@nayafia You do not code in a black box
@nayafia How to be a good citizen?
@nayafia As a user
@nayafia Say thank you <3
@nayafia Don’t complain needlessly in public
@nayafia Open an issue or fix it yourself, if you’re able
@nayafia Use appropriate channels to log issues
@nayafia We want to avoid this outcome
@nayafia As a contributor
@nayafia “Every person who...comment[s] on an issue or submit[s] code is a member of a project’s community. Just being abl...
@nayafia (psst- how do I find projects to contribute to?)
@nayafia Start with projects you use
@nayafia Find nice people and communities :>
@nayafia Look for issues tagged for first timers
@nayafia Assume you don’t know anything
@nayafia Read the docs before you ask for things
@nayafia Baby steps are ok
@nayafia Make contributions as clear and simple as possible
@nayafia Don’t contact maintainers privately(unless security-related or they ask)
@nayafia As a maintainer
@nayafia Make sure your project has these three things:
@nayafia LICENSE.MD
@nayafia Pick a license http://choosealicense.com
@nayafia README.MD
@nayafia CONTRIBUTING.MD
@nayafia It’s not all about you
@nayafia Optimize for a good first experience
@nayafia Make it easy for others to participate
@nayafia Call out bad behavior
@nayafia Questions?
Upcoming SlideShare
Loading in …5
×

How to be a Good Open Source Citizen (Devmonth Talk)

2,286 views

Published on

Some best practices for encouraging a healthy, sustainable open source environment, whether you're a casual user, contributor or maintaining your own project. From a Devmonth talk in Toronto, April 15 2016.

ADDITIONAL READING
All the content in here comes from watching and learning from others. These links are great additional reading on this topic, and I recommend following all of these authors' work.

[1] http://writing.jan.io/2015/11/20/sustainable-open-source.html
[2] https://medium.com/the-javascript-collection/healthy-open-source-967fa8be7951
[3] https://medium.com/code-zen/how-to-maintain-a-successful-open-source-project-aaa2a5437d3a#.6t77ivt8w
[4] http://docs.writethedocs.org/writing/beginners-guide-to-docs/
[5] http://www.kennethreitz.org/essays/be-cordial-or-be-on-your-way (thanks @the_compiler for the heads up!)

Josh Matthews (@lastontheboat) also mentioned OpenHatch and Issuehub.io as great resources for contributing to open source. Thanks Josh!

Thanks to André Arko for sharing the story of RubyGems.org with me. If you're a Ruby developer or company, Ruby Together (http://rubytogether.org) is a great community model for supporting Ruby infrastructure.

FOOTNOTES

Slides 4 and 5: https://news.ycombinator.com/item?id=5139583
Slide 12: https://twitter.com/jedwatson/status/679878484634644482
Slide 14: https://github.com/audreyr/cookiecutter/issues/651
Slide 15: https://m.reddit.com/r/Clojure/comments/2u8tqp/psa_repl_by_default_opens_port_the_world_no/
Slide 18: https://medium.com/the-javascript-collection/healthy-open-source-967fa8be7951
Slide 20: https://github.com/gruntjs/grunt/issues/1403
Slide 24: http://docs.python-requests.org/en/latest/index.html
Slide 25: https://github.com/bower/bower/pull/2071
Slide 26: https://github.com/fabric/fabric/issues/1409
Slide 27: https://twitter.com/mperham/status/717092048902303744
Slide 34: Quote from Dan Katz http://www.scientific-computing.com/news/news_story.php?news_id=2759
Slide 35: https://github.com/plataformatec/simple_form
Slide 36: hood.ie/contribute
Slide 37: https://twitter.com/mikeal/status/713393409474465792/photo/1

Published in: Software
no profile picture user

  • Be the first to comment

Show More

How to be a Good Open Source Citizen (Devmonth Talk)

  1. 1. @nayafia How to be a Good Open Source Citizen @nayafia for Devmonth
  2. 2. @nayafia
  3. 3. @nayafia RubyGems.org
  4. 4. @nayafia Hi everyone, a full post-mortem is coming, but here's what happened from my perspective. I got mentioned on twitter about this thread while I was on the bus. I asked @evanphx to put the site into maintenance mode immediately. Just a general PSA, please, if you find an issue like this, be nice. Tell the maintainers privately. Don't post to Reddit, HN, or a public Gist. RubyGems.org is completely volunteer run. No one gets paid to work on it. Thanks for your patience everyone. -- @qrush (HN)
  5. 5. @nayafia Nick. I don’t support today's PoC, I don't, really. But I told you. Twice in a week. I feel deeply sad now. --blambeau (HN) Yes, and thanks for telling us. Really, we should have disabled gem pushes immediately. Hindsight is 20/20, and I'm not sure why I didn't think of doing so earlier. The pain of not being able to push gems would have forced us to fix it. I'm sorry about this. I don't know what else to say. I wish we didn't have to deal with this kind of problem in the Ruby community. --qrush (HN)
  6. 6. @nayafia RubyGems.org
  7. 7. @nayafia Ruby Together http://rubytogether.org
  8. 8. @nayafia Ruby Together http://rubytogether.org (you should totally sponsor!)
  9. 9. @nayafia You do not code in a black box
  10. 10. @nayafia How to be a good citizen?
  11. 11. @nayafia As a user
  12. 12. @nayafia Say thank you <3
  13. 13. @nayafia Don’t complain needlessly in public
  14. 14. @nayafia Open an issue or fix it yourself, if you’re able
  15. 15. @nayafia Use appropriate channels to log issues
  16. 16. @nayafia We want to avoid this outcome
  17. 17. @nayafia As a contributor
  18. 18. @nayafia “Every person who...comment[s] on an issue or submit[s] code is a member of a project’s community. Just being able to see them means that they have crossed the line from being a user to being a contributor.” Node.js contributor definition
  19. 19. @nayafia (psst- how do I find projects to contribute to?)
  20. 20. @nayafia Start with projects you use
  21. 21. @nayafia Find nice people and communities :>
  22. 22. @nayafia Look for issues tagged for first timers
  23. 23. @nayafia Assume you don’t know anything
  24. 24. @nayafia Read the docs before you ask for things
  25. 25. @nayafia Baby steps are ok
  26. 26. @nayafia Make contributions as clear and simple as possible
  27. 27. @nayafia Don’t contact maintainers privately(unless security-related or they ask)
  28. 28. @nayafia As a maintainer
  29. 29. @nayafia Make sure your project has these three things:
  30. 30. @nayafia LICENSE.MD
  31. 31. @nayafia Pick a license http://choosealicense.com
  32. 32. @nayafia README.MD
  33. 33. @nayafia CONTRIBUTING.MD
  34. 34. @nayafia It’s not all about you
  35. 35. @nayafia Optimize for a good first experience
  36. 36. @nayafia Make it easy for others to participate
  37. 37. @nayafia Call out bad behavior
  38. 38. @nayafia Questions?

×