Project

General

Profile

Misc #15996

DevelopersMeeting20190820Japan

Added by mame (Yusuke Endoh) 10 days ago. Updated 10 days ago.

Status:
Open
Priority:
Normal
Assignee:
-
[ruby-core:93683]

Description

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/20 (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.


Related issues

Related to Ruby master - Misc #14770: [META] DevelopersMeetingOpenActions

History

Updated by mame (Yusuke Endoh) 10 days ago

I added the following note.

**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.

Please consider adding a short summary comment to the ticket you want us to discuss.

Updated by mame (Yusuke Endoh) 10 days ago

Carry over.

  • [Feature #11460] Unhelpful error message when naming a module with the same name as an existing class (nobu)
  • [Misc #15805] Let memory sizes of the various IMEMO object types be reflected correctly (methodmissing)
  • [Misc #15806] Explicitly initialise encodings on init to remove branches on encoding lookup (methodmissing)
    • Currently rb_enc_from_index and related methods explicitly check for encoding table init on each call - I think this should be initialised at boot time instead as even the simple case of loading the interpreter requires the encoding table to be loaded anyways (symbol.c)
    • PR: https://github.com/ruby/ruby/pull/2128
#3

Updated by mame (Yusuke Endoh) 10 days ago

  • Related to Misc #14770: [META] DevelopersMeeting added

Also available in: Atom PDF