Project

General

Profile

Actions
Copy link

Misc #21689

open

DevMeeting-2025-12-11

Misc #21689: DevMeeting-2025-12-11

Added by mame (Yusuke Endoh) 14 days ago. Updated 3 days ago.

Status:
Open
Assignee:
-
[ruby-core:123815]

Description

The next dev meeting

Date: 2025/12/11 13:00-17:00 (JST)
Log: TBD

  • Dev meeting IS NOT a decision-making place. All decisions should be done at the bug tracker.
  • Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly.
  • Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue).
  • We will write a record of the discussion in the file or to each ticket in English.
  • All activities are best-effort (keep in mind that most of us are volunteer developers).
  • The date, time and place of the meeting are scheduled according to when/where we can reserve Matz's time.
  • DO NOT discuss then on this ticket, please.

Call for agenda items

If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format:

* [Ticket ref] Ticket title (your name)
  * Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.)

Example:

* [Feature #14609] `Kernel#p` without args shows the receiver (ko1)
  * I feel this feature is very useful and some people say :+1: so let discuss this feature.
  • It is recommended to add a comment by 2025/12/08. We hold a preparatory meeting to create an agenda a few days before the dev-meeting.
  • The format is strict. We'll use this script to automatically create an markdown-style agenda. We may ignore a comment that does not follow the format.
  • Your comment is mandatory. We cannot read all discussion of the ticket in a limited time. We appreciate it if you could write a short summary and update from a previous discussion.

Related issues 1 (1 open — 0 closed)

Related to Ruby - Misc #14770: [META] DevelopersMeetingOpenActions

Updated by mame (Yusuke Endoh) 14 days ago Actions
Copy link
 #1

  • Related to Misc #14770: [META] DevelopersMeeting added

Updated by Eregon (Benoit Daloze) 14 days ago · Edited Actions
Copy link
 #2 [ruby-core:123823]

  • [Bug #21375] Set[] does not call #initialize (eregon)
    • This broke concurrent-ruby and there is no good fix.
    • I believe Set[] should call #initialize, it's simple and avoids a major breaking change. The performance impact seems insignificant.
    • The PR from Jeremy LGTM: https://github.com/ruby/ruby/pull/15228

Updated by chucke (Tiago Cardoso) 4 days ago · Edited Actions
Copy link
 #3 [ruby-core:123925]

[Feature #21619] logger context API

  • Blog post detailing motivation here
    • logger doesn't have a context API to enrich payload for structured logging
    • other languages have some of the kind (the post details examples from java, go, python)
  • PR with proposal here
    • some public API feedback to address.
    • sonots (gem maintainer) didn't reply since I opened the proposal.
logger = Logger.new(STDOUT)
logger.with_context("user_id" => 1) do
  logger.info("foo")
    #=> I, [2025-11-28T17:57:50.947152 #3705893] [user_id=1] INFO -- : foo
    # if using a hypothetical json formatter
    #=> { "message" => "foo", "user_id" => 1, ....
  end
logger.info("foo", context: { "user_id" => 1 }) #=> same thing, but single call only

Updated by ioquatix (Samuel Williams) 3 days ago · Edited Actions
Copy link
 #4 [ruby-core:123929]

Actions
Copy link

Also available in: PDF Atom