How to improve experiences of Ruby

on YouTube ↗05m

" summary

Lists concrete first steps: start by filing a bug with a minimal reproducible case, note which Ruby versions reproduce it, and attach crash logs or coredumps so maintainers can narrow causes. For feature work, open a ticket with clear use cases and a careful name, and include an implementation patch or docs change. Fixing RubyGems, Rails annoyances, or the website counts too. Use GitHub for small patches and Redmine for larger core proposals.

AI-written summary · about

" chapters (4)

1. 0:00Introduction
2. 0:57Who are making Ruby
3. 2:13How to control Ruby without trunk
4. 3:01Things of good future requests

" related talks

• 50mWriting Solid Ruby CodeJim Weirich · RubyConf 2011
• 08mHow to Begin Developing Ruby CoreHiroshi Shibata · RedDotRubyConf 2016
• 42mDissecting Ruby with RubyRichard Schneeman · Wicked Good Ruby 2013
• 27mget /betterMark Bates · Burlington Ruby Conference 2013
• 30mFrom no OSS experience to the core team in 15 minutes a dayAndre Arko · RubyConf 2016
• 35mYour First Open-Source ContributionRachael Wright Munn · Blue Ridge Ruby 2026
• 33mRaising the BarTyler Hunt · RubyConf 2011
• 34mSource-Diving for Fun and ProfitKevin Kuchta · RubyConf 2019