[ruby-core:94605] [Ruby master Misc#15996] DevelopersMeeting20190829Japan

[shevegen@gmail.com]

Issue #15996 has been updated by shevegen (Robert A. Heiler).


> I know I shouldn't comment on individual issues here

While I agree, one problem is that e. g. Dan0042 did not read the prior comments here - in
particular he linked in "[Misc #15723] Reconsider numbered parameters", which already was
linked in by sikachu. IMO, these issues become quite a lot of discussion work in general
and I am not sure matz has enough time to comment on every single one when people just 
copy/paste new issues without looking whether others already linked these in. :\

 Otherwise I agree with Martin's statement of "work out an overview of what's missing and
how to address it", in regards to the functional approach. I myself use ruby almost 
exclusively from an OOP view (mostly); other ruby users seem to like a more functional
approach, such as zverok. Sometimes these styles seem to clash, in my opinion.

The dev-meeting discussions are great for others in the ruby community who are not e. g.
in japan, but this here is probably the longest individual issue tracker for any dev
meeting as of yet; I am not sure it is possible to discuss all of this in e. g. 4 hours.
But I digress too, apologies for that.

----------------------------------------
Misc #15996: DevelopersMeeting20190829Japan
https://bugs.ruby-lang.org/issues/15996#change-81082

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