From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS4713 221.184.0.0/13 X-Spam-Status: No, score=-3.4 required=3.0 tests=BAYES_00,FROM_SUSPICIOUS_NTLD, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by dcvr.yhbt.net (Postfix) with ESMTP id F0B311F454 for ; Mon, 4 Nov 2019 21:13:20 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id EC91D1209A5; Tue, 5 Nov 2019 06:13:09 +0900 (JST) Received: from xtrwkhkc.outbound-mail.sendgrid.net (xtrwkhkc.outbound-mail.sendgrid.net [167.89.16.28]) by neon.ruby-lang.org (Postfix) with ESMTPS id E16DD1209A1 for ; Tue, 5 Nov 2019 06:13:07 +0900 (JST) Received: by filter0077p3las1.sendgrid.net with SMTP id filter0077p3las1-27790-5DC09467-46 2019-11-04 21:13:11.418474133 +0000 UTC m=+8429.051328458 Received: from herokuapp.com (unknown [3.88.230.70]) by ismtpd0033p1iad2.sendgrid.net (SG) with ESMTP id sCvHQCa6TvyImorrb1MiSA for ; Mon, 04 Nov 2019 21:13:11.349 +0000 (UTC) Date: Mon, 04 Nov 2019 21:13:11 +0000 (UTC) From: jonathan@hefner.pro Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 71270 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 16262 X-Redmine-Issue-Author: mame X-Redmine-Sender: jonathanhefner X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-SG-EID: =?us-ascii?Q?y87fQmSTkDB0MB8oF=2FSr+wCExKhWErwiIVXChRtBifv=2FVVHayLzgxnLLFKT2Zn?= =?us-ascii?Q?YpazyggFkbJVQr2qNsDt0pJFah2IU6vjHZQPAbJ?= =?us-ascii?Q?hsXcaAa1dqF9Cfrm+Oh8=2FTdImyZ6V+YTrLZ014p?= =?us-ascii?Q?sIh9YyKOPularwcfnW01wEM4SEMxv4BETMtuoQB?= =?us-ascii?Q?WAEk0hwRn1UiaNiMXRluG8IulEl8I4ilXWA=3D=3D?= To: ruby-core@ruby-lang.org X-ML-Name: ruby-core X-Mail-Count: 95678 Subject: [ruby-core:95678] [Ruby master Misc#16262] DevelopersMeeting20191128Japan X-BeenThere: ruby-core@ruby-lang.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ruby developers List-Id: Ruby developers List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" Issue #16262 has been updated by jonathanhefner (Jonathan Hefner). * [Feature #15323] Enumerable#filter_map * This feature has already been merged, but there may have been some confusion regarding the implementation. * It currently selects only truthy values, but should it select all non-nil values, like `Array#compact`? (See https://bugs.ruby-lang.org/issues/15323#note-17) * If so, is the name `filter_map` still a good choice? Or should it be changed to something like `compact_map`? ---------------------------------------- Misc #16262: DevelopersMeeting20191128Japan https://bugs.ruby-lang.org/issues/16262#change-82465 * Author: mame (Yusuke Endoh) * Status: Open * Priority: Normal * Assignee: ---------------------------------------- Please comment on your favorite ticket numbers you want to ask to discuss with your *SHORT* comment or summary. (your summary/comment will help us because we don't need to read all of the ticket comments) *DO NOT* discuss then on this ticket, please. ---- Date: 2019/11/28 13:00-17:00 Place, Sign-up, and Log: https://docs.google.com/document/d/1AZ74HXEedKksJwhEUPIlnRxAUgchndZPZYAKjGPMsFI/edit# # NOTES - 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 log about the discussion to a 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 are scheduled according to when/where we can reserve Matz's time. # Agenda ## Next dev-meeting ## About 2.7 timeframe ## Check security tickets ## Discussion ---- Please comment on your favorite ticket we need to discuss with *the following format*. ``` * [Ticket ref] Ticket title (your name) * your comment why you want to put this ticket here if you want to add. ``` Your comment is very important if you are no attendee because we can not ask why you want to discuss it. 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. ``` We don't guarantee to put tickets in the agenda if the comment violates the format (because it is hard to copy&paste). **A short summary of a ticket is strongly recommended. We cannot read all discussion of the ticket in a limited time.** A proposal is often changed during the discussion, so it is very helpful to summarize the latest/current proposal, post it as a comment in the ticket, and write a link to the comment. -- https://bugs.ruby-lang.org/