[ruby-core:92365] [Ruby trunk Misc#15782] DevelopersMeeting201905XXJapan

[ruby-core:92365] [Ruby trunk Misc#15782] DevelopersMeeting201905XXJapan

[takashikkbn]

Issue #15782 has been reported by k0kubun (Takashi Kokubun).

----------------------------------------
Misc #15782: DevelopersMeeting201905XXJapan
https://bugs.ruby-lang.org/issues/15782

* Author: k0kubun (Takashi Kokubun)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Please comment 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 ticket comments)

*DO NOT* discuss then on this ticket, please.

----

Date: 2019/05/XX (XXX)
Time: 13:00-17:00 (JST)
Place: TODO
Sign-up: TODO
log: TODO
logedit: TODO

# 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 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 is scheduled according to when/where we can reserve Matz's time.

# Agenda

## Next dev-meeting

## About 2.7 timeframe

## Check security tickets

## Carry-over from previous meeting(s)

## From Attendees

## From non-attendees

----

Please comment 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 about 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 about this feature.
```

We don't guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).



-- 
https://bugs.ruby-lang.org/

[ruby-core:92366] [Ruby trunk Misc#15782] DevelopersMeeting201905XXJapan

[takashikkbn]

Issue #15782 has been updated by k0kubun (Takashi Kokubun).


* [Misc #15743] git.ruby-lang.org: See [5da52d1210](https://github.com/ruby/ruby/commit/5da52d1210625fb00acd573b3f32281b4bde1730). I committed tentative `RUBY_REVISION`/`RUBY_DESCRIPTION` behaviors for preview1 as follows. Is it okay?
  * `RUBY_REVISION #=> "5da52d1210"` (instead of Integer like `67701`. 10 chars like email notification and rubyci.)
  * `RUBY_DESCRIPTION #=> "ruby 2.7.0dev (2019-04-22 trunk 5da52d1210) [x86_64-linux]"` (10 chars, same as the above)

----------------------------------------
Misc #15782: DevelopersMeeting201905XXJapan
https://bugs.ruby-lang.org/issues/15782#change-77713

* Author: k0kubun (Takashi Kokubun)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Please comment 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 ticket comments)

*DO NOT* discuss then on this ticket, please.

----

Date: 2019/05/XX (XXX)
Time: 13:00-17:00 (JST)
Place: TODO
Sign-up: TODO
log: TODO
logedit: TODO

# 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 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 is scheduled according to when/where we can reserve Matz's time.

# Agenda

## Next dev-meeting

## About 2.7 timeframe

## Check security tickets

## Carry-over from previous meeting(s)

## From Attendees

## From non-attendees

----

Please comment 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 about 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 about this feature.
```

We don't guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).



-- 
https://bugs.ruby-lang.org/

[ruby-core:92373] [Ruby trunk Misc#15782] DevelopersMeeting20190522Japan

[tenderlove]

Issue #15782 has been updated by tenderlovemaking (Aaron Patterson).


* [Feature #15281] Speed up Set#intersect with size check.
  * Everyone likes faster code. But the question is: are Sets ordered? I think Matz must decide.

----------------------------------------
Misc #15782: DevelopersMeeting20190522Japan
https://bugs.ruby-lang.org/issues/15782#change-77721

* Author: k0kubun (Takashi Kokubun)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Please comment 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 ticket comments)

*DO NOT* discuss then on this ticket, please.

----

Date: 2019/05/22 (Wed)
Time: 13:00-17:00 (JST)
Place: TODO
Sign-up: TODO
log: TODO
logedit: TODO

# 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 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 is scheduled according to when/where we can reserve Matz's time.

# Agenda

## Next dev-meeting

## About 2.7 timeframe

## Check security tickets

## Carry-over from previous meeting(s)

## From Attendees

## From non-attendees

----

Please comment 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 about 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 about this feature.
```

We don't guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).



-- 
https://bugs.ruby-lang.org/

