Feedback on Ruby Hack Challenge #2

[ko1]

Please tell us your feedback about RHC#2.
Your feedback will help next RHC.

• Your activities
• Keep
• Problem
• Try

This time, we held in one day. If you feel lack of time, please write about it.

Japanese feedback is also welcome.

Thanks,
Koichi

[naofumi-fujii]

• Your activities
  • https://bugs.ruby-lang.org/issues/4824
  • https://bugs.ruby-lang.org/issues/14357
• Keep
  • super helpful ruby commiters 🎉
  • learned how ruby commiter walk through the code. 👀
  • wrote patch and comment for issue 4824(thank you Endoh san!!!)
• Problem
  • issues were very hard to solve. (easy ones already fixed 🔧 )
  • very hard to reproduce issue 14357
  • want to know more easier or better debugging way(maybe not exist?)
  • my pc was very slow(should get new one)
  • english 🗣
• Try
  • solve some issues by myself 💪

[aycabta]

• Your activities
  • hacking IRB for replacement lexical analyzer
• Keep
  • understanding IRB source code
  • discussion with Ruby committers
• Problem
  • it's very hard to hack the legacy code
• Try
  • I'll try to move some methods from RubyLex to Irb

[osyo-manga]

• Your activities
  • https://bugs.ruby-lang.org/issues/14417
• Keep
  • Ruby hacking!!
• Problem
  • Room was hot.
  • eigo.
• Try
  • Fix a bug in Ruby.

Thanks for Ruby committers and Ruby Hack Challenge!

[nexl]

• Your activities
  • MRI hacking and exercises
• Keep
  • discussion and feedback from ruby commiters
• Problem
  • hacking ruby interpreter is not easy
• Try
  • know more about ruby and participate in open source

[Hiroshi123]

• Your activities

  • Going through part of provided exercises which I haven't finished by the day.
  • reading RHG debugging ruby source code.

• Keep

  • Having a working chance to be with greatest commiters in ruby ecosystems.
  • It was kind of suprising that how easy source code edition will affect language features, although
    it was not the impression that I got in that day, but the day that I read the tutorial.

• Problem

  • Due to lack of my debug skill and lack of preparation, I lost very good chance to ask decent questions.
  • I might be very nervous to work with good engineers as it Is disturbed autonomic nervous next day.

• Try

• I have no idea I can say I will contribute its ecosystems, but at least could initialise positive impression to step forward to contribution by talking with commiters.

• I need to find my best way to debug considerable size of codes.

[kysnm]

• Your activities
  • https://bugs.ruby-lang.org/issues/14403#note-3
    • but this is already fixed at https://bugs.ruby-lang.org/issues/14273#note-1
  • https://bugs.ruby-lang.org/issues/14398
    • I don't know how to debug with puppet...
  • https://bugs.ruby-lang.org/issues/14106
    • Failed to build a suitable ruby version by my mistakes.
• Keep
  • Ruby Hack Challenge!!
• Problem
  • I did not read related tickets well.
• Try
  • Want to make it smoother to build the ruby binary from source code.