of library named standard library a.k.a stdlib. •Ruby 1.9.x bundled rubygems that is ruby library packaging and distributing. •Many of libraries was born after that. Example for rspec, nokogiri, rake and thor. It’s start time for Ruby language and library ecosystems. •First Authors of famous library is burnout. •Some of useful gems are changed maintainers of second generation. •Ruby 2.4, 2.5 2013 2017 2009 2008
comments to Issue, an send a pull request to repository. Current maintainer add commit bit to you. 2. Request to take over via E-Mail/DM/slack…Etc 3. Request to take over via face to face communication.
passed away in February 2014. •This repository was originally hosted at github.com/ jimweirich/rake, It has been moved to github.com/ruby/rake by @drbrain •Rake adopted SemVer policy. (v0.9.x to v10.x.y) •@drbrain and @hsbt maintain ruby/rake now.
`@last_comment` with deprecated code. • I found a my commit is “breaking changes” when it happens. • It was referenced yard, rspec and rubocop. When users updated Rake 11, It breaks rake task with these gems. We should prepare “Transition Path” for breaking changes.
bundled libyaml-* sources. You can build psych without libyaml-devel(dev) packages. # Load YAML in to a Ruby object Psych.load('--- foo') # => 'foo' # Emit YAML from a Ruby object Psych.dump("foo") # => "--- foo\n...\n"
personal repository of Github to organization account named “ruby” • Now, canonical repository of psych is https://github.com/ruby/ psych • I can update CI configuration and team of contributors. Face to Face is a best practice for OSS development.
issue. so all of release maintainer are volunteer work. If you have a plan for OSS take over, you should concern security handling. • Do you have a connection of security community? • Do you have a friends of security specialist? • etc…
Therefore json-2.x breaks Ruby 2.4.x or later. • You could not install rails with Ruby 2.4 at it time. • `gem i rails` was stopped caused by json dependency via rdoc/ sdoc. See details: https://www.hsbt.org/diary/20160829.html And my talk of RubyKaigi 2017
rdoc and management releases(not product management) • I have no idea for improving documentation tool about rdoc If you are interested in rdoc or documentation tools of Ruby, Please discuss to me. (It’s a take over chance)
created a patch for rubygems/rubygems from ruby core. • But I felt that rubygems has no project/product manager. In the past, @drbrain released new version of rubygems. But it decreased a number of releases in 2015. • In Q4 of 2015, RubyTogether taken over the rubygems projects.
ruby core collaboration. (It’s my point of view.) In the past, We easily discuss maintenance plan and policy about ruby and rubygems to @tenderlove and @drbrain. I hard to backport a patch to rubygems from ruby core. Because these patch only need ruby trunk. It is needless stable versions.
gems. You can update it separated ruby core releases same as rubygems, rdoc, bigdecimal. • https://github.com/ruby/openssl • It’s maintained by @rhenium • Upstream was changed github repository from svn.ruby-lang.org • He aggressively maintains new feature of openssl
fiddle was already reserved another implementation rubygems.org https://github.com/bsm/fiddle I did coordinate to transfer above namespace and override CRuby implementation now. https://github.com/ruby/fiddle