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=-2.6 required=3.0 tests=AWL,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FORGED_FROMDOMAIN, FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=no 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 A55D11F4C0 for ; Thu, 17 Oct 2019 02:38:10 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 440A8120AAF; Thu, 17 Oct 2019 11:38:02 +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 F2066120AA6 for ; Thu, 17 Oct 2019 11:37:59 +0900 (JST) Received: by filter0082p3iad2.sendgrid.net with SMTP id filter0082p3iad2-13040-5DA7D406-48 2019-10-17 02:37:58.451156471 +0000 UTC m=+541407.642023949 Received: from herokuapp.com (unknown [54.158.28.124]) by ismtpd0040p1mdw1.sendgrid.net (SG) with ESMTP id 2qta40sATY290vTDv6t05Q for ; Thu, 17 Oct 2019 02:37:58.343 +0000 (UTC) Date: Thu, 17 Oct 2019 02:37:58 +0000 (UTC) From: manga.osyo@gmail.com Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 70965 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 16232 X-Redmine-Issue-Author: mame X-Redmine-Sender: osyo 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?EoIqruA4Er0CjiyK1+U6TJuuQMCAZ3OX2ybarlx6ke79uZiq7QoCMFp+1przn5?= =?us-ascii?Q?yauMQNJiZuAQUrIs8MbCJS0REeM=2FJMf1ozlmZa6?= =?us-ascii?Q?P4WF98mFNilPN6759l4pnL5hjRDDZSLTrg40S7w?= =?us-ascii?Q?2rLeqI059heGpZEcg5m+iCXfVy60iEL9KmU5Qej?= =?us-ascii?Q?i+WOAc5PZ0zPZ5UX4mCJS1cKg4d=2FlG8LnCg=3D=3D?= To: ruby-core@ruby-lang.org X-ML-Name: ruby-core X-Mail-Count: 95376 Subject: [ruby-core:95376] [Ruby master Misc#16232] DevelopersMeeting20191017Japan 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 #16232 has been updated by osyo (manga osyo). * [Feature #16142] Implement code_range in Proc and Method - Ruby master - Ruby Issue Tracking System * Propose an API to get code position of Proc and Method so that we can get body of them (especially of a Proc). * I want to discuss method names and return values ---------------------------------------- Misc #16232: DevelopersMeeting20191017Japan https://bugs.ruby-lang.org/issues/16232#change-82087 * 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: 10/17 13:00-17:00 Place and Sign-up: (See the Log) log: https://docs.google.com/document/d/1-IC98nOPY_FZnne2PXILYAaxt6PqHfhphAI908K3vD8 # 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/