From: "hsbt (Hiroshi SHIBATA) via ruby-core" Date: 2024-09-26T06:11:25+00:00 Subject: [ruby-core:119295] [Ruby master Misc#20717] DevMeeting-2024-10-03 Issue #20717 has been updated by hsbt (Hiroshi SHIBATA). * [Feature #10459] [PATCH] rfc3339 method for Time * https://github.com/rails/rails/blob/b88d9af34fbc1c84ce2769ba02584eab2c28ac6e/activesupport/lib/active_support/time_with_zone.rb#L152 * It seems reasonable. * We introduce that with C ext same as `xmlschema`? * [Feature #17295] Feature: Create a directory and file with Pathname#touch * I found same use case for that today. How about this? * https://github.com/BerkeleyLibrary/util/blob/main/spec/berkeley_library/util/files_spec.rb#L16 * https://github.com/ruby/ruby/pull/3706 * [Feature #17297] Feature: Introduce Pathname.mktmpdir * How about this? * https://github.com/ruby/ruby/pull/3709 * [Feature #17294] Feature: Allow method chaining with Pathname#mkpath Pathname#rmtree * How about this? * https://github.com/ruby/ruby/pull/3705 * [Feature #17296] Feature: Pathname#chmod use FileUtils.chmod instead of File * It's reasonable and useful. * Does anyone have concern? * https://github.com/ruby/ruby/pull/3708 * [GH-2974] Pathname#mountpoint? to support bind mount * https://github.com/ruby/ruby/pull/2974 ---------------------------------------- Misc #20717: DevMeeting-2024-10-03 https://bugs.ruby-lang.org/issues/20717#change-109907 * Author: mame (Yusuke Endoh) * Status: Open ---------------------------------------- # The next dev meeting **Date: 2024/10/03 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 2024/09/30. 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/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/