Skip to content

Fix list-item headings in 2017-2018 meeting logs #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hsbt merged 1 commit into from
Feb 16, 2026
Merged

Fix list-item headings in 2017-2018 meeting logs #5

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
68 changes: 34 additions & 34 deletions 2017/DevMeeting-2017-01-19.md
View file
Open in desktop

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion 2017/DevMeeting-2017-03-13.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -123,7 +123,7 @@ Write your name and your interest (what do you want to ask and to whom?) please.

## About 2.5 timeframe

- ## [https://bugs.ruby-lang.org/projects/ruby-trunk/wiki/ReleaseEngineering25](https://www.google.com/url?q=https://bugs.ruby-lang.org/projects/ruby-trunk/wiki/ReleaseEngineering25&sa=D&source=editors&ust=1686087099213820&usg=AOvVaw3vacAuKsyIn9qLjxob6FaO)
## [https://bugs.ruby-lang.org/projects/ruby-trunk/wiki/ReleaseEngineering25](https://www.google.com/url?q=https://bugs.ruby-lang.org/projects/ruby-trunk/wiki/ReleaseEngineering25&sa=D&source=editors&ust=1686087099213820&usg=AOvVaw3vacAuKsyIn9qLjxob6FaO)

- 合宿

Expand Down
2 changes: 1 addition & 1 deletion 2017/DevMeeting-2017-04-17.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -142,7 +142,7 @@ Write your name and your interest (what do you want to ask and to whom?) please.

## About 2.5 timeframe

- ## [https://bugs.ruby-lang.org/projects/ruby-trunk/wiki/ReleaseEngineering25](https://www.google.com/url?q=https://bugs.ruby-lang.org/projects/ruby-trunk/wiki/ReleaseEngineering25&sa=D&source=editors&ust=1686087122716162&usg=AOvVaw1NHej4Qvc-yFM-fEqLMqsg)
## [https://bugs.ruby-lang.org/projects/ruby-trunk/wiki/ReleaseEngineering25](https://www.google.com/url?q=https://bugs.ruby-lang.org/projects/ruby-trunk/wiki/ReleaseEngineering25&sa=D&source=editors&ust=1686087122716162&usg=AOvVaw1NHej4Qvc-yFM-fEqLMqsg)

- Previrew 1 in June?
- 合宿
Expand Down
2 changes: 1 addition & 1 deletion 2017/DevMeeting-2017-05-19.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -152,7 +152,7 @@ Write your name and your interest (what do you want to ask and to whom?) please.

## About 2.5 timeframe

- ## [https://bugs.ruby-lang.org/projects/ruby-trunk/wiki/ReleaseEngineering25](https://www.google.com/url?q=https://bugs.ruby-lang.org/projects/ruby-trunk/wiki/ReleaseEngineering25&sa=D&source=editors&ust=1686087156480146&usg=AOvVaw0VF_ATzWdeZPXffCleFlIC)
## [https://bugs.ruby-lang.org/projects/ruby-trunk/wiki/ReleaseEngineering25](https://www.google.com/url?q=https://bugs.ruby-lang.org/projects/ruby-trunk/wiki/ReleaseEngineering25&sa=D&source=editors&ust=1686087156480146&usg=AOvVaw0VF_ATzWdeZPXffCleFlIC)

- Previrew 1 in June?

Expand Down
118 changes: 59 additions & 59 deletions 2017/DevMeeting-2017-06-16.md
View file
Open in desktop

Large diffs are not rendered by default.

80 changes: 40 additions & 40 deletions 2017/DevMeeting-2017-07-14.md
View file
Open in desktop

Large diffs are not rendered by default.

216 changes: 108 additions & 108 deletions 2017/DevMeeting-2017-08-31.md
View file
Open in desktop

Large diffs are not rendered by default.

72 changes: 36 additions & 36 deletions 2017/DevMeeting-2017-09-25.md
View file
Open in desktop

Large diffs are not rendered by default.

34 changes: 17 additions & 17 deletions 2018/DevMeeting-2018-01-24.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,24 +150,24 @@ Do we have to support such old toolchains? For instance, is it unable for us to