[ruby-core:92385] [Ruby trunk Misc#15782] DevelopersMeeting20190522Japan

[grzegorz.jakubiak]

Issue #15782 has been updated by greggzst (Grzegorz Jakubiak).


* [Feature #15323] [PATCH] Proposal: Add Enumerable#filter_map
 * It's expressive as Ruby lang itself
 * Should also consider adding #filter_map!
 * It enables developers to get rid of such code(below) and has been already accepted by Matz:
 
 ~~~ ruby
 (1..10).map{ |elem| elem * 2 if elem % 2 == 0 }.compact
 ~~~



----------------------------------------
Misc #15782: DevelopersMeeting20190522Japan
https://bugs.ruby-lang.org/issues/15782#change-77737

* Author: k0kubun (Takashi Kokubun)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Please comment 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 ticket comments)

*DO NOT* discuss then on this ticket, please.

----

Date: 2019/05/22 (Wed)
Time: 13:00-17:00 (JST)
Place: TODO
Sign-up: TODO
log: TODO
logedit: TODO

# 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 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 is scheduled according to when/where we can reserve Matz's time.

# Agenda

## Next dev-meeting

## About 2.7 timeframe

## Check security tickets

## Carry-over from previous meeting(s)

## From Attendees

## From non-attendees

----

Please comment 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 about 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 about this feature.
```

We don't guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).



-- 
https://bugs.ruby-lang.org/

[ruby-core:92415] [Ruby trunk Misc#15782] DevelopersMeeting20190522Japan

[koic.ito]

Issue #15782 has been updated by koic (Koichi ITO).


* [Bug #15745] There is no symmetry in the beginless range and the endless range using `Range#inspect` (koic)
  * I think that the symmetry of beginless range and endless range becomes more clear by unifying whether it displays `nil` or not.

----------------------------------------
Misc #15782: DevelopersMeeting20190522Japan
https://bugs.ruby-lang.org/issues/15782#change-77774

* Author: k0kubun (Takashi Kokubun)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Please comment 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 ticket comments)

*DO NOT* discuss then on this ticket, please.

----

Date: 2019/05/22 (Wed)
Time: 13:00-17:00 (JST)
Place: pixiv (Tokyo, Japan)
Sign-up: https://ruby.connpass.com/event/129507/
log: TODO
logedit: TODO

# 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 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 is scheduled according to when/where we can reserve Matz's time.

# Agenda

## Next dev-meeting

## About 2.7 timeframe

## Check security tickets

## Carry-over from previous meeting(s)

## From Attendees

## From non-attendees

----

Please comment 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 about 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 about this feature.
```

We don't guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).



-- 
https://bugs.ruby-lang.org/

[ruby-core:92430] [Ruby trunk Misc#15782] DevelopersMeeting20190522Japan

[merch-redmine]

Issue #15782 has been updated by jeremyevans0 (Jeremy Evans).


* [Feature #14915] Deprecate String#crypt
  * I think we should add a real deprecation warning in 2.7 so we can remove it in a later version.

----------------------------------------
Misc #15782: DevelopersMeeting20190522Japan
https://bugs.ruby-lang.org/issues/15782#change-77784

* Author: k0kubun (Takashi Kokubun)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Please comment 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 ticket comments)

*DO NOT* discuss then on this ticket, please.

----

Date: 2019/05/22 (Wed)
Time: 13:00-17:00 (JST)
Place: pixiv (Tokyo, Japan)
Sign-up: https://ruby.connpass.com/event/129507/
log: TODO
logedit: TODO

# 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 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 is scheduled according to when/where we can reserve Matz's time.

# Agenda

## Next dev-meeting

## About 2.7 timeframe

## Check security tickets

## Carry-over from previous meeting(s)

## From Attendees

## From non-attendees

----

Please comment 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 about 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 about this feature.
```

We don't guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).



-- 
https://bugs.ruby-lang.org/

[ruby-core:92437] [Ruby trunk Misc#15782] DevelopersMeeting20190522Japan

[alanwucanada]

Issue #15782 has been updated by alanwu (Alan Wu).


* [Feature #15765] [PATCH] Module#name without global constant search
  * This fixes the performance problems for `#name` on anonymous module / classes, but also comes with some small behavioral changes. Are they okay?

----------------------------------------
Misc #15782: DevelopersMeeting20190522Japan
https://bugs.ruby-lang.org/issues/15782#change-77791

* Author: k0kubun (Takashi Kokubun)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Please comment 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 ticket comments)

*DO NOT* discuss then on this ticket, please.

----

Date: 2019/05/22 (Wed)
Time: 13:00-17:00 (JST)
Place: pixiv (Tokyo, Japan)
Sign-up: https://ruby.connpass.com/event/129507/
log: TODO
logedit: TODO

# 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 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 is scheduled according to when/where we can reserve Matz's time.

# Agenda

## Next dev-meeting

## About 2.7 timeframe

## Check security tickets

## Carry-over from previous meeting(s)

## From Attendees

## From non-attendees

----

Please comment 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 about 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 about this feature.
```

We don't guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).



-- 
https://bugs.ruby-lang.org/

[ruby-core:92439] [Ruby trunk Misc#15782] DevelopersMeeting20190522Japan

[manga.osyo]

Issue #15782 has been updated by osyo (manga osyo).


* [Feature #15772] Proposal: Add Time#ceil
  * I want to hear the opinions of developers.
* [Feature #13645] Syntactic sugar for indexing when using the safe navigation operator
  * I presented a use case.


----------------------------------------
Misc #15782: DevelopersMeeting20190522Japan
https://bugs.ruby-lang.org/issues/15782#change-77793

* Author: k0kubun (Takashi Kokubun)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Please comment 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 ticket comments)

*DO NOT* discuss then on this ticket, please.

----

Date: 2019/05/22 (Wed)
Time: 13:00-17:00 (JST)
Place: pixiv (Tokyo, Japan)
Sign-up: https://ruby.connpass.com/event/129507/
log: TODO
logedit: TODO

# 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 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 is scheduled according to when/where we can reserve Matz's time.

# Agenda

## Next dev-meeting

## About 2.7 timeframe

## Check security tickets

## Carry-over from previous meeting(s)

## From Attendees

## From non-attendees

----

Please comment 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 about 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 about this feature.
```

We don't guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).



-- 
https://bugs.ruby-lang.org/

[ruby-core:92496] [Ruby trunk Misc#15782] DevelopersMeeting20190522Japan

[manga.osyo]

Issue #15782 has been updated by osyo (manga osyo).


* [Feature #15813] Proposal: Add exception support in `Range#first`
  * I want to hear the opinions of developers

----------------------------------------
Misc #15782: DevelopersMeeting20190522Japan
https://bugs.ruby-lang.org/issues/15782#change-77856

* Author: k0kubun (Takashi Kokubun)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Please comment 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 ticket comments)

*DO NOT* discuss then on this ticket, please.

----

Date: 2019/05/22 (Wed)
Time: 13:00-17:00 (JST)
Place: pixiv (Tokyo, Japan)
Sign-up: https://ruby.connpass.com/event/129507/
log: TODO
logedit: TODO

# 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 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 is scheduled according to when/where we can reserve Matz's time.

# Agenda

## Next dev-meeting

## About 2.7 timeframe

## Check security tickets

## Carry-over from previous meeting(s)

## From Attendees

## From non-attendees

----

Please comment 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 about 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 about this feature.
```

We don't guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).



-- 
https://bugs.ruby-lang.org/

[ruby-core:92512] [Ruby trunk Misc#15782] DevelopersMeeting20190522Japan

[lourens]

Issue #15782 has been updated by methodmissing (Lourens Naudé).


* [Misc #15800] [PATCH] Reduce `ONIG_NREGION` size from 10 to 4
 * Power of 2 and testing revealed most pattern matches are less than or equal to 4 results
 * `MatchData` instances over allocate memory for the most common cases
* [Misc #15802] [PATCH] Reduce the minimum string buffer size from 127 to 63 bytes
 * The most common case for string buffers in Rails processes are less than 63 bytes

----------------------------------------
Misc #15782: DevelopersMeeting20190522Japan
https://bugs.ruby-lang.org/issues/15782#change-77875

* Author: k0kubun (Takashi Kokubun)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Please comment 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 ticket comments)

*DO NOT* discuss then on this ticket, please.

----

Date: 2019/05/22 (Wed)
Time: 13:00-17:00 (JST)
Place: pixiv (Tokyo, Japan)
Sign-up: https://ruby.connpass.com/event/129507/
log: TODO
logedit: TODO

# 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 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 is scheduled according to when/where we can reserve Matz's time.

# Agenda

## Next dev-meeting

## About 2.7 timeframe

## Check security tickets

## Carry-over from previous meeting(s)

## From Attendees

## From non-attendees

----

Please comment 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 about 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 about this feature.
```

We don't guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

[ruby-core:92521] [Ruby trunk Misc#15782] DevelopersMeeting20190522Japan

[samuel]

Issue #15782 has been updated by ioquatix (Samuel Williams).


* [Feature #14736] Thread selector for flexible cooperative fiber based concurrency
 * Is it something we want to move forward with?
 * Extend hooks for `wait_one_pid` and `Kernel::sleep`. Are there other areas to hook into?
 * Add some default implementation using `IO.select`, e.g. `IO::Selector`, similar to test spec. Should `IO.select` accept raw file descriptors?
 * Should IO be non-block by default? Should we adjust behaviour dynamically based on context? How to handle `File.read` which doesn't give opportunity to assign to nonblock.



----------------------------------------
Misc #15782: DevelopersMeeting20190522Japan
https://bugs.ruby-lang.org/issues/15782#change-77884

* Author: k0kubun (Takashi Kokubun)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Please comment 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 ticket comments)

*DO NOT* discuss then on this ticket, please.

----

Date: 2019/05/22 (Wed)
Time: 13:00-17:00 (JST)
Place: pixiv (Tokyo, Japan)
Sign-up: https://ruby.connpass.com/event/129507/
log: TODO
logedit: TODO

# 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 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 is scheduled according to when/where we can reserve Matz's time.

# Agenda

## Next dev-meeting

## About 2.7 timeframe

## Check security tickets

## Carry-over from previous meeting(s)

## From Attendees

## From non-attendees

----

Please comment 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 about 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 about this feature.
```

We don't guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).



-- 
https://bugs.ruby-lang.org/

[ruby-core:92570] [Ruby trunk Misc#15782] DevelopersMeeting20190522Japan

[grzegorz.jakubiak]

Issue #15782 has been updated by greggzst (Grzegorz Jakubiak).


greggzst (Grzegorz Jakubiak) wrote:
> * [Feature #15323] [PATCH] Proposal: Add Enumerable#filter_map
>  * It's expressive as Ruby lang itself
>  * Make `filter_map(&:predicate) { |elem| elem * 2 }` syntax possible
>  * Should also consider adding #filter_map!
>  * It enables developers to get rid of such code(below) and has been already accepted by Matz:
>  
>  ~~~ ruby
>  (1..10).map{ |elem| elem * 2 if elem % 2 == 0 }.compact
>  ~~~

Updated


----------------------------------------
Misc #15782: DevelopersMeeting20190522Japan
https://bugs.ruby-lang.org/issues/15782#change-77930

* Author: k0kubun (Takashi Kokubun)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Please comment 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 ticket comments)

*DO NOT* discuss then on this ticket, please.

----

Date: 2019/05/22 (Wed)
Time: 13:00-17:00 (JST)
Place: pixiv (Tokyo, Japan)
Sign-up: https://ruby.connpass.com/event/129507/
log: TODO
logedit: TODO

# 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 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 is scheduled according to when/where we can reserve Matz's time.

# Agenda

## Next dev-meeting

## About 2.7 timeframe

## Check security tickets

## Carry-over from previous meeting(s)

## From Attendees

## From non-attendees

----

Please comment 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 about 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 about this feature.
```

We don't guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).



-- 
https://bugs.ruby-lang.org/

[ruby-core:92624] [Ruby trunk Misc#15782] DevelopersMeeting20190522Japan

[nobu]

Issue #15782 has been updated by nobu (Nobuyoshi Nakada).


k0kubun (Takashi Kokubun) wrote:
>   * Can we decide the date to rename the branch "trunk" to "master"? Does anyone have any objection for it? What do we need to prepare for it?
>      * Motivation: I've often typo-ed trunk to master even in the git-svn age, because "master" is the standard name for the upstream branch in Git.
>      * As @yugui suggested, should we just use `git symbolic-ref refs/remotes/origin/master refs/remotes/origin/trunk`?

Just to get rid of a typo, `symbolic-ref` seems working enough.

----------------------------------------
Misc #15782: DevelopersMeeting20190522Japan
https://bugs.ruby-lang.org/issues/15782#change-77985

* Author: k0kubun (Takashi Kokubun)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Please comment 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 ticket comments)

*DO NOT* discuss then on this ticket, please.

----

Date: 2019/05/22 (Wed)
Time: 13:00-17:00 (JST)
Place: pixiv (Tokyo, Japan)
Sign-up: https://ruby.connpass.com/event/129507/
log: TODO
logedit: TODO

# 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 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 is scheduled according to when/where we can reserve Matz's time.

# Agenda

## Next dev-meeting

## About 2.7 timeframe

## Check security tickets

## Carry-over from previous meeting(s)

## From Attendees

## From non-attendees

----

Please comment 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 about 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 about this feature.
```

We don't guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).



-- 
https://bugs.ruby-lang.org/

[ruby-core:92626] [Ruby trunk Misc#15782] DevelopersMeeting20190522Japan

[takashikkbn]

Issue #15782 has been updated by k0kubun (Takashi Kokubun).


(from my previous comment, I changed a plan for the following one and filed another ticket)

* [Misc #15843] Make "trunk" a symbolic-ref of "master" on git.ruby-lang.org
  * Please see "Expected outcome" part. Do you have any objection for it?

----------------------------------------
Misc #15782: DevelopersMeeting20190522Japan
https://bugs.ruby-lang.org/issues/15782#change-77988

* Author: k0kubun (Takashi Kokubun)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Please comment 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 ticket comments)

*DO NOT* discuss then on this ticket, please.

----

Date: 2019/05/22 (Wed)
Time: 13:00-17:00 (JST)
Place: pixiv (Tokyo, Japan)
Sign-up: https://ruby.connpass.com/event/129507/
log: TODO
logedit: TODO

# 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 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 is scheduled according to when/where we can reserve Matz's time.

# Agenda

## Next dev-meeting

## About 2.7 timeframe

## Check security tickets

## Carry-over from previous meeting(s)

## From Attendees

## From non-attendees

----

Please comment 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 about 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 about this feature.
```

We don't guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).



-- 
https://bugs.ruby-lang.org/

[ruby-core:92655] [Ruby trunk Misc#15782] DevelopersMeeting20190522Japan

[eregontp]

Issue #15782 has been updated by Eregon (Benoit Daloze).


* [Feature #15778] Expose an API to pry-open the stack frames in Ruby
  * Several points were made in favor of Ruby API. Can we make it so this API is clearly marked as "should only be used for debugging"? Are there other concerns?

----------------------------------------
Misc #15782: DevelopersMeeting20190522Japan
https://bugs.ruby-lang.org/issues/15782#change-78018

* Author: k0kubun (Takashi Kokubun)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Please comment 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 ticket comments)

*DO NOT* discuss then on this ticket, please.

----

Date: 2019/05/22 (Wed)
Time: 13:00-17:00 (JST)
Place: pixiv (Tokyo, Japan)
Sign-up: https://ruby.connpass.com/event/129507/
log: TODO
logedit: TODO

# 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 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 is scheduled according to when/where we can reserve Matz's time.

# Agenda

## Next dev-meeting

## About 2.7 timeframe

## Check security tickets

## Carry-over from previous meeting(s)

## From Attendees

## From non-attendees

----

Please comment 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 about 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 about this feature.
```

We don't guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).



-- 
https://bugs.ruby-lang.org/

[ruby-core:92658] [Ruby trunk Misc#15782] DevelopersMeeting20190522Japan

[hsbt]

Issue #15782 has been updated by hsbt (Hiroshi SHIBATA).


* [Bug #7300] Hash#[] の挙動が 1.9.3 と異なっている
  * Can we merge this?

----------------------------------------
Misc #15782: DevelopersMeeting20190522Japan
https://bugs.ruby-lang.org/issues/15782#change-78021

* Author: k0kubun (Takashi Kokubun)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Please comment 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 ticket comments)

*DO NOT* discuss then on this ticket, please.

----

Date: 2019/05/22 (Wed)
Time: 13:00-17:00 (JST)
Place: pixiv (Tokyo, Japan)
Sign-up: https://ruby.connpass.com/event/129507/
log: TODO
logedit: TODO

# 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 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 is scheduled according to when/where we can reserve Matz's time.

# Agenda

## Next dev-meeting

## About 2.7 timeframe

## Check security tickets

## Carry-over from previous meeting(s)

## From Attendees

## From non-attendees

----

Please comment 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 about 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 about this feature.
```

We don't guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).



-- 
https://bugs.ruby-lang.org/

[ruby-core:92671] [Ruby trunk Misc#15782] DevelopersMeeting20190522Japan

[eregontp]

Issue #15782 has been updated by Eregon (Benoit Daloze).


* [Feature #14844] Future of RubyVM::AST?
  * What can we do about this? The current situation is confusing for everyone, the API sounds "blessed" by being in core but it's actually experimental and unstable.
    Can we document it as clearly as possible when this API should be used?
    Could we improve the API so it's less fragile to parser changes and could be reasonably implemented on other Ruby implementations?

----------------------------------------
Misc #15782: DevelopersMeeting20190522Japan
https://bugs.ruby-lang.org/issues/15782#change-78034

* Author: k0kubun (Takashi Kokubun)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Please comment 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 ticket comments)

*DO NOT* discuss then on this ticket, please.

----

Date: 2019/05/22 (Wed)
Time: 13:00-17:00 (JST)
Place: pixiv (Tokyo, Japan)
Sign-up: https://ruby.connpass.com/event/129507/
log: TODO
logedit: TODO

# 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 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 is scheduled according to when/where we can reserve Matz's time.

# Agenda

## Next dev-meeting

## About 2.7 timeframe

## Check security tickets

## Carry-over from previous meeting(s)

## From Attendees

## From non-attendees

----

Please comment 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 about 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 about this feature.
```

We don't guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).



-- 
https://bugs.ruby-lang.org/

[ruby-core:92724] [Ruby trunk Misc#15782] DevelopersMeeting20190522Japan

[bogdanvlviv]

Issue #15782 has been updated by bogdanvlviv (Bogdan Denkovych).


* [Feature #15863] Add `Hash#slice!` and `ENV.slice!`(bogdanvlviv)
  * I would like to discuss these methods(name, behavior, implementation), and whether we want to add them to Ruby.
* [Feature #15831] Add `Array#extract`, `Hash#extract`, and `ENV.extract` (bogdanvlviv)
  * I would like to discuss these methods(name, behavior, implementation), and whether we want to add them to Ruby.

----------------------------------------
Misc #15782: DevelopersMeeting20190522Japan
https://bugs.ruby-lang.org/issues/15782#change-78083

* Author: k0kubun (Takashi Kokubun)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Please comment 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 ticket comments)

*DO NOT* discuss then on this ticket, please.

----

Date: 2019/05/22 (Wed)
Time: 13:00-17:00 (JST)
Place: pixiv (Tokyo, Japan)
Sign-up: https://ruby.connpass.com/event/129507/
log: TODO
logedit: TODO

# 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 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 is scheduled according to when/where we can reserve Matz's time.

# Agenda

## Next dev-meeting

## About 2.7 timeframe

## Check security tickets

## Carry-over from previous meeting(s)

## From Attendees

## From non-attendees

----

Please comment 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 about 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 about this feature.
```

We don't guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).



-- 
https://bugs.ruby-lang.org/

[ruby-core:92726] [Ruby trunk Misc#15782] DevelopersMeeting20190522Japan

[shyouhei]

Issue #15782 has been updated by shyouhei (Shyouhei Urabe).


* [Feature #14915] Deprecate String#crypt
    - Is anybody against adding warning?


----------------------------------------
Misc #15782: DevelopersMeeting20190522Japan
https://bugs.ruby-lang.org/issues/15782#change-78085

* Author: k0kubun (Takashi Kokubun)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Please comment 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 ticket comments)

*DO NOT* discuss then on this ticket, please.

----

Date: 2019/05/22 (Wed)
Time: 13:00-17:00 (JST)
Place: pixiv (Tokyo, Japan)
Sign-up: https://ruby.connpass.com/event/129507/
log: TODO
logedit: TODO

# 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 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 is scheduled according to when/where we can reserve Matz's time.

# Agenda

## Next dev-meeting

## About 2.7 timeframe

## Check security tickets

## Carry-over from previous meeting(s)

## From Attendees

## From non-attendees

----

Please comment 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 about 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 about this feature.
```

We don't guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).



-- 
https://bugs.ruby-lang.org/

[ruby-core:92734] [Ruby trunk Misc#15782] DevelopersMeeting20190522Japan

[manga.osyo]

Issue #15782 has been updated by osyo (manga osyo).


* [Feature #15864] Proposal: Add methods to determine if it is an infinite range
  * I want to hear the opinions of developers.


----------------------------------------
Misc #15782: DevelopersMeeting20190522Japan
https://bugs.ruby-lang.org/issues/15782#change-78094

* Author: k0kubun (Takashi Kokubun)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Please comment 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 ticket comments)

*DO NOT* discuss then on this ticket, please.

----

Date: 2019/05/22 (Wed)
Time: 13:00-17:00 (JST)
Place: pixiv (Tokyo, Japan)
Sign-up: https://ruby.connpass.com/event/129507/
log: TODO
logedit: TODO

# 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 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 is scheduled according to when/where we can reserve Matz's time.

# Agenda

## Next dev-meeting

## About 2.7 timeframe

## Check security tickets

## Carry-over from previous meeting(s)

## From Attendees

## From non-attendees

----

Please comment 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 about 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 about this feature.
```

We don't guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).



-- 
https://bugs.ruby-lang.org/

[ruby-core:92735] [Ruby trunk Misc#15782] DevelopersMeeting20190522Japan

[mame]

Issue #15782 has been updated by mame (Yusuke Endoh).


* [Feature #15865] `<expr> in <pattern>` expression
  * One-line pattern matching.  ktsj, ko1, nobu, and me like it.  WDYT?

----------------------------------------
Misc #15782: DevelopersMeeting20190522Japan
https://bugs.ruby-lang.org/issues/15782#change-78095

* Author: k0kubun (Takashi Kokubun)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Please comment 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 ticket comments)

*DO NOT* discuss then on this ticket, please.

----

Date: 2019/05/22 (Wed)
Time: 13:00-17:00 (JST)
Place: pixiv (Tokyo, Japan)
Sign-up: https://ruby.connpass.com/event/129507/
log: TODO
logedit: TODO

# 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 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 is scheduled according to when/where we can reserve Matz's time.

# Agenda

## Next dev-meeting

## About 2.7 timeframe

## Check security tickets

## Carry-over from previous meeting(s)

## From Attendees

## From non-attendees

----

Please comment 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 about 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 about this feature.
```

We don't guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).



-- 
https://bugs.ruby-lang.org/

[ruby-core:92753] [Ruby trunk Misc#15782] DevelopersMeeting20190522Japan

[muraken]

Issue #15782 has been updated by mrkn (Kenta Murata).


Today's venue has been changed to Speee Inc. at Roppongi.
Do not go pixiv.

----------------------------------------
Misc #15782: DevelopersMeeting20190522Japan
https://bugs.ruby-lang.org/issues/15782#change-78115

* Author: k0kubun (Takashi Kokubun)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Please comment 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 ticket comments)

*DO NOT* discuss then on this ticket, please.

----

Date: 2019/05/22 (Wed)
Time: 13:00-17:00 (JST)
Place: pixiv (Tokyo, Japan)
Sign-up: https://ruby.connpass.com/event/129507/
log: TODO
logedit: TODO

# 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 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 is scheduled according to when/where we can reserve Matz's time.

# Agenda

## Next dev-meeting

## About 2.7 timeframe

## Check security tickets

## Carry-over from previous meeting(s)

## From Attendees

## From non-attendees

----

Please comment 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 about 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 about this feature.
```

We don't guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).



-- 
https://bugs.ruby-lang.org/