Issue #15129 has been updated by zverok (Victor Shepelev).


I am not sure if it is appropriate, but I'd also be very glad to hear about some "stale" discussions. They were typically reacted on developer meetings as "in general, good proposal (but not sure when it would be implemented/not sure about the name)", or something like that, and I'd like to know maybe we should do something to push them further? List of tickets:
* [Feature #14799] Startless range: usefulness discussed, patch provided by @mame, waits for Matz's decision (?)
* [Feature #14784] `Comparable#clamp` accepting range: comment for @akr about "needlessly big" proposal, I answered it, is it makes the proposal more likely to be accepted?
* [Feature #6284] Composition for procs: the last thing Matz has said is the operators are chosen (`<<` and `>>`), and "We need more discussion if we would add combination methods to the `Symbol` class." Is there a chance proc composition would make it way in the 2.6?
* [Feature #13581] Syntax sugar for method reference. The last thing Matz have said is: "`.:` looks best to me (followed by `:::`). Let me consider it for a while." Are there any choices made? Could we expect this for 2.6?
* [Feature #14781] `Enumerator#generate` It seems like people feel cautious enthusiasm about it, but not sure about the name. What should be done here? Voting on the name? Providing the patch with _some_ name, and then voting for the name?

----------------------------------------
Misc #15129: DevelopersMeeting201801010Japan
https://bugs.ruby-lang.org/issues/15129#change-74340

* Author: mame (Yusuke Endoh)
* 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: 2018/10/10 (Wed)
Time: 14:00-18:00 (JST)
Place: pixiv Inc. (Tokyo, Japan)
Sign-up: https://ruby.connpass.com/event/101832/
log: https://docs.google.com/document/d/18f8peqDQ_nkLapK3BWFaAkEHaAIvD6hP0IhdkgDgTJI/pub
logedit: https://docs.google.com/document/d/18f8peqDQ_nkLapK3BWFaAkEHaAIvD6hP0IhdkgDgTJI/edit
Past meetings: https://bugs.ruby-lang.org/projects/ruby/wiki#Developer-Meetings

# 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.6 timeframe

## Carry-over from previous meeting(s)

## From Attendees

(will be edited later)
(if you have a write access permission, please list directly)

## From non-attendees

(will be edited later)
(if you have a write access, please list directly)

# Comment format

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

I 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>