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=-4.0 required=3.0 tests=AWL,BAYES_00, 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 6B6C71F731 for ; Wed, 7 Aug 2019 03:05:05 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 435D9120A86; Wed, 7 Aug 2019 12:04:57 +0900 (JST) Received: from o1678948x4.outbound-mail.sendgrid.net (o1678948x4.outbound-mail.sendgrid.net [167.89.48.4]) by neon.ruby-lang.org (Postfix) with ESMTPS id 3F633120A83 for ; Wed, 7 Aug 2019 12:04:55 +0900 (JST) Received: by filter0151p3mdw1.sendgrid.net with SMTP id filter0151p3mdw1-1887-5D4A3FD9-3A 2019-08-07 03:04:57.996407797 +0000 UTC m=+977754.238571447 Received: from herokuapp.com (unknown [54.164.239.186]) by ismtpd0066p1mdw1.sendgrid.net (SG) with ESMTP id vwYL0U1LTWiDLv1Y_r0eoQ for ; Wed, 07 Aug 2019 03:04:57.898 +0000 (UTC) Date: Wed, 07 Aug 2019 03:04:57 +0000 (UTC) From: ko1@atdot.net Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 69679 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 15996 X-Redmine-Issue-Author: mame X-Redmine-Sender: ko1 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?fVTMYOBjtdvXNcWwrscBhLsHItUXVK5L4mtnq0mdcRf12++F9KfBzM3tjkDKaH?= =?us-ascii?Q?MQ+=2FybgyXKXez76Pr51LVal0s5ydBlr=2FNdDiPLK?= =?us-ascii?Q?UMENn4KTkf0CtYQzDzSVoZ=2FHIYPZRFOgk9hQ7nC?= =?us-ascii?Q?hus6k2IS8Zx8hQdL0IQvQOHber=2FXK+LzVymAHJt?= =?us-ascii?Q?6KoFpHjfy6UjC?= To: ruby-core@ruby-lang.org X-ML-Name: ruby-core X-Mail-Count: 94170 Subject: [ruby-core:94170] [Ruby master Misc#15996] DevelopersMeeting20190820Japan 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 #15996 has been updated by ko1 (Koichi Sasada). Description updated Schedule was changed!! Before: 2019/08/20 (Thu) 13:00-17:00 (JST) After: 2019/08/29 (Thu) 13:00-17:00 (JST) Thanks, Koichi ---------------------------------------- Misc #15996: DevelopersMeeting20190820Japan https://bugs.ruby-lang.org/issues/15996#change-80425 * 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/08/29 (Thu) Time: 13:00-17:00 (JST) Place and Sign-up: https://connpass.com/event/139231/ log: https://docs.google.com/document/d/1XypDO1crRV9uNg1_ajxkljVdN8Vdyl5hnz462bDQw34/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/