## Revisions r61785, r61786, r61787 were introduced by the request from @naruse. However [shyouhei](https://www.google.com/url?q=https://bugs.ruby-lang.org/users/10&sa=D&source=editors&ust=1686087512360881&usg=AOvVaw0ePcJzCf5XdJSgCLsuD24q) thinks the request was somewhat vague.

- ## Do we have to support such old toolchains? (shyouhei)
- Do we have to support such old toolchains? (shyouhei)

- ## Things we discussed:
- Things we discussed:


- ## Let’s make configure show the version of BASERUBY
- Let’s make configure show the version of BASERUBY

- ## That way we can detect failures on the CI matrix.
- That way we can detect failures on the CI matrix.


## From attendees

- ## \[Feature [#14223](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14223&sa=D&source=editors&ust=1686087512361697&usg=AOvVaw2qoIVwRQ21jZGfCNmt4Avp)\] Enable #to\_proc by Refinements at &hoge (nobu)
## \[Feature [#14223](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14223&sa=D&source=editors&ust=1686087512361697&usg=AOvVaw2qoIVwRQ21jZGfCNmt4Avp)\] Enable #to\_proc by Refinements at &hoge (nobu)


- Matz: LGTM.

- ## \[Feature [#14371](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14371&sa=D&source=editors&ust=1686087512362186&usg=AOvVaw3C2jlghrPiW2dGUkolCj4y)\] New option "recursive: true" for Hash#transform\_keys! (nobu)
## \[Feature [#14371](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14371&sa=D&source=editors&ust=1686087512362186&usg=AOvVaw3C2jlghrPiW2dGUkolCj4y)\] New option "recursive: true" for Hash#transform\_keys! (nobu)


- Mrkn: This is deep\_stringify\_keys!
Expand All @@ -177,43 +177,43 @@ Do we have to support such old toolchains? For instance, is it unable for us to
- Knu: This method changes values as well as keys, which seems wrong.
- Matz: This particular API seems NG to me.

- ## \[Bug #14380\] Expected transform\_keys! to work just as transform\_keys, but it doesn't (mame)
## \[Bug #14380\] Expected transform\_keys! to work just as transform\_keys, but it doesn't (mame)


- Shyouhei: This behaviour was inherited from ActiveSupport.
- Mrkn: we can fix it by preserving entries that conflict.
- Matz: I have strong opinion on this.  Isn’t the current behaviour acceptable in sake of space efficiency?

- ## \[Bug [#14374](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14374&sa=D&source=editors&ust=1686087512363214&usg=AOvVaw2B1puv_rNMyUOXl6K4ljSU)\] for does not splat elements (nobu)
## \[Bug [#14374](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14374&sa=D&source=editors&ust=1686087512363214&usg=AOvVaw2B1puv_rNMyUOXl6K4ljSU)\] for does not splat elements (nobu)


- Ko1: is it me?
- Nobu: because it’s since 1.9
- Matz: please fix.

- ## \[Feature [#14313](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14313&sa=D&source=editors&ust=1686087512363750&usg=AOvVaw2KpS-czrNodNpwLcBg2XDl)\] Support creating KeyError with receiver and key from Ruby (mrkn/kou)
## \[Feature [#14313](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14313&sa=D&source=editors&ust=1686087512363750&usg=AOvVaw2KpS-czrNodNpwLcBg2XDl)\] Support creating KeyError with receiver and key from Ruby (mrkn/kou)


- Mrkn: I was asked to bring this.
- Matz: Understand the needs.
- Shyouhei: Should it be keyword arguments?

- ## Maintainers of csv (mrkn/kou)
- Maintainers of csv (mrkn/kou)


- Mame: JEG2.
- Mrkn: But he doesn’t have the repo access bit, nor gem release right.
- Mame: He’s active on twitter etc.  You should ask his current status.

- ## \[Feature [#4831](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/4831&sa=D&source=editors&ust=1686087512364553&usg=AOvVaw2NGtLMxfwqnTu1GnsVIkwn)\] Integer#prime\_factors (mrkn)
## \[Feature [#4831](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/4831&sa=D&source=editors&ust=1686087512364553&usg=AOvVaw2NGtLMxfwqnTu1GnsVIkwn)\] Integer#prime\_factors (mrkn)


- Mrkn: name?
- Shyouhei: yugui is on the ticket.

- ## \[Feature [#14235](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14235&sa=D&source=editors&ust=1686087512365105&usg=AOvVaw3eDxHEK0-D0acn16JHMRMx)\] Merge MJIT infrastructure with conservative JIT compiler (k0kubun)
## \[Feature [#14235](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14235&sa=D&source=editors&ust=1686087512365105&usg=AOvVaw3eDxHEK0-D0acn16JHMRMx)\] Merge MJIT infrastructure with conservative JIT compiler (k0kubun)

- ## \[Feature [#14386](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14386&sa=D&source=editors&ust=1686087512365387&usg=AOvVaw2AN5f2c2f_uvaRIS83hIRi)\] Add option to let Kernel.#system raise error instead of returning false (k0kubun)
## \[Feature [#14386](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14386&sa=D&source=editors&ust=1686087512365387&usg=AOvVaw2AN5f2c2f_uvaRIS83hIRi)\] Add option to let Kernel.#system raise error instead of returning false (k0kubun)


- Nobu: is this request to raise error when spawn fails, or when the spawned process fails?
Expand All @@ -222,7 +222,7 @@ Do we have to support such old toolchains? For instance, is it unable for us to
- Mrkn: I see similarity for discussion on Integer(). \[ruby-core:77171\] \[Feature#12732\]
- Akr: There are \`exception: true\`

- ## \[Bug [#14353](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14353&sa=D&source=editors&ust=1686087512365973&usg=AOvVaw1oixIdf58UwAT9WWQAxiYg)\] $SAFE should stay at least thread-local for compatibility (ko1)
## \[Bug [#14353](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14353&sa=D&source=editors&ust=1686087512365973&usg=AOvVaw1oixIdf58UwAT9WWQAxiYg)\] $SAFE should stay at least thread-local for compatibility (ko1)


- Matz: This feature is something to extinct in future.
Expand All @@ -248,15 +248,15 @@ Do we have to support such old toolchains? For instance, is it unable for us to

## From non-attendees

- ## \[Feature [#14382](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14382&sa=D&source=editors&ust=1686087512367039&usg=AOvVaw3gFB_Lay0sGojfbewW7Sa7)\] Make public access of a private constant call const\_missing (jeremyevans0)
## \[Feature [#14382](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14382&sa=D&source=editors&ust=1686087512367039&usg=AOvVaw3gFB_Lay0sGojfbewW7Sa7)\] Make public access of a private constant call const\_missing (jeremyevans0)


- Nobu: sounds like a bug to me
- Matz: I’m positive, but not sure if it’s 100% safe.
- Matz: Let’s try.
- Nobu: I’d like to review the patch.

- ## \[Feature [#14385](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14385&sa=D&source=editors&ust=1686087512367688&usg=AOvVaw0eQ3yNpD38-9kMww4Bo970)\] Deprecate back-tick for Ruby 3 (hsbt)
## \[Feature [#14385](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14385&sa=D&source=editors&ust=1686087512367688&usg=AOvVaw0eQ3yNpD38-9kMww4Bo970)\] Deprecate back-tick for Ruby 3 (hsbt)


- Matz: I see several objections are there.
Expand All @@ -268,7 +268,7 @@ Do we have to support such old toolchains? For instance, is it unable for us to
- Mame: should we also deprecate def \`; end; self.\` ? If so, warning on parsing is dangerous.
- Matz: I think we don’t necessarily warn this as soon as 2.6.

- ## \[Feature [#13969](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/13969&sa=D&source=editors&ust=1686087512368511&usg=AOvVaw3WyXrLdBrk8ACvBw3WmPmA)\] Dir#each\_child (znz)
## \[Feature [#13969](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/13969&sa=D&source=editors&ust=1686087512368511&usg=AOvVaw3WyXrLdBrk8ACvBw3WmPmA)\] Dir#each\_child (znz)


- Matz: OK.
34 changes: 17 additions & 17 deletions 2018/DevMeeting-2018-02-20.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -151,24 +151,24 @@ Next Developper Meetings

## Revisions r61785, r61786, r61787 were introduced by the request from @naruse. However [shyouhei](https://www.google.com/url?q=https://bugs.ruby-lang.org/users/10&sa=D&source=editors&ust=1686087534729949&usg=AOvVaw0zCOxnLHfD-SAJpu3U4FWv) thinks the request was somewhat vague.

- ## Do we have to support such old toolchains? (shyouhei)
- Do we have to support such old toolchains? (shyouhei)

- ## Things we discussed:
- Things we discussed:


- ## Let’s make configure show the version of BASERUBY
- Let’s make configure show the version of BASERUBY

- ## That way we can detect failures on the CI matrix.
- That way we can detect failures on the CI matrix.


## From attendees

- ## \[Feature [#14223](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14223&sa=D&source=editors&ust=1686087534730902&usg=AOvVaw0hKDkPhy2smcNbHV7h3t95)\] Enable #to\_proc by Refinements at &hoge (nobu)
## \[Feature [#14223](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14223&sa=D&source=editors&ust=1686087534730902&usg=AOvVaw0hKDkPhy2smcNbHV7h3t95)\] Enable #to\_proc by Refinements at &hoge (nobu)


- Matz: LGTM.

- ## \[Feature [#14371](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14371&sa=D&source=editors&ust=1686087534731456&usg=AOvVaw0138Z7WbBbP8sVNjKJtboU)\] New option "recursive: true" for Hash#transform\_keys! (nobu)
## \[Feature [#14371](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14371&sa=D&source=editors&ust=1686087534731456&usg=AOvVaw0138Z7WbBbP8sVNjKJtboU)\] New option "recursive: true" for Hash#transform\_keys! (nobu)


- Mrkn: This is deep\_stringify\_keys!
Expand All @@ -178,43 +178,43 @@ Next Developper Meetings
- Knu: This method changes values as well as keys, which seems wrong.
- Matz: This particular API seems NG to me.

- ## \[Bug #14380\] Expected transform\_keys! to work just as transform\_keys, but it doesn't (mame)
## \[Bug #14380\] Expected transform\_keys! to work just as transform\_keys, but it doesn't (mame)


- Shyouhei: This behaviour was inherited from ActiveSupport.
- Mrkn: we can fix it by preserving entries that conflict.
- Matz: I have strong opinion on this.  Isn’t the current behaviour acceptable in sake of space efficiency?

- ## \[Bug [#14374](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14374&sa=D&source=editors&ust=1686087534732782&usg=AOvVaw23Evsh07gKVvWVGJqwzzPf)\] for does not splat elements (nobu)
## \[Bug [#14374](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14374&sa=D&source=editors&ust=1686087534732782&usg=AOvVaw23Evsh07gKVvWVGJqwzzPf)\] for does not splat elements (nobu)


- Ko1: is it me?
- Nobu: because it’s since 1.9
- Matz: please fix.

- ## \[Feature [#14313](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14313&sa=D&source=editors&ust=1686087534733360&usg=AOvVaw01wZt0etef0uPW3YdiOET2)\] Support creating KeyError with receiver and key from Ruby (mrkn/kou)
## \[Feature [#14313](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14313&sa=D&source=editors&ust=1686087534733360&usg=AOvVaw01wZt0etef0uPW3YdiOET2)\] Support creating KeyError with receiver and key from Ruby (mrkn/kou)


- Mrkn: I was asked to bring this.
- Matz: Understand the needs.
- Shyouhei: Should it be keyword arguments?

- ## Maintainers of csv (mrkn/kou)
- Maintainers of csv (mrkn/kou)


- Mame: JEG2.
- Mrkn: But he doesn’t have the repo access bit, nor gem release right.
- Mame: He’s active on twitter etc.  You should ask his current status.

- ## \[Feature [#4831](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/4831&sa=D&source=editors&ust=1686087534734216&usg=AOvVaw000s7NUFCbXTK8QZm0leib)\] Integer#prime\_factors (mrkn)
## \[Feature [#4831](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/4831&sa=D&source=editors&ust=1686087534734216&usg=AOvVaw000s7NUFCbXTK8QZm0leib)\] Integer#prime\_factors (mrkn)


- Mrkn: name?
- Shyouhei: yugui is on the ticket.

- ## \[Feature [#14235](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14235&sa=D&source=editors&ust=1686087534734701&usg=AOvVaw3sHZaMuYBRg9KZEliD_l-L)\] Merge MJIT infrastructure with conservative JIT compiler (k0kubun)
## \[Feature [#14235](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14235&sa=D&source=editors&ust=1686087534734701&usg=AOvVaw3sHZaMuYBRg9KZEliD_l-L)\] Merge MJIT infrastructure with conservative JIT compiler (k0kubun)

- ## \[Feature [#14386](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14386&sa=D&source=editors&ust=1686087534735005&usg=AOvVaw0rq2r3IXro64FgAE0y6TSU)\] Add option to let Kernel.#system raise error instead of returning false (k0kubun)
## \[Feature [#14386](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14386&sa=D&source=editors&ust=1686087534735005&usg=AOvVaw0rq2r3IXro64FgAE0y6TSU)\] Add option to let Kernel.#system raise error instead of returning false (k0kubun)


- Nobu: is this request to raise error when spawn fails, or when the spawned process fails?
Expand All @@ -223,7 +223,7 @@ Next Developper Meetings
- Mrkn: I see similarity for discussion on Integer(). \[ruby-core:77171\] \[Feature#12732\]
- Akr: There are \`exception: true\`

- ## \[Bug [#14353](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14353&sa=D&source=editors&ust=1686087534735695&usg=AOvVaw3VLRR_Wp944LrfkBaowubO)\] $SAFE should stay at least thread-local for compatibility (ko1)
## \[Bug [#14353](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14353&sa=D&source=editors&ust=1686087534735695&usg=AOvVaw3VLRR_Wp944LrfkBaowubO)\] $SAFE should stay at least thread-local for compatibility (ko1)


- Matz: This feature is something to extinct in future.
Expand All @@ -249,15 +249,15 @@ Next Developper Meetings

## From non-attendees

- ## \[Feature [#14382](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14382&sa=D&source=editors&ust=1686087534736923&usg=AOvVaw1k6X3Y-H2yxkyqjbUiHTjO)\] Make public access of a private constant call const\_missing (jeremyevans0)
## \[Feature [#14382](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14382&sa=D&source=editors&ust=1686087534736923&usg=AOvVaw1k6X3Y-H2yxkyqjbUiHTjO)\] Make public access of a private constant call const\_missing (jeremyevans0)


- Nobu: sounds like a bug to me
- Matz: I’m positive, but not sure if it’s 100% safe.
- Matz: Let’s try.
- Nobu: I’d like to review the patch.

- ## \[Feature [#14385](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14385&sa=D&source=editors&ust=1686087534737578&usg=AOvVaw1e4UbeKafR4WFVvojciJ0F)\] Deprecate back-tick for Ruby 3 (hsbt)
## \[Feature [#14385](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/14385&sa=D&source=editors&ust=1686087534737578&usg=AOvVaw1e4UbeKafR4WFVvojciJ0F)\] Deprecate back-tick for Ruby 3 (hsbt)


- Matz: I see several objections are there.
Expand All @@ -269,7 +269,7 @@ Next Developper Meetings
- Mame: should we also deprecate def \`; end; self.\` ? If so, warning on parsing is dangerous.
- Matz: I think we don’t necessarily warn this as soon as 2.6.

- ## \[Feature [#13969](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/13969&sa=D&source=editors&ust=1686087534738407&usg=AOvVaw08WBvi8j7alCbpQ1j1kSuU)\] Dir#each\_child (znz)
## \[Feature [#13969](https://www.google.com/url?q=https://bugs.ruby-lang.org/issues/13969&sa=D&source=editors&ust=1686087534738407&usg=AOvVaw08WBvi8j7alCbpQ1j1kSuU)\] Dir#each\_child (znz)


- Matz: OK.
Loading