 Thank you so much for accepting to my proposal. I love Singapore. My name is Hiroshi Shibata. Please call me Hiroshi. My GitHub account name is HSBT. I'm Ruby Committer. My mission is improved to experiences of Ruby. So I'm maintaining to our official site named RubyLangorg. I'm working for GMO Peppa Bo in Japan. We provide a lot of web services. Making Ruby is a part of my job. Today, I describe about who I'm making Ruby. Is it Matt? It's no. Matt's main work is making a Ruby. It's competitor or C-Ruby. So Matt is our competitor. And the banned version of C-Ruby. So Matt's committed only one commit last year. It is. Again, who are making Ruby? This other is community. Committee means you and me and the people on this conference and the Ruby's in the world. I'll show my examples. Basically, I use drunk and the head of all branches build. This is example of incompatible changes on Ruby 2.2. Ruby 2.2 returns nil. It isn't assignment same name over default value. This changes break rails. But it already fix rails 4.1 and 4.0 by tender. But it isn't backped to rails 3 bunch. If you still use rails 3, you can use Ruby 2.2. Ruby 2.2 is often broken. I can't recommend it this way. How to contribute to Ruby without using 2.1? First, bug report. I'll show good bug report. Add description of minimum case that defects is happened. Second, try defined version of Ruby. It's really reduce our investigate time. Last, it's most important things. Clash log attaches. Ruby committer easily detects causes of segmentation fault with crash logs. But many of people forgot to attach to this. Next contributor is future request. What are things of good to future request? It is use case. Use case is clearly. Ruby have a lot of users. Why your future makes they are happy? You need to describe it. Second, naming is important things of Ruby. Mats said too. But naming is rejected by Mats. It's same situation with Ruby committer, including Koichi-san and me. Third, secret important things is attaching cause. If you hope to accept your idea, please attach to your implementations. You can submit future request to GitHub with pull request. I and Zack and Nobu are checking GitHub every day. If pull request is only documentation changes, we manage it immediately. But GitHub is a minor platform on Ruby committers. Really minor platform. Especially Mats is only available on our issue trackers. But MLuby uses GitHub. If you have big future requests, you need to make a ticket to red mine. Please make the account our issue tracker and please submit your future requests. Finally, who are making Ruby now? It's you. Please submit bug report and the future request to our issue tracker and GitHub. We welcome all rights. Thanks.