ruby · hsbt · Feb 24, 2026 · Feb 19, 2026
diff --git a/2013/DevMeeting-2013-12-05.md b/2013/DevMeeting-2013-12-05.md
@@ -76,7 +76,7 @@ Season's greetings everyone!
 
 You can watch the recording from Thursday's meeting on[ustream](http://www.ustream.tv/recorded/41393753), thanks to[@mrkn](https://twitter.com/mrkn) for the recording!
 
-Although we didn't have a video recording from the meeting on Friday, werecorded our skype conference and is available on[soundcloud](https://soundcloud.com/zzak-2/ruby-core-developer-meeting). Thanksto [@sora\_h](https://twitter.com/sora_h) for the recording and moderating skype!
+Although we didn't have a video recording from the meeting on Friday, werecorded our skype conference and is available on[soundcloud](https://soundcloud.com/zzak-2/ruby-core-developer-meeting). Thanksto [@sora_h](https://twitter.com/sora_h) for the recording and moderating skype!
 
 Below I have summarized the meetings for each day and organized them intoagenda items. Each agenda item should have an associated ticket on our [bugtracker](http://bugs.ruby-lang.org/) that you can follow for more information.I will be updating these tickets with our conclusion shortly!
 
@@ -115,38 +115,38 @@ To summarize:
 - We accept proposal of [@hsbt](https://twitter.com/hsbt)
 - The following proposal will begin with 2.1.0
 
-#### Version Schema \`ruby-{MAJOR}.{MINOR}.{TEENY}\`[¶](https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeetingDecember2013Japan#Version-Schema-ruby-MAJORMINORTEENY)
+#### Version Schema `ruby-{MAJOR}.{MINOR}.{TEENY}`[¶](https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeetingDecember2013Japan#Version-Schema-ruby-MAJORMINORTEENY)
 
-- \`MAJOR\`: increased when incompatible change which can't be released in MINOR
+- `MAJOR`: increased when incompatible change which can't be released in MINOR
 - "MAJOR is for party", reserved for special events
-- \`MINOR\`: increased every christmas, may be API incompatible
-- \`TEENY\`: security or bug fix which maintains API compatibility
-- \`PATCH\`: number of commits since last MINOR release (will be reset at 0 when releasing MINOR)
+- `MINOR`: increased every christmas, may be API incompatible
+- `TEENY`: security or bug fix which maintains API compatibility
+- `PATCH`: number of commits since last MINOR release (will be reset at 0 when releasing MINOR)
 
-\`TEENY\` may be increased more than 10 (such as \`2.1.11\`), and will be releasedevery 2-3 months.
+`TEENY` may be increased more than 10 (such as `2.1.11`), and will be releasedevery 2-3 months.
 
-Matz and other attendees were concerned about \`TEENY >= 10\`.
+Matz and other attendees were concerned about `TEENY >= 10`.
 
 #### Branches[¶](https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeetingDecember2013Japan#Branches)
 
 We will maintain the following branches:
 
 - trunk
-- \`ruby\_{MAJOR}\_{MINOR}\`
-- \`ruby\_{MAJOR}\_{MINOR}\` across \`TEENY\` releases
+- `ruby_{MAJOR}_{MINOR}`
+- `ruby_{MAJOR}_{MINOR}` across `TEENY` releases
 - tags will be used for each release
 
 #### API Compatibility[¶](https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeetingDecember2013Japan#API-Compatibility)
 
 - Removing API is an incompatible change
-- such as (\`STDIO\_READ\_DATA\_PENDING\`, etc.) must wait for 2.2.0
-- an incompatible change must increase \`MINOR\`
+- such as (`STDIO_READ_DATA_PENDING`, etc.) must wait for 2.2.0
+- an incompatible change must increase `MINOR`
 
 #### ABI Compatibility[¶](https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeetingDecember2013Japan#ABI-Compatibility)
 
-- Scheme of \`{MAJOR}.{MINOR}.0\`
-- Keep ABI compatibility with same \`MINOR\` release, so \`TEENY\` is fixed at 0
-- Retain compatibility across \`TEENY\` releases
+- Scheme of `{MAJOR}.{MINOR}.0`
+- Keep ABI compatibility with same `MINOR` release, so `TEENY` is fixed at 0
+- Retain compatibility across `TEENY` releases
 
 We are concerned with changes required for existing tools, such as:
 
@@ -155,18 +155,18 @@ We are concerned with changes required for existing tools, such as:
 
 #### Documentation[¶](https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeetingDecember2013Japan#Documentation)
 
-We need to announce our plans for removing patch level semantics, in order touse \`{MAJOR}.{MINOR}.{TEENY}\`.
+We need to announce our plans for removing patch level semantics, in order touse `{MAJOR}.{MINOR}.{TEENY}`.
 
 ### Maintenance Policy for 1.8.7 and 1.9.2[¶](https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeetingDecember2013Japan#Maintenance-Policy-for-187-and-192)
 
 [misc. #9216](http://bugs.ruby-lang.org/issues/9216)
 
 1.8.7 and 1.9.2 will be supported for security fixes until June 2014.
 
-- [@hone02](https://twitter.com/hone02) and [@\_zzak](https://twitter.com/_zzak) will assume maintainership
+- [@hone02](https://twitter.com/hone02) and [@_zzak](https://twitter.com/_zzak) will assume maintainership
 - After the 6 month maintenance period, we can add more committers to extend another 6 months.
 
-In the past we have supported vendors who wish to maintain legacy versions. In2009 the maintenance of Ruby \`1.8.6\` was transferred to Engine Yard when theyreleased \`1.8.6-p369\`.
+In the past we have supported vendors who wish to maintain legacy versions. In2009 the maintenance of Ruby `1.8.6` was transferred to Engine Yard when theyreleased `1.8.6-p369`.
 
 We were given permission from Matz to release backport versions of Ruby forsecurity fixes.
 
@@ -222,7 +222,7 @@ Every issue can escalate to Matz, should he become inactive maybe we need torepl
 
 Asking to declare an expected maintenance period during appointment was rejected, see below:
 
-[@nagachika](https://twitter.com/nagachika), current maintainer of \`2.0.0\` madethe following comment:
+[@nagachika](https://twitter.com/nagachika), current maintainer of `2.0.0` madethe following comment:
 
 I never publish maintenance period for 2.0.0. I thought I can maintain it
 for 2 years in "normal maintenance mode" and then turn into "security only
@@ -264,8 +264,8 @@ We discussed this ticket, and concluded the following statements:
 
 After watching the video I wrote a [roughsummary](https://gist.github.com/zzak/7821769), since most of thediscussion was in English. The following other events took place during themeeting:
 
-- [@a\_matsuda](https://twitter.com/a_matsuda) commits typo patches, he is the typo monster!
+- [@a_matsuda](https://twitter.com/a_matsuda) commits typo patches, he is the typo monster!
 - [Martin Duerst commits too!](https://github.com/ruby/ruby/commit/737c7d8)
 - [@hone02](https://twitter.com/hone02) joined the skype call to discuss his feedback on maintainer appointment and discharge
-- [@a\_matsuda](https://twitter.com/a_matsuda) will propose gemifying the stdlib at the next meeting
+- [@a_matsuda](https://twitter.com/a_matsuda) will propose gemifying the stdlib at the next meeting
 
diff --git a/2013/DevMeeting-2013-12-06.md b/2013/DevMeeting-2013-12-06.md
@@ -58,25 +58,25 @@ Please follow the [[DevelopersMeetingIRCGuidelines]] for irc
 
 On Friday, several committers met to discuss the events that took place duringthe previous meeting. We made important decisions on the maintenance policy forbackport versions and commercial support.
 
-### Branch Schema for Semantic Versioning \`ruby\_MAJOR\_MINOR\`[¶](https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeetingDecember2013Japan#Branch-Schema-for-Semantic-Versioning-ruby_MAJOR_MINOR)
+### Branch Schema for Semantic Versioning `ruby_MAJOR_MINOR`[¶](https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeetingDecember2013Japan#Branch-Schema-for-Semantic-Versioning-ruby_MAJOR_MINOR)
 
 [misc. #8835](http://bugs.ruby-lang.org/issues/8835)
 
 We discussed a concern with handling security releases given the proposed branching schema.
 
-During the 1.8 series we had a dedicated ruby\_1\_8 branch with no \`TEENY\`version in the name. In this time we had to release a security fix from thisbranch, however there were existing unreleased bug fix patches on this branchcausing a regression.
+During the 1.8 series we had a dedicated ruby_1_8 branch with no `TEENY`version in the name. In this time we had to release a security fix from thisbranch, however there were existing unreleased bug fix patches on this branchcausing a regression.
 
-The previous solution was to create a new branch (\`ruby\_1\_8\_6\`) and beginmaintaining two branches for the 1.8 series.
+The previous solution was to create a new branch (`ruby_1_8_6`) and beginmaintaining two branches for the 1.8 series.
 
 - Additional branches may be added to support cherry-picking of security fixes.
 
 We are concerned because security versions may occur more frequently betweenMINOR branch changes.
 
 #### SemVer[¶](https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeetingDecember2013Japan#SemVer)
 
-After reviewing the discussion from the previous meeting we discussed theconcern of \`TEENY >= 10\`.
+After reviewing the discussion from the previous meeting we discussed theconcern of `TEENY >= 10`.
 
-- String comparison bugs exist, such as: \`"2.2.2" <= "2.2.10" #=> false\`
+- String comparison bugs exist, such as: `"2.2.2" <= "2.2.10" #=> false`
 - We can fix this by abandoning strings
 - The version number can be anything that acts like String
 - We will postpone this situation
@@ -157,7 +157,7 @@ That about wraps up the summary of both meetings, thank you to everyone who coul
 Thanks for everyone who helped make this meeting possible, especially:
 
 - Cookpad for hosting both meetings on short notice
-- [@sora\_h](https://twitter.com/sora_h) for moderating irc, skype, and creating the audio recordings
+- [@sora_h](https://twitter.com/sora_h) for moderating irc, skype, and creating the audio recordings
 - [@mrkn](https://twitter.com/mrkn) for the video recording on Thursday
 - [@lchin](https://twitter.com/lchin) for translation support on Friday
 - Everyone who attended and helped discuss the future of Ruby

diff --git a/2014/DevMeeting-2014-05-17.md b/2014/DevMeeting-2014-05-17.md
@@ -31,7 +31,7 @@ Attendees: sign up required: http://cruby.doorkeeper.jp/events/10778
 
 # Log
 
-attendee: sora\_h, shyouhei, akr, naruse, ko1, hsbt, tarui
+attendee: sora_h, shyouhei, akr, naruse, ko1, hsbt, tarui
 
 online: matz, n0kada,
 
@@ -109,15 +109,15 @@ bundle gem にして、time が依存する箇所だけ ext に持っていく.
 
 →matzがOKと返信する
 
-## [[Feature #9826]](https://bugs.ruby-lang.org/issues/9826) Enumerable#slice\_between (akr)
+## [[Feature #9826]](https://bugs.ruby-lang.org/issues/9826) Enumerable#slice_between (akr)
 
 ニーズはある
 
 matz: 機能としては採用してあげたいけど、この名前では採用できない。これはbetweenではない。
 
 #slice? → Array#slice があるのでNG
 
-## [[Feature #9071]](https://bugs.ruby-lang.org/issues/9071) Enumerable#slice\_after (akr)
+## [[Feature #9071]](https://bugs.ruby-lang.org/issues/9071) Enumerable#slice_after (akr)
 
 対称性
 
@@ -145,19 +145,19 @@ Matz: sysconf と confstr で同じ機能だけど、数値と文字列を返す
 
 Windows でどうしよう →NotImplementedError
 
-## [[Feature #9834]](https://bugs.ruby-lang.org/issues/9834) Float#{next\_float,prev\_float} (akr)
+## [[Feature #9834]](https://bugs.ruby-lang.org/issues/9834) Float#{next_float,prev_float} (akr)
 
 これは用途があまり明らかでない→テストで便利(printfのテストとか)。
 
-## [[Feature #9632]](https://bugs.ruby-lang.org/issues/9632) \[offtopic\] remove doxygen?
+## [[Feature #9632]](https://bugs.ruby-lang.org/issues/9632) [offtopic] remove doxygen?
 
 ccan フォルダの追加に伴って doxygen の警告が凄いでてきた、そもそも使ってないなら消したい
 
 ko1: 消すのではなくて、デフォルトで動くのはやめて make doxygen とかしたら動くようにしたらどうか
 
 Matz: デフォルトでは動かさないようにして、何かレポートきたら誰か頑張る.
 
-## [[Feature #9711]](https://bugs.ruby-lang.org/issues/9711) Remove test-unit and minitest from stdlib. Can I remove test-unit? /cc sora\_h (hsbt)
+## [[Feature #9711]](https://bugs.ruby-lang.org/issues/9711) Remove test-unit and minitest from stdlib. Can I remove test-unit? /cc sora_h (hsbt)
 
 lib/test, lib/minitest を使うのはもうやめている.
 
@@ -199,7 +199,7 @@ ko1: gem にしてメンテナンスサイクルを分けよう
 
 Matz: 名前がイマイチ
 
-## \[ANN\] chkbuildXXX.hsbt.org
+## [ANN] chkbuildXXX.hsbt.org
 
 Ruby Association の資金で4台マシンを用意しました. 必要に応じてアカウント作るのでご連絡ください.
 
@@ -226,7 +226,7 @@ pLinux が何なのかよくわからないので RubyCI のサーバー名を
 
 ## Attendance[¶](https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeetingSummary20140517Japan#Attendance)
 
-- in person: sora\_h, shyouhei, akr, naruse, ko1, hsbt, tarui
+- in person: sora_h, shyouhei, akr, naruse, ko1, hsbt, tarui
 - online: matz, n0kada
 
 ## \[Feature [#9772](https://bugs.ruby-lang.org/issues/9772 "Feature: IO#statfs and File::Statfs (Rejected)")\] IO#statfs and File::Statfs[¶](https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeetingSummary20140517Japan#Feature-9772-IOstatfs-and-FileStatfs)
@@ -252,11 +252,11 @@ going separate it into a bundled gem
 
 accepted
 
-## \[Feature [#9826](https://bugs.ruby-lang.org/issues/9826 "Feature: Enumerable#slice_between (Closed)")\] Enumerable#slice\_between (akr)[¶](https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeetingSummary20140517Japan#Feature-9826-Enumerableslice_between-akr)
+## \[Feature [#9826](https://bugs.ruby-lang.org/issues/9826 "Feature: Enumerable#slice_between (Closed)")\] Enumerable#slice_between (akr)[¶](https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeetingSummary20140517Japan#Feature-9826-Enumerableslice_between-akr)
 
 Matz likes the idea, but it needs a better name. There is already Array#slice.
 
-## \[Feature [#9071](https://bugs.ruby-lang.org/issues/9071 "Feature: Enumerable#slice_after (Closed)")\] Enumerable#slice\_after (akr)[¶](https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeetingSummary20140517Japan#Feature-9071-Enumerableslice_after-akr)
+## \[Feature [#9071](https://bugs.ruby-lang.org/issues/9071 "Feature: Enumerable#slice_after (Closed)")\] Enumerable#slice_after (akr)[¶](https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeetingSummary20140517Japan#Feature-9071-Enumerableslice_after-akr)
 
 accepted
 
@@ -268,15 +268,15 @@ accepted
 
 accepted
 
-## \[Feature [#9834](https://bugs.ruby-lang.org/issues/9834 "Feature: Float#{next_float,prev_float} (Closed)")\] Float#{next\_float,prev\_float} (akr)[¶](https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeetingSummary20140517Japan#Feature-9834-Floatnext_floatprev_float-akr)
+## \[Feature [#9834](https://bugs.ruby-lang.org/issues/9834 "Feature: Float#{next_float,prev_float} (Closed)")\] Float#{next_float,prev_float} (akr)[¶](https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeetingSummary20140517Japan#Feature-9834-Floatnext_floatprev_float-akr)
 
 accepted
 
-## \[Feature [#9632](https://bugs.ruby-lang.org/issues/9632 "Feature: [PATCH 0/2] speedup IO#close with linked-list from ccan (Closed)")\] \[offtopic\] remove doxygen?[¶](https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeetingSummary20140517Japan#Feature-9632-offtopic-remove-doxygen)
+## \[Feature [#9632](https://bugs.ruby-lang.org/issues/9632 "Feature: [PATCH 0/2] speedup IO#close with linked-list from ccan (Closed)")\] [offtopic] remove doxygen?[¶](https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeetingSummary20140517Japan#Feature-9632-offtopic-remove-doxygen)
 
 dropping support for doxygen
 
-## \[Feature [#9711](https://bugs.ruby-lang.org/issues/9711 "Feature: Remove test-unit and minitest from stdlib. (Closed)")\] Remove test-unit and minitest from stdlib. Can I remove test-unit? /cc sora\_h (hsbt)[¶](https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeetingSummary20140517Japan#Feature-9711-Remove-test-unit-and-minitest-from-stdlib-Can-I-remove-test-unit-cc-sora_h-hsbt)
+## \[Feature [#9711](https://bugs.ruby-lang.org/issues/9711 "Feature: Remove test-unit and minitest from stdlib. (Closed)")\] Remove test-unit and minitest from stdlib. Can I remove test-unit? /cc sora_h (hsbt)[¶](https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeetingSummary20140517Japan#Feature-9711-Remove-test-unit-and-minitest-from-stdlib-Can-I-remove-test-unit-cc-sora_h-hsbt)
 
 continuing to discuss about bundling test libraries test-unit/minitest.
 
@@ -296,11 +296,11 @@ accepted: going to fade out callcc support
 - unclear what the usecase is
 - continue to discuss on redmine
 
-## \[ANN\] chkbuildXXX.hsbt.org[¶](https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeetingSummary20140517Japan#ANN-chkbuildXXXhsbtorg)
+## [ANN] chkbuildXXX.hsbt.org[¶](https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeetingSummary20140517Japan#ANN-chkbuildXXXhsbtorg)
 
 Using Ruby Association's funds, 4 machines have been prepared for chkbuild. chkbuild is the Ruby CI platform powering [http://rubyci.org](http://rubyci.org/). We also want something besides Intel like running ARM on top of QEMU.
 
 ## Next Meetings[¶](https://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeetingSummary20140517Japan#Next-Meetings)
 
-- 6/18, 18:30 JST: discussing \[Feature [#9711](https://bugs.ruby-lang.org/issues/9711 "Feature: Remove test-unit and minitest from stdlib. (Closed)")\], [doorkeeper](http://cruby.doorkeeper.jp/events/11795?utm_campaign=event_11795_7773&utm_medium=email&utm_source=not_replied_message)
+- 6/18, 18:30 JST: discussing [Feature [#9711](https://bugs.ruby-lang.org/issues/9711 "Feature: Remove test-unit and minitest from stdlib. (Closed)")], [doorkeeper](http://cruby.doorkeeper.jp/events/11795?utm_campaign=event_11795_7773&utm_medium=email&utm_source=not_replied_message)
 - 7/26: big features for 2.2