Summarized using AI

Lightning Talk: One Way to Encourage the Open Source Community

Takayuki Matsubara • June 23, 2017 • Singapore • Lightning Talk

In the lightning talk titled 'One Way to Encourage the Open Source Community,' Takayuki Matsubara, a software engineer at M3 Inc, presents an innovative approach to bolster contributions and recognition within the open source community, particularly focusing on GitHub projects. The central theme of the talk revolves around the significance of 'starring' projects on GitHub as a means of showing appreciation and support to developers. A GitHub star symbolizes recognition and can serve as a motivator for developers to maintain or create projects. Matsubara emphasizes that the total number of stars on a project is reflective of the overall activity and engagement within the open source community.

Key points discussed include:

  • The Importance of Starring Projects: Matsubara explains that putting a star on a GitHub project helps recognize and encourage the open source community, particularly emphasizing that many essential projects rely on cross-contributions from other open source projects.
  • Acknowledging Dependencies: He highlights a common disconnect where users often overlook the gems and libraries that their projects depend on, despite these gems being crucial to their development. This neglect creates a gap in visibility and support for those dependencies.
  • Introducing a Solution - 'understa': To bridge this gap, Matsubara introduces a command-line tool called 'understa' that enables users to automatically star the GitHub projects their own projects depend on. Users can execute this tool after running a bundle install command, which facilitates the seamless recognition of these dependencies.
  • Practical Demonstration: A demo is presented showing how to utilize 'understa' to add stars to these dependent projects, ensuring that contributions and acknowledgments flow back into the community. The demo illustrates the ease of use and the positive impact of recognizing the foundational tools of one’s own projects.
  • Cultivating a Supportive Environment: Matsubara encourages attendees to not only star their favorite projects but to also actively engage with and contribute to these projects to foster a richer open source ecosystem.

The conclusion of the talk underscores that every contribution to the open source community, no matter how small, can potentially amplify support and encourage the collaborative spirit inherent in open source development. Starring projects, learning, and actively participating in the open source community are highlighted as crucial components for nurturing growth and innovation within this space.

Lightning Talk: One Way to Encourage the Open Source Community
Takayuki Matsubara • Singapore • Lightning Talk

Date: June 23, 2017
Published: unknown
Announced: unknown

Speaker: Takayuki Matsubara, Software Engineer, M3 Inc

From the conclusion, it is to put a star on projects at GitHub. I'm very happy someone putting a star on my project. So if you already put a star on any projects, it encourage the open source community. But have you put a star on projects developed as oss used in your project? All of them? This talk proposes a solution that activates open source community by putting a star on projects which you depend.

Speaker's Bio

Takayuki Matsubara is a software engineer at M3, Inc. His day job is building and maintaining web apps. He loves open source community, has created chrono_logger, Power Assert in Elixir and other various.

Event Page: http://www.reddotrubyconf.com/

Produced by Engineers.SG

Red Dot Ruby Conference 2017

00:00:03.800 okay I come from Japan this is my pasta
00:00:10.139 trip to Singapore and also let's go
00:00:13.170 through be calm
00:00:15.260 thank you yesterday I experienced the
00:00:21.930 durian and also beer so my body
00:00:30.420 condition is a beta ever before so my
00:00:35.309 name is Takayuki matsubara
00:00:36.870 I am a subsidy Nia and working sm-3 I
00:00:41.339 like to be extra and OSS so I have been
00:00:45.899 creating Ruby and xri rice and also
00:00:49.409 publishing on github please put us stuff
00:00:53.789 and sing this so PR time because 20,000
00:01:04.650 217 will be held from September 18th to
00:01:09.180 20th in Hiroshima Japan please delete a
00:01:13.530 la ostracize and come so I would like to
00:01:22.350 introduce one way to enter it the open
00:01:25.770 source community by the way what is the
00:01:30.480 top star or someone who puts a star
00:01:35.640 it means appreciation support or manage
00:01:39.990 reverse trajectories
00:01:43.509 ossama who has owned projects
00:01:46.689 it means fear present like me so
00:01:50.840 motivation to maintain or create project
00:01:55.330 for someone who use this github project
00:01:58.670 it means the aim of the popularity or
00:02:01.280 Adam the reliability lies in the
00:02:05.570 obstruction a result the total number of
00:02:08.179 github stars represented represents the
00:02:11.630 activity of the OSS community so I think
00:02:15.760 putting a style ring close to the
00:02:18.410 encouragement of the OSS community so
00:02:23.140 how will you study our favorite projects
00:02:26.510 let the hunt thank you many people next
00:02:33.170 have used as a raise project Oh many
00:02:40.930 okay next have used as Mary James at the
00:02:44.780 rate of the actual Mara depends on oh
00:02:48.820 sure that's not a subscription have used
00:02:54.260 as the Lima types gels that the male
00:02:57.140 gender depends on all its nice Oh friend
00:03:03.640 Jerry we do not acknowledge the downs
00:03:06.500 but usual gems that we use sometimes
00:03:09.280 depend on as a gem so there is a gap
00:03:15.350 this picture shows that total download
00:03:17.600 is is almost the same but those are not
00:03:20.989 same so these gems are used as much as
00:03:24.470 large labels so I would like to turn the
00:03:30.170 spotlight to them because OSS is made up
00:03:33.739 of other OSS so I have created under
00:03:38.720 stuff
00:03:50.560 what does render so do under self-adjust
00:03:54.140 on github projects that your projects it
00:03:56.569 depends on when you execute the bundle
00:03:59.270 install comment so how to use the
00:04:02.270 understa let's give it a try if you okay
00:04:05.480 so for the step demo insert one star and
00:04:09.500 then make a directory when the start
00:04:12.140 index even do stop and render image to
00:04:14.870 create gem file and a go gem bondo start
00:04:18.290 to gem file also understands a tiny
00:04:21.829 wrapper of the vendor command commander
00:04:25.370 line arguments that has two origin open
00:04:28.250 the command undersell cusp is only
00:04:30.680 putting a staff so let's run bundle
00:04:34.940 install bundle stud tries to find a
00:04:38.690 github ID and a token from a certified
00:04:42.380 rotated Pina system to home directory if
00:04:46.160 you don't have an LLC vendor stock
00:04:49.250 retreat with the input so please
00:04:51.950 investigate already in the total so if
00:04:55.850 everything runs smoothly you can see
00:04:58.850 something like this so almost the same
00:05:08.870 husband during stuff but vendors under
00:05:12.260 separate app also gets a tap on general
00:05:16.540 so wonder some makes many stuff this is
00:05:22.700 a render stuff
00:05:29.450 now we can encourage the OSS community
00:05:33.120 with van der stadt but better sighs
00:05:36.900 we'll just one way to anchor Italy as a
00:05:39.870 community the really important point is
00:05:42.990 that we not value of oil sales project
00:05:45.900 and try to know more about sound ending
00:05:50.940 so we can get new knowledge and
00:05:53.910 contribute to those projects we can
00:05:56.790 encourage the OSS committee more if we
00:05:59.730 do those things
00:06:01.190 so enjoy thank you for listening
Explore all talks recorded at Red Dot Ruby Conference 2017
+12