Summarized using AI

Lightning Talk: How to improve experiences of Ruby

Hiroshi Shibata • June 26, 2014 • Singapore • Lightning Talk

In this lightning talk titled 'How to Improve Experiences of Ruby' presented by Hiroshi Shibata at the Red Dot Ruby Conference 2014, the speaker discusses easy and accessible ways for developers to contribute to the Ruby programming language. Hiroshi introduces how community contributions can significantly enhance Ruby experiences for users.

Key Points Discussed:
- Community Contribution: Hiroshi emphasizes that Ruby is maintained by its community, which includes everyone in attendance at the conference. He encourages developers to participate and contribute to Ruby's development.
- Methods to Contribute: Several practical ways to contribute are outlined, including:
- Making RubyGems
- Fixing defects in Rails
- Writing documentation
- Reporting bugs and issues
- Successful Bug Reports: Hiroshi provides guidance on creating effective bug reports by including comprehensive descriptions, test cases, and attaching relevant segmentation fault logs.
- Feature Requests: He elaborates on how to make substantial feature requests by defining use cases clearly and ensuring proper naming conventions, as well as including implementation code where possible.
- Communication Platforms: The speaker notes the importance of utilizing platforms such as GitHub and Redmine for submitting requests and tracking issues effectively.
- Encouragement to Participate: Hiroshi concludes by reinforcing the idea that anyone can make a difference in Ruby’s development through submissions and requests, emphasizing that contributions are welcomed and needed for the continued growth of Ruby.

Overall, Hiroshi inspires Ruby developers to engage with the community and improve the language by making their voices heard through coding contributions and bug fixing efforts, allowing for a more enjoyable Ruby programming experience for all users.

Lightning Talk: How to improve experiences of Ruby
Hiroshi Shibata • June 26, 2014 • Singapore • Lightning Talk

How can we make Ruby programming more pleasant? The most common (and easiest) methods are to make RubyGems or fix Rails defects. How about contributing to Ruby? Most people think that it's difficult to contribute or fix Ruby. Well, it is actually easy to contribute to or fix Ruby and many more people would be affected by your effort!

How can you start fixing Ruby? I'll introduce the methods to get started in improving Ruby, such as proposals of new features, writing documents, fixing websites, reporting defects and more.

Furthermore, there are techniques to help get your proposals accepted, and I'll talk about those too. You can improve the world by contributing to Ruby.

Help us caption & translate this video!

http://amara.org/v/FGZG/

Red Dot Ruby Conference 2014

00:00:14.920 uh
00:00:20.720 hello thank you so much for accepting to
00:00:24.240 my proposal
00:00:25.519 i love singapore my name is hiroshivata
00:00:29.359 please call me hiroshi my gihabakan name
00:00:32.559 is is hsbt i'm ruby committer my mission
00:00:37.760 is improved to experiences
00:00:40.800 of ruby so i'm maintaining to
00:00:44.000 our official sites named rubyrangorg
00:00:47.680 i'm working for gmo paperball in japan
00:00:51.039 we provide a lot of web services making
00:00:54.160 ruby is
00:00:54.960 a part of my job today
00:00:58.640 i describe about who are making ruby
00:01:02.960 is it much it's no
00:01:06.320 matter matthew's main work is
00:01:09.680 making a movie it's competitor or zero v
00:01:13.280 so much is our competitor and bam
00:01:16.560 version of c ruby
00:01:18.159 so max committed only one commit last
00:01:20.799 year
00:01:21.680 it is again who are making ruby
00:01:26.880 this answer is community committee means
00:01:30.000 you
00:01:30.640 and me and the people on these
00:01:32.560 conferences
00:01:34.000 and ruiz in the world i'll show my
00:01:37.200 examples
00:01:38.720 basically i use trunk and the head of
00:01:41.520 all branches build
00:01:43.360 this is the example of incompatible
00:01:45.520 changes on ruby 2.2
00:01:48.399 ruby 2.2 returns near it isn't
00:01:51.680 assignment same name over default value
00:01:55.360 this changes by grades but it's already
00:01:58.719 fixed
00:01:59.360 raised 4.1 and 4.0
00:02:02.719 by tender but it isn't back but to raise
00:02:06.240 three branch
00:02:07.119 if you still use registry
00:02:10.160 you can use ruby 2.2
00:02:14.560 louis trunk is often broken i can't
00:02:16.879 recommend it
00:02:18.160 this way how to control it ruby without
00:02:20.800 using trunk
00:02:22.480 first bug report i'll show good bug
00:02:25.680 report
00:02:28.319 the description or minimum case that
00:02:31.200 defects
00:02:31.840 is happened second
00:02:34.959 try different version of ruby it really
00:02:38.000 reduce
00:02:38.560 our investigate time last
00:02:42.640 its most important things crosstalk
00:02:45.040 attaches
00:02:46.000 rubicomita easily detects causes or
00:02:49.120 segmentation part with crushers but many
00:02:52.080 of people
00:02:52.959 forgot to attach this
00:02:56.239 next contributor is future requests
00:03:01.840 what are things of good future requests
00:03:08.239 it is use case use cases query
00:03:12.400 we have a lot of users why
00:03:15.680 your future makes them happy you need to
00:03:18.879 describe
00:03:19.680 it second
00:03:24.159 naming is important things of ruby much
00:03:27.280 said too but but naming
00:03:30.640 is rejected by maths it's the same
00:03:33.840 situation with ruby committee including
00:03:36.400 koichi
00:03:37.280 and me
00:03:40.400 third secret important things is
00:03:43.440 attaching codes if you hope to accept
00:03:47.120 your idea please attach your
00:03:49.640 implementations
00:03:53.360 you can submit future requests to github
00:03:56.000 with prerequest
00:03:58.000 i and the jack and nobu are checking
00:04:01.200 github every day
00:04:03.040 if prerequisite is the only
00:04:04.480 documentation changes
00:04:06.400 we measured it immediately
00:04:11.599 but github is a minor platform on ruby
00:04:14.239 committees
00:04:17.359 really minor platform especially math is
00:04:20.560 only available on our issue trackers
00:04:23.120 but mrv uses github
00:04:27.840 if you have big future requests
00:04:30.880 you need to make a ticket to redmine
00:04:34.240 please make the account our issue
00:04:37.280 tracker
00:04:37.919 and please submit your future requests
00:04:42.720 finally who are making ruby now
00:04:46.560 it's you please please submit by report
00:04:49.840 and future requests to our issue tracker
00:04:52.560 and
00:04:52.960 github we welcomed all right
00:05:08.840 thanks
00:05:24.240 you
Explore all talks recorded at Red Dot Ruby Conference 2014
+20