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.
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 2026/08/03. We hold a preparatory meeting to create an agenda a few days before the dev-meeting.
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.
[Feature #22213] Allow no-argument and chained calls of Proc#refined (shugo)
A no-argument call returns the receiver itself, and a chained call returns a Proc with additional refinements: prc.refined(*ms).refined(*ns) is equivalent to prc.refined(*ms, *ns)
The copy of the block is deferred until the first call, so a Proc that is never called is never copied, and a chained call is memoized like a single call with all the modules
I'd like to deprecate and eventually remove ruby2_keywords; feedback on the ticket is positive, and the proposed schedule is in the description
Should Hash.ruby2_keywords_hash? and Hash.ruby2_keywords_hash be deprecated one phase later than the marking methods (they are needed as long as flagged hashes exist), or on the same schedule?
Proposes a portable API returning a Ruby::SourceRange for an exception's backtrace_locations or for caller_locations.
This gives tools stable start/end line/column coordinates without version-specific node_id values (examples of node_id instability).
Examples which could use this API instead of currently the CRuby-specific RubyVM::AST.node_id_for_backtrace_location, and therefore work reliably on TruffleRuby/JRuby: Prism.find(Thread::Backtrace::Location), Rails exception printing, error_highlight, power_assert.
It does not require the Prism gem or create Prism::Node objects, separating source-code location from parsing that code into an AST.
The implementation reparses on demand to avoid persistent memory overhead, uses source-hash validation based on @mame (Yusuke Endoh) 's work, and supports RubyVM.keep_script_lines = true to avoid re-reading files from disk.
Extensive specs ensure Prism and parse.y return identical user-facing coordinates, including for blocks.
I am looking for matz's approval for the new method.
[Feature #22068] Adding post-quantum cryptography (PQC) support across Ruby standard libraries (jaruga)
I explain the feature with my motivations, and answer questions from other developers.
I want to share how to proceed for possible target libraries to modify: ruby/rubygems, bundler, ruby/net-http, ruby/open-uri, ruby/spec, ruby/drb, ruby/rbs.