Issue #19357 has been updated by jeremyevans0 (Jeremy Evans). * [Bug #11230] Should rb_struct_s_members() be public API? (jeremyevans0) * This C function was previous decided to be removed from the public API after Ruby 3.2. * The function is still exported as it is needed by `marshal.c`. * One stated reason for removal is that `rb_struct_s_members` returns a hidden Array. `rb_struct_members` appears to return the same Array. * Should we consider removing `rb_struct_members` from the public API as well? * [Feature #19347] Add Dir.fchdir (jeremyevans0) * This was discussed last developer meeting, with 4 possible approaches. * I've given comments for each approach. Can we decide on an approach? * [Feature #19388] Deprecate SecurityError (jeremyevans0) * SecurityError was used historically for `$SAFE` violations. It hasn't been used since Ruby 3.0. * I think we should deprecate SecurityError in Ruby 3.3 and remove it Ruby 3.4. Is this OK? ---------------------------------------- Misc #19357: DevMeeting-2023-02-09 https://bugs.ruby-lang.org/issues/19357#change-101558 * Author: mame (Yusuke Endoh) * Status: Open * Priority: Normal ---------------------------------------- # The next dev meeting **Date: 2023/02/09 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 2023/02/06. 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](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86). 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. -- https://bugs.ruby-lang.org